Additional System Center tools and components for managing infrastructure, applications, and services
Confirm the actual failure in PkgXferMgr.log and SMSDPProv.log before changing permissions, because the status message lists disk space and source access only as possible causes.
1. Identify where the transfer fails
- On the site server, filter PkgXferMgr.log for:
- Package ID
LG2008DE - The affected DP name
- Errors such as
0x80070070or “not enough space”
- Package ID
- On the affected DP, inspect SMSDPProv.log at the same timestamp.
- Also review DistMgr.log on the site server for the package-processing thread.
For a standard DP, PkgXferMgr first copies the files and then calls the DP’s WMI provider to add them to the content library. Consequently, SMSDPProv.log often contains the specific reason when PkgXferMgr.log reports only a generic WMI failure.^1^
Check free space on every drive containing:
-
SCCMContentLib - Any secondary
SCCMContentLib<DriveLetter>$library - The temporary staging share
SMS_DP$
Configuration Manager stops using a content-library drive when it reaches its configured drive space reserve, so a drive can be reported as low even though it is not completely full. Metadata remains on the primary drive; only the file library spans secondary drives.^2^
2. If the DP is genuinely low on space
Do not manually delete files from SCCMContentLib; altering that folder can corrupt packages or the content library.^2^
Use one of these supported options.
Remove orphaned DP content
ContentLibraryCleanup.exe removes content that is no longer associated with a Configuration Manager object. It requires an account equivalent to the Full Administrator security role and cannot clean the site server’s own content library.^3^
- On the site server, locate:
CD.Latest\SMSSETUP\TOOLS\ContentLibraryCleanup - Run a non-destructive what-if scan first:
ContentLibraryCleanup.exe /dp <DP-FQDN>
- Review the generated log. If the identified content is safe to remove, run:
ContentLibraryCleanup.exe /dp <DP-FQDN> /delete
The /delete operation is destructive, but it prompts before deleting each orphaned item. For a DP attached to a secondary site, also provide /ps <PrimarySiteFQDN> and /sc <SiteCode>.^3^
Move the existing library to a larger drive
If cleanup cannot provide sufficient capacity, add or identify an empty drive and run ContentLibraryTransfer.exe locally on the DP:
ContentLibraryTransfer.exe -SourceDrive E -TargetDrive G
Run it with local administrative permissions. During the transfer:
- Prevent clients from accessing content on that DP.
- Do not distribute new content to the DP.
- Schedule a maintenance window.
Concurrent reads or writes can leave the destination library incomplete or unusable.^4^
Drive priority and reserve settings are selected when installing a new DP and cannot be changed afterward through the existing DP’s properties. The transfer tool is the supported method for moving an established DP content library.^5^
3. Retry and verify
After restoring adequate capacity:
- In the Configuration Manager console, select package
LG2008DE. - Validate its content on the affected DP.
- Monitor PkgXferMgr.log and SMSDPProv.log for successful transfer and library insertion.
- If validation finds no mismatch but the update remains failed, redistribute the package to that DP. Microsoft lists redistribution as the last content-library recovery action.^2^
If the logs instead show source-path access errors, address that branch rather than changing DP storage: grant the site server computer account read access to the package source and verify that the source remains reachable. If they show file locks, check antivirus activity against both the content library and SMS_DP$; Microsoft recommends excluding those locations from automatic antivirus scanning.^2^
References