Last week I was working on operating system deployment and I came across a weird issue SCCM DP Cannot delete remote file Win32 Error 5.
On one of the client machines, the TS failed due to content not available on the distribution point. The DP was set up recently and was healthy.
The task sequence was working fine on other sites in the setup. The Win32 Error 5 came up for one particular site. So, I re-distributed the content to the distribution point.
The content distribution failed for the site DP and when I checked the content status of that package I saw the below error.
Package Transfer Manager failed to update the package “PKGID”, Version 13 on distribution point SERVERNAME. Review PkgXferMgr.log for more information about this failure.
Possible cause: Site server does not have sufficient rights to the source directory.
Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.
Possible cause: There is not enough disk space available on the distribution point.
Solution: Verify that there is enough free disk space available on the distribution point.
I had verified that it was not a disk space issue nor permission issue. So, I went ahead and reviewed the PkgXferMgr.log file.
Read: How to use SCCM Error Lookup Tools
When I opened the PkgXferMgr.log file I found that the content was not being distributed. There were multiple errors in the log file. One thing was clear that the package was not copied over to the distribution point.
Cannot create/open the remote file SERVER_NAMESMS_DP$3B08535B4ADD194F5661E1131C8E81AF373CA-P010020D.18.temp, Win32 error 5 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 05:46:42 15744 (0x3D80)
CSendFileAction::SendFiles failed 0x80004005 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 05:46:42 15744 (0x3D80)
CSendFileAction::SendFiles failed 0x80004005 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 05:46:42 15744 (0x3D80)
CSendFileAction::SendContent failed 0x80004005 SMS_PACKAGE_TRANSFER_MANAGER 10/06/2016 05:46:42 15744 (0x3D80)
SCCM DP Cannot delete remote file Win32 Error 5
Let’s look at the solutions for Cannot delete remote file Win32 error 5.
- Solution 1 – If you see Win32 Error 5 on SCCM DP, the first step is to reboot the DP. Restarting the DP in most cases resolves the Win32 Error 5. If the file is locked or in use by a DP, rebooting DP shall help you.
- Solution 2 – If rebooting the distribution point server doesn’t help, check if there is any security software like antivirus software that is locking the file. Most of the Antivirus software are configured to scan all the file types. In my case, on the distribution point, Sophos antivirus was locking the temp file and was not allowing the content to be added. We had configured the exclusions in the Sophos to allow some file types but on this server the exclusion policy was not applied. After applying the correct policy the missing content was distributed to the DP successfully. The OSD process went smoothly after this.
Still Need Help?
If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.