locked
Unable to connect to WMI on remote machine "MachineName", error = 0x800706ba RRS feed

  • Question

  • Hi,

    I have System Center 2012 Configuration Manager SP1, I'm not able to install/migrate clients from SCCM 2007, installation fail with the following error from CCM.LOG file:

    ---> The 'best-shot' account has now succeeded 5065 times and failed 598 times.
    ---> Unable to connect to WMI on remote machine "MachineName", error = 0x800706ba.
    Execute query exec [sp_CP_SetLastErrorCode] 2097152551, -2147023174  

    For more details:

    ======>Begin Processing request: "2097152508", machine name: "MachineName"  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.133-180><thread=3328 (0xD00)>
    Execute query exec [sp_IsMPAvailable] N'P01'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.133-180><thread=3328 (0xD00)>
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.135-180><thread=3328 (0xD00)>
    ---> Attempting to connect to administrative share '\\MachineName\admin$' using account 'MEC\sccmadmin'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.135-180><thread=3328 (0xD00)>
    ---> The 'best-shot' account has now succeeded 5344 times and failed 640 times.  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.166-180><thread=3328 (0xD00)>
    ---> Connected to administrative share on machine SMOHAMMED using account 'MEC\sccmadmin'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.166-180><thread=3328 (0xD00)>
    ---> Attempting to make IPC connection to share <\\SMOHAMMED\IPC$> ~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.166-180><thread=3328 (0xD00)>
    ---> Searching for SMSClientInstall.* under '\\SMOHAMMED\admin$\'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:31.167-180><thread=3328 (0xD00)>
    Submitted request successfully  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:33.133-180><thread=5088 (0x13E0)>
    Getting a new request from queue "Incoming" after 100 millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:33.133-180><thread=5088 (0x13E0)>
    Waiting for change in directory "D:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:40:33.133-180><thread=5088 (0x13E0)>
    ---> Unable to connect to WMI on remote machine "SMOHAMMED", error = 0x800706ba.  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:41:13.205-180><thread=3328 (0xD00)>
    ---> Deleting SMS Client Install Lock File '\\SMOHAMMED\admin$\SMSClientInstall.P01'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:41:13.205-180><thread=3328 (0xD00)>
    Execute query exec [sp_CP_SetLastErrorCode] 2097152508, -2147023174~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:41:13.210-180><thread=3328 (0xD00)>
    Stored request "2097152508", machine name "SMOHAMMED", in queue "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:41:13.211-180><thread=3328 (0xD00)>
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152508, 2~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:41:13.212-180><thread=3328 (0xD00)>
    Execute query exec [sp_CP_SetLatest] 2097152508, N'01/09/2013 11:41:13', 19~  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:41:13.213-180><thread=3328 (0xD00)>
    <======End request: "2097152508", machine name: "MachineName".  $$<SMS_CLIENT_CONFIG_MANAGER><01-09-2013 14:41:13.213-180><thread=3328 (0xD00)>

    Windows Firewall is disable and Hardware firewall configured to open the following ports:

    File and Printer Sharing

    Outbound and inbound

    Windows Management Instrumentation (WMI)

    Inbound

    TCP Port 80

    Outbound

    TCP Port 443

    Outbound

    TCP Port 10123

    Outbound

    TCP port 2701

    Inbound

    TCP port 445

    Outbound and inbound

    TCP port 135
      UDP port 135

    Outbound and inbound

     

    Plus RPC dynamic ports between the site server and the client computer.


    Abduljalil Abolzahab

    Wednesday, January 9, 2013 11:50 AM

Answers

  • Thanks for your help,

    I found the issue, Port TCP 1027 was blocked from Server to Client and some dynamic ports was blocked also from Server to Client... so we open RPC dynamic ports from Server to Clients and the client installation start, before RPC ports it were open from client to server only.


    Abduljalil Abolzahab

    Thursday, January 10, 2013 8:44 AM

All replies

  • 800706ba = The RPC server is unavailable.
    Can you connect to the remote machine using explorer (admin$), regedit and WMI (wbemtest)?

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

    Wednesday, January 9, 2013 11:58 AM
  • Hi,

    It could be conflict DNS record too. Did your DNS server enabled scavenging?

    If you can ping the machine,

    1. try "ping" MachineName,
    2. then do a "ping -a" on the IP resolved
    3. and cross check to see whether it is the same MachineName.

    Regards,
    Hau

    Wednesday, January 9, 2013 12:17 PM
  • 800706ba = The RPC server is unavailable.
    Can you connect to the remote machine using explorer (admin$), regedit and WMI (wbemtest)?

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


    Yes I can connect to admin$ and I open dynamic RPC dynamic port. but I didn't check if I can connect to regedit and WMI, if this is the issue what could be the solution?

    Abduljalil Abolzahab

    Wednesday, January 9, 2013 5:08 PM
  • Hi,

    It could be conflict DNS record too. Did your DNS server enabled scavenging?

    If you can ping the machine,

    1. try "ping" MachineName,
    2. then do a "ping -a" on the IP resolved
    3. and cross check to see whether it is the same MachineName.

    Regards,
    Hau


    I have no issue with DNS, I can ping to computer name, I can ping to IP address with -a and no duplicates records in DNS for machine name.

    Abduljalil Abolzahab

    Wednesday, January 9, 2013 5:10 PM
  • Thanks for your help,

    I found the issue, Port TCP 1027 was blocked from Server to Client and some dynamic ports was blocked also from Server to Client... so we open RPC dynamic ports from Server to Clients and the client installation start, before RPC ports it were open from client to server only.


    Abduljalil Abolzahab

    Thursday, January 10, 2013 8:44 AM
  • Friday, September 27, 2013 8:00 AM
  • Hi all,

    I just want to report that in our case this 0x800706ba error was caused by firewall as well.

    Monday, April 14, 2014 11:13 AM
  • Hi All,

    If respective static and Dynamic ports from SCCM Server and Client is already opened and you are still facing issues then Run Wbemtest from SCCM Server and put \\clientname\root\cimv2 then click connect.

     

    if it is giving error.. 0x800706ba, then run wf.msc in clientmachine like windows 7 and turn off firewall at domain profile level.

     

    then again connect or test wbemtest from sccm server and put \\clientname\root\cimv2 then click connect.

    it should work !!!

    Note: Clientname will be hostname or computername of desktop/laptop machine at destination.


    Kirpal Singh




    Saturday, May 23, 2015 9:11 AM
  • This solved my problem...

    I use both LAN and wireless on my Windows 10 PC.

    When i try to initiate the CM client installation from the console, i get the above error even after our SCCM server had been upgraded to 2012 R2 SP1.

    All I had to do was to ensure what kwokhau said and the installation worked. Now my Windows 10 PC is being managed.

    Thanks kwokhau.

    Friday, October 2, 2015 1:10 PM
  • Thanks for your help,

    I found the issue, Port TCP 1027 was blocked from Server to Client and some dynamic ports was blocked also from Server to Client... so we open RPC dynamic ports from Server to Clients and the client installation start, before RPC ports it were open from client to server only.


    Abduljalil Abolzahab

    Hi Abduljalil, how did you accomplish this?  The firewall is turned off on the client workstation... thanks
    Tuesday, February 2, 2016 10:50 PM
  • Replying to this in case someone else runs into the same issue in the future - 

    Turns out the error code above was appearing on the ccm log, but was not at all affecting the final output. The issue was that the Intune client was already installed on the PC. After uninstalling that using a powershell script available online (https://gallery.technet.microsoft.com/Uninstall-the-Intune-b42111d1), I ran it again, and it took a few minutes but the client is now installing on the machine. 

    I hope that saves someone a few days of frustration :)

    Friday, May 11, 2018 4:53 PM