SBS2003R2 Freezes and hangs on boot

[tisgrandupnorth]

I've just won a battle with a SBS2003R2 server. Some time between 0600 (it emailed me the Server Performance Report) and 0845 (when the first user [didn't] log on) it froze.

When I asked an employee to log onto the server, it was on, but didn't respond to any kb / mouse input and the monitor was blank.

After a hardware reset, it hangs for 5 mins+ on Preparing Network Connections and another 5 mins+ on Applying Computer Settings before giving me a Ctrl - Alt - Del prompt.

It also pops up a "service failed to start" dialogue and, in the eventvwr, there's 7022s for Kerberos Key Distribution Center and Data Protector Express. Both are Started when I check them in the services.

I'm nervous that it's going to 'just freeze' again. There's nothing in any eventlogs bout the crash or any possible causes.

 

[tisgrandupnorth]

*bump*
Anyone?

 

[wahnula]

How long had the server been up & running fine before this event? Is it working normally now? Anything added/removed or environmental changes before this event?

Tony

 

[tisgrandupnorth]

Right. Well, it happened again this morning so I drove up to sort it out.

It happened today (15-06-07) and last on the (11-06-07). Between those dates it ran, pretty much, like a model server.

Nothing changed in the environment - I've been adding clients steadily over the last 2 months, local and VPN, setting up SharePoint - generally setting up a SBS.

The only non-standard things running on there are Sophos for SBS (AV and PureMessage) and a UVNC repeater for VNC-ing to workstations.

When I got in today:
- The screensaver was on and moving, but;
- Keyboard and mouse unresponsive - couldn't even numlock - and the screesaver stopped moving after I bashed the KB and froze on the screen.
- HDDs 5&6 (RAID5) were flashing away, but nothing else suggesting OS usage but not Exchange, User Files or Shadow.
- I could ping it locally but not telnet into any normally open ports (80, 5901, 444, 4125, 21, 25) - just got blank DOS box and flashing cursos (not 'could not open connection to the host').

I've done a hardware reset and, agian, it's hanging on 'Applying computer settings'. I'd done a couple of remote, polite restarts between the two dates above and it started in a perfectly reasonable time.

 

[wahnula]

Of course you did all your changes using the wizards...correct? If not there could be collisions that could lock up an SBS server.

I am an SBS user but not really a pro sysadmin, I had a similar problem (locked up server) recently that I am guessing was caused by a night of being exposed to high heat and humidity. I am just here to get more info from you about your event and hopefully keep the topic current until it catches the attention of the resident SBS gurus.

Sorry I can't be of more help.

Tony

PS: I like the term "polite restarts"...first time I've heard it!

 

[mattjurado]

1. Bashing a keyboard on a live server. Brilliant idea.
2. Small Business Servers are often the most difficult to troubleshoot. I absolutely hate this product line and wish Microsoft had never made it. All you ever hear from a functionality and security standpoint, is that each major Microsoft product should be its own server, yet here is SBS with firewall, Exchange, faxing, Active Directory, etc...
3. Start with the basics. Research any new messages in your event logs. Run any hardware diagnostics (I'm sure you at least have a tool to check your hardware RAID array).

The fact that your mouse and keyboard don't respond, tell me there is likely a loose connection/hardware issue, or your OS is REALLY busy with something, so that it can't respond to basic input devices.

Matt

Please always take the time to backup important data and verify that backup, before making any changes suggested.

 

[tisgrandupnorth]

1. It was a euphemism. I gently tapped the space bar. Don't panic.
2. But not all companies have got the cash. It's not perfect, but it's a stepping stone between POP3 email and paper diaries and a full-on multiple server setup.
3. All things I've done / thought. I don't throw threads up without good reason.

 

[mattjurado]

1. I had no idea.
2. I know, I have to deal with SBS all the time.
3. I don't know you or your troubleshooting skills, so I have to start at the bottom. I wasn't trying to be rude, but it sounded like one of those situations where you were banging your head against a wall, and you might be overlooking something simple.

So did you find anything of interest in your event logs?

What is the hardware configuration of this server?

What specific services are used on this SBS server (exchange, etc...)?

Matt

Please always take the time to backup important data and verify that backup, before making any changes suggested.

 

[tisgrandupnorth]

There's nothing at all in the event logs, except the VSS scheduled for 0700. I've moved that now to earlier in the AM so I'll know if that was it - I'll not get the Server Performnce Report in the morning.

It's a HP ML150G3 - standard spec, but 2GB RAM - w/ 3 x 80GB drives in RAID5 for data and 2 x 80GB in RAID1 for OS with an E200i SATA / SCSI Raid controller and a Ultrium 448 SCSI card controlling the tape drive.

It's used primarily as a file and Exchange server, but also does WSUS and a very basis SharePoint site.

I'm just creating some Counter Logs now to monitor it - see if I can see anything there. Strugging on what exactly to track though.

 

[tisgrandupnorth]

There's nothing at all in the event logs, except the VSS scheduled for 0700. I've moved that now to earlier in the AM so I'll know if that was it - I'll not get the Server Performnce Report in the morning.

It's a HP ML150G3 - standard spec, but 2GB RAM - w/ 3 x 80GB drives in RAID5 for data and 2 x 80GB in RAID1 for OS with an E200i SATA / SCSI Raid controller and a Ultrium 448 SCSI card controlling the tape drive.

It's used primarily as a file and Exchange server, but also does WSUS and a very basis SharePoint site.

I'm just creating some Counter Logs now to monitor it - see if I can see anything there. Strugging on what exactly to track though.