Http Error 12152 Exchange 2010
red. It's because it's the color of flames and/or red hot coals and it means you may be in PowerShell Hell. That's what recently happened when I updated the Antivirus on my PC from Eset NOD32 version 4 to version 5. A few days after updating, I was in PowerShell Hell as shown below:When trying to run Get-ChildItem against WSMan:localhost, I received the following:Get-ChildItem : WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (12152) is: The server returned https://social.technet.microsoft.com/Forums/en-US/2d371b29-4234-460a-921c-675b73ce7fcc/error-connecting-to-the-exchange-management-shell-and-no-one-can-connect-w-outlook-or-owa?forum=smallbusinessserver an invalid or unrecognized response . At line:1 char:1 + dir WSMan:localhost + ~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-ChildItem], InvalidOperationException + FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.PowerShell.Commands.Get ChildItemCommandWhen trying to use Invoke-Command (PowerShell Remoting), I received the following error which made me think the issue was on the destination end and not the source. I tried the same command from another machine and it http://mikefrobbins.com/2012/06/21/welcome-to-powershell-hell/ worked without issue so that eliminated the computer I was trying to run PowerShell remoting commands against as the problem.[remote-pc] Connecting to remote server remote-pc failed with the following error message : The WinRM client cannot process the request. The encrypted message body has an invalid format and cannot be decrypted. Ensure that the service is encrypting the message body according to the specifications. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (:) [], PSRemotingTransportException + FullyQualifiedErrorId : PSSessionStateBrokenWhen trying to use Enter-PSSession (1 to 1 Remoting), I received the following error:Enter-PSSession : Connecting to remote server localhost failed with the following error message : The WinRM client cannot process the request. The encrypted message body has an invalid format and cannot be decrypted. Ensure that the service is encrypting the message body according to the specifications. For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1 + Enter-PSSession localhost + ~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (localhost:String) [Enter-PSSession], PSRemotingT ransportException + FullyQualifiedErrorId : CreateRemoteRunspaceFailedWhen trying to run Enable-PSRemoting, I received another error. I was able to u
2010 Management Console Home » Exchange » Cannot Access Exchange 2010 Management Console KB ID 0000477 Dtd 02/05/13 Problem Since Exchange 2007, its management tasks have been done via PowerShell, (yes even http://www.petenetlive.com/KB/Article/0000477 the GUI Management). Which is fine, however it runs all that PowerShell from a virtual directory that lives in the servers' IIS webserver. When that fails or there is a problem, Exchange runs quite happily, but you can't run the management tools. There are a number of reasons for this to fail and a number of different error messages, I will list them as I come http error acoss them. Error 1 (Seen 16/10/12) Error: Connecting to the remote server 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 http error 12152 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. It was running the command 'Discover-exchangeserver- useWIA $true - suppressError $true' -CurrentVersion 'Version 14.1(Build 218.15). I got the same when trying to access the Exchange Management Shell as well. Update 16/10/12: I got this problem today again! It seems AVG 2012 causes this problem as well, if you have AVG installed remove it and try again. Solution (Error 1) 1. Firstly drop to command line > then (as asked) run "WinRM QuickConfig". Carry out any changes that it asks by simply pressing "y". 2. Run the same command again untill it returns two positive results. 3. Start > Run > Services.msc {enter} Locate the following three services, make sure that they are set to "automatic startup" and are running. IIS Admin Service Windows Remote Management (WS-Management) World Wide Web Publishing Service 4. Start > Administrative Tools > Expand Sites > Default Web Site > Make sure the default web site IS STARTED. THIS WAS MY PROBLEM! If you can see the green start arrow then its NOT started. 5. When I