It states that the possible causes could be one of the following:

• Site server does not have sufficient rights to the source directory. 
• There is not enough disk space available on the distribution point.

I am quite certain it is not the second option, but it could be the first. 

How do I verify the permissions and what are the permissions supposed to be?

I have searched all over online and I haven't found anything substantial that can shed any light on this for me. 

The smsdpprov.log shows the following errors:

[A0C][Wed 07/15/2015 18:20:18]:Hash mismatch Original : 61BC5FD2808CEE31E96F48ECAE572BCE6529D960EE2CA9EA79E6CAC1F6C691F9 Downloaded : F138AAADBB195D72B161D79D3B6E077035A9105EA3620FB789AB8B5B75214A84
[A0C][Wed 07/15/2015 18:20:18]:Failed to add file 'FEPInstall.exe' to content library. Error code: 0X80091007
[A0C][Wed 07/15/2015 18:20:18]:CreateFileW failed for D:\SMS_DP$\61BC5FD2808CEE31E96F48ECAE572BCE6529D960EE2CA9EA79E6CAC1F6C691F9-45af4a47-8560-4b28-bcfb-888a0ea28c52.PRI00024.temp
[A0C][Wed 07/15/2015 18:20:18]:FileOpen failed; 0x80070002
[A0C][Wed 07/15/2015 18:20:18]:FileGetSize failed; 0x80070002
[A0C][Wed 07/15/2015 18:20:18]:CFileLibrary::AddFile failed; 0x80070002
[A0C][Wed 07/15/2015 18:20:18]:CContentDefinition::AddFile failed; 0x80070002
[A0C][Wed 07/15/2015 18:20:18]:Failed to add file 'FEPInstall.exe' to content library. Error code: 0X80070002

I know there is an issue with the SCEP installation executable (FEPInstall.exe) showing an error of 0x80070002 which means that "The system cannot find the file specified", but I have no clue how to resolve this. 

BTW, nothing is showing up in the distmgr.log with errors. 

Could this be caused by antivirus? I am running System Center Endpoint Protection. How could I test to see if SCEP is the culprit?

Thank you all very much for your help. 

• Edited by I AM Sir Ask Alot 14 hours 26 minutes ago

Definitely verify that any anti-virus software excludes the ConfigMgr directories on the distribution point.  Also, make sure the site server computer account is part of the local administrator group on the DP.

Jeff

Thanks Shawn

I ran that tool and it shows that TCP ports 135 and 445 are listening, but UDP port 135 is not. 

Could this be the problem you think?

Thanks

The site server is a member of the local admins, if it wasn't, the DP folder structure would not be able to be created on the drive and I made sure of that. You saw my earlier posting where I stated that I forgot to add the site server to the local admins group on a new DP I just deployed, but I caught that today and fixed it. 

I just NOW added the necessary exclusions to my SCEP antimalware policy for my SCCM servers and I just initiated a a machine policy retrieval and evaluation cycle. 

I then updated the packages on the DPs and it is still giving me this error. 

• Edited by I AM Sir Ask Alot Thursday, July 16, 2015 5:37 AM

Hi,

Since you have went through all the basic checks, just a wild guess, could it be firewall appliances or Windows firewall that is blocking some ports like 135, 445 or dynamic port range?

Last time we have DP setup issue, the folder is there but the DP just refuse to work, the log file was not helping, once we add the dynamic port range, everything started working.

You might want to give it a try?

Thank you.

Shawn Yuen

• Edited by SY72 Thursday, July 16, 2015 6:08 AM Forget to add in port number 135

That is a very good question. I know that we are using some packetshaper appliance by Blue Coat. I believe that may be the culprit here, but that does not fall within my purview of responsibilities as an SCCM guy. I would need to get in touch with the individual that is responsible for managing that. 

I can configure Firewall policies from the SCCM 2012 R2 console, right?

Maybe I can do that and see if that could be the issue. 

• Edited by I AM Sir Ask Alot Thursday, July 16, 2015 7:14 AM

You could do a simple port query from your DP to your SCCM server, for the dynamic ports, I believe only your Network colleagues will be able to see it from their appliance.

Port query would help you to justify to your Network colleagues to take a look at their firewall appliances.

Port query tool I always use

Thank you.

Shawn Yuen

Looking at this closer it is only two packages that fail to update, so the port issue must not be it. 

I am at a loss here. 

How do I go about clearing this up?

Will running this script by David O'Brien work?

http://www.david-obrien.net/2013/11/redistribute-failed-packages-configmgr-dps/

I have these remote DPs setup for prestage content and I CANNOT these packages cross these ridiculously SLOW WAN links, because it will severely interrupt productivity at these remote sites. 

Thanks

• Edited by I AM Sir Ask Alot 12 hours 55 minutes ago