macondo100
asked on
service on Local Computer started then stopped. Somer services ...
I'm setting up user-defined services and get the following error on Windows 2003 Server.
The <service name> service on Local Computer started then stopped. Somer services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
I'm simple settin up an application to run as a service. It's always worked on Windows 2000 using Windows 2000 Resource Kit (files instsrv.exe and srvany) and w/ Windows XP, also using the Windows 2000 Resource Kit.
On Windows 2003 Server, using its own resource kit, it fails w/ the above error.
However, If I use the instsrv.exe and srvany.exe files from the Windows 2000 Resource Kit on the Windows 2003 Server box the services run ok. Is there a known issue w/ the Resource Kit for Windows 2003?
I know this is a known error, but from the research I've done, there are no issues when setting up a simple application to run as a service.
Thanks in advanced.
The <service name> service on Local Computer started then stopped. Somer services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service.
I'm simple settin up an application to run as a service. It's always worked on Windows 2000 using Windows 2000 Resource Kit (files instsrv.exe and srvany) and w/ Windows XP, also using the Windows 2000 Resource Kit.
On Windows 2003 Server, using its own resource kit, it fails w/ the above error.
However, If I use the instsrv.exe and srvany.exe files from the Windows 2000 Resource Kit on the Windows 2003 Server box the services run ok. Is there a known issue w/ the Resource Kit for Windows 2003?
I know this is a known error, but from the research I've done, there are no issues when setting up a simple application to run as a service.
Thanks in advanced.
ASKER
Got it resolved.
Actually, I was using (instructing someone to do so) the reg.exe from Windows 2003 Server to create certain keys, but it was failing. It always worked w/ NT, XP, and 2000 (using the Windows 2000 Resouce Kit's reg.exe). I wasn't able to figure it out because I was working w/ a couple of folks unfamiliar to the services and they sweared the keys were correct when they were actually not.
Thanks.
Actually, I was using (instructing someone to do so) the reg.exe from Windows 2003 Server to create certain keys, but it was failing. It always worked w/ NT, XP, and 2000 (using the Windows 2000 Resouce Kit's reg.exe). I wasn't able to figure it out because I was working w/ a couple of folks unfamiliar to the services and they sweared the keys were correct when they were actually not.
Thanks.
For what it's worth, that's one of the reasons I make my services self-installing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I suspect you're falling prey to that.
Presuming you've already checked the event logs, I'd suggest you trace program execution with your own log file to see where it's failing. A simple text file you open and close for each trace point will ensure that buffered messages at the point of failure won't be lost.