Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING Disributing content is failing on some updates packages

  • Thread starter Thread starter lalajee2018
  • Start date Start date
  • Replies Replies 8
  • Views Views 20K

lalajee2018

Well-Known Member
Messages
143
Reaction score
6
Points
18
Hi,

I keep getting this error
Distribution Manager failed to access the source directory "\\DFSR\sccm_source\Updates\Office 365 Updates\baed5b06-3040-45ef-bb45-7d367a8189ae" for content "baed5b06-3040-45ef-bb45-7d367a8189ae" (content ID = baed5b06-3040-45ef-bb45-7d367a8189ae).

Possible cause: Distribution Manager 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 site server.
Solution: Verify that there is enough free disk space available on the site server.

Retry Interval is 30 minutes, number of retries left is 99.


----------------------------------------
Distribution Manager failed to process package "ADR (New) - Office 365 Updates" (package ID = xxx001B9).

Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.

Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.

Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.

Possible cause: The package source directory contains files that might be in use by an active process.
Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.


-------------------------------------------------

I have check all of the DP and can confirm that SCCM Server is part of local admin group and DP have lots of free space.
Does anyone know how to fix this.
I been fixing this by recreated the packages again but now its become like this eveytime they is update.

Can someone please help on this.
 
I am not sure why you want to do a site reset for this before you troubleshoot this issue. Do you see any error code in dismgr.log file ?.
 
Thank you for reply. I saw same error on other forum so this is why i ask if this can help with this problem.

I also found out that we dont validate any contents. the option is disable at the moment.

Capture.PNG
 
If you have not selected content validation it is ok. But the issue with distributing a package to DP.
 
Hi ,i have created a pull dp and content distribution is failing with the error

Failed to update package Package Transfer Manager failed to update the package "QPSXXXXX", Version 4 on distribution point RTLXXXXXXX.FMR.COM. 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. Error QPSXXXXX.
Before I enable the server as pull dp,content distributed successfully as a remote dp .It failed only after enabling it as pull dp
 
It looks like you have permission issues. Make sure that your DP have all of the accounts in local admin groups and make sure the primary site server is part of the local admin group on DP.


If you still have issue raises new post
 

Forum statistics

Threads
7,170
Messages
27,985
Members
18,289
Latest member
CharmedToast

Trending content

Back
Top