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!

SOLVED ADR package failing to process on all DPs

Greg Shafer

Member
Messages
20
Solutions
1
Reaction score
1
Points
3
I have created new ADRs for Windows 7, 8.1 and 10 in my environment. While the 7 and 8.1 packages have distributed with no issues, the 10 is being a real pain and I am seeing the following error:

Distribution Manager failed to process package "PKG - Windows 10 Updates" (package ID = xxx00071).

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.

It certainly does not appear to be a space issue (>100GB on all DPs), and I think I can also safely say it isn't an issue of paths hitting a max length, as there are no issues with the 7 or 8.1 ADR packages. I have also rebooted the primary server on the off chance that a process had the package locked. Redistributing the package on the DPs also results in immediate failure.

distmgr.log
Code:
Snapshot processing content with ID 16791844 ...    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)
The source directory \\SCCMServer\Share$\Updates\Windows10\Express_e652c264-f6c7-423d-926f-509b03609132 doesn't exist or the SMS service cannot access it, Win32 last error = 2    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)
STATMSG: ID=2306 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCMServer.DOMAIN.COM SITE=AFS PID=10956 TID=23012 GMTDATE=Mon Sep 23 19:29:41.144 2019 ISTR0="\\SCCMServer\Share$\Updates\Windows10\Express_e652c264-f6c7-423d-926f-509b03609132" ISTR1="XXX00071" ISTR2="30" ISTR3="97" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="XXX00071"    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)
Failed to take snapshot of one or more contents in package XXX00071    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=XXX00071, Version=6, Status=2302    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCMServer.DOMAIN.COM SITE=AFS PID=10956 TID=23012 GMTDATE=Mon Sep 23 19:29:41.164 2019 ISTR0="PKG - Windows 10 Updates" ISTR1="XXX00071" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="XXX00071"    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)
Failed to process package XXX00071 after 3 retries, will retry 97 more times    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)
Exiting package processing thread for package XXX00071.    SMS_DISTRIBUTION_MANAGER    9/23/2019 2:29:41 PM    23012 (0x59E4)

While the "The source directory \\SCCMServer\Share$\Updates\Windows10\Express_e652c264-f6c7-423d-926f-509b03609132 doesn't exist or the SMS service cannot access it" stands out, and no there is no data there, I see the same behavior with the 7 and 8.1... but no error on these packages.

Thoughts as to what I should look at next?
 
Check the security & share permissions for the Windows 10 Package folder and compare it with Windows 7.

You can also try to create new Software Update package for Windows 10.
 
Unfortunately I think my only recourse is to recreate this ADR/package and hope for the best. Patch Tuesday is tomorrow night, so I should know in a couple days where I stand.
 
Greg, did you resolve your issue, i'm somewhat having the same. After i upgraded to 1902, it removed all my permissions. I'm giving local admin to the contentlib as we speak.
 

Forum statistics

Threads
7,168
Messages
27,979
Members
18,281
Latest member
kerber

Trending content

Back
Top