J
Jeff Nokes
Hi,
I'm currently setting up a home network for my parents, where they
have one main pc that acts as a file/print server, running Windows
2000 Prof. I'm just using the standard file and printer sharing
service, which means I'm going to need the "Server" service running at
all times. The issue I'm having is that the "Server" service doesn't
start up when the machine boots, eventhough it is set to automatically
start up upon boot. When I open the service control manager (SCM)
after boot-up, I can manually start the "Server" service without any
issues or errors. But, the service will only run for an hour or two,
and then just stop randomly. At that time, I can open the SCM again
and start it manually again, and everything is OK for the next hour,
and so on ...
One thing I've noticed is the "services.exe" process is running, even
if the "Server" service or SCM is not running, not sure if that's
normal or not. When monitoring "services.exe", when I start up the
"Server" service, I can see elevated activity in the process for about
a second, and then it just goes back to a steady-state condition, with
the "Server" service now flagged as running.
Through all of this, there isn't one event recorded in any of the
event logs. I've tried setting the Recovery options for this service
but Windows doesn't let you since the "Server" service runs in the
same process as the SCM. I've resorted to running a batch on boot-up
that will start the service via a 'NET START', and also I have a
schedular running that will attempt a "NET START' every 10 min, I
don't know what else to do. This seems to work OK to keep their
file/printer sharing going, but it seems like a 'hack' to me, I
shouldn't have to do this.
I've re-installed the latest service pack (SP4), I've downloaded and
installed every update possible, I've looked on Microsoft's KB, found
nothing. I've scoured the web and newsgroups, still can't find any
matching situation. I've never ran into this problem before ... weird
....
If anyone has any suggestions, I'd sure like to hear them. Thanks in
advance for any help you offer.
Regards,
- Jeff
I'm currently setting up a home network for my parents, where they
have one main pc that acts as a file/print server, running Windows
2000 Prof. I'm just using the standard file and printer sharing
service, which means I'm going to need the "Server" service running at
all times. The issue I'm having is that the "Server" service doesn't
start up when the machine boots, eventhough it is set to automatically
start up upon boot. When I open the service control manager (SCM)
after boot-up, I can manually start the "Server" service without any
issues or errors. But, the service will only run for an hour or two,
and then just stop randomly. At that time, I can open the SCM again
and start it manually again, and everything is OK for the next hour,
and so on ...
One thing I've noticed is the "services.exe" process is running, even
if the "Server" service or SCM is not running, not sure if that's
normal or not. When monitoring "services.exe", when I start up the
"Server" service, I can see elevated activity in the process for about
a second, and then it just goes back to a steady-state condition, with
the "Server" service now flagged as running.
Through all of this, there isn't one event recorded in any of the
event logs. I've tried setting the Recovery options for this service
but Windows doesn't let you since the "Server" service runs in the
same process as the SCM. I've resorted to running a batch on boot-up
that will start the service via a 'NET START', and also I have a
schedular running that will attempt a "NET START' every 10 min, I
don't know what else to do. This seems to work OK to keep their
file/printer sharing going, but it seems like a 'hack' to me, I
shouldn't have to do this.
I've re-installed the latest service pack (SP4), I've downloaded and
installed every update possible, I've looked on Microsoft's KB, found
nothing. I've scoured the web and newsgroups, still can't find any
matching situation. I've never ran into this problem before ... weird
....
If anyone has any suggestions, I'd sure like to hear them. Thanks in
advance for any help you offer.
Regards,
- Jeff