Errors on EMC or EMS


EMC

[Server.domain.com] connecting to remote server 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 absence or invalid. For more information see the remote troubleshooting help topic discover-exchange server –use WIA $ true – suppress error $ true

EMS

[Server.doamin.com] connecting to remote server 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 absence or invalid.

Step 1:

Run WinRM quick config

WinRM already is set up to receive requests on this machine.

WinRM already is set up for remote management on this machine.

 

Step 2:

IIS manager à Default website à Edit bindings à Confirm HTTP is configured to work on port 80

(If customer is running more than 1 website make sure default website is working on port 80 )

WinRM 2.0 no longer uses Port 80.

Since Power shell virtual directory is placed under default website if the default website is not configured to work on port 80. We will not be able to browse any virtual directories under default website.

Step 3:

IIS manager à Default website à Edit bindings à HTTP à hostname value should be blank

(Some time you will see hostname as local host)

Step 4:

Try accessing OWA and the default website from the IIS and make sure we are able to access the websites.  (Some time we may get HTTP error 500)

SSL is not required on the Powershell virtual directory.

 

Step 5:

Go to this location

C:\windows\system 32\inetsrv\config àopen Application.config file in a notepad and check for lines starts with (add name)

Below the <global module>

Add this syntax

<Add name = “wsman” image = “%windir%\system 32\wsmsvc.dll” />

Also check for kerburath (if wrong add this line)

<Add name = “kerbauth” image =”c:\program files \Microsoft\exchange server\v14\bin\kerbauth.dll” />

(We have to be careful while doing this step if required involve IIS team consult with TL before performing this step)

Step 6:

IIS Manager à Default website à Module à Make sure we don’t have kerbauth module loaded. If you see Kerbauth in the Default website module remove it.

(By default kerbauth authentication is give to power shell and not for the default website)

Step 7:

IIS Manager à Default website à Power shell virtual directory à Module à check do we have kerbauth module loaded and it should be in Native mode not as a managed mode

If you see in managed mode à remove the kerbauth à add it again and choose native mode

Kerbauth authentication method should be in local and not inherited

Step 8:

Check Exchange is communicating with the domain controller (Nic settings on the Exchange server)

Check for the application logs

Advertisements
This entry was posted in Exchange 2007, Exchange 2010 and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s