[German]As of March 8, 2022, Microsoft has released several cumulative updates for Microsoft Exchange Server 2013, 2016 and 2019. However, some systems are experiencing issues such as Exchange Control Panel (ECP) no longer working. On some systems, the "Microsoft Exchange Service Host" crashes regularly. However, there is a solution for this crash.
Advertising
I had reported in the blog post Security updates for Exchange Server (March 8, 2022) about these security updates for Microsoft Exchange Server 2013, 2016 and 2019. The good news: the DAG bug known from January 2022 (see here):
Modifying DAG network settings or customizing voicemail greetings might fail with error 0xe0434352 after January SUs are installed. At this time, we do not have a workaround for the voicemail related error.
is fixed according to this comment (and the follow-up comment).
ECP does not work anymore
An administrator contacted Microsoft in this comment and reported that on several test machines, the Exchange Control Panel (ECP) stopped working after installation on Exchange Server 2013 and 2016. The following runtime error is reported.
A ticket has been created for this issue – I do not have a solution yet.
Advertising
Microsoft Exchange Service Host crashes
German blog reader Holger reported in this comment and reported a fat issue:
Exchange 2016 CU 22 on Windows Server 2012 R2 – after update "Microsoft Exchange Service Host" crashes continuously in our environment :-( – verified on 6 servers – after uninstalling everything is fine again.
In the Windows Application event log then Event ID 4999 entries are written cyclically. The cause is expired – or soon to expire certificates on the affected Exchange Server. There are other users who report this error to Microsoft on the Exchange post. A Microsoft employee then gave the tip to delete expired or soon to expire certificates.
Please do the following action, it should resolve the issue:
- Replace any expired certificate on the system
- Renew any certificate that expires in <= 30 days
Blog reader Holger confirmed in this comment that deleting outdated certificates fixed the Microsoft Exchange Service host crash problem. Holger also posted a PowerShell script there that searches for and removes the old certificates.
The DAG Bug is NOT fixed as of Exch 2019 CU 12!