Exchange 2013 has the Managed Availability functions. Among other things, Managed Availability is able to put Exchange services into maintenance mode. This is important, for example, when updates or service packs are installed on Exchange 2013 servers.
During the installation of the CU3, however, it happened to me that the maintenance mode was not terminated again, which led to the following error when receiving e-mails:
421 4.3.2 Service not active
The session was then disconnected. This error message then appeared in the event log:
Source: MSExchangeFrontEndTransport
ID: 7012
The service status for frontend transport is inconsistent. Current state - inactive. Expected state - active.
Unfortunately, the CMDlet "Set-ServerComponentState" also had no effect. However, there is a way out via ADSIEdit:
The "msExchComponentStates" attribute contains the components that are offline or in maintenance mode:
The entries can be deleted, they will be recreated if necessary. The "Microsoft Exchange Transport" service must then be restarted.
Then it will work again with the mail dispatch:
