Service runs on XP and WIn2003 but not on Win2000
-
Anyone has a hint as to why a service might start successfully on WinXP and Win2003 machines, but not on Win2000 machines?
How do you define "successfully"? First thought is that you are using an API function that is only supported in XP or W2K3.
-
How do you define "successfully"? First thought is that you are using an API function that is only supported in XP or W2K3.
-
Successfully as in starts up, runs, and keeps running until i decide to stop it. On Win2000 it displays that infamous message box saying that the service cannot start in a timely fashion.
My first rule of writing services - start a ssecnd thread as quickly as possible, and do all your REAL work in the second thread. Leave the primary thread to report status back to the service control handler and to respond to the service requests. You probably are doing everything in a signle thread, and on Windows 2000 something is taking longer than the 6 or 10 seconds Win2K is willing to wait before declaring your service 'stuck'.
-
My first rule of writing services - start a ssecnd thread as quickly as possible, and do all your REAL work in the second thread. Leave the primary thread to report status back to the service control handler and to respond to the service requests. You probably are doing everything in a signle thread, and on Windows 2000 something is taking longer than the 6 or 10 seconds Win2K is willing to wait before declaring your service 'stuck'.
Your first rule also happens to be my rule as well ;) Actually it is a service pack issue. On some Win2K's it was working ok, but on some others it wasn't. The ones on which it failed did not have SP4 installed. We're still investigating it further...thanks for stopping by and help just the same!