Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an old 32bit delphi application (with no source code), that is used as a windows service. It runs fine on windows 2003 32bit.

I do not know if it has been created as a service originally, or converted to one later on. It is supposed to get installed to the server using a /install flag on the command line.

When attempting to install it on a Windows 2008 R2 virtual machine, I am getting an APPCRASH event in the event log.

The service is supposed to read a blob from a remote SQL Server instance and write it out to the local HD. It also reads some initialization data from the registry.

Is there any way I can install this application as a service on windows 2008 r2 64bit?

If not, are there any workarounds I can try?

What are your suggestions?

share|improve this question
What error are you getting in the appcrash? Can you get a trace from the application? – pehrs Apr 5 '10 at 12:08

I had the same problem, but Ricardo Pardini's hint with Process Monitor was the solution, I found out that the service (even at the time of just installing it) was looking for a dbExpress DLL which was not in the application directory nor in the search path. Copying the DLLs into the same folder resolved the problem.

share|improve this answer

Without access to the application or any trace why it might crash I can only offer some general ideas for what might help.

If it's just a POS (Plain Old Service ;) ) you can follow the instructions here to manually install it as a service. That way you will get around a failing install routine if the application itself works.

You can also try to run it using the compatibility mode. Old Delphi applications can benefit a lot from this.

share|improve this answer

also ms has several app compatibilty updates to r2, so if you haven't hit windows update and download.

also can you run the app directly without the /install parameter?

share|improve this answer

It's probably trying to read something from the 64 bit version of windows rather than the 32 bit version of windows. Make sure that you have the 32 bit sql server client installed and functioning properly. Other than that post the appcrash which should tell you which DLL to put in wow32.

share|improve this answer

We've written quite a few of those Delphi 32-bits services ourselves, and the only thing that actually helps us "debug" the services running on servers (64-bit included) without the source code is Sysinternal's (now Microsoft Technet) Process Monitor.

In your specific case, I'd download Process Monitor (it's a simple executable) and run it and then set it up to filter only your service's .exe application. Look around for it's docs, but this is actually a very simple filter.

Keep Process Monitor running (filtered) on both machines while you start the service. Compare results from Process Monitor. I bet you have something like a missing registry key, or a missing directory or permission which causes the Delphi app to raise and Exception. This should be easy to spot on Process Monitor. Even more if you have a working machine to compare to.

share|improve this answer
I have used process monitor, but the service will not even install and I could not see anything that looked like an exception coming up :( – Oded Apr 10 '10 at 8:28
up vote 0 down vote accepted

We have decided to keep running on a 32bit OS in the meantime and rewrite this app in .NET...

share|improve this answer

You didn't mention anything about UAC. Disable UAC altogether and try it again.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.