I have an interesting issue with distribution point updating a deployment package.  I have ADRs that run for AV definition updates.  The rules run, add to an existing deployment package and update distribution points.  This works great for about a month at a time.  After that, I have to delete the package and recreate it.  I can try to update DPs, use Powershell to update, remove all DPs and add them again as if it were a new distribution, but none of those work.  Does anyone else experience this or have seen it in the past?  The error I'm getting is the 80070003 in Package Transfer Manager.  Note, this happens every 4-5 weeks and I've experienced it now for the 3rd time.  Thanks i

0x80070003 = "The system cannot find the path specified."

Make sure your deployment package where you download definitions is configured properly and accessible.
Is the source folder of the package on shared storage or saved locally on SCCM server?
What release of CM12 are you on?

I would also recommend looking at A/V exclusions for SCCM server:

http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx

http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012

This package replicates properly for a month on end so I know the permissions are fine.  The source folder is on the SCCM server.  I'm running SCCM 2012 SP1 UR3.  This happened without UR3 as well.  I've removed AV from those servers as a test and the same problem happens.  All of the servers are a local admin of each other.  It seems that once a package is updated X number of times, it stops.  No other packages, stored in the same structure, have ever had this problem. 

Hi,

Have you checked ruleengine.log on the site server?

Please make sure definition updates have been downloaded.

Best Regards,

Joyce Li 

Hey Joyce,

The rulengine log is clean.  There have been no failures in some time.  One thing I tried was just leaving it in failed status to see if it would heal itself.  After a couple of days, the package transferred to all distros successfully.  I did nothing different and the ADRs are running 3 times per day.  I have verified that all files were downloaded and in the package.  It really doesn't make sense how it would heal itself in a couple of days, but it does.  Hopefully R2 will resolve it.

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.