Microsoft KB Archive/889720

= The InventoryAgent.log file contains &quot;...does not exist out&quot; errors in Systems Management Server 2003 with Service Pack 1 =

PSS ID Number: 889720

Article Last Modified on 12/30/2004

-

The information in this article applies to:


 * Microsoft Systems Management Server 2003 SP1

-





SYMPTOMS
After you upgrade your Microsoft Systems Management Server (SMS) 2003 site to SMS 2003 with Service Pack 1 (SP1), the following errors appear in the InventoryAgent.log file on the SMS Advanced Client computers:

Collection: Class &quot;Win32_Vulnerability_Detail&quot; does not exist out. Collection: Class &quot;Win32_PatchState_Extended&quot; does not exist out. Collection: Class &quot;SMS_ActiveSyncService&quot; does not exist out. Collection: Class &quot;SMS_ActiveSyncConnectedDevice&quot; does not exist out. Collection: Class &quot;Win32_Vulnerability&quot; does not exist out. Inventory: 5 Collection Task(s) failed.

Note These errors may appear at various locations in the InventoryAgent.log file. They may not be grouped together as in this example.



CAUSE
These symptoms occur because Microsoft Systems Management Server (SMS) 2003 Service Pack (SP) 1 adds new Windows Management Instrumentation (WMI) classes to the master copy of the Sms_def.mof file. These new WMI classes provide support for new features in SMS 2003 SP1.



WORKAROUND
To work around these symptoms, disable the WMI classes in the master Sms_def.mof file. Disable these classes on all SMS site servers. To do this, follow these steps.

Note If your SMS site has more than one server, you can modify the master Sms_def.mof file on each SMS site server. Alternatively, you can modify this file on one SMS site server and then copy the file to all other SMS site servers.

Warning Modifying the master Sms_def.mof file incorrectly may cause inventory to fail. We recommend that you create a backup copy of the master Sms_def.mof file before you make any changes.  On the SMS site server, start Notepad, and then open the master Sms_def.mof file. By default, this file is located in the Sms\Inboxes\Clifiles.src\Hinv folder. On the Edit menu, click Find, type a class name in the Find what box, and then click Find Next.

Note You will perform this step a number of times. The first time that you perform this step, type Win32_Vulnerability_Detail in the Find what box. After you find the class name, find the line that starts with &quot;[SMS_Report(TRUE).&quot; This line appears several lines before the class listing. For example, after you search for the class name Win32_Vulnerability_Detail, you see the following lines:

[SMS_Report(TRUE), SMS_Group_Name(&quot;Vulnerability Detail&quot;), SMS_Class_ID(&quot;MICROSOFT|VULNERABILITYDETAIL|1.0&quot;), Namespace(&quot;\\\\\\\\.\\\\root\\\\ccm\\\\VulnerabilityAssessment&quot;)]

class Win32_Vulnerability_Detail: SMS_Class_Template

 In the line that starts with &quot;[SMS_Report(TRUE),&quot; change the SMS_Report value from TRUE to FALSE. Repeat steps 2 through 4 for the following classes: <ul> Win32_PatchState_Extended</li> SMS_ActiveSyncService</li> SMS_ActiveSyncConnectedDevice</li> Win32_Vulnerability</li></ul> </li> Save the modified master Sms_def.mof file.</li> Repeat steps 1 through 6 for all other SMS site servers, or copy the modified master Sms_def.mof file to all other SMS site servers.</li></ol>

Keywords: kbSMSInventory kbSMSClients kbtshoot kbClient kberrmsg kbInventory KB889720

Technology: kbSMS2003 kbSMS2003Search kbSMS2003SP1 kbSMSSearch

-

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

© Microsoft Corporation. All rights reserved.