running windows services on Win2003 Server
-
A client has recently upgraded from Windows 2000 Server (on single processor) to Windows 2003 Server (on dual processor). A windows service that I had written worked fine on 2000, but since the upgrade the service has been hanging and crashing. I cannot figure out why. The service in question is a simple thing: it polls a directory regularly and if it finds the file it is looking for then it system calls a bat file to process the file. The bat file process is simple also and takes ~ 1 second to run. On Win2003 Server, the service hangs at the point of calling the bat file. Any suggestions? Is Win2003 inherently different to Win2000 in the way it runs services? Does the dual processor cause any issues? Matt Bache
-
A client has recently upgraded from Windows 2000 Server (on single processor) to Windows 2003 Server (on dual processor). A windows service that I had written worked fine on 2000, but since the upgrade the service has been hanging and crashing. I cannot figure out why. The service in question is a simple thing: it polls a directory regularly and if it finds the file it is looking for then it system calls a bat file to process the file. The bat file process is simple also and takes ~ 1 second to run. On Win2003 Server, the service hangs at the point of calling the bat file. Any suggestions? Is Win2003 inherently different to Win2000 in the way it runs services? Does the dual processor cause any issues? Matt Bache
Matt Bache wrote:
A client has recently upgraded from Windows 2000 Server (on single processor) to Windows 2003 Server (on dual processor). A windows service that I had written worked fine on 2000, but since the upgrade the service has been hanging and crashing. I cannot figure out why. The service in question is a simple thing: it polls a directory regularly and if it finds the file it is looking for then it system calls a bat file to process the file. The bat file process is simple also and takes ~ 1 second to run. On Win2003 Server, the service hangs at the point of calling the bat file. Any suggestions? Is Win2003 inherently different to Win2000 in the way it runs services? Does the dual processor cause any issues?
In my opinion, you should use Event viewer to check the status of your system and what is the cause of the problem that cause your service could not run properly.