Trouble creating and starting a new service...

[JonnieStyle]

Hi folks,

I've got a W2K Server that needs to be running an older DOS-based
server program for the workstations to communicate with. If I logon
as an admin, and put this program in "startup" everything works great.
But I'd rather not have my account logged onto the server all day...

I used sc.exe to "create" a service.

I ran (sc.exe create "ATRT" binPath= "C:\atrt\atrt.exe")

I got the message that the service was created successfully, and when
I go to "services.msc" I can see it listed there, but when I click to
try to start it I run into the fabled "ERROR 1053" and something about
having the service start in a timely manner...

Any ideas with how I can troubleshoot this?

Cheers.

 

[Joe Richards [MVP]]

First this isn't an AD problem. AD has nothing to do with it actually.

Second, SC doesn't create services, it registers applications that were written
as services. If the application wasn't written to be a service (i.e. implements
the SCM hooks) then SC doesn't help it.

Third, there are tools that will crutch SOME applications into working as
services, check out srvany or FireDaemon. That being said, if the apps writes to
databases or files you can get corruption from crutching apps like that into
being services. Some apps just will not work that way period no matter what you do.

The best thing is to get the application rewritten as a service or contact the
vendor for a new version that is written as a service.

joe

 

[JonnieStyle]

First this isn't an AD problem. AD has nothing to do with it actually.

My apologies.

Second, SC doesn't create services, it registers applications that were written
as services. If the application wasn't written to be a service (i.e. implements
the SCM hooks) then SC doesn't help it.

http://support.microsoft.com/?kbid=251192


Third, there are tools that will crutch SOME applications into working as
services, check out srvany or FireDaemon. That being said, if the apps writes to
databases or files you can get corruption from crutching apps like that into
being services. Some apps just will not work that way period no matter what you do.

The best thing is to get the application rewritten as a service or contact the
vendor for a new version that is written as a service.

Done and done.