• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4831
  • Last Modified:

WinRM issue with Exchange 2013

Hello Experts –

I have a client with a small branch office with a single Windows 2012 server.  This server is a DC and does have Exchange 2013 on it as well.  All was fine until their IT removed the WSUS role from it.  When this occurred, the feature “WinRM IIS Extension” was removed.

They first notice a problem when one of the local users tried to access their mailbox that is hosted on that server (Ex2013) and could not.  They went to open the Exchange Admin Center and got the following error:

“This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.
For more information about HTTP errors, see Help.”

I was brought in at this time to see if I could figure it out.  Once I was informed of what had transpired I tried to get into the Exchange Management Shell (Powershell) and got the following errors:

VERBOSE: Connecting to ServerX.domainY.local.
New-PSSession : [serverX.domainY.local] Connecting to remote server serverX.domainY.local 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], PSRemotingTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
VERBOSE: Connecting to ServerX.domainY.local.
New-PSSession : [serverX.domainY.local] Connecting to remote server serverX.domainY.local 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], PSRemotingTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
VERBOSE: Connecting to ServerX.domainY.local.
New-PSSession : [serverX.domainY.local] Connecting to remote server serverX.domainY.local 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], PSRemotingTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
WARNING: No Exchange servers are available in the Active Directory site Default-First-Site-Name. Connecting to an
Exchange server in another Active Directory site.
VERBOSE: Connecting to ServerX.domainY.local.
New-PSSession : [serverX.domainY.local] Connecting to remote server serverX.domainY.local 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], PSRemotingTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
VERBOSE: Connecting to ServerX.domainY.local.
New-PSSession : [serverX.domainY.local] Connecting to remote server serverX.domainY.local 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], PSRemotingTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:


The steps I have taken to resolve the issue are as follows:

•      Added the WinRm IIS Extension back under Features
•      Ran winrm quickconfig (twice – all looks good there)
•      In IIS Manager, on the PowerShell VD \ Basic Settings, I changed the Physical Path to: XX:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell

Despite these attempts, the issue has not changed and the messages are the same.

I am at a loss of where to go next as most other posts I see talk about simply reinstalling…not something I really want to do.  I think it is a straight forward WinRM issue but I wonder if when they removed WSUS something else was removed.

Anyone have any thoughts?

Thanks in advance –

Brad
0
dasmail2000
Asked:
dasmail2000
  • 2
1 Solution
 
Tej Pratap Shukla ~DexterServer AdministratorCommented:
Hey Brad,

You might have Kerbauth module configured incorrectly in Internet Information Services (IIS)  refer to this tech-net article to understand the issue clearly : http://support.microsoft.com/kb/2028305

Thanks
~Dex
0
 
dasmail2000Author Commented:
You nailed it - I missed that in my searching.  Thanks!
0
 
Tej Pratap Shukla ~DexterServer AdministratorCommented:
Most Welcome :)
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now