No members appear on a collection that is replicated to an SMS 2.0 child site if you create the collection on a SMS 2003 parent site (886154)



The information in this article applies to:

  • Microsoft Systems Management Server 2003

SYMPTOMS

You create a collection on a Microsoft Systems Management Server (SMS) 2003 site. The collection is replicated to an SMS 2.0 child site. When you try to view the members of the collection on the SMS 2.0 child site, no members appear. The following information is logged in the SMS\Logs\Colleval.log on the SMS 2.0 child site.

Note Some of these lines have been wrapped for readability.
********~Evaluating collectionID
Next due date for collection collectionID is 05/25/04 14:49:00
Preparing to refresh collection collectionID
SQL Err #10007> General SQL Server error: Check messages from the SQL Server.
SQL Msg #208> Invalid object name 'Add_Remove_Programs_DATA'.
CCollectionSource_SQL::RefreshResults - Err in SQL cmd insert 
into Temp1__RES_COLL_collectionID (MachineID,ArchitectureKey,Name,SMSID,
Domain ,IsClient) select  all SMS_R_System.ItemKey,SMS_R_System.DiscArchKey,
SMS_R_System.Name0,SMS_R_System.SMS_Unique_Identifier0,SMS_R_System.Resource_Domain_OR_Workgr0,
SMS_R_System.Client0 from System_DISC AS SMS_R_System INNER JOIN 
Add_Remove_Programs_DATA AS __System_ADD_REMOVE_PROGRAMS0 ON 
__System_ADD_REMOVE_PROGRAMS0.MachineID = SMS_R_System.ItemKey   
where UPPER(__System_ADD_REMOVE_PROGRAMS0.DisplayName00) = UPPER("Microsoft SQL Server 2000")
CStatusReporter::Report() ERROR: Caller passed NULL for pSM.
Could not refresh results for collection collectionID.
In this example, the SMS 2003 collection is based on collection query criteria that uses the Add/Remove Programs attribute.

CAUSE

This issue occurs if the following conditions are true:
  • You create a collection that is based on a query at the SMS 2003 parent site.
  • The collection query criteria uses an attribute that is not available on the SMS 2.0 child site. For example, the Add/Remove Programs attribute is not available on an SMS 2.0 site.

STATUS

This behavior is by design.

MORE INFORMATION

This issue may occur if different versions of the SMS_def.mof file are used in your hierarchy. For more information about SMS 2.0 and SMS 2003 interoperability, see "Administering a mixed-version hierarchy" in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide. To review this information online, visit the following Microsoft Web site:

Modification Type:MinorLast Reviewed:6/13/2005
Keywords:kbSMSInventory kbSMS2003bug kbtshoot kbCollections kberrmsg kbInventory kbinterop KB886154 kbAudITPRO