Package content is not distributed in System Center 2012 Configuration Manager


In System Center 2012 Configuration Manager, you may experience the following symptoms, which are related to content distribution:
  • Content distribution fails when many distribution points (typically more than 75) are updated at the same time. When this occurs, the HTTPUrl value for Package Status will be blank, and the locationservices.log file on target clients will contain entries that resemble the following:
    Calling back with empty distribution points list.
  • The Distribution Manager component stalls when it updates multiple distribution points. This occurs when there's a problem with IIS communication on a single remote distribution point. When that problem occurs, communication with other distribution points stalls. Additionally, messages that resemble the following will be recorded approximately every two minutes in the distmgr.log on the site server:
    There are still 1 DP threads active for package CAS00101, waiting for them to complete.
    There are still 1 DP threads active for package CAS00102, waiting for them to complete.
    There are still 1 DP threads active for package CAS00103, waiting for them to complete.
    There are still 2 DP threads active for package CAS00104, waiting for them to complete.
  • The StoredPkgVersion value is not restored when a secondary site is recovered from the console. This triggers later failures in content validation, and the distmgr.log file on the secondary site contains entries that resemble the following, which also indicate that the StoredPkgVersion value in the database has been reset to 0:
    StoredPkgVersion (0) of package Package_ID. StoredPkgVersion in database is 0.

    Note Installing this hotfix will not restore that value for a previously recovered secondary site. It will only prevent the issue after future recoveries.


Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. 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 website: 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.


To apply this hotfix, you must have Cumulative Update 3 for System Center 2012 Configuration Manager Service Pack 2 and System Center 2012 R2 Configuration Manager Service Pack 1.

Restart information

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

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information


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


Learn about the terminology that Microsoft uses to describe software updates.

ID do Artigo: 3174047 - Última Revisão: 25 de jul de 2016 - Revisão: 1