The WinRM Shell Client Cannot Process the Request

There are probably many different reasons why this particular PowerShell error can occur on an Exchange server, but this is what happened in my specific case.

The problem was that when I opened the Exchange management shell on one of my two Exchange 2013 test servers it would fail to connect to the local server, and would instead connect to the other server.

The PowerShell window displayed this error.

exchange-2013-ssl-powershell-00

VERBOSE: Connecting to E15MB2.exchange2013demo.com.
New-PSSession : [e15mb2.exchange2013demo.com] Processing data from remote server e15mb2.exchange2013demo.com failed
with the following error message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException
+ FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed

The cause of this error in my specific case was that the SSL certificate was no longer bound to the Exchange Back End website on that Exchange 2013 server.

exchange-2013-ssl-powershell-01

To fix this, in IIS Manager right-click the Exchange Back End website and click Bindings.

exchange-2013-ssl-powershell-02

Highlight https and click Edit.

exchange-2013-ssl-powershell-03

If you see “Not selected” like I did, click on Select.

exchange-2013-ssl-powershell-04

Choose the certificate you want to bind to the site.

exchange-2013-ssl-powershell-05

Apply the changes and retry the Exchange management shell. If it connects successfully to the server then you have most likely resolved this issue.

exchange-2013-ssl-powershell-06

About Paul Cunningham

Paul is a Microsoft Exchange Server MVP and publisher of Exchange Server Pro. He also holds several Microsoft certifications including for Exchange Server 2007, 2010 and 2013. Connect with Paul on Twitter and Google+.

Comments

  1. Very very very thanks !!!
    This solved my problem !

    Thanks a lot.

    Petr Kallen
    CZECH REPUBLIC

  2. Daoud Ghannam says:

    Thanks , this helped me :)

  3. Chris Brown says:

    Thanks…had this twice now, both times after replacing the IIS cert in Exchange through PowerShell. Confirmed bug?

  4. fparis says:

    Thanks !!!!!

  5. I am seeing similar issue on one of my Exchange 2010 SP3 on W2K12. I cannot use this solution. Do you have another solution to fix this?

    Thanks,
    pallavi

  6. Abdelhaleem says:

    i was have the same issue and its fix by following your steps thanks alo :)

  7. Francis says:

    Hi

    I had the same problem and with the help of your post, i solved it.

    In my case, i had two exchange servers running as VMs with all roles installed. My second VM was created cloning the first before exchange installed. Without knowing this , i installed my second exchange server in the new VM. it went fine. but i had problems executing shell commands and EAC actions (connecting to ex01 and tried creating MDBs in ex02, got Access denied error) from the first exchange server.

    Then i came to know about the cloning, so i ran “sysprep” in the second machine and did other network configs and started the server. All exchange services started fine, but i was unable to connect to ecp, powershell, and owa.

    I verified the “binding” setting and it was also correct. then i read somewhere in the internet that the self signed certificate might havebeen corrupted. so i created a new self signed certificate for ex02 server from the first exchange server. Then i installed the certificate in the trusted root of the second server and selected the new certificate in the “Binding” setting. it worked well.

    Thought of sharing this.

    Thanks
    Francis.

  8. This solved my problem as well Cheers.

  9. Thank you so much for this nice article problem solved

  10. Big thanks for this workaround. Good luck!

  11. BIG BIG Thanks!

    Had a Blank owa and ecp screen and the same error.

    Following youre guide solved my issue!

  12. Thanks Paul the problem Solved with these few steps

  13. This blogpost worked for me!
    Perfect!

  14. Thank you! This solved Event ID 15021 that occured in EX2013 after change to a “real” certificate. This was an easy fix, and you found the right buttons :)

  15. Thank you!! This worked for me too.

  16. Herbert Buckel says:

    Did the trick for me! Thanks much! :)

  17. Thanks; but what the heck? Why did it happen in the first place? Oh well…

  18. Thanks a lot for the pointer. however exchange product group should fix it along with mapping of other services.

  19. Very very very thanks !!!

    This solved my problem !

    YOU ARE A HERO……..

  20. After installing two servers Exchange 2013 CAS/MAILBOX roles in the environment Exch 2010, I can’t access eighter the EMS or ECP on both servers. I’ve got these mistakes:

    EMS Error:
    New-PSSession : [s-mail-nd01] Processing data from remote server s-mail-nd01 failed with the
    following error message: [Server=s-mail-nd01,RequestId=***********,TimeStamp=*****].
    For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed

    ECP Error:
    403 Access is denied.

    If I exclude server’s name from AD groups: “Exchange Servers” and “Exchange Trusted Subsysem” ECP and EMS begin to start ! But, if it’s right !? What will happen when I begin to organize DAG and migrate mailboxes, without locating the servers in these groups !? Can’t solve this problem for a week.

  21. Ed Crowley says:

    Thanks for the tip! This was hard to find, but I’m happy you published it.

  22. This solved my problem! Thanks a million :)

  23. ZAHOOR RATHER says:

    Below is the solution that solved my problem to access the management shel and console to exchange 2010.
    Before the change

    netsh winhttp show proxy

    Current WinHTTP proxy settings:

    Proxy Server(s) : http=10.214.17.11:8080
    Bypass List : (none)
    After the change

    C:\Windows\system32>netsh winhttp set proxy proxy-server=”http=10.214.17.11:8080″
    bypass-list=”*.xxx.com.xx”

    Current WinHTTP proxy settings:

    Proxy Server(s) : http=10.214.17.11:8080
    Bypass List : *.xxx.com.xx

    I remember lately that we set the winhttp proxy and did not put any bypas list there.

    thanks.

  24. THANKS YOU! This also solved our problem too!

    I am very distraught over this version of Exchange and feel this is going to be a huge problem if anything with IIS screws up….. I’m sure this is just the beginning……

  25. I am getting the same error, but your post didn’t fix my issue.

    VERBOSE: Connecting to EXMBX.domain.com
    New-PSSession : [exmbx.domain.com Connecting to remote server exmbx.domain.com failed with the
    following error message : The client cannot connect to the destination specified in the request. Verify that the
    service on the destination is running and is accepting requests. Consult the logs and documentation for the
    WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
    run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more
    information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
    VERBOSE: Connecting to EXCAS.domain.com.
    VERBOSE: Connected to EXCAS.domain.com.
    PS] C:\Windows\system32>
    [PS] C:\Windows\system32>winrm quickconfig
    WinRM service is already running on this machine.
    WinRM is already set up for remote management on this computer.
    PS] C:\Windows\system32>

    Can you suggest anything else?

  26. ZAHOOR RATHER says:

    I faced the smae issue. Please check your proxy settings of the IE explorere.
    OR check winhttp settings using netsh.

    Reset your winhttp settings and bypass the server and your local domain .
    If it was similar problem i faced then it should work after resetting the winhttp settings.

  27. I don’t have any proxy server in my environment.

    VERBOSE: Connected to EXCAS.domain.com
    [PS] C:\Windows\system32>netsh winhttp show proxy

    Current WinHTTP proxy settings:

    Direct access (no proxy server).

    [PS] C:\Windows\system32>

    I have one more EXMBX2, that’s working fine. any other solution?

  28. Thanks a lot; this solves my problem on Exchange 2013 without CU.

  29. Tx a lot for this. Solved my issue also. Was testing in accordance to the unvalid SAN certs end of 2015. Couldn’t access ECP nor OWA nor Outlook itself. Now I can again :)

  30. Darwin Mendez says:

    I don’t have any certificate to select, all the certificates disappear. I couldn’t access ECP nor Powershelll, so, how can i charge a new certificate?

  31. thanks a lot!!!!!!!!!
    Solve my problem!

    i love you ;)

  32. This is my test environment. I have 3 exchange 2013 server with DAG.
    I installed the SSL on my three servers after that i am getting the same error one of my server.

    Thanks a lot; this solves my problem on Exchange 2013 CU2 V2.

  33. Musqueteer says:

    Thanks a lot, I already received a load of http errors notifying certificate error on 0.0.0.0:444
    using netsh http show sslcert and netsh http del sslcert I removed the certificate and still having the same error.

    replacing the certificate in IIS per your instructions I got it working again.

    *happy person again*

  34. this saved my day. thanks a lot.

  35. Guillaume says:

    Many thanks!

  36. Nick Nighitngale says:

    Saved my day too. Thank you so much. It seemed to happened after my C: drive ran out of space.

  37. Alex Dimmock says:

    Phew, spent a good 2-3 hours on this. Favorited for future reference!

  38. I am getting below error while opening 2013 exchange through epc

    Exchange 2013 has been installed newly but Not able to connect through EPC console.

    Please check below error and please let me know the solution.

    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Processing data from remote server domain.com
    failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
    management roles. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Connecting to remote server domain.com failed
    with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
    valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
    enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
    access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
    Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Processing data from remote server domain.com
    failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
    management roles. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Connecting to remote server domain.com failed
    with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
    valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
    enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
    access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
    Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Processing data from remote server domain.com
    failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
    management roles. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
    WARNING: No Exchange servers are available in the Active Directory site CHE. Connecting to an Exchange server in
    another Active Directory site.
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Connecting to remote server domain.com failed
    with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
    valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
    enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
    access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
    Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Processing data from remote server domain.com
    failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
    management roles. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Connecting to remote server domain.com failed
    with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is
    valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is
    enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits
    access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting
    Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMOperationTimeout,PSSessionOpenFailed
    VERBOSE: Connecting to domain.com
    New-PSSession : [domain.com] Processing data from remote server domain.com
    failed with the following error message: The user “domain.com/Users/Administrator” isn’t assigned to any
    management roles. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.:
    VERBOSE: Connecting to .
    New-PSSession : Cannot bind parameter ‘ConnectionUri’. Cannot convert value
    “http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer=”
    to type “System.Uri”. Error: “Invalid URI: The hostname could not be parsed.”
    At line:1 char:30
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidArgument: (:) [New-PSSession], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand

    • “The user “domain.com/Users/Administrator” isn’t assigned to any management roles.”

      Either the account has not been assigned any Exchange management permissions, or there is an AD problem preventing the permissions from being enumerated.

  39. Celal Kurul says:

    Many thanks!

  40. Erich Meier says:

    Thank you very much for sharing this and other exeriences.
    Your blog is great and very helpful in many situations.

  41. Tony Perez says:

    Thanks gain Paul, this resolved the issue with both exchange servers 2013.

  42. William Knox says:

    Thanks Paul, your suggestion worked like a charm!

    You are a bl**dy legend mate! :)

    MVP definitely is the correct title! :))

    Thanks again.

    Wil

  43. You are my hero! Thanks a lot!!

  44. Wery thank’s!

  45. I had to run iisreset from command prompt afterwards but this resolved the issue for me.

    Thanks for you help Paul, this site has helped me more than one.

  46. how would I fix this error foe Ex2010. We installed SP2 Update Rollup 8 and of our 3 mailbox servers the first one spits out this error.

    Thank you.

  47. Wow. Awesome, dude! You saved my butt.

  48. Solved my issue on too. Great site. Thank you!

  49. YOU Saved me !!!! Thank you!!!

  50. Hello Paul,

    Thank you so much. Resolved my issue. Great.

  51. Thierry IMELE says:

    Thanks alot for this website…
    help me to solve more than 80% of the issues i face.

  52. thanks, really helped me.

  53. Hello,

    I have another problem.

    Can you help?

    Welcome to the Exchange Management Shell!

    Full list of cmdlets: Get-Command
    Only Exchange cmdlets: Get-ExCommand
    Cmdlets that match a specific string: Help **
    Get general help: Help
    Get help for a cmdlet: Help or -?
    Exchange team blog: Get-ExBlog
    Show full output for a command: | Format-List

    Show quick reference guide: QuickRef
    Tip of the day #29:

    Tab completion reduces the number of keystrokes required to complete a cmdlet. Just press the TAB key to complete the cm
    dlet you’re typing. Tab completion kicks in whenever there is a hyphen (-) in the input. For example:

    Get-Send

    should complete to Get-SendConnector. You can even use wildcards, such as:

    Get-U*P*

    Pressing the TAB key when you enter this command cycles through all cmdlets that match the expression, such as the Unifi
    ed Messaging Mailbox policy cmdlets.

    VERBOSE: Connecting to SWINDOWS.colop.local.
    New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
    message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
    r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
    VERBOSE: Connecting to SWINDOWS.colop.local.
    New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
    message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
    r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
    VERBOSE: Connecting to SWINDOWS.colop.local.
    New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
    message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
    r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
    VERBOSE: Connecting to SWINDOWS.colop.local.
    New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
    message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
    r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
    VERBOSE: Connecting to SWINDOWS.colop.local.
    New-PSSession : [swindows.colop.local] Connecting to remote server swindows.colop.local failed with the following error
    message : The WinRM client received an HTTP server error status (500), but the remote service did not include any othe
    r information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : WinRMHttpError,PSSessionOpenFailed
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.:

  54. Man!! What a lifesaver!! Thakxxx

  55. Just wanted to add to the conversation, I didn’t have the original problem (the cert was still bound in IIS, wasn’t expired), but I was getting the error connecting in powershell.

    An iisreset fixed the issue.

    Thanks for the article and other comments steering in the right direction.

  56. Thanks. This saved my life this mornig. Also had the Problem that I replaced a cert via powershell but it was not updated in IIS.

  57. THX! My live was saved too this morning ;)

  58. Thank you very much, like 30 minutes of panic…

  59. thanks for the blogpost!

  60. Hi Paul,
    Thanks for this post, worked for me, its still obviously fixing a lot of these issues!

    Thanks,

    Adrian.

Leave a Comment

*

We are an Authorized DigiCert™ SSL Partner.