Service Won't Start

[Guest]

I am having a strange problem starting a service. When I start it, it immediately (not after the standard 30 seconds) returns error 1053 "service did not respons in a timely fashion." Here is the strange part

It seems the problem is with the User the service logs in as. If I set the service to log on as LocalSystem it starts (doesn't work though as I need domain privileges). Also if I stop another service which logs in as a domain user it will allow my service to start but I can not restart the service which I stopped. It definitely looks like something is limiting the total # of domain users logged on as a service but I can't figure out what is doing the limiting. There are 25 services running as domain users on this machine. I have also reproduced this problm on another server. They are both Windows 200 Server

Anyone seens anything like this before?

 

[John Campbell]

Yep I've seen this due to desktop heap limitations.
If you run under SYSTEM account your service will use the SYSTEM desktop.
However if you have things set to run under user accounts each service will
use a desktop and you have a limited number of desktops depending on your
desktop heap setting (see KB 184802 which explains it a bit).

You would normally see something in the eventlog when the service tries to
start indicating this but I can't remember exactly what it is for Win2K

I am having a strange problem starting a service. When I start it, it

immediately (not after the standard 30 seconds) returns error 1053 "service
did not respons in a timely fashion." Here is the strange part.

It seems the problem is with the User the service logs in as. If I set

the service to log on as LocalSystem it starts (doesn't work though as I
need domain privileges). Also if I stop another service which logs in as a
domain user it will allow my service to start but I can not restart the
service which I stopped. It definitely looks like something is limiting the
total # of domain users logged on as a service but I can't figure out what
is doing the limiting. There are 25 services running as domain users on
this machine. I have also reproduced this problm on another server. They
are both Windows 200 Server.