locked
failed to open the runspace pool. The Server manager WinRM plug-in might be corrupted or missing RRS feed

  • Question

  • HI,

    I am creating failover cluster for VPN but when I am trying to install failover feature in server 2012 but getting below error message.

    "failed to open the runspace pool. The Server manager WinRM plug-in might be corrupted or missing"

    Regards,

    Sachin


    Jitendra Gautam

    Monday, January 12, 2015 9:57 AM

Answers

  • We need to verify http.sys listening to local loop back IP address (127.0.0.1)

    To verify  that, Run below command.

    netsh http show iplist

    If you are unable to see 127.0.0.1 is not registered, run 

    netsh http add iplisten 127.0.0.1


    Regards,
    Manjunath Sullad

    • Marked as answer by AnnaWY Monday, January 19, 2015 8:49 AM
    Monday, January 12, 2015 1:02 PM

All replies

  • We need to verify http.sys listening to local loop back IP address (127.0.0.1)

    To verify  that, Run below command.

    netsh http show iplist

    If you are unable to see 127.0.0.1 is not registered, run 

    netsh http add iplisten 127.0.0.1


    Regards,
    Manjunath Sullad

    • Marked as answer by AnnaWY Monday, January 19, 2015 8:49 AM
    Monday, January 12, 2015 1:02 PM
  • Hi,

    Thanks for your help. Now I am able to add or remove any role or feature from server manager.

    Basically I want to create a new cluster for RRAS. So is it possible to create cluster for RRAS?

    Regards,

    Jitendra Gautam


    Jitendra Gautam

    Tuesday, January 13, 2015 7:26 AM
  • Below Technet library will suggest how to configure RRAS as cluster.

    http://technet.microsoft.com/en-us/library/jj134175.aspx 

    http://technet.microsoft.com/en-us/library/jj134252.aspx


    Regards,
    Manjunath Sullad

    Tuesday, January 13, 2015 10:07 AM
  • Hi,

    I am running into the same issue and have entered the commands above to register the loopback since it originally was not present, but it has not resolved my issue. 

    I ran (winrm invoke restore winrm/config/plugin) but this returned an error.

    I also ran (winrm quickconfig) and it says the WinRM service is already running followed by same errors.  Can you please assist me?

    Tuesday, January 13, 2015 11:42 PM
  • Hi,

    Thanks for you help. I have one more query as we have wsus server and we have windows 7, Vista and XP in our domain. But I want that some of the Windows 7 machine should not receive some specific updates like IE Updates. So how can I configure this. Please help

    Regards,

    Sachin


    Jitendra Gautam

    Tuesday, January 20, 2015 6:20 AM
  • I have this problem on my AD Certificate Services Root CA, The error message comes up in server manager, I ran the netsh command, but I have 127.0.0.1 and also ::1 listed. The error still remains, I have tried restoring plugins with the commands winrm invoke restore winrm/config @{} and winrm invoke restore winrm/config/plugin @{} and both commands bring Restore_OUTPUT.

    I have restarted the machine several times, I have ran sfc /scannow as well as DISM /online /StartComponentCleanup /RestoreImage.  I cannot afford to reinstall windows server, I am running 2012R2 and once again this is my root CA, please help. thanks

    Friday, December 4, 2015 5:26 AM
  • I have the same issue with my AD CS issuing authority as the root and intermediate are offline as part of this 3-tier architecture.... I have done the same netsh and have the loopback listed and winrm quickconfig says its up and running.....

    Robert

    Friday, December 4, 2015 5:36 PM
  • Also when I try to restore winrm/config I get this:

    WSManFault
        Message = The WinRM client cannot process the request. The WinRM client tried to use Negotiate authentication mechan
    ism, but the destination computer (localhost:47001) returned an 'access denied' error. Change the configuration to allow
     Negotiate authentication mechanism to be used or specify one of the authentication mechanisms supported by the server.
    To use Kerberos, specify the local computer name as the remote destination. Also verify that the client computer and the
     destination computer are joined to a domain. To use Basic, specify the local computer name as the remote destination, s
    pecify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server:
         Kerberos

    Error number:  -2147024891 0x80070005
    Access is denied.

    Robert

    Friday, December 4, 2015 5:38 PM
  • In my circumstance, I had renamed the local administrator account and did not logoff/logon with new name. As soon as I did, I stopped receiving the error.
    Thursday, January 7, 2016 6:54 PM
  • Hi,

    my solution: enable remote shell sessions in the group policies.

    "computer > admin templates > windows components > windows remote shell > allow remote shell access."

    Regards,

    Joerg Hundgeburth


    Best regards, joerg.

    • Proposed as answer by nero787 Friday, February 24, 2017 4:58 PM
    Monday, November 21, 2016 1:03 PM
  • Thanks, for me it's works
    Thursday, January 5, 2017 10:28 AM
  • Thanks, it worked for me!
    Friday, February 24, 2017 4:58 PM
  • Hi

    if you have a problem with install .NET 3.5:
    follow these comands with powershell:

    DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs

    Get-WindowsFeature *Framework*
    Install-WindowsFeature Net-Framework-Core -source d:\sources\sxs

    mr.gerami@live.com


    Tuesday, January 2, 2018 11:30 AM
  • I had no luck with adding the loopback to http.sys, the allow remote shell access, and my winrm config appeared healthy (returned no errors).

    Based on suggestion from Mohammad using PS to install .NET, I just want straight to Add-WindowsFeature for my install objective and it worked like a charm.

    Add-WindowsFeature RSAT-ADDS-TOOLS

    Monday, January 29, 2018 1:15 PM
  • Thank you so much for your help.

    Working fine Great.

    Wednesday, August 22, 2018 12:14 PM
  • As I fall into this too and it was none of the above solution, here is a new one : 

    winrm set winrm/config/client @{TrustedHosts="your local ip"}

    It seems this is a problem with the server not allowing any management from any address (even local) if it's not trusted before.



    Frederic@wm

    Thursday, September 27, 2018 8:42 AM
  • Dear Joerg

    Your Solution is perfectly working thank you so much

    Khalid

    Friday, October 12, 2018 8:08 AM
  • I have this problem on my AD Certificate Services Root CA, The error message comes up in server manager, I ran the netsh command, but I have 127.0.0.1 and also ::1 listed. The error still remains, I have tried restoring plugins with the commands winrm invoke restore winrm/config @{} and winrm invoke restore winrm/config/plugin @{} and both commands bring Restore_OUTPUT.

    I have restarted the machine several times, I have ran sfc /scannow as well as DISM /online /StartComponentCleanup /RestoreImage.  I cannot afford to reinstall windows server, I am running 2012R2 and once again this is my root CA, please help. thanks

    Any fix for this. we had same issues on a CA which is windows 2012 R2.

    Thursday, March 7, 2019 5:07 PM