|
There is a 12 hour gap in my error logs where no information is reported and it occurs right before a server crashed. Is there another way to get information on what caused this crash... a reason why SQL Server stopped reporting information udirng this time?
(comments are locked)
|
|
It sounds like, possibly, the problem was 12 hours in the past and the crash just resolved it? How about errors in the OS error logs? There are only a few places to get errors from and it sounds like your error did something to the log. That or someone edited the log during/after the crash (the log is just a text file). That's the mystery here.... we had this happen twice over the weekend so no one was here the second time it happened. The OS error logs has activity but does not show any errors that indicate an issue with SQL Server. We would normally assume this is a issue with the box (not enough RAM, etc) but there is another instance on this box that was unaffected and did not lock up. So it is isolated to one instance. It's been a challenge to troubleshoot this one any suggestions would be great!
Sep 12 '11 at 06:00 AM
colibri
Two instances... one fails, the other does not, you lose the log on the one that failed... Any chance the logs are writing on top of each other?
Sep 12 '11 at 07:12 AM
Grant Fritchey ♦♦
(comments are locked)
|
