27 thoughts on “SOLVED | Exchange 2010 | Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500)”

1. Yuta September 14, 2013 at 11:17 am

   ❗ ❗ ❗
   omg thank you SO much Aurel, saved me from hours of remote troubleshooting whilst on holiday in the Maldive islands… 😕
   cheers to a knowledgeable and kind man! 🙂
   1. Mohammad February 13, 2015 at 6:44 am

      Thanks a lot. You are the great person. My issue has been RESOLVED.
      1. admin Post authorApril 7, 2015 at 3:06 pm

         You’re welcome guys!
2. pavansk July 8, 2014 at 9:28 am

   Thnq very much bro…………….
3. offsite exchange server July 11, 2014 at 4:44 am

   I am really enjoying the theme/design of your blog.
   Do you ever run into any browser compatibility issues?
   A small number of my blog readers have complained about my website not working correctly in Explorer
   but looks great in Safari. Do you have any suggestions to help fix
   this issue?
4. Brian August 4, 2014 at 2:43 pm

   Helped me out! Thank you!
5. David Phyo August 29, 2014 at 4:48 am

   Thanks a lot.
6. Lucky Saud September 5, 2014 at 5:59 pm

   Hi
   I did the same steps but still same problem 👿
   1. admin Post authorSeptember 8, 2014 at 3:05 pm

      Can you give more details?
7. Sam November 24, 2014 at 5:10 pm

   Hi Aurel,

   Excellent Post, Thanks for sharing your knowledge.
   I have a problem with exchange server, Do you can help me?
   The error when I open the EMS (Exchange Management Shell) is:

   [server.domain] Processing data from remote server failed with the following error message: Could not load file or assembly ‘Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=*********** ‘ or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) For more information, see the about_Remote_Troubleshooting Help topic.
   + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc eption
   + FullyQualifiedErrorId : PSSessionOpenFailed

   And with EMC console:
   MMC has detected an error in a snap-in and will unload it.

   Thanks for your help.
   I’m sorry for my bad English 😉
   1. admin Post authorNovember 28, 2014 at 11:04 am

      Hello Sam,

      I suppose from the error that we are talking about Exchange 2010.

      Did you update to RU5, or did any updates?
      This is usually a known issue for RU5 and can be solved by uninstalling the update.

      If this is the issue try RU5 v2: http://support.microsoft.com/?kbid=2785908

      Hope it helps,
      Aurel.

8. Pingback: How To Fix Tubemate Http Response Error 500 in Windows

9. Werner February 19, 2015 at 8:18 am

   Thanks, fixed the issue with no catch.
10. Wilson Tan March 9, 2015 at 4:14 am

    Thank you very much!
11. manjit April 15, 2015 at 10:27 am

    thank u very much
12. Cip June 15, 2015 at 11:37 am

    Thank you! It works like a charm… wasted hours of searches and this did it!
13. Charlie July 10, 2015 at 5:31 pm

    Thank BRO!
    Genius.
14. Griese July 15, 2015 at 8:41 pm

    Why cant MS make such easy answers….This post is fantastic!
15. Mike December 30, 2015 at 7:39 am

    Still stuck…installed the IISRM extension, but same error

    The following error occurred while searching for the on-premise Exchange server:

    […server name] Connecting to remote server failed with the following error message: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP was not available.

    It was running the command “Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion “Version 14.1 (Build 218.15)”

    Please help!
16. Gaetan March 23, 2016 at 3:35 pm

    Merci beaucoup !
17. olalekan April 20, 2016 at 12:46 pm

    thank you
18. Sean Dorsey June 16, 2016 at 5:45 pm

    Just another person saying that fixed my issue. All the other help stuff from Microsoft really did not help.

    No idea how other IDs worked without the “WinRM IIS Extensions” not installed, but installing it worked for me !
19. manjit singh July 12, 2016 at 9:43 am

    thanks
20. David February 23, 2017 at 10:31 pm

    So, I tried to uninstall WinRM IIS extension so I could re-install it, and it say it can’t find it even though it is clearly labeled as installed. Help?
21. Asokan March 21, 2017 at 7:47 am

    I have similar EMC issues ” [**Exchange Server*] connecting to remote server failed with the following error message : The WinRM client cannot process the request The WinRM client tried to use Kerberos authentication mechanism,but the destination computer ( ” it is Exchange Server”) returned an ‘access denied’ error. Change the configuration to allow kerberos authentication mechanism to be used or specify one of then authentication mechanisms supported by the server. To use Kerberos,specify the local computer name as the remote destination……………..It was running the command ‘Discover-ExchangeServer -UseWIA $true-SupportError $true -Correction ‘Version 14.3(Build 123.4)”
22. tahir July 22, 2017 at 8:29 am

    The following error occurred while searching for the on-premises Exchange server:
    [mailbox01] Connecting to remote server failed with following error message: The WinRM client cannot not process the request because the server name cannot be be resolved. For more information see the about_remote_Troubleshooting Help topic. It was running command ‘Discover-ExchangeServer -UseWIA $true-SupressError $true -‘CurrentVersion 14.2(Build 247.5)’.
23. Nishant January 17, 2018 at 2:31 pm

    WE had same issue connecting the Exchange Management Shell. And your solution work for us, so thank you so much for sharing this and much appreciated

Comments are closed.