I have an SBS2008 server that has been running fine since it was installed about 4 months ago. This morning, users started reporting that they could not log in. I had an on-site contact check the console and it was blank; no response to mouse or keyboard. The power lights were on the server. From a member server, I could ping the LAN NIC just fine but I could not RDP to the server. I tried to telnet to the server port 25. It appeared to conect but I received no reply from Exhange.
From a member server, I had the on-site contact type shutdown -i from the Start-->Run menu and enter the SBS Server name, select restart and click OK. It timed out with no response.
So, at this pint the server is obviously powered up and the NIC is pingable but everything else appears hung. With no other option, I had the on-site contact do a power cycle. It took over 4 hours to come back up to where I could access the server via RWW and the users could log in.
The lengthy delay before it was fully operational, I believe, is because of the use of Intel on-board RAID 5 controller. During the whole 4 hour time period, the drive lights of the array were eithre flashing rapidly or on solid. I do not have Intel Matrix installed. I just have the RAID array defined in the BIOS. This is an issue I need to adress and would be interested in any feedback from anyone who may have had a similar problem with the long startup after a hard power reset.
The main issue, though, is why the console locked up in the first place. After gaining access to the server, I looked at the logs and there were no errors prior to the power cycle restart. The power cycle restart happened at 8:28am this morning. The lst log entry in the system or applicaiotn log prior to that time was at 12:28am and it was an MSExchange Anti-virus update with the signature 3.3.7909.80. I am using Forefront for Exchange on the server.
It is unusual for there not to be any log entries between 12:28am and 8:28am when the server was power cycled. I am inclined to assume that the AV update may be the cause of the lockup.
I could use any ideas as to where to look for further diagnostic informaiton about the lockup or if anyone else has had any problems with MSExchange AV updates.
Thanks in advance for any help you can offer.