Home/ Questions/Q 5997657
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T00:17:43+00:00

Solved the problem see the bottom of my post. So I have a simple

  • 0

Solved the problem see the bottom of my post.

So I have a simple windows service that watches a specific folder and upploads files that come into it to a server using a web service.

It’s working fine on my machine using windows 7 but when I try to start it on a windows server 2003, I receive an error: Error 1053: the service did not respond to start or control request in a timely fashion. But I get this message after only a few seconds.

I have created the ServicesPipeTimeout and set it to 60000 milliseconds.

I have tried running it from command line using sc query command and found out that the WIN32_EXIT_CODE is 0, which I think means that the service doesn´t even try to start because it find an error before it starts.

In the event viewer I get errors 7000 and 7009.
I am the Administrator on the windows server.
The only thing I haven´t tried is a hotfix I found from microsoft but I don´t want to use it because as I understand it, it is for when the service actually times out.http://support.microsoft.com/kb/886695

I have tried everything I can think of, is there anything that I am missing?

Gísli

EDIT: Re-installed the .NET framework and now I get a new error, Saying that the service controller can not be found.

EDIT: I setup the service with a setup project, not using the installutil command. This is because I need to get user input during the installation and save that in the registry.

EDIT: I have installed the .NET 4.0 framework, it wasn´t possible to install the service with out doing that.

In addition to what I wrote above I have also tried:
Rebooting.
Re-installing.
I have tried to change the permissions on the files that the service needs to access.
Changing permissions in the registry editor.
Edited the code so that the onStart function only starts one thread.

I think it is some kind of permission problem but I don´t have much experience dealing with Windows server.

Solution:
It turned out to be two seperate problems. The .NET framwork had to be repaired and I had to remove the try/catch clause that I had when starting the service. For some reason (unknown to me) the try catch block did something that made it impossible to start the service in a windows server 2003 but it ran fine on windows 7.

It would be very interesting to know why this is.

Thanks for all the help.

Gísli

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Have you installed the right version of .NET Framework on the Server 2003 PC? What comes as standard on Windows 7 will need to be installed manually on an older OS.

    You say “I have tried everything I can think of”. Please edit the question to show what you have already tried so we don’t suggest something you have already done.

    EDIT:
    Try also the Fusion Log viewer. Set it to log failures then start your service. Hit refresh then see if any errors are logged. Double-click a line for more details.

    • 0