daknetworks.com

Cancel EXCHANGE update (CU13) because it requires a HOTFIX (or two) before it continues. Afterwards, OUTLOOKs are disconnected; OUTLOOK-WEB-ACCESS works; sending & receiving email doesn't work. Hmmmm.... what to do.

Checking the WINDOWS logs and I see:

"Failed to discover Ews Url for mailbox"

Then I check for the EXCHANGE COMPONENT STATUS:

• Get-ServerComponentState –Identity ServerNameHere

This will tell you the state of the server components in an ACTIVE/INACTIVE way. If something is INACTIVE, you can turn it to ACTIVE by:

• Get-ServerComponentState –Identity ServerNameHere -Component ServerWideOffline -State Active -Requester Functional
• sc stop MSExchangeTransport
• sc stop MSExchangeFrontEndTransport
• timeout 80
• sc start MSExchangeTransport
• sc start MSExchangeFrontEndTransport

It should turn back to ACTIVE. However, if there was a second REQUESTER making the change to INACTIVE, this REQUESTER must also set to ACTIVE for the whole status to be ACTIVE:

• Get-ServerComponentState –Identity ServerNameHere -Component ServerWideOffline -State Active -Requester Maintenance
• sc stop MSExchangeTransport
• sc stop MSExchangeFrontEndTransport
• timeout 80
• sc start MSExchangeTransport
• sc start MSExchangeFrontEndTransport

Another way to fix this is to install the HOTFIXES that are needed and then proceed with the EXCHANGE update. Wait about an hour or so and viola! Working server automatically. Apparently, the EXCHANGE update automatically turns off some of the components. If the update is canceled, these components are left in the INACTIVE state. Going through the update process turns the components to the ACTIVE state automatically.

NOTES:
-https://blogs.technet.microsoft.com/exchange/2013/09/26/server-component-states-in-exchange-2013/
-google: "Failed to discover Ews Url for mailbox"
-google: "ServerWideOffline"
-to test mail flow use: Test-Mailflow -TargetEmailAddress This e-mail address is being protected from spambots. You need JavaScript enabled to view it