locked
Package distribution frequently failing with Failed to get object class and CSendFileAction::AddFile failed; 0x800706ba RRS feed

  • Question

  • Dear Experts,

    Frequently I see packages that are being transferred over WAN links failing with the below posted error.

    We're running SCCM 2012 SP1, the DP's are rate limited and firewalled.

    Some applications end up on the DP's fine (even OS images), some don't. When they don't, the issue is non-recoverable, even if I retry it 100 times the error will remain the same while other applications do distribute properly. This seems like there can't be a firewall issue at play. Logs on the DP's do not show any errors.

    Here is the PkgXferMgr.log

    Attempt to write 750652 bytes to \\SERVER\SMS_DP$\Content_0a017ff5-3a9b-4794-ab57-e4e50ba2db79.1-F6BCF13B583E95DC14FBA81B712675EAD0A2A8D25D1C5127B3E79519897D1337 at position 394372096 SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:53:42 AM 7476 (0x1D34) Wrote 750652 bytes to \\SERVER\SMS_DP$\Content_0a017ff5-3a9b-4794-ab57-e4e50ba2db79.1-F6BCF13B583E95DC14FBA81B712675EAD0A2A8D25D1C5127B3E79519897D1337 at position 394372096 SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:53:44 AM 7476 (0x1D34) Sending completed [E:\SCCMContentLib\FileLib\F6BC\F6BCF13B583E95DC14FBA81B712675EAD0A2A8D25D1C5127B3E79519897D1337] SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:53:44 AM 7476 (0x1D34) Failed to get object class SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:54:05 AM 7476 (0x1D34) ExecStaticMethod failed (800706ba) SMS_DistributionPoint, AddFile SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:54:05 AM 7476 (0x1D34) CSendFileAction::AddFile failed; 0x800706ba SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:54:05 AM 7476 (0x1D34) Deleting remote file \\SERVER\SMS_DP$\Content_0a017ff5-3a9b-4794-ab57-e4e50ba2db79.1-F6BCF13B583E95DC14FBA81B712675EAD0A2A8D25D1C5127B3E79519897D1337 SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:54:06 AM 7476 (0x1D34) CSendFileAction::SendFiles failed; 0x800706ba SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:54:06 AM 7476 (0x1D34) CSendFileAction::SendFiles failed; 0x800706ba SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:54:06 AM 7476 (0x1D34) Notifying pkgXferJobMgr SMS_PACKAGE_TRANSFER_MANAGER 6/4/2014 11:54:06 AM 7476 (0x1D34)

    Wednesday, June 4, 2014 10:03 AM

Answers

  • 0x800706ba = "The RPC server is unavailable."

    This is often associated with some sort of network connectivity issue but is very hard to track down without watching the traffic because there is no way to know why traffic didn't make it.

    Generally, it is also associated with WMI communication so it's possible that WMI is having issues or is being blocked on the destination system.

    If this is happening sporadically on the same DP for the same content but works for other content, that would indicate to me that some type of network filter or security mechanism is in place that has for some reason decided that that content should not be allowed. This is pure speculation though.

    Do you happen to have a WAN accelerator in place or something else that is supposed to help, scan, or filter traffic? If so, this is where you should concentrate your investigation and exclude ConfigMgr traffic from interference.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Jos Lieben Thursday, June 12, 2014 12:41 PM
    Wednesday, June 4, 2014 2:33 PM

All replies

  • 0x800706ba = "The RPC server is unavailable."

    This is often associated with some sort of network connectivity issue but is very hard to track down without watching the traffic because there is no way to know why traffic didn't make it.

    Generally, it is also associated with WMI communication so it's possible that WMI is having issues or is being blocked on the destination system.

    If this is happening sporadically on the same DP for the same content but works for other content, that would indicate to me that some type of network filter or security mechanism is in place that has for some reason decided that that content should not be allowed. This is pure speculation though.

    Do you happen to have a WAN accelerator in place or something else that is supposed to help, scan, or filter traffic? If so, this is where you should concentrate your investigation and exclude ConfigMgr traffic from interference.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Jos Lieben Thursday, June 12, 2014 12:41 PM
    Wednesday, June 4, 2014 2:33 PM
  • Thanks Jason,

    It ended up being a misconfiguration by the network team. They opened up 135 for RPC, and SOME of the dynamic ports. Because they didn't open up the full range, the issue was so intermittent.

    Thanks for the quick reply, and hope someone else who googles the error can use this thread.

    Thursday, June 12, 2014 12:41 PM