Verbose Windows Management Instrumentation (WMI) logging can help in troubleshooting various WMI related problems (like ones mentioned in the KB27 article). By default, verbose WMI logging is disabled. To troubleshoot a WMI related problem you usually need to enable logging, reproduce the problem and then explore the generated logs (or send the generated logs to the VisualSVN Support Team). This article describes how to deal with verbose WMI logging on various operating systems.
Windows XP/Windows Server 2003
To enable verbose WMI logging on Windows XP/Windows Server 2003:
- Start the WMI Control snap-in (wmimgmt.msc).
- Right-click on WMI Control node and select Properties. This brings up the WMI Control Properties dialog.
- Select the Logging tab.
- Set the Logging level to Verbose.
On Windows XP/Windows Server 2003 operating systems WMI logs are stored as a plain textual files in the %windir%\System32\WBEM\Logs directory. It's recommended to put these log files into a single .zip archive before sending them to us.
Windows Vista/Windows 7/Windows Server 2008
To enable verbose WMI logging on Windows Vista/Windows 7/Windows Server 2008:
- Start the Event Viewer snap-in (eventvwr.msc).
- Make sure that the View | Show Analytic and Debug Logs checkbox is checked in the Event Viewer's main menu.
- Expand the Applications and Services Logs / Microsoft / Windows / WMI-Activity section on the right panel.
- Then right click on the Trace item and choose Enable Log context menu command.
To export WMI logs on Windows Vista/Windows 7/Windows Server 2008:
- Start the Event Viewer snap-in (eventvwr.msc).
- Make sure that the View | Show Analytic and Debug Logs checkbox is checked in the Event Viewer's main menu.
- Expand the Applications and Services Logs / Microsoft / Windows / WMI-Activity section on the right panel.
- Then right click on the Trace item and choose Save Events As context menu command.
- Save log entries to a file.