Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

On only one server of many, the SQL log is blank and shows a message "the log file is not using Unicode Format" when viewed via SSMS. The log is in the right location as specified in the service properties and is readable with notepad. Log looks normal, just won't show up in Log File Viewer in SSMS. Any ideas why?

SQL Server 2012 in active passive Windows failover cluster on Windows 2012. SQL Server ver 11.0.3368

This instance is the SQL Server for MS SCCM. It has trace flags -T8295 and -T4199 as service startup parms. These were added by SCCM when its DB's were installed.

Thanks

share|improve this question
    
I had an idea which worked. I forced creation of a new log using sp_cycle_errorlog and the new log can be read fine in SSMS. This server recently had a bad crash due to a SAN connection failure. I think that the SQL log file may have bcome corrupted as a result of that. –  WoodyDBA Sep 6 '13 at 3:15
    
Any chance you (or someone) opened it up in notepad and then saved it with the wrong format? If the SQL Server service was stopped and restarted as a result of this crash, the error log should have cycled anyway... –  Aaron Bertrand Sep 6 '13 at 3:16
    
Aaron, thanks. No it had not been saved by anyone. I had tried restarting the instance and a new log was not created. Interestingly, the log from the restart was just appended to the current log. –  WoodyDBA Sep 6 '13 at 3:19
    
Is the "Write OEM error log" option selected? –  Martin Smith Sep 6 '13 at 11:00
    
Seems like this solution will work (dba.stackexchange.com/a/34422/8783) which @MartinSmith has pointed out. –  Kin Sep 6 '13 at 16:51
show 1 more comment

1 Answer

I had an idea which worked. I forced creation of a new log using sp_cycle_errorlog and the new log can be read fine in SSMS. This server recently had a bad crash due to a SAN connection failure. I think that the SQL log file may have bcome corrupted as a result of that.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.