When Server 2003 goes down unexpectedly

Forum Moderators: open

Message Too Old, No Replies

When Server 2003 goes down unexpectedly

How do I avoid the popup asking for a reason for the unexpected shut-down?

GaryK

8:29 pm on Oct 30, 2006 (gmt 0)

I know there is a workaround to avoid the situation I mentioned in the Subject and Description. Three of my servers have it. One does not.

Please help me find a solution to this problem. Thank you.

GaryK

8:46 pm on Oct 30, 2006 (gmt 0)

Never mind. I found the solution in Group Policy Editor.

Disable Administrative Templates/System/Display Shutdown Event Tracker.

aspdaddy

7:10 pm on Nov 1, 2006 (gmt 0)

Be carefull with that setting, the virus that needs a rebboot to finish installing will sneak in now ;)

GaryK

10:11 pm on Nov 1, 2006 (gmt 0)

I appreciate your advice. Thank you.

Is there a better approach to getting my server to restart after an unexpected reboot? I'm using dedicated, self-managed servers.

mrMister

9:49 am on Nov 3, 2006 (gmt 0)

Your servers should start after a reboot, even with shutdown event tracker, it's just that nobody can log in until a reason for the shutdown has been entered.

Even though you can't log in, all services that are set to start, will start automatically, so your servers should resume as normal. I can't imagine why you'd find this a problem, can you please explain more?

You can disable the shutdown event tracker. I can't see how disabling it will aid viruses. If a virus needs to reboot then it can do so. Even if the machine doesn't start automatically, the virus will take hold as soon as it is started manually.

Easy_Coder

10:44 am on Nov 3, 2006 (gmt 0)

Windows Server 2003 has been incredibly reliable for my operations. I've never seen one reboot unexpectedly yet. Any idea what's causing it to do that?

GaryK

6:19 pm on Nov 3, 2006 (gmt 0)

Windows Server 2003 has been incredibly reliable for my operations. I've never seen one reboot unexpectedly yet. Any idea what's causing it to do that?

I've also found Server 2003 to be very reliable. I suspect memory leaks from ADODB.Stream are the source of the problem but I cannot confirm that yet.

I can't imagine why you'd find this a problem, can you please explain more?

It's not so much a problem as it is annoying. I'm not yet at a point where I can honestly state the reason for the reboot and since I'm the only person with administrative access I don't see how supplying a possibly inaccurate reason serves any useful purpose. :)

Thanks for the replies. ;)

aspdaddy

11:04 am on Nov 4, 2006 (gmt 0)

The only time I have had w2k3 reboot was when it got too hot in the server room. Id be very surprised if its software related.

Your event logs should tell you whats going on, make sure all your hardware devices are logging problems. If not look at your vendors own event logs, compaq has software that monitors the status of RAM/Power/Fans/Disk etc.

Also check your Power, if you have a lot of USB devices you might be pulling too much power from the server and causing it to heat up

Easy_Coder

11:54 am on Nov 4, 2006 (gmt 0)

Gary, search the microsoft support site for windows 2003 unexpectedly shuts down. Theres a handful of results that might shed some light for you.

GaryK

7:30 pm on Nov 4, 2006 (gmt 0)

The only time I have had w2k3 reboot was when it got too hot in the server room.

That's only happened once when the power went out at the DC and the ATS didn't kick over to generator power. The company has since abandoned that DC.

Your event logs should tell you whats going on, make sure all your hardware devices are logging problems. If not look at your vendors own event logs, compaq has software that monitors the status of RAM/Power/Fans/Disk etc.

My event logs are very clean except for the occasional (once a week or so) communications failure between a COM object and WWW Publishing service. Vendor event logs are also clean. I have software running that sends me an e-mail if any h/w is not operating within acceptable specs. The only time I received one was during the aforementioned power failure.

Also check your Power, if you have a lot of USB devices you might be pulling too much power from the server and causing it to heat up

The only time a USB device is connected to the servers is when a tech needs to physically access the server. I'm told they use a USB-based KVM and I have seen it in the systray when I'm having problems.

search the microsoft support site for windows 2003 unexpectedly shuts down

I'm going to do that right now.

Again, thanks for your ongoing help with this issue. Each of you in your own way has given me something to think about. :)