Exchange 2010 is suddenly unmanageable

Question

Hi --
On a SBS 2011 box running Exchange 2010 SP2, Exchange has suddenly become unmanageable. I have no idea what happened overnight to cause this. But I've been trying to get this fixed for two hours already, with no luck.
Nobody can open OWA. From anywhere. Including from the server itself. IE network diagnostics reveal that "The device or resource (whatever) is not set up to accept connections on port "https".
The Exchange Management Console won't open. I get the error "The attempt to connect to http://server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client cannot process the
request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication
mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination,
specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic."
Opening an Exchange Management Shell results in the error:
>>>>>>>>>>>>>>>>>>>>>>>>
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
ooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
<<<<<<<<<<<<<<<<<<<<<<<<
I have checked and double-checked bindings, Kerberos settings, and a slew of other things. I have reset IIS and rebooted the server multiple times. I can't get past this. Everything referenced in the following articles was checked and verified to be as the
articles said they should be:
http://blogs.technet.com/b/bshukla/archive/2012/05/04/exchange-management-shell-error-500-internal-server-error.aspx
http://technet.microsoft.com/en-us/library/ff607221%28v=EXCHG.80%29.aspx
http://support.microsoft.com/kb/2028305
I installed and ran the EMTshooter script referenced in http://blogs.technet.com/b/exchange/archive/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures.aspx. This it what it reported:
>>>>>>>>>>>>>>>>>>>>>>>>
Welcome to the Exchange Management Troubleshooter!
We recommend that you run the troubleshooter after making changes to
IIS to ensure that connectivity to Exchange Powershell is unaffected.
Checking IIS Service...
Checking the Exchange Install Path variable...
Checking the Powershell Virtual Directory...
Checking the Powershell vdir SSL setting...
Checking the Powershell vdir path setting...
Checking HTTP Port 80...
Checking HTTP Port 80 Host Name...
Testing for errors...
VERBOSE: Connecting to server.domain.local
[server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a r
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
    + FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:
server.domain.local
Failed to connect to any Exchange Server in the current site.
Problem found:
Looking for error...
These are the possible causes for this error:
1. The default http binding has been removed from the Default Web Site. Exchange Powershell needs http to be configured
so that the IP Address is "All Unassigned", the Port is "80", and the Host Name is "".  A common scenario for changing t
his is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by req
uiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Re
mote PowerShell requires port 80 to be available on the Default Web Site for all Internet Addresses. If you want to set
up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at:
http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx
and follow the directions under the section:
"For a Configuration in Which SSL is required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0."
2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue,
 you need to clear out the Hostname field under the port 80 bindings on the Default Web Site.
After each error is resolved, close this window and re-run the tool to check for additional problems.
<<<<<<<<<<<<<<<<<<<<<<<<
However, the bindings on the Default Web site are correct (I've checked them multiple times).
And the server's System, Security and Application logs are devoid of anything that could even begin to explain what is going on.
And this was all working yesterday ...
I have automatic replies to modify/remove and have no way to get to them. Outlook on the PCs won't pull up Automatic Replies, claiming that the server is unavailable. On the other hand, email is coming and going fine ...
I need to get this fixed _now_. Does anybody know how to get to the bottom of this -- and what could have possibly happened to cause this in the first place?
Thanks
CL

Answer 1

Hi --
C:\Users\Administrator>winrm quickconfig
WinRM already is set up to receive requests on this machine.
WinRM already is set up for remote management on this machine.
C:\Users\Administrator>winrm invoke Restore winrm/Config
Restore_OUTPUT
C:\Users\Administrator>winrm get winrm/config
Config
    MaxEnvelopeSizekb = 150
    MaxTimeoutms = 60000
    MaxBatchItems = 32000
    MaxProviderRequests = 4294967295
    Client
        NetworkDelayms = 5000
        URLPrefix = wsman
        AllowUnencrypted = false
        Auth
            Basic = true
            Digest = true
            Kerberos = true
            Negotiate = true
            Certificate = true
            CredSSP = false
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        TrustedHosts
    Service
        RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
        MaxConcurrentOperations = 4294967295
        MaxConcurrentOperationsPerUser = 15
        EnumerationTimeoutms = 60000
        MaxConnections = 25
        MaxPacketRetrievalTimeSeconds = 120
        AllowUnencrypted = false
        Auth
            Basic = false
            Kerberos = true
            Negotiate = true
            Certificate = false
            CredSSP = false
            CbtHardeningLevel = Relaxed
        DefaultPorts
            HTTP = 5985
            HTTPS = 5986
        IPv4Filter = *
        IPv6Filter = *
        EnableCompatibilityHttpListener = false
        EnableCompatibilityHttpsListener = false
        CertificateThumbprint
    Winrs
        AllowRemoteShellAccess = true
        IdleTimeout = 180000
        MaxConcurrentUsers = 5
        MaxShellRunTime = 2147483647
        MaxProcessesPerShell = 15
        MaxMemoryPerShellMB = 150
        MaxShellsPerUser = 5
C:\Users\Administrator>winrm enumerate winrm/config/listener
C:\Users\Administrator>netstat -aon | find ":80"
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
  TCP    0.0.0.0:808            0.0.0.0:0              LISTENING       4856
  TCP    192.168.214.20:80      192.168.214.20:15979   ESTABLISHED     4
  TCP    192.168.214.20:15979   192.168.214.20:80      ESTABLISHED     6336
  TCP    192.168.214.20:15980   192.168.214.20:80      TIME_WAIT       0
  TCP    192.168.214.20:15997   192.168.214.20:8014    SYN_SENT        8528
  TCP    [::]:80                [::]:0                 LISTENING      
4
  TCP    [::]:808               [::]:0                 LISTENING      
4856
  TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15926
  TIME_WAIT       0
  TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15973
  TIME_WAIT       0
  TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15978
  TIME_WAIT       0
  TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15982
  TIME_WAIT       0
  TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15984
  TIME_WAIT       0
  TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15989
  TIME_WAIT       0
  TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15990
  TIME_WAIT       0
C:\Users\Administrator>
PID 4 is c:\Windows\system32\ntoskrnl.exe
PID 6336 is DataCollectorSvc.exe
I'm still getting all the same errors.