I came in this morning to find a package that was distributed overnight had failed to distribute to one distribution point. Checking the PkgXferMgr.log, I saw:
ExecStaticMethod failed (80041001) SMS_DistributionPoint, FinalizeContent
CSendFileAction::SendContent failed; 0x80041001
Checking the log file smsdpprov.log on the distribution point, it showed 0x80070002 (ERROR_FILE_NOT_FOUND):
[4A0][Wed 03/13/2024 19:06:17]:CreateFileW failed for K:\SCCMContentLib\FileLib\0182\01826CBC5986BB6108A23578DD01A63E2E99C7ADFC64DD5CB367062AA192B937.SIG
[4A0][Wed 03/13/2024 19:06:17]:FileOpen failed; 0x80070002
[4A0][Wed 03/13/2024 19:06:17]:FileAddToTar failed; 0x80070002
[4A0][Wed 03/13/2024 19:06:17]:CContentDefinition::PackSignatures failed; 0x80070002
[4A0][Wed 03/13/2024 19:06:17]:CContentDefinition::CreatePackedSignature failed; 0x80070002
[4A0][Wed 03/13/2024 19:06:17]:Failed to create packed signatures for content '116B2AD4-07E0-4E66-BA32-F996AAA6B7F7' for package 'XYZ02546'. Error code: 0X80070002
I looked at the folder K:\SCCMContentLib\FileLib\0182 and the SIG file was indeed missing:
I tried a few things – I verified the site server could write to the folder, restarted the copy job, removed and readded the package, restarting the winmgmt service on the DP, all to no avail.
There were no errors in the event log on the DP, so I decided to delete the 0182 folder and try the distribution again:
Once I restarted the distribution, it completed without errors:
I validated the content for good measure, and it came back successful:
Problem solved!