A package is sent to the wrong clients or is not sent at all if you try to distribute a package to a collection that is based on a query in Systems Management Server 2003

Members of a Microsoft Systems Management Server (SMS) 2003 collection are deleted. This symptom occurs if the following conditions are true:

• The collection is based on a query.
• The SMS Collection Evaluator component receives an error when it tries to evaluate the collection members.

The SMS Collection Evaluator component later repopulates the collection if the membership rule is successfully evaluated. If you have advertisements that run on a repeating schedule, the advertisements may run again on the clients after the scheduled time.

Entries that are similar to the following entries are logged in the Colleval.log file:

[40001][1205][Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 54) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction. CCollectionSource_SQL::RefreshResults - could not execute SQL cmd QueryScript Results refreshed for collection collectionID, 36089 entries changed. Could not evaluate one of the rules for collection collectionID.

The following events are logged in the Application log:

Event ID: 2542

Description: SMS Collection Evaluator failed to update the query rule "MembershipRule" of collection "CollectionName" (CollectionID).

Event ID: 2511

Description: SMS Collection Evaluator failed to update the membership of collection "CollectionID".

Event ID: 2544

Description: SMS Collection Evaluator is updating the results for collection "CollectionID", there are 0 member changes.

Event ID: 2543

Description: "SMS Collection Evaluator failed to evaluate some of the query rules for collection "CollectionName" (CollectionID)"

In these events, CollectionName is the name of the collection, MembershipRule is the name of the collection's membership rule, and collectionID is the eight digit collection ID

This problem occurs if a Microsoft SQL Server deadlock condition occurs when the SMS Collection Evaluator component tries to evaluate the membership rule for the collection. When the SMS Collection Evaluator component encounters an error, the query-refresh task continues, and then returns no members for the collection. Therefore, the collection members are removed from the collection until the collection is reevaluated correctly.

Service pack information

To resolve this problem, obtain the latest service pack for Systems Management Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SMS 2003 Service Pack 1 (SP1) to apply this hotfix.

Restart requirement

This hotfix stops the following services and then prompts you to perform a site reset:

• SMS_SITE_COMPONENT_MANAGER
• SMS_EXECUTIVE
• SMS_SQL_MONITOR
• SMS Agent Host
• Windows Management Instrumentation

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. The English SMS 2003 International Client Pack 1 version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. The English SMS 2003 International Client Pack 2 version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Hotfix installation instructions

You must apply this hotfix to all SMS 2003 SP1 primary site servers in your hierarchy. To apply this hotfix, follow these steps:

1. Copy the Sms2003-sp1-kb886136-x86-enu.exe file to a folder on your primary site server.
2. Run Sms2003-sp1-kb886136-x86-enu.exe on your primary site server.
3. Click Next to start the Setup wizard.
4. Click I Agree, and then click Next.
5. Click Continue to let the Setup wizard stop the SMS services.
6. Click Yes to let the Setup wizard reset the SMS site. If you click No, you must manually perform a site reset to make sure that the hotfix installation is completed. To manually perform a site reset, follow these steps:
   1. Click Start, point to All Programs, point to Systems Management Server, and then click SMS Setup.
   2. Warning Do not complete this step until you read this warning. By default, Remove SMS is selected. You must make sure that you click Modify or reset the current installation to perform a site reset. If you do not clear the Remove SMS option, the Setup program automatically removes your SMS installation.
      
      Click Next two times, click Modify or reset the current installation, and then click Next.
   3. Click Next four times, and then click Finish.
   4. Click Yes to reset the site.

To work around this problem, move the clients into subcollections of the primary collection. By dividing the larger collection into smaller subcollections, you can base the primary collection on a smaller query. When you use smaller subcollections, you have more control over advertisements. You can still distribute advertisements to the whole collection by using the Include members of subcollections option on the General tab of the advertisement properties dialog box.

For more information about how to distribute software in Microsoft Systems Management Server (SMS) 2003, see the "Distributing Software" topic in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide. To view this information online, visit the following Microsoft Web site:For more information about how to manage collections and queries in SMS 2003, see the "Managing Collections and Queries" topic in the Systems Management Server 2003 Concepts, Planning, and Deployment Guide. To view this information online, visit the following Microsoft Web site:

Microsoft 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 Systems Management Server 2003 Service Pack 2.

This hotfix does not prevent the SQL Deadlock condition. This hotfix makes a change in the way that SMS handles the condition by preventing Collection Evaluator from removing the query results when a SQL error occurs and leaving the collection empty.

This change is accomplished by forcing an "Access Denied" message back to SQL during the deadlock. This message preserves the query results and the collection membership. This "Access Denied" error message may appear in the SQL or Colleval logs, and it is expected behavior.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: