Select the product you need help with
The Framework.log file grows larger than 64 KB when you use WMI on a Windows Server 2003 or Windows XP computerArticle ID: 836605 - View products that this article applies to. SYMPTOMSWhen you use Windows Management Instrumentation (WMI) and
you configure it to log all events on your Microsoft Windows Server 2003-based computer or Microsoft Windows XP-based computer
for quick analysis and troubleshooting of problems, the file size of both the
Framework.log and the Framework.lo_ files
may be greater than what you configured for them. RESOLUTIONWindows Server 2003To resolve this problem, set the permissions on the %systemroot%\system32\wbem\logs folder so that the Network Service account has the Delete permission.To set the permissions on the %systemroot%\system32\ wbem\logs folder, follow these steps:
Windows XPTo resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:322389
(http://support.microsoft.com/kb/322389/
)
How to obtain the latest Windows XP service pack
MORE INFORMATIONYou can configure an error log for WMI through the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging The logging entry uses the following values:
The default value for the Log File Max Size entry is 64 kilobytes (KB). When a log file reaches this size, the log file will be backed up to Log_file_name.lo_, and a new log file starts collecting entries. The only exception to this is the Framework.log file. The Framework.log file continues to increase even after the file has exceeded the Log File Max Size setting. During the DCPROMO process, the DefltDC.inf template is used to apply certain NTFS permissions, registry permissions, and default user rights. The DefltDC.inf template removes the previously configured delete permissions for the NETWORK SERVICE account again. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2. PropertiesArticle ID: 836605 - Last Review: October 26, 2006 - Revision: 3.3 APPLIES TO
| Article Translations |


Back to the top








