I have searched a lot for an answer, maybe my issue is unique.  We have recently (within the past 6 months) migrated from 2007 to 2012.  I have worked through a lot of changing Secondary sites to Distribution Points.  Most of these have had only the occational stuck package. 

I have two DPs - both are 2008 R2 servers that are setup similarly, they both have the DP on D$ and have a Hyper - V Application server on them. They have not been able to successfully process content for a week or more.  I have tried redistribute, remove and redistribute, prestage and redistribute  and remove, prestage then install.  I have tried to install content that was not previously pushed, all fail. 

There is no activity since the last "successful" in the smsdpprov.log.  I do not see any temp files in the SMS_DP$ folder while the packages are being copied over (set DP to pulse to verify file transfering). 

The error I see in the PkgXferMgr.log is

ExecStaticMethod failed (80041013) SMS_DistributionPoint, AddFile

CSendFileAction::AddFile failed; 0x80041013

CSendFileAction::SendFiles failed; 0x80041013

CSendFileAction::SendFiles failed; 0x80041013

I have disabled the firewall to check for restricting RPC traffic.  I have followed the instructions on the article Getting a CMD prompt as SYSTEM in Windows Vista and Windows Server 2008  to verify WMI connection for the SYSTEM account. 

I am running out of things to try and logs to check.  Any suggestions?

0x80041013 = Provider load failure

Source: Windows Management (WMI)

i would look into permission issue or something wrong with the WMI.

Did you ever change the location of the DP from F: to D: ?

https://social.technet.microsoft.com/Forums/en-US/0b14870a-0f6a-4445-b06e-3a565011ceb4/package-distribution-not-working-suddenly?forum=configmanagergeneral

What does smsdpprov.log on the DP tell?

Fredrick,

The location of the DP has always been D:, no change needed.  The DP did work for a while, then stopped.  I actually do believe it is an access issue, just not sure how to proceed to troubleshoot permissions.  I do not have the rights to change/refresh rights for accounts.  Would like to have something to go to security with to validate my request.

Torsten,

The amsdpprov.log does not update.  The last time it did was the last successful distribution.

well to test the right the first thing i would do is start a CMD using the account that is being use to gain access to the DOP (most of the time it's the computer account of the primary site).

you can use psexec to start a cmd as system account. From this point try to connect to the WMI and the server. 

Did you look at the post i link earlier the person said something about being access right.

Ok, I went to the primary server and used the PSEXEC -i -s -d cmd so I could wbemtest to the DP and verify access to the WMI namespaces, I was able to get there without any problems and I could modify some atributes, others were read only.

• Edited by Drkman47 10 hours 53 minutes ago

Confirm the following details for each DP

• The ConfigMgr site server has local admin rights on each DP server
• That IIS is configured on each DP server, that the default web site is started and that the DP virtual directories exist beneath the default web site
• Check the smsdpprov.log for any errors during the installation

The DP provider cannot be loaded by WMI. Normally, this is due to missing binaries, mismatch in binaries or corrupted binaries. It is also possible that the DP provider is not registered or its registration in WMI has been corrupted.

I think you would have to re-install the DP to recover from this situation.