OK, I have a problem that I'm pretty sure is related to IIS but is causing me a whole heap of issues.
Server was rebooted to install a new tape drive. Following reboot OWA stopped working as well as ActiveSync. Believed it to be a faulty install of Exchange 2010 rollup 4v2 so followed advice and installed it with elevated administrative priveledges.
This didn't fix the issue but now means I can't get into Exchange management AT ALL. Exchange itself is working. Event Viewer is littered with ASP errors Error messages at bottom – I’ll detail what I’ve tried to fix it first (as I’ve tried a LOT)
1) Tried uninstalling the rollup
2) Registered ASP 2.0, allowed .NET Framework 1.1 in IIS. Confirmed all AppPools are started
3) Tried everything in http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx including running EMTShooter which gave me a supremely unhelpful output
4) Renamed security.config
5) Installed WinRM for IIS and also confirmed WinRM is correctly configured
6) Checked that Kerbauth is native and just in powershell (not also def website)
7) Checked WSMan module is in ApplicationHost.config
8) Confirmed port 80 is bound to the default website
9) Confirmed the location of Exchange install and powershell is correct
10) Ran ExBPA.exe directly from its location – no issues
So I’m basically at my wits end and any help would be appreciated J
ASP Errors in Event Viewer:
Event 1334 ASP>NET 2…
Failed to initialize the AppDomain:/LM/W3SVC/1/ROOT/Microsoft-Server-ActiveSync
Exception: System.SystemException
Message: Failed to create AppDomain.
Plus
IIS-W3SVC-SP 2299
An application has reported as being unhealthy. The worker process will now request a recycle. Reason given: ASP.NET application initialization failed.. The data is the error.
When I try to connect to Exchange Console I get:
Attempt to connect using Kerberos failed. ..WinRM client received an HTTP server status (500)
Connecting to powershell gives:
VERBOSE: Connecting to SBS2011.Blah.local
[sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client rece
ived an HTTP server error status (500), but the remote service did not include any other information about the cause of
the failure. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to SBS2011.blah.local
[sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client rece
ived an HTTP server error status (500), but the remote service did not include any other information about the cause of
the failure. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to SBS2011.Blah.local
[sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client cann
ot process the request. It cannot determine the content type of the HTTP response from the destination computer. The co
ntent type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed