In a three-tier SMS 2003 hierarchy, packages may not be decompressed or copied to the distribution point of the secondary site

A three-tier Microsoft Systems Management Server (SMS) 2003 hierarchy has a central site, a child primary site, and a secondary site. In this hierarchy, compressed packages may not be decompressed or copied to the distribution point of the secondary site. Therefore, you cannot deploy the packages to the clients that connect to this distribution point.

This problem may occur if the following conditions are true:

• The package's Send from the nearest site in the hierarchy option is enabled on the central site.
• The distribution point of the secondary site is added to the package at the child primary site.
• The child primary site is the nearest site to the secondary site.
  
  Note In this configuration, the child primary site is always the parent site of the secondary site.
• The child primary site already has a compressed copy of the package that is defined at the central site.
• You may see the following error message in the DISTMGR.log file:
  Package <packageName> requires a newer version (3) of source files and the new compressed files haven't arrived yet, current version is 1, skip E:\SMS\inboxes\distmgr.box\INCOMING\<packageName>.PKG SMS_DISTRIBUTION_MANAGER x/x/xxxx x:xx:xx xx 5764 (0x1684)

This problem occurs because of a timing issue. This timing issue causes an action instruction to be discarded.

The child primary site is flagged as the closest site to the secondary site. In this situation, the central site instructs the child primary site to forward the compressed package to the secondary site.

The package definitions and the action instructions are stored in an instruction file that has a .pkg extension. The instruction file includes a LastRefreshTime field that is used for synchronization. If a site receives a .pkg file, and if the LastRefreshTime field in the received .pkg file is older than the LastRefreshTime field in the last .pkg file that was processed, the site discards the received .pkg file.

The central site sends package definitions that are included in a .pkg file to the secondary site, because the package is created at the central site. The child primary site also sends action instructions in a .pkg file to the secondary site. In this situation, the following scenario may occur:

• The secondary site receives a .pkg file from the child primary site. The .pkg file includes an action instruction to copy the package contents to the distribution point of the secondary site. The secondary site waits for the compressed source to arrive from the child primary site.
• At the same time, the central site sends package information to the secondary site in a .pkg file that has a newer LastRefreshTime field. Then, the LastRefreshTime field on the secondary site is updated.

The .pkg file from the child primary site arrives at the secondary site before the .pkg file from the central site arrives. The secondary site waits for the compressed source to arrive from the child primary site. Then, the .pkg file at the secondary site is refreshed when the .pkg file from the central site arrives.

When the compressed source finally arrives from the child primary site, the LastRefreshTime field in the .pkg file is older than the LastRefreshTime field of the .pkg file that is already at the secondary site. Therefore, the secondary site discards the instruction to copy the package contents to the distribution point.

To resolve this problem, apply this hotfix to all SMS sites in the hierarchy.

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.

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, submit a request to 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

To apply this hotfix, you must have SMS 2003 Service Pack 2 or SMS 2003 Service Pack 3 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.

SMS 2003 with Service Pack 3, x86-based versions

SMS 2003 with Service Pack 2, x86-based versions

To work around this problem, use one of the following methods.

Method 1: Disable the "Send package from the nearest site in the hierarchy" option on the central site

Disable the Send package from the nearest site in the hierarchy option on the central site. To do this, follow these steps:

1. Click Start, point to Programs, point to Systems Management Server, and then click SMS Administrator Console.
2. In the console tree, expand Site Database, expand Site Hierarchy, expand the node that corresponds to the site, expand Site Settings, and then click Component Configuration.
3. In the details pane, right-click Software Distribution, and then click Properties.
4. On the Distribution Point tab, click to clear the Send package from the nearest site in the hierarchy check box, and then click OK.

Method 2: Add the distribution points of the secondary site to the package on the central site

You can keep the Send package from the nearest site in the hierarchy option enabled. However, you must make sure that the distribution points of the secondary site are added to the package on the central site instead of the package on the child primary site. To do this, follow these steps:

1. Click Start, point to Programs, point to Systems Management Server, and then click SMS Administrator Console.
2. In the console tree, expand Site Database, expand Packages, expand the node that corresponds to the package, right-click Distribution Points, point to New, and then click Distribution Points.
3. Follow the New Distribution Points Wizard to create add the distribution point.

Method 3: Update the affected distribution points from the child primary site

If this problem has already occurred, update (refresh) the affected distribution points from the child primary site. To do this, follow these steps:

1. Click Start, point to Programs, point to Systems Management Server, and then click SMS Administrator Console.
2. In the console tree, expand Site Database, expand Packages, expand the node that corresponds to the package, and then click Distribution Points.
3. In the details pane, right-click the distribution point, point to All Tasks, and then click Refresh Distribution Point.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

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