June 14, 2004 at 8:54 am
Update: - Ive tried opening the ERRORLOG file with notepad and pasting text into it. As soon as I save the file, it gets wiped out again and is blank. - No error messages, nothing!
This applies to the 'Current' SQL log file - not the Transaction log file. Errors are being logged in event viewer, but not in the SQL log file. there are 6 generations of log files, and all contain data except for the current one
Prior generation log file indicates that the ERRLOG file should be located in:
Logging SQL Server messages in file 'G:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
We have a SQL 2000 cluster server and the current SQL log file is empty! - No startup information, - it is Zero bytes and has been since the server was restared about a week ago...
FYI - one of our DBA's attempted to stop SQL services without using the cluster manager.- does that have anything to do with it?
I have physically logged on to both sides of the cluster and they are both empty. - any ideas on why we aren't logging anything?
June 15, 2004 at 8:12 am
Are there any messages in the Windows Event Viewer logs (application, security, system) that might shed light on this?
-SQLBill
June 15, 2004 at 9:47 am
Did you try cycling the error log to see if that will get you going again? sp_cycle_errorlog
June 15, 2004 at 11:28 am
Are there any ntfs errors in the eventlog for a corrupt filesystem ?
Can you also try connecting to Query analyzer and execute sp_readerrorlog and see if that gives any output ?
June 15, 2004 at 12:59 pm
I could not read the error log file at all, regardless of the access method. The recyling of the error log fixed (at least for now) the problem. Thanks for the suggestion though.
June 15, 2004 at 1:05 pm
Thank you for the suggestion, it worked! Now I'm hoping its not going to happen again. Although I now know how to stop it. We do have a third party package that monitors the log regularly and perhaps that is the culprit.
Thanks again!
June 16, 2004 at 1:27 am
Jim,
Now that you mention the 3rd party monitor, I have previously experienced a HP monitoring system that took over control of the errorlog in a similar fashion. I think at the time we used the "oh" resource kit utility to confirm it.
Cheers,
- Mark
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply