Orphaned distribution point data in a Systems Management Server 2.0 database (823655)


The information in this article applies to:

  • Microsoft Systems Management Server 2.0

SYMPTOMS

This articles describes a hotfix that addresses two different but related problems.

Problem 1

If you delete a Microsoft Systems Management Server (SMS) 2.0 secondary site, a site system that belongs to the site that you delete may still be present in the SMS SQL database on the parent site after the deletion. For example, when you delete the site, the SMS Distribution Manager may try to distribute a package to a non-existent SMS distribution point.

Problem 2

If you have a script or application that uses the SMS_DistributionPointGroup class in the SMS 2.0 software development kit (SDK) to distribute an SMS package to members of a distribution point group, SMS may target a distribution point that belonged to a child site that no longer exists.

CAUSE

Problem 1 may occur if you click Delete the site in the SMS Administrator Console but not if you click Deinstall the site. The problem may also occur if you run the preinst /DELSITE:{SiteCode,ParentCode} command to delete the site.

Both of these problems occur because, when a secondary site is removed, not all the references to the site are removed from its parent site SQL database.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SMS 2.0 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this SMS 2.0 Service Pack 4 sites has the file attributes (or later) 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 tool in Control Panel. 
   Date         Time   Size   File name
   -------------------------------------
   05-Nov-2003  23:19  1,906  Update.sql
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

How to install the hotfix

Hotfix installer

Note This method is only for Intel-based computers.
  1. Create a folder that is accessible to your SMS site servers.
  2. Copy the Sms2.0-spX-kb823655-x86-enu.exe update file (where X is the service pack version) to the new folder.
  3. From each of the primary SMS site servers in your environment, use an account that has administrative credentials to log on to your site server.
  4. Exit the SMS Administrator console if it is running.
  5. Run the Sms2.0-spX-kb823655-x86-enu.exe file, and then follow the instructions in the wizard.

Manual installation

  1. Create a folder that is accessible to your SMS site servers.
  2. Run the following command, and then extract the hotfixed files to the folder you just created:

    SMS2.0-SPX-KB823655-X86-ENU.exe /x

    Where X is the service pack version.
  3. From each of the primary SMS site servers in your environment, use an account that has administrative credentials to log on to your site server.
  4. Exit the SMS Administrator console if it is running.
  5. Stop all the SMS services.
  6. Use a SQL server query tool (such as Query Analyzer or ISQL/W) to load the Update.sql script.
  7. In the SQL server query tool, click the SMS database, and then run the script.
  8. Restart the SMS services.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Modification Type:MinorLast Reviewed:6/5/2006
Keywords:kbHotfixServer kbQFE KB823655
©2004 Microsoft Corporation. All rights reserved.