Hi All, i just wanted to ask if anyone else had experienced this issue yet?
We have ~200 Pull DP's and for some time have been having issues with OSD Task Sequences randomly failing with the error 80070002.
More specifically:
Invalid path. \\server\share format needed .. Failed to find an available source location
Our Task sequence is configured to access content directly from the DP. We checked the PackageShare$ and validation state and both were fine. Next we inspected WMI (root\sccmdp:SMS_PackagesInContLib) and this was fine as well. Until today, we had been redistributing the failing package to remediate, but this is very time consuming with some of the large WIMs and Driver Packages, especially over some very slow WAN links.
Today I decided to explore this a little further by examining the Database..This led me to the table ContentDPMap and the two columns in particular 'URL' and 'URLSubPath'.
I noticed that the packages we were having issues with had a URL of the ServerName in UNC format, and a URLSubPath of just '\'. Other packages had a fully qualified UNC path to the package for URL and a full sub path for URLSubPath.
When we queried the DB further, we revealed 1190 packages to be in this state (for packages supposed to be in the share) out of a total of 42,000 records.
The query we used for this was:
select ContentID,ServerName,AccessType,URL,URLSubPath,URLProtocol,vpkg.Name from ContentDPMap as cdpm join v_Package as vpkg on vpkg.PackageID = cdpm.ContentID where cdpm.AccessType = 2 --UNCProtocol and cdpm.URLSubPath not like '%SMS%' --Packages with issues only have a '\' and vpkg.PkgFlags = (vpkg.PkgFlags | 0x80) --Limit to only show packages with the 'Copy To Package Share' flag set
Also of note, when a package is marked with a State = 2 the values for URL/URLSubPath are NULL. (State =2 is In Progress).
So my question:
Firstly, has anyone else encountered this?
Secondly - how should I fix it - we tested in our DEV and found that updating the entries remediates the issue with Clients not being able to locate content, but realise this is is an unsupported method.
I will also log this on Connect as it appears to me to be a Bug.
Cheers,
David