when trying to update a package in SCCM, one of the DP is getting an error stating the low on disk space

Moua, Kongmeng 0 Reputation points
2026-11-17T18:41:00.7333333+00:00

Package Transfer Manager failed to update the package "LG2008DE", Version 20 on distribution point SCCM-DP-DS1.LHA.ORG. Review PkgXferMgr.log for more information about this failure.

 

Possible cause: Site server does not have sufficient rights to the source directory.

Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.

 

Possible cause: There is not enough disk space available on the distribution point.

Solution: Verify that there is enough free disk space available on the distribution point.

Microsoft System Center | Other
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-17T18:41:52.26+00:00

    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

    1. On the site server, filter PkgXferMgr.log for:
      • Package ID LG2008DE
      • The affected DP name
      • Errors such as 0x80070070 or “not enough space”
    2. On the affected DP, inspect SMSDPProv.log at the same timestamp.
    3. 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^

    1. On the site server, locate: CD.Latest\SMSSETUP\TOOLS\ContentLibraryCleanup
    2. Run a non-destructive what-if scan first:
    ContentLibraryCleanup.exe /dp <DP-FQDN>
    
    1. 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:

    1. In the Configuration Manager console, select package LG2008DE.
    2. Validate its content on the affected DP.
    3. Monitor PkgXferMgr.log and SMSDPProv.log for successful transfer and library insertion.
    4. 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

    1. Troubleshoot content distribution
    2. The content library in Configuration Manager
    3. Content library cleanup tool
    4. Content Library Transfer tool
    5. Install and configure distribution points in Configuration Manager
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.