Microsoft KB Archive/266149

= WMI Event Trace Does Not Contain CID or Client Computer Name =

Article ID: 266149

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition

-



This article was previously published under Q266149



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
You can use the System Monitor tool to create a Windows Management Instrumentation (WMI) Event Trace log that can provide helpful information when you are troubleshooting domain controller performance problems. For example, if a processor spike were occurring on a domain controller, the WMI Event Trace log could provide you with details about the specific cause of the processor spike.

However, the WMI Event Trace log is missing the Client SID and Client Machine Name (NetBIOS name or IP address) fields. This hotfix enables a registry entry that you can use to add the Client SID and the Client Machine Name fields to the WMI Event Trace log.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:   Date        Time    Size     File name -  01/25/2001  06:24p  130,320  Adsldpc.dll 01/25/2001 06:24p  348,944  Advapi32.dll 01/25/2001 06:23p  502,032  Instlsa5.dll 01/25/2001 06:24p  140,560  Kdcsvc.dll 01/17/2001 05:17p  198,928  Kerberos.dll 12/20/2000 01:13a   69,456  Ksecdd.sys 01/25/2001 06:24p  484,112  Lsasrv.dll 01/02/2001 12:45p   33,552  Lsass.exe 01/23/2001 09:06p  108,816  Msv1_0.dll 01/25/2001 06:24p  912,656  Ntdsa.dll 01/25/2001 06:24p  363,280  Samsrv.dll 01/25/2001 06:24p  128,272  Wldap32.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.



MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To add the Client SID and the Client Machine Name fields to the WMI Event Trace log:  Start Registry Editor. Locate and click the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA

 Add the following registry value:

Name: TraceSamEventLogInDetail

Type: REG_DWORD

Value: 1



Note that The WMI Event Trace Log file must be parsed be read correctly. There are two Microsoft Windows 2000 Resource Kit tools that can help you parse the file and obtain meaningful information. These tools are named Tracedmp.exe and Reducer.exe.

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp2fix KB266149

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.