I recently rolled out Cumulative Update 12 (CU12) on our Exchange 2013 servers, and after completing the install on one of the multirole servers, it wouldn't come out of Maintenance Mode. The HubTransport Component was stuck in the Draining State.
What happened was, when running the "Set-ServerComponentState $Computer -Component HubTransport -State Active -Requester Maintenance" Maintenance cmdlet, it just hung and didn't return to the next line in the EMS.
To verify that the Component State is stuck, in the Exchange Management Shell (EMS) on another server run:
Get-ServerComponentState "servername"
**Note** Change "servername" to affected server
You'll see something like this:
Server Component State
------ --------------- ------
MBX1 ServerWideOffline Active
MBX1 HubTransport Draining
MBX1 FrontendTransport Active
MBX1 Monitoring Active
MBX1 RecoveryActionsEnabled Active
MBX1 AutoDiscoverProxy Active
MBX1 ActiveSyncProxy Active
On the server that you ran the above cmdlet on, run:
Set-ServerComponentState -Identity "servername" -Requester Maintenance -Component HubTransport -State Active
**Note** Again, change "servername" to affected server.
Now, check the components again, and it should be Active:
Server Component State
------ --------------- ------
MBX1 ServerWideOffline Active
MBX1 HubTransport Active
MBX1 FrontendTransport Active
MBX1 Monitoring Active
MBX1 RecoveryActionsEnabled Active
MBX1 AutoDiscoverProxy Active
MBX1 ActiveSyncProxy Active
Once it's Active, you can continue bringing the server out of Maintenance Mode.
Happy updating!
Money! Many Thanks for the information as it fixed my issue.
ReplyDelete