Connecting Remote Server Failed Following Error Message Client Cannot Connect
(500) 23 Replies One quite common error I faced during the Exchange 2010 era is the
The Winrm Client Cannot Process The Request Exchange 2010 Kerberos
WinRM HTTP Error: If i use the management tools GUI
Connecting To Remote Server Failed With The Following Error Message The Ws-management Service
i get an error message saying: “Connecting to remote server failied with the following error exchange 2010 connecting to remote server failed access is denied message: The WinRM client received an HTTP server error status (500), but the remove service did not include any other informaition about the cause of the https://support.microsoft.com/en-us/kb/3063897 failure. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command ‘Discover-ExchangeServer -UseWIA $true -SuppressError $true’.” Using the Exchange Management Shell is get a similar error: “Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), but the remove http://www.aurelp.com/2013/01/19/solved-exchange-2010-connecting-to-remote-server-failied-with-the-following-error-message-the-winrm-client-received-an-http-server-error-status-500/ service did not include any other informaition about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException + FullyQualifiedErrorId: PSSessionOpenFailed” FIRST THING YOU MUST DO: DO NOT PANIC ! DO NOT REBOOT THE SERVER !!! I WILL EXPLAIN HOW TO SOLVE THIS IN A FEW EASY STEPS: 1. When you open the EMC ( Exchange Management Console ), you will get an error similar to this: 2. Go to START / Administrative Tools / Server Manager / Features / Add Features / And check WinRM IIS Extensions / NEXT / NEXT / CLOSE: !!! IF YOU ALREADY HAVE THIS ROLE INSTALLED, JUST REINSTALL IT ! 3. Close / Reopen EMC and it will work like a charm ( NO REBOOT REQUIRED ): ENJOY. And if you encounter any problems feel free to comment / contact me. This entry was posted in Exchange Server HowTo and tagged Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), do not panic Connecting to remote ser
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About http://serverfault.com/questions/657918/remote-ps-session-fails-on-non-domain-server Us Learn more about Stack Overflow the company Business Learn more about hiring developers http://exchangeserverpro.com/the-winrm-shell-client-cannot-process-the-request/ or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted remote server up and rise to the top Remote PS session fails on non-domain server up vote 2 down vote favorite 1 I'm trying to connect to a non-domain joined remote Win2008R2 server using PS from a Win8 host (same subnet, it's a local VM). Tried everything I could find, nothing works. SERVER: PS C:\Users\Administrator> winrm quickconfig PS C:\Users\Administrator> enable-psremoting CLIENT: PS C:\scripts> $cred = get-credential -username "administrator" -message remote server failed "Enter password" PS C:\scripts> $sess = new-pssession -computername 10.10.106.2 -credential $cred -authentication default new-pssession : [10.10.106.2] Connecting to remote server 10.10.106.2 failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:9 + $sess = new-pssession -computername 10.10.106.2 -credential $cred -authenticatio ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : ServerNotTrusted,PSSessionOpenFailed PS C:\scripts> winrm set winrm/config/client '@{TrustedHosts="10.10.106.2"}' WSManFault Message = The client cannot connect to the destination specified in the request. Verify that the service on the dest ination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running o n the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
Availability Migration You are here: Home / Solutions / The WinRM Shell Client Cannot Process the RequestThe WinRM Shell Client Cannot Process the Request March 12, 2013 by Paul Cunningham 98 Comments 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. 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. To fix this, in IIS Manager right-click the Exchange Back End website and click Bindings. Highlight https and click Edit. If you see "Not selected" like I did, click on Select. Choose the certificate you want to bind to the site. Apply the changes and retry the Exchange management shell. If it connects successfully to the server then you have most likely resolved this issue. Solutions Exchange 2013, IIS, PowerShell, SSL, WinRMAbout Paul CunninghamPaul is a Microsoft MVP for Office Servers and Services, specializing in Exchange Server and Office 365, and is the publisher of Exchange Server Pro. He lives in Brisbane, Australia, and works as a consultant, writer and trainer. Find Paul on Twitter, LinkedIn, or Facebook. Comments Petr Kallen says April 8, 2013 at 3:46 am Very very very thanks !!! This solved my problem !