Frank Reynolds
New Member
- Messages
- 2
- Reaction score
- 0
- Points
- 1
Good Morning, I'm trying to push a driver pack which is part of a TS our remote site uses. When trying to push the driver pack I get the following errors out of the pkgxfermrg.log:
CContentDefinition::GetFileProperties for \\?\E:\SCCMContentLib\DataLib\EF5A1BE4-9400-4A95-9BD4-39DC4BCC37EC\iqvw64e.sys.INI failed. Error code = 0x80070003
CSendFileAction::SendFiles failed for path iqvw64e.sys. Error code = 0x80070003 SMS_PACKAGE_TRANSFER_MANAGER 3/27/2023 10:30:19 AM 13904 (0x3650)
CSendFileAction::SendContent failed; 0x80070003 SMS_PACKAGE_TRANSFER_MANAGER 3/27/2023 10:30:19 AM 13904 (0x3650)
Sending failed. Failure count = 2, Restart time = 3/27/2023 11:00:19 AM -0500 SMS_PACKAGE_TRANSFER_MANAGER 3/27/2023 10:30:19 AM 13904 (0x3650)
I can browse to the unc path from the site server and the file appears to be there. I have tried deleting the content from the remote DP, running content clean up, rebooting, and redistributing but I still encounter the same issue. I've also checked permissions for the directory and they seem like they're inline with the rest of our content. I applied the hotfix patch to 2211 the Friday before this became an issue too. Any insights would be wonderful.
CContentDefinition::GetFileProperties for \\?\E:\SCCMContentLib\DataLib\EF5A1BE4-9400-4A95-9BD4-39DC4BCC37EC\iqvw64e.sys.INI failed. Error code = 0x80070003
CSendFileAction::SendFiles failed for path iqvw64e.sys. Error code = 0x80070003 SMS_PACKAGE_TRANSFER_MANAGER 3/27/2023 10:30:19 AM 13904 (0x3650)
CSendFileAction::SendContent failed; 0x80070003 SMS_PACKAGE_TRANSFER_MANAGER 3/27/2023 10:30:19 AM 13904 (0x3650)
Sending failed. Failure count = 2, Restart time = 3/27/2023 11:00:19 AM -0500 SMS_PACKAGE_TRANSFER_MANAGER 3/27/2023 10:30:19 AM 13904 (0x3650)
I can browse to the unc path from the site server and the file appears to be there. I have tried deleting the content from the remote DP, running content clean up, rebooting, and redistributing but I still encounter the same issue. I've also checked permissions for the directory and they seem like they're inline with the rest of our content. I applied the hotfix patch to 2211 the Friday before this became an issue too. Any insights would be wonderful.
