PENDING Recurring issue with missing updates in deployment packages

[LeeBold]

Everytime I deploy a group of updates or when my ADR deploys updates, one update will go missing. It's been happening for months and happens with every update package I deploy.

The error...

The source directory "\\rs-sccm01\Sources\Updates\2018 Q3 Updates\1962c598-59ae-448d-8b8d-c2b05fe974aa" for package "KHQ00158" does not exist. The operating system reported error 2: The system cannot find the file specified.

Solution: Make sure you have specified a valid package source directory on the Data Source tab in the Package Properties dialog box in the Configuration Manager Console. If you specify a local path, it must be a local path on the site server. If you specify a path on a network drive, verify that the path exists and that the path is typed correctly.

I have a unique folder for each update package. No other deployment is using \\rs-sccm01\Sources\Updates\2018 Q3 Updates\ but for some reason SCCM is looking for an update in a folder named 1962c598-59ae-448d-8b8d-c2b05fe974aa but that folder does not exist. Last week, same issue, different folder name that does not exist.

I've attached a screenshot of my Distribution Manager component error log. It looks like this all the time. My packages seem to deploy and work fine. Clients get updates so the package does deploy but is always missing one (sometimes two) updates.

I did find a SQL query that allows me to figure out which specific update is missing. I can manually create the folder and put the update in there then the error goes away. But I don't want to do this every time I deploy a bunch of updates.

Does anyone know what is causing this? Or has anyone else had this issue? I've created a post on Microsoft TechNet but they were not helpful at all :-(

I'm on SCCM Version 1806. Console version 5.1806.1074.1507. Site version 5.0.8692.1000

 

[LeeBold]

No one at all had this issue?

 

[LeeBold]

No one at all had this issue?

I'll take that as a no. Thanks for all the help

 

[WasifAQ]

I am not using ADR but I am getting the same error with distribution of updates package. Were you able to find a solution to this?

 

[michaelj]

I also have the same issue. Anyone have an anwser on this topic


Any Idea? Using 2012R2 and CCM 2002. Thank you

 

[Mark Phillips]

Not sure it is the exact same problem, but I recently resolved an issue where I had a \\SERVERNAME\SHARENAME\UPDATES
And would always create a new sub-folder for a "Deployment Package" in there as the source folder. But someone else who I am training created a Deployment Package and used the parent, \\SERVERNAME\SHARENAME\UPDATES
as the source folder for that "test" Deployment Package. When SCCM gets around to maintaining the object they created, it cleans out any content not currently relevant to that "test" Deployment Package. So you might consider reviewing the Source Folders for all the other Deployment Packages.

 

[JamesVreeling]

I'm currently having the same issue. Recreated the Package manually, then once the ADR ran again to put updates in here, its having the same problem again.

Yet looking at the Unique Update ID's that I have that are in the apparently in the package, I can't see the ID there.

 

[Gigaminds]

Microsoft's official solution for this problem is to recreate the whole Deployment package.
But i guess that it depends on the situation and what has been done to lose these missing folders .. in my case it always happened while multiple admins are logged onto the server doing different things and one of them or myself was running the (Remove-SCCMExpiredSupersededContent_1.0.ps1) script .. rerunning it again after a restart sometimes just fixes things on its own but in case it didn't help (run it a 3rd time to make sure) then i have managed to fix it in several of my Primary site servers and their DPs by a long process of redownloading the packages again to a new Package first then manually look for the missing folders and copy them to the main package one by one until the redistribution of the package succeeds on the Primary site server then it will succeed on the DPs later on too.
Now if it didn't have all the missing folders still then i resort to following Microsoft's official resolution on the matter and create a brand new package by a different name first connected to a brand new Shared folder as well then a brand new ADR and run it so that it starts downloading until it finishes then disable the old ADR and let clients get their updates from the new one instead then after a month or 2 .. then i remove old package folder to free up space (mine is almost always over 1TB).