exchange management shell not working

Article
2020-05-24

Question

_{Sunday, May 24, 2020 12:50 AM}

Our exchange server is having issues with the management shell as it will not load properly. But the OWA and ECP are working just fine. When we try to go to localhost/powershell site it gives us an http 400 error. When we open up the exchange management shell, we get error below. Not sure exactly how to fix it as there isn't much on the internet that we haven't tried. We are eable to do psession to the localhost so the connection is working just fine

Show quick reference guide: QuickRef
VERBOSE: Connecting to exchange.ravens.dom
New-PSSession : [exchange.com.dom] Connecting to remote server exchange.com.dom failed with the following error message
: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the
destination computer. The content type is absent or invalid. 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 : -2144108297,PSSessionOpenFailed
VERBOSE: Connecting to exchange.ravens.dom
New-PSSession : [exchange.com.dom] Connecting to remote server exchange.com.dom failed with the following error message
: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the
destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1

New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...

New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...

+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
WARNING: No Exchange servers are available in the Active Directory site Montreal. Connecting to an Exchange server in
another Active Directory site.
VERBOSE: Connecting to exchange.ravens.dom
New-PSSession : [exchange.com.dom] Connecting to remote server exchange.com.dom failed with the following error message
: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the
destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1

New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...

New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...

If we type the full FQDN of our server name it still will not load as it gives us the same error listed above

All replies (5)

_{Thursday, May 28, 2020 7:30 AM ✅Answered}

Hi, I'm here to confirm with you if your issue has been resolved. If the problem is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

Regards,

Eric Yin

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Sunday, May 24, 2020 9:43 AM}

on Exchange server open a CMD windows as administrator and run WinRM Quickconfig

If you find my reply helpful, please “Mark as Answer” and “Vote”

Get help on demand > expertise-as-a-service.com

_{Sunday, May 24, 2020 9:52 AM}

Refer Microsoft guidance to fix this,

https://support.microsoft.com/en-za/help/2028305/error-message-when-you-try-to-start-exchange-management-shell-ems-or-e

_{Sunday, May 24, 2020 10:21 AM}

Hello,

There are couple of checks you can follow:

1. Check PowerShell Virtual Directory settings from ECP. Make sure that it is matching like ECP or OWA virtual directory settings for external and internal url.

2. Make sure that you logged in as domain user (not on local admin user)

3. Check the certificate bindings from IIS. Click 'Exchange Backend'. Select Bindings at the right side options. Edit the bindings. Check a valid certificate is selected. If not, select 'Microsoft Exchange' from the list and apply the settings. Try again

Regards From: Exchange Online | World of Cloud Computing

_{Monday, May 25, 2020 5:59 AM}

Hi bubba19831983,

Which CU are you using?

Have you tried to re-create the Powershell Virtual Directory?

Do you have any other Exchange 2016 servers that not affected by this error?

If yes, compare the web.config files under "C:\ProgramFiles\Microsoft\ExchangeServer\V15\FrontEnd\HttpProxy\PowerShell" and see if any differences between them.

Copy the file to the problematic Server and run IISReset.

Make sure "Require SSL " is not ticked in SSL Settings and correct certificate is selected in Bindings.

Run the following command and check the Exchange services are running:

Get-Service | Where {$_.DisplayName -Like "*Exchange*"} | ft DisplayName, Name, Status