Custom Services Failing on Restart when 70+ are running
- From: concept <concept@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 12 May 2007 17:44:00 -0700
Hello,
Im currently having a problem with having 70+ services running. Briefly, I
used firedaemon to make a basic .exe a service. Everything is fine while the
machine is running, services run perfect I can add more and what not.
However depending on the machine, somewhere between 70-100 services going,
once the machine restarts 2-4 of the services fail to start. These refuse
to start until i stop every single firedaemon service, and then start all of
them. After this happens all is well.
At first i thought it was releated to the desktop
heapsize(http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q184/8/02.asp&NoWebContent=1 )
But now I am not so sure. Here is a more detailed rundown any help would be
great.
Ive been having this issue on a box im messing around with. I run custom
services that launch an exe file. Everything runs fine while the server is
running. But on reboot random custom services fail. Terminal services also
fails to start.
The number of services that need launched on restart seems to be random each
time. Sometimes services start to fail, at around 70+ being setup. Other
times you don't see it failing until 100+ services needs started on reboot.
The server load with all services running is 2-5% and physical memory is
about 200 megs of 1gig, paged, is about 300-400 megs used.
It is normally 3-4 custom services that fail on reboot. The ones that fail
have the following error in event viewer.
Event Type: Error
Event Source: Aprog
Event Category: None
Event ID: 116
Date: 5/10/2007
Time: 7:08:40 PM
User: N/A
Computer: XXXXXXXXX
Description:
Subprocess monitoring failed due to subprocess is no longer active. The
subprocess is probably dead. Restarting the process. Error detail: Overlapped
I/O operation is in progress.
It will keep getting this error over and over again. However, if i stop all
custom services and then start them, everything launches fine.
When this happens on reboot Terminal services also fails to start. It will
not start, until I stop all the custom services. At which point it allows me
to start TS without any errors.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 5/10/2007
Time: 7:02:10 AM
User: N/A
Computer: XXXXXXX
Description:
The Terminal Services service terminated with the following error:
A dynamic link library (DLL) initialization routine failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
What I am trying to accomplish is a way to automatically launch these EXE
files, and have something that restarts them if they crash or fail. I haven't
been able to find a specific reason this is happening or how to fix it. So I
am open to any other suggestions on how to do this.
.
- Follow-Ups:
- Prev by Date: Re: Windows only sees 3GB memory on a 4GB Dell PE 1850
- Next by Date: RE: Custom Services Failing on Restart when 70+ are running
- Previous by thread: Re: Help and Support Service has been disappeared
- Next by thread: RE: Custom Services Failing on Restart when 70+ are running
- Index(es):
Relevant Pages
|
Loading
