I recently worked on a database corruption issue. In order to troubleshoot this I had to collect all the Event Logs from the server. But when I tried to open Event Viewer, MMC would fail with the following error. MMC could not create the snap-in. Name: Event Viewer CLSID: FX:{b05566ad-fe9c-7a4cbb7cb510} For that matter any MMC snap-in on the server would fail with the same error. But getting the event logs was critical to get troubleshooting going. Thats when Wevtutil.exe which ships with the Windows Operating System came to the rescue. Wevtutil.exe is by default located in the C:\windows\system32 folder. I had to just execute the following command to export the System Event Log to C:\SystemLogBackup.evtx wevtutil.exe epl System C:\SystemLogBackup.evtx The “epl” parameter exports the event log specified (System in this case) to the destination file. All I had to do is copy the exported file to my local desktop and double click it to open in the Event Viewer snap-in. This is indeed a good tool to have in a DBA’s armory. Related posts: Event ID 318 | Unable to read local eventlog (reason: The data area passed to a system call is too small) SQL Service does not start. Error “The system cannot find the file specified” What’s in a name? Enough to make the backup jobs fail
↧