We had an Exchange 2016 server running Exchange 2016 Cumulative Update 15 where as part of Windows Updates it rendered the server not functional. The update that we installed was the Security Update for Exchange 2016 - KB4536987.
After the update, the following symptoms were experienced.
All Outlook clients received the following message when attempting to open Outlook.
Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed.
Users could log onto Outlook Web App (OWA) however could not send email. All messages sent would go straight to Draft folder with the message:
Something went wrong and we haven't been able to send your message yet.
Something went wrong and we haven't been able to send your message yet.
The Exchange Remote Connectivity Analyzer tool passed all tests under "Outlook Connectivity".
Attempting to connect to the SMTP service on localhost results in the SMTP Error Code "421 4.3.2 Service not active".
This lead me to a previous blog post:
The Server Component States were inactive on all Exchange Services after the patch.
This however did not work... All components remained in the state Inactive.
To change the component states to Active, I needed to change the requester to Functional.
Boom we were back online!
Attempting to connect to the SMTP service on localhost results in the SMTP Error Code "421 4.3.2 Service not active".
This lead me to a previous blog post:
The Server Component States were inactive on all Exchange Services after the patch.
In my previous blog post, I used the following command to activate the component states.
Set-ServerComponentState -State Active -Requester Maintenance -Identity SERVER -Component ServerWideOffline
To change the component states to Active, I needed to change the requester to Functional.
Boom we were back online!
Note: If Requester Maintenance doesn't work, try Functional istead.
Set-ServerComponentState -Identity Bentley-MAIL -Component ServerWideOffline -State Active -Requester Functional
No comments:
Post a Comment