Microsoft KB Archive/256073
Article ID: 256073
Article Last Modified on 10/27/2006
- Microsoft Systems Management Server 2.0 Standard Edition
This article was previously published under Q256073
After you delete a custom group class using the DelGrp.exe tool, the Dataloader is unable to load a Management Information File (MIF) that contains changed attributes for the same group class.
When this occurs, the information from the updated MIF does not appear in the Administrators Console.
This issue can occur because the DelGrp.exe tool does not delete the stored procedures associated with the group class.
To work around this issue after you run the DelGrp.exe tool to delete the Group Class, manually delete the two stored procedures associated with the Group Class that you deleted.
If you are deleting a group called User_info_DATA, you need to delete the stored procedures dUser_info_DATA and pUser_info_DATA.
For information about how to delete a stored procedure, view the books online for SQL Server. For SQL 6.5, query on "Drop Procedure". For SQL 7.0, search on "How to delete a stored procedure".
If you are planning on adding the custom group class back after making modifications to the smsdef.mof that deviate from the original modification, then you may need to follow the additional items below to remove the architecture. Otherwise, when the new architecture is created, there may be 2 references created in Resource Explorer; one containing the original architecture that will not be displaying any data, the other with the new architecture that does display the new data. Because the same group class name was used, Delgrp.exe will delete BOTH objects.
- Make a backup of the SMS server, using the native SMS backup task.
- Make sure unwanted MIF files are removed from all client machines. (NOIDMIFS directory)
- Use DELGRP.exe (part of BORK 4.5 in the SMS section) to remove the unwanted tables from SQL server.
- Through SQL Enterprise Manager, manually removed the associated Stored Procedures, prefixed by 'p' and 'd'. (right click and delete) This is per the workaround in Q256073.
- Run CONV20.exe (This will look at the SMS database and verify/repair its structure.)
- Stop the WMI service.
- Delete all files located in the c:\winnt\system32\wbem\repository directory.
- Restart the WMI service.
Important: Rebuilding the WMI repository in Windows 2000 or later versions can yield unpredictable results.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When Dataloader processes a new MIF that contains information for the deleted Group Class name and you have changed the format of the data, the tables for the group class are created again but the associated stored procedures are not. The earlier stored procedures still exist.
The stored procedures become out of sync with the tables structure and the Dataloader cannot update the MIF information.
For example, you may see the following text in the Dataloader log:
CDefinedGroup::InsertDefinedAttribute - could not find table $$<SMS_INVENTORY_DATA_LOADER> SQL>>>rollback transaction $$<SMS_INVENTORY_DATA_LOADER> SQL>>>>> Done. $$<SMS_INVENTORY_DATA_LOADER> CGroup::DefineAttributes - couldn't defined attribute $$<SMS_INVENTORY_DATA_LOADER> CGroup::DefineGroupAndAttributes - couldn't define attributes for MICROSOFT|INVENTORY_FILES|1.0 $$<SMS_INVENTORY_DATA_LOADER> CMachineSource::InsertMachine - could not validate machine $$<SMS_INVENTORY_DATA_LOADER> ~Cannot process MIF XGY6OD1Q5.MIF, moving it to D:\SMS\inboxes\dataldr.box\BADMIFS\IUSH4YZ5.MIF
In some instances, when the group class is re-created, duplicate stored procedures may exist. Changes to the name of the MIF or the data collected by the MIF will result in changes to the table name and table contents respectively. To determine which stored procedure should be retained, examine the properties of the stored procedure for reference to the tables being queried.
Additional query words: prodsms
Keywords: kbbug kbdatabase kbdataloader kbprb KB256073