July 7, 2005 at 4:54 am
Today in the morning when I got to my workplace I noticed through EM that one of the our Prod SQL servers doesn't work. I have tried to connect to it remotly but with no success. Then I have tried to ping it - failed again. The only way to bring it back was to go to the place where it resides and manually reset it. It was hanged
After restarting it works normal. I went through SQL Server and Windows Server 2003 event logs - nothing! I hadn't found any event that could explain me what has happen last night. In logs all was OK. Only in my e-mail I found a message from our MOM server:
Severity: Critical Error
Status: New
Source: EventLog
Name: Erorsecurity
Description: The previous system shutdown at 19:50:10 on 2005.07.06 was unexpected.
Domain: dom1
Agent: Server_name
Time: 7/7/2005 08:15:35
We have Windows Server 2003 SP1 and SQL server 2000 ent SP3
Does anyone experienced something like that?
July 7, 2005 at 5:05 am
No idea what caused this, but I would do a memory check and possibly look at other hardware items.
July 7, 2005 at 7:26 am
To piggy-back on Chris, we've seen this with several different issues:
a) bad motherboard
b) bad memory
c) bad driver for a piece of hardware
K. Brian Kelley
@kbriankelley
July 7, 2005 at 7:47 am
Thanks for replies. A half year before our company purchased 6 servers with the same hardware configuration. All drivers on all servers where installed the same. Three servers were made as SQL Servers and yesterday one of them hanged up. Could it be truth what you have said if other servers with the same hardware and drivers work without problem?
July 7, 2005 at 8:00 am
Yes. If that one server has bad memory or a bad motherboard, it would have the issue you described while the others would be fine. We have seen occasions where we've bought a batch of identical types of servers and 1 in that batch had a hardware issue (turned out to be a bad motherboard). The last time I can remember this is we had a batch of 4 Compaq (now HP) DL380G2s and 1 developed a bad motherboard after running fine for a while. The other 3 still have not exhibited the same issue (knock on wood).
K. Brian Kelley
@kbriankelley
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply