Microsoft Windows Server 2003 for SBS keeps shutting down by itself
Posted on 2006-05-26
Ok, confession time. I know nothing about Microsoft Windows Server 2003 for SBS. I am a babe in the woods here.
I installed it from scratch, not knowing what I was doing, living by my wits...
So be gentle with my ego please :)
Ok, installed it, called the server JUSTINE, because the old one that was being replaced was called JUSTINE. I figured it would slot in without requiring any client computer updates that way. Well, that didn't work - the client computers wouldn't log on to the shared folders as the seemed to be "confused" or otherwise "loyal" to the original "JUSTINE" at some lower level.
I managed to (forget the proper terminology) rename the server from JUSTINE to SERVER (yay for me). It went through a lengthy process where it seemed to erase any and all internal knowledge of JUSTINE and replaced it with SERVER. Once it rebooted, the server was called SERVER.
I then had a temporary problem accessing the Shared Folders, but I sorted that permission problem out.
I also had a problem with the server wanting to be the DHCP server, but there is already a hardware firewall doing that job, so I shut down the DHCP server and set it to manual.
The clients were happy to see the new SERVER, they're logging into the shares just fine and life appears to be happy. Except
(que horror movie music as villain creeps up behind the protagonist...)
The server shuts itself down regularly. First I suspected this to be a hardware issue, but I just now (finally) caught it. Windows suddently says it is shutting down, and does so followed by powering the box down. It does this about 3-5 times per working day (7am-6pm), and the interval appears to be roughly between 1.5 and 2.5 hours since the last restart.
The idea of a server going into hybernation seemed abusurd to me, and an inspection of the power schemes shows monitor, hard disks and system standby are all set to "Never". Hybernation is disabled altogether, there is no UPS and the UPS service is stopped. The server is in use all the time via the shares, but no keyboard or mouse activity on the system itself.
The only thing that looks like it may be involved says "When I press the power button on my computer:" with the value "Shutdown". So, as I'm writing this I have disconnected all the front panel connectors, just in case there is some weird periodic short in the power button... but for the purpose of this topic, let's assume that's not the source of the problem.
As you experienced server jocks probably are aching to yell by now: what about the Event Viewer? Indeed, lets go there next.
Let's mention the event logs that are clear of anything odd: System, Security, File Replication and Directory service.
The DNS Event log complains every two minutes that it can't open the zone 1.168.192.in-addr.arpa in the Active Directory. It complains about not being able to find any primary or secondary zones, it complains that it is unable to open zone_mscds.smallbusiness.local. Although untidy, I don't see this as a problem as the clients all get their DNS services from the hardware firewall.
The Application Event log has the same error every 5 seconds.... (that can't be good :)
#50070: Unable to connect to the database STS_Config on JUSTINE\SharePoint (etc). Event ID: 1000. I have a sick feeling this may be related to the cause of my shutdown problem, but then there is no other message suggesting this is escalating or otherwise overflowing some kind of buffer, or... who knows.
But what is MOST interesting is that there is no message that I can find indicating WHY Windows is deciding to do a nice tidy shutdown. Not in any log I know how to find, anyway.
Now then. My primary (short term) objectibe is to stop the system from shutting itself down. It's not making the people in that office happy :)
Have I accidentally told you enough to suggest where I could start looking for the solution? Why does ANY server shut itself down? That's just so... non-server-like! :)