Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

WinRM issue with Exchange 2013

Posted on 2014-07-30
3
Medium Priority
?
4,486 Views
Last Modified: 2014-08-02
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
Comment
Question by:dasmail2000
  • 2
3 Comments
 
LVL 12

Accepted Solution

by:
Tej Pratap Shukla ~Dexter earned 2000 total points
ID: 40231047
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
 
LVL 1

Author Closing Comment

by:dasmail2000
ID: 40236179
You nailed it - I missed that in my searching.  Thanks!
0
 
LVL 12

Expert Comment

by:Tej Pratap Shukla ~Dexter
ID: 40237029
Most Welcome :)
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
Mailbox Corruption is a nightmare every Exchange DBA wishes he never has. Recovering from it can be super-hectic if not entirely futile. And though techniques like the New-MailboxRepairRequest cmdlet have been designed to help with fixing minor corr…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Suggested Courses

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question