Service Control Manager - hitting some resource limit

Service Control Manager - hitting some resource limit

Post by Si5TYXVlcn » Fri, 28 Jan 2005 01:53:02


W2k Advanced Server SP 4
I have a server with a high number of windows services (150) started. I
have added more services and when I try and start them I get a error 1053
within a couple of seconds with event ids of 7009 & 7000 being logged in the
event log. If I stop a running service I can start one of these new
services. Also my Vertias Netbackup Client service (bpinetd.exe) cannot
spawn a new process (bpcd.exe) to do a backup. Again if I stop a running
service, then the process will spawn.
It appears I have hit some sort of resource limitation. It also appears to
be limited to those processes controled by the Service Control Manager as I
have no problem running programs from the desktop. I have searched the KB
and MSDN and googled everything I can think of and cannot find an answer
short of trying to replicate this problem on a test server and putting the
program into debug.
 
 
 

Service Control Manager - hitting some resource limit

Post by Dave Patri » Fri, 28 Jan 2005 13:44:36

There's a limit in Windows 2000 as to how many services you can have running
under user accounts. It has to do with a type of memory call "Desktop Heap"
The hard limit is 48MB. This article explains it somewhat.

http://www.yqcomputer.com/ ;[LN];184802

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.yqcomputer.com/


| W2k Advanced Server SP 4
| I have a server with a high number of windows services (150) started. I
| have added more services and when I try and start them I get a error 1053
| within a couple of seconds with event ids of 7009 & 7000 being logged in
the
| event log. If I stop a running service I can start one of these new
| services. Also my Vertias Netbackup Client service (bpinetd.exe) cannot
| spawn a new process (bpcd.exe) to do a backup. Again if I stop a running
| service, then the process will spawn.
| It appears I have hit some sort of resource limitation. It also appears
to
| be limited to those processes controled by the Service Control Manager as
I
| have no problem running programs from the desktop. I have searched the KB
| and MSDN and googled everything I can think of and cannot find an answer
| short of trying to replicate this problem on a test server and putting
the
| program into debug.

 
 
 

Service Control Manager - hitting some resource limit

Post by Bruce Sand » Fri, 28 Jan 2005 14:19:43

See if http://www.yqcomputer.com/ ;en-us;304101 helps.

--
Bruce Sanderson MVP Printing
http://www.yqcomputer.com/

It is perfectly useless to know the right answer to the wrong question.
 
 
 

Service Control Manager - hitting some resource limit

Post by Si5TYXVlcn » Sun, 30 Jan 2005 05:01:02

Dave,
I think you are right that the desktop heap is involved in this some how.
Though 98% of the 150 services run as LocalSystem. So I don't think I am
hitting the 48MB limit because when I hit this problem where the service
won't start I can chage the service login from LocalSystem to a Domain
account and it will start. So could it be the "Default" desktop heap that
the LocalSystem services share in the noninteractive service windows station
Service-0x0-3e7$ is exhausted? Is there a way to check that out? Am I even
playing in the right ballpark?

Thanks!!!
J.Sauers
 
 
 

Service Control Manager - hitting some resource limit

Post by Dave Patri » Mon, 31 Jan 2005 02:03:55

Take a look at the data in;
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\Windows
to see what follows;
SharedSection=

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.yqcomputer.com/


| Dave,
| I think you are right that the desktop heap is involved in this some how.
| Though 98% of the 150 services run as LocalSystem. So I don't think I am
| hitting the 48MB limit because when I hit this problem where the service
| won't start I can chage the service login from LocalSystem to a Domain
| account and it will start. So could it be the "Default" desktop heap that
| the LocalSystem services share in the noninteractive service windows
station
| Service-0x0-3e7$ is exhausted? Is there a way to check that out? Am I
even
| playing in the right ballpark?
|
| Thanks!!!
| J.Sauers
 
 
 

Service Control Manager - hitting some resource limit

Post by Si5TYXVlcn » Wed, 02 Feb 2005 03:21:14

SharedSection=1024,3072,512

But if I was hitting the 48MB Desktop Heap I wouldn't be able to change the
service login from LocalSystem to a domain account and start it correct?
Which I can. I understand how with user accounts you can exhaust the 48MB
desktop heap limit. But obviously LocalSystem works differently since I have
120+ services running out of that account 120*512=61.5MBs. The KB you
referred me to says "All services executed under the LocalSystem account with
Allow Service to interact with the desktop not selected share the desktop
heap of the "Default" destop in the noninteractive service windows station."
So the question seems to be what resource limit am I exhausting with my
LocalSystem services and can it be modified? Is it the 512kb default desktop
heap allocated to the window station Service-0x0-3e7$? And if I increase
that third value, I reduce the number of services I can run under a user
account, but do I increase the number of services I can run with the
LocalSystem account?
 
 
 

Service Control Manager - hitting some resource limit

Post by Dave Patri » Thu, 03 Feb 2005 10:18:03

I agree with your interpretation and would try increasing the third
parameter by 128 and see what happens. Since you run very few services with
user logons these shouldn't be impacted.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.yqcomputer.com/


| SharedSection=1024,3072,512
|
| But if I was hitting the 48MB Desktop Heap I wouldn't be able to change
the
| service login from LocalSystem to a domain account and start it correct?
| Which I can. I understand how with user accounts you can exhaust the 48MB
| desktop heap limit. But obviously LocalSystem works differently since I
have
| 120+ services running out of that account 120*512=61.5MBs. The KB you
| referred me to says "All services executed under the LocalSystem account
with
| Allow Service to interact with the desktop not selected share the desktop
| heap of the "Default" destop in the noninteractive service windows
station."
| So the question seems to be what resource limit am I exhausting with my
| LocalSystem services and can it be modified? Is it the 512kb default
desktop
| heap allocated to the window station Service-0x0-3e7$? And if I increase
| that third value, I reduce the number of services I can run under a user
| account, but do I increase the number of services I can run with the
| LocalSystem account?