Wednesday, February 13, 2013

Exchange EMC

Running EMC would cause this:

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 absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic. 

Tried every single thing I could find on google, set winrm maqxrequests, reinstall exchange, reinstall winRM, spent 12 hours. 

My solution (issue was caused by wsus messing with dynamiccompression module)

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

Tuesday, February 12, 2013

Exchange 2010 ECP event ID 4

New exchange2010 installation, ECP complained with

Test-ecpconnectivity -verbose | fl

PerformanceCounterName      : ECP Web Sevice Logon Latency
Result                      : Failure
Error                       : An exception was thrown by the Web service: The remote server returned an error: (500)

and event viewer had getlist failures on msexchagne control panel 4

failed with the following error:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeLoadException: Could not load type 'System.ServiceModel.Activation.HttpHandler' from assembly 'System.ServiceModel, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

reloading counters didn't help, removing and reinstall ECP did not help.

Solution in IIS set the application pool for msexchagneECPapppool to .net 2.0 instead of .net 4.0.