locked
SCCM 2012: failed to connect to distribution point RRS feed

  • Question

  • Hi folks,

    I have an intermittent issue and can't figure out the reason so far.

    I have a primary server and multiple distribution points. The primary does not have a DP configured. When I deploy a new distribution point, I have the following messages:

    Distribution Manager failed to connect to the distribution point. Check your network and firewall settings.

    and

    Distribution Manager failed to find or create the defined share or volume on distribution point.

    DistMgr.log shows the following:

    CWmi::Connect() failed to connect to \\AMB-SCCM-E.domain.name\root\CIMv2. Error = 0x800706BA

    STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBD-SCCM-E.domain.name SITE=IDC PID=2120 TID=3376 GMTDATE=do jun 28 07:24:17.463 2012 ISTR0="["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\"

    ERROR DPConnection::ConnectWMI() - Failed to connect to  AMB-SCCM-E.domain.name. error = 0x800706ba

    Failed to find a valid drive on the distribution point ["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\

    Cannot find or create the package share.

    Error occurred. Performing error cleanup prior to returning.

    However, after a while (couple of hours), it looks like everything is distributed on the DP. But this message keeps on coming back during the course of the day and every time a new DP is deployed.

    I checked permissions, IIS, WMI, but I can't find out the cause of this behavior. I have events about WMI (id 5605) but I can connect to the WMI workspace (root\MicrosoftIISv2) with no issues.

    Can anyone shed some light on this please? It would be greatly appreciated.

    Cheers,

    Safdar.

    Thursday, June 28, 2012 7:53 AM

All replies

  • 0x800706BA = The RPC server is unavailable, so it's most likely not related to ConfigMgr, but firewall, network etc

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Ron Santotomas Wednesday, June 15, 2016 9:48 PM
    Thursday, June 28, 2012 8:00 AM
  • Hi Torsten,

    I've disabled Windows Firewall and both the primary and the DP are sitting in the same subnet. No other firewall in between.

    I can telnet ports and while doing a netstat -ano I can see that connections are established.

    Cheers,

    Safdar.



    Thursday, June 28, 2012 8:33 AM
  • Other suggestions to help out maybe?

    Thanks,

    Safdar.

    Thursday, June 28, 2012 9:03 AM
  • Network layer issues like this are tricky to troubleshoot because there is no way for the application to know why its traffic did not go through and unless you replicate exactly what the app does, your manual testing may or may not be conclusive. The error message in this case is a clear connectivity issue thus Telneting on random ports and checking for connections on other ports is pretty meaningless as the issue may only be on a specific port (or set of ports).

    Have you tried to connect to WMI on the target DP from the primary site server?  


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    • Proposed as answer by Raman Katoch Monday, October 26, 2015 11:26 AM
    Monday, July 2, 2012 2:57 AM
  • I've been running into this same issue when trying to install a remote DP.  The remote DP was previously used as a DP for our SCCM 2007 infrastructure so connections from the Primary site to the remote site have always worked fine.

    What i had to do to was to select an admin account to install the site system role rather than the Site Server computer account even though the primary site server is a local admin in the remote dp system.


    • Proposed as answer by Dan_754 Saturday, December 1, 2012 12:06 AM
    Thursday, July 12, 2012 6:26 PM
  • Is this the name of the DP or the Primary? AMB-SCCM-E.domain.name


    Rob Marshall | UK | My Blog | WMUG

    Friday, December 21, 2012 9:32 PM
  • having the same exact issue here.  No firewalls in the way... worked as 2007 DPs.  i'm stuck.
    Wednesday, April 24, 2013 7:31 PM
  • Same issue as in exact same error log message?

    Jason | http://blog.configmgrftw.com

    Wednesday, April 24, 2013 9:21 PM
  • I had the same issue. For me, uninstalling and reinstalling the DP fixed that issue.

    Cheers

    Sebastian


    Sebastian Bammer

    Wednesday, July 24, 2013 12:59 PM
  • I had the same issue. For me, uninstalling and reinstalling the DP fixed that issue.

    Cheers

    Sebastian


    Sebastian Bammer

    But unfortunately not for all DPs, there's still one out that has this issue :(


    Sebastian Bammer

    Wednesday, July 24, 2013 6:37 PM
  • I Had the same issue with 6 DP's... is uninstalling and reinstalling only the fix ??? it is very difficult to replicate all packages again if uninstall and reinstall ....  Please advice.....
    Tuesday, August 20, 2013 4:12 PM
  • Hi Jason,

    Please let me know steps to connect to WMI on the target DP from the primary site server?

    I am having a same problem. Even re-installing DP in my environment is not solving above issue. 

    Tuesday, January 28, 2014 7:49 AM
  • You can use wbemtest.exe to connect to WMI on (remote) machines.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, January 28, 2014 8:09 AM
  • Hi Try this

    In my case, It has worked.

    While installing and configuring DP, Enable "Install and configure IIS if required by configuration manger" option.

    This error will go and check the status in Distribution status (In Monitoring)


    Thanks, Prabha G

    Monday, February 3, 2014 12:13 PM
  • I fixed this by doing the following two things

    1. Enable Windows Authentication in IIS

    2. Installed IIS 6 WMI Compatability

    Hopefully this helps someone else.

    • Proposed as answer by Aayush Bhatt Thursday, September 18, 2014 6:55 AM
    Friday, May 30, 2014 1:52 AM
  • Works like a charm! Thanks Man!
    • Proposed as answer by Martin Little Monday, October 31, 2016 2:31 PM
    • Unproposed as answer by Martin Little Monday, October 31, 2016 2:31 PM
    Tuesday, August 26, 2014 11:12 AM
  • Superb... thanks for the insight.
    Thursday, September 18, 2014 6:57 AM
  • Thanks Nick. This also worked for me.

    A.P>

    Wednesday, October 1, 2014 9:58 PM
  • This worked like a champ.  If the need for IIS 6 WMI compatibility is in the manual somewhere I missed it.

    Thank you Nick.

    Thursday, November 20, 2014 9:30 PM
  • To clarify: it's not enough to tick "Windows Authentication" in Add Roles/Features - it actually has to be enabled in IIS configuration. 

    There are also suggestions to run mofcomp.exe smsdpprov.mof  


    Tip of me hat:

    http://weikingteh.wordpress.com/2013/12/03/failed-to-install-a-new-distribution-point-error-0x800706ba/

    Wednesday, December 10, 2014 2:51 AM
  • Thank you Nick Kershner.
    • Edited by Oded BR Wednesday, January 14, 2015 9:55 AM
    Wednesday, January 14, 2015 9:51 AM
  • My HERO!   Finally a solution.   I was getting the infamous:

    Failed to get DP locations as the expected version from MP

    Tried redistributing the client package, got an error.   tried the IIS 6 WMI compatibility, fixed my issue.   Thanks mucho!

    


    Networking: It's not just a job, it's an OBSSESION!

    Tuesday, May 12, 2015 10:49 PM
  • I had the same experience as Brian.  I was getting the 0x800706BA error on one of the SCCM DPs that I was upgrading.  I tried just installing a new DP and used a regular account with admin permissions on the DP and it worked.  Of course, it may have just worked because I installed it as a new DP instead of upgrading.  Thanks!

    Shane Curtis

    Thursday, June 4, 2015 6:12 PM
  • thanks it worked for me too

    thanks Nick

    Thursday, June 11, 2015 4:36 PM
  • It worked for me. Thanks Nick

    FaniK

    Thursday, December 24, 2015 5:12 PM
  • For me this does not change anything.

    I'm not having problems because of this error 5605 (at least I think I haven't) but

    - I'm wondering why I only see this on distribution points that are not part of a site server (primary or secondary).

    - It only seems to occur with a scheduled update (via package properties) and not via a manual update DPs (or maybe it is only on the first update DP's from the day)

    - Can the error have some impact and what does it actually mean?

    Thanks,

    WiM

    Tuesday, May 3, 2016 12:11 PM
  • Hi

    hope this helps someone.

    had exact same error as mentioned.

    TCP port 80, 135, 445 needs to be openend as per the following article.

    https://technet.microsoft.com/en-us/library/hh427328.aspx

    once ports were openend by our network team installation of DP started successfully.

    no errors in distmgr.log

    Thanks.

    • Proposed as answer by shu_ZA Monday, June 20, 2016 1:04 PM
    Monday, June 20, 2016 1:04 PM
  • I still have issue with one of our DP, we have verified all the above mentioned ports, IIS etc. all are good

    still package is getting failed.

    CWmi::Connect() failed to connect to \\contoso.com\root\CIMv2. Error = 0x800706BA 
    STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=primarysite.abc.comSITE=1PR PID=5072 TID=1336 GMTDATE=Sun Mar 12 16:09:09.813 2017 ISTR0="["Display=\\contoso.com\"]MSWNET:["SMS_SITE=1PR"]\\contoso.com\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\contoso.com\"]MSWNET:["SMS_SITE=1PR"]\\contoso.com\" 
    ERROR DPConnection::ConnectWMI() - Failed to connect to  contoso.com. error = 0x800706ba 
    Failed to find a valid drive on the distribution point ["Display=\\contoso.com\"]MSWNET:["SMS_SITE=1PR"]\\contoso.com\ 
    Cannot find or create the signature share.
    STATMSG: ID=2324 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=primarysite.abc.comSITE=1PR PID=5072 TID=1336 GMTDATE=Sun Mar 12 16:09:09.892 2017 ISTR0="["Display=\\contoso.com\"]MSWNET:["SMS_SITE=1PR"]\\contoso.com\" ISTR1="CAS00750" ISTR2="" ISTR3="2" ISTR4="1" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="CAS00750" AID1=404 AVAL1="["Display=\\contoso.com\"]MSWNET:["SMS_SITE=1PR"]\\contoso.com\" 
    Error occurred. Performing error cleanup prior to returning.


    Prashanth Kumar System Center Administrator

    Monday, March 13, 2017 4:48 AM
  • Hi Prashanth

    "error = 0x800706ba Failed to find a valid drive on the distribution point"

    Please check, if the HDD/SMS folder is available and all security settings are correct.

    You also can check SCCM Monitoring for your DP (SMS_DISTIRIBUTION_MANAGER) to get more information about this error.

    Cheers
    Dominik

    Monday, March 13, 2017 11:04 AM
  • yes its DP name

    Prashanth Kumar System Center Administrator

    Saturday, March 18, 2017 10:04 AM
  • I have followed all the above comments and all are fine, but still we are facing the issue.

    raised a case with MS waiting for their update


    Prashanth Kumar System Center Administrator

    Saturday, March 18, 2017 10:05 AM
  • any new? i have the same issue....
    Thursday, March 23, 2017 11:21 AM
  • Go to the DP and Run as different account.
    Monday, April 24, 2017 7:27 AM
  • I have added the PRI\CAS server account to the local policy->run as batch job, and then it worked fine.

    Prashanth Kumar System Center Administrator

    Tuesday, April 25, 2017 2:29 PM
  • I have added the PRI\CAS server account to the local policy->run as batch job, and then it worked fine.

    Prashanth Kumar System Center Administrator

    Hi,
    I have an intermittent issue on some DPs. Also checked dstmgr.log and found....

    Error: Distribution Manager failed to connect to the distribution point ["Display=\\server.x\"]MSWNET:["SMS_SITE=Y"]\\server.x\. Check your network and firewall settings.

    "error = 0x800706ba Failed to find a valid drive on the distribution point"

    The following things are in place....
    1. Enable Windows Authentication in IIS
    2. Installed IIS 6 WMI Compatibility
    3. TCP port 80, 135, 445 are open

    Can any one help me out ?

    Rgds, Irshad

           
    Wednesday, September 20, 2017 8:47 AM
  • You already posted this at https://social.technet.microsoft.com/Forums/en-US/e9ca30bf-1778-4f8f-8b37-25d7b501ea8f/distribution-point-issue?forum=configmanagerdeployment#e9ca30bf-1778-4f8f-8b37-25d7b501ea8f

    Please don't double post.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, September 20, 2017 5:01 PM
  • I have been through all the stuff mentinoed here and in the end I figured out, Management Point and DP were off by 6 minutes from each other! As soon as we resynced time on the host and guest VM, packages started pushing out. Hoping this might help someone

    Monday, October 2, 2017 10:22 PM
  • Worked like a charm after enabling Windows auth and re installing the DP. Been working on this for 3 days solid now and reinstalled the whole lot 4 times. 
    Thursday, November 23, 2017 2:57 PM
  • Check if someone configure RPC Dynamic ports settings under HKLM\Software\Microsoft\RPC\Internet\Ports in both servers (SCCM Primary and DP).

    https://support.microsoft.com/en-us/help/154596/how-to-configure-rpc-dynamic-port-allocation-to-work-with-firewalls


    Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

    Sunday, February 18, 2018 12:38 PM
  • This was the same problem in our environment.  The DC time and the time on the new DP were out by 5 minutes.

    Once we rectified the time difference the DP installed.

    Tuesday, May 7, 2019 10:41 PM
  • Thanks a lot @ Nick Kershner....
    You have saved my day! Precise answer for distribution manager failed to connect to the distribution point check your network and firewall
    Sunday, March 15, 2020 2:48 PM
  • I fixed this by doing the following two things

    1. Enable Windows Authentication in IIS

    2. Installed IIS 6 WMI Compatability

    Hopefully this helps someone else.

    yes it helped a lot ! thanks .. in my case i had to deselect hilighted security/auth since some thing was interfering even if I have above 1 and 2 . So you  just need Windows Authentication in IIS . not the hilighted ones

    Tuesday, April 21, 2020 11:47 AM