Package Replication Issues
Below post will guide you on how to troubleshoot issues that may arise during the replication of packages assigned to Distribution Points (DPs). If a package is targeted to a child site, the Package Distribution process includes replicating the package files to the child site, decompressing them, and copying them to the appropriate locations on the child site. The Distribution Manager manages the replication of package definition files and package source files to child sites. If there is a child site to replicate the package, the Distribution Manager creates the package replication file in the appropriate directory. If a compressed version of the package source files does not exist, the Distribution Manager compresses the package source directory into a temporary directory and stores the compressed copy of the package in the relevant directory.
If Distribution Manager must replicate a package to a child site, it creates a package replication file in Replmgr.box file. At the child site, it copies source files to its distribution points, updates the site database, and distributes objects to the appropriate inboxes.
When package replication fails, error messages appear on the Site Server Console. Alternatively, error messages may appear in the System Status → Package Status → Component Status tree for any of the components related to package distribution. In addition, error messages may also appear due to insufficient disk space. When package replication fails, you need to complete the following steps to implement the workaround procedure:
- Verify package status at central site
- Verify package status at destination servers
- Enforce package distribution
Verifying Package Status at Central Site
To verify the package status at the central site, perform the following steps:
1. In the SMS Administrator Console, navigate to Site Database ® System Status ® Package Status.
2. Select the required Distribution Point within the package.
3. If the package status is “Install Pending,” right-click the Distribution Point (within the package) and select Show All Messages to view the package details. Alternatively, you can open the distmgr.log file and view the package details. The “Install Pending” state denotes that the package has been running since a long time.
4. Open Site Status tree and select the required Distribution Point.
5. Open Component Status to verify the SMS_DISTRIBUTION_MANAGER status messages.
6. If the description of the status displays “SMS Distribution Manager failed to process package” message, verify the .PCK file size from SMSPKG directory and compare it with the destination .PCK file.
7. Open the distmgr.log file at the site server. If the description of the status displays “Failed to decompress package,” verify the free disk space availability on the source drive. If the package status displays the “Installed” message, it denotes that the package was successfully sent to the Distribution Point. To confirm, verify the package folder of the Distribution Point.
Package(s) in Hung State
- Check if there is enough disk space.
2. From CS Server, remove the Package from the Site Server it is failing on.
a. Open ConfigMgr Console
b. Locate the Package and Alt Click and select Manage Distribution Points
c. Click Next, Select Delete the package from Selected DP and click Next
d. Check the box next to the servers experiencing the issue and click next two times
e. Wait 15 minutes before proceeding to step 3
3.Update package source version in the CS ”Central server” and PS “Primary server” (Use PS that the child site server reports to) SCCM Databases. Do the following for both Databases.
a. Open SQL Server Management Studio.
b. Run a new query against the SMS_<SITE> database.
c. Run the following query to check the current SourceVersion of the stuck package:
select * from pkgstatus
where sitecode = '<SiteCode>' and id = '<ID>' and location like ‘%<site server name>%’
Replace <> items with the appropriate values as used in the prior query.
d. Run the following query to reset the SourceVersion of the stuck package to 0:update pkgstatus
set SourceVersion = '0'
where sitecode = '<SiteCode>' and id = '<ID>' and location like ‘%<site server name>%’
4. On the site server experiencing the issue, rename package.pck files.
a. Browse to SMSPKG location and search for <PACKAGEID>.PCK
i. Alt click and rename to <PACKAGEID>.PCK.OLD
b. Browse to DISTMGR.BOX and for <PACKAGEID>.PCK
i. Alt click and rename to <PACKAGEID>.PCK.OLD
c. Wait 15 minutes before proceeding to step 5
F 5. From CS Server, add the Package to the Site Server it is failing on.
a. Open ConfigMgr Console
b. Locate the Package and Alt Click and select Manage Distribution Points
c. Click Next, Select Add the package to Selected DP and click Next
d. Check the box next to the servers experiencing the issue and click next until the end.
3. 6.On site server, open DISTMGR.LOG and monitor for the entries pertaining to the specified package id.
