From 7a2751653fcf5ae672250f55fa59121d1257abcf Mon Sep 17 00:00:00 2001
From: Bhalchandra Atre-MSFT <39634045+Batre-MSFT@users.noreply.github.com>
Date: Wed, 16 Mar 2022 16:11:19 +0530
Subject: [PATCH] Added public KB

Added link to the public KB in workaround steps
---
 docs/Emerging-Issues.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/docs/Emerging-Issues.md b/docs/Emerging-Issues.md
index fc91eab5f9..9284ed885e 100644
--- a/docs/Emerging-Issues.md
+++ b/docs/Emerging-Issues.md
@@ -7,12 +7,11 @@ hide:
 
 This page lists emerging issues for Exchange On-Premises deployments, possible root cause and solution/workaround to fix the issues. The page will be consistently updated with new issues found and reflect current status of the issues mentioned.
 
-**Updated on 3/10/2022**
+**Updated on 3/16/2022**
 
 **Issue** |**Possible reason**| **Workaround/Solution**
 -|-|-
-After installing [March 2022 Security Update For Exchange Server 2013, 2016, 2019](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2022-exchange-server-security-updates/ba-p/3247586), the Microsoft Exchange Service Host service may crash repeatedly with Event ID 7031 in system log and Event ID 4999 in application log. <BR><BR>  Event ID 4999 <BR> Watson report about to be sent for process id: 4564, with parameters: E12IIS, c-RTL-AMD64, 15.01.2375.024, M.Exchange.ServiceHost, M.Exchange.Diagnostics, M.E.D.ChainedSerializationBinder.LoadType, M.E.Diagnostics.BlockedDeserializeTypeException, c0e9-dumptidset, 15.01.2375.024.|The issue can occur if there are any expired certificates present on or any certificates nearing expiry on the server| Use following steps to remove the expiry certificate notifications: <BR> 1)	The user will need to have full access to arbitration mailbox. To grant it, run: <BR>Get-Mailbox -Arbitration "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}" \| Add-MailboxPermission -User administrator -AccessRights FullAccess <BR> 2)	Run [this Script](https://aka.ms/RemoveCertExpiryNotifications) from Exchange Management Shell login as the user with full permission assigned to arbitration mailbox <BR> 3)	Confirm all the messages are deleted <BR> 4) Start the service MSExchangeServiceHost and confirm that it is not Crashing <BR> 5) Revoke the full Access permission for the user by running: <BR>Get-Mailbox -Arbitration "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}" \| Remove-MailboxPermission -User administrator -AccessRights FullAccess
-After installing [March 2022 Security Update For Exchange Server 2013](https://www.microsoft.com/en-us/download/details.aspx?id=104001), where Exchange 2013 is installed in co-existence with Exchange 2016/2019: <BR> 1) Get-MailboxDatabaseCopyStatus command from Exchange 2013 server fails for databases hosted on Exchange 2016/2019 servers with following error: <BR><BR> A server-side administrative operation has failed. Operation failed with message: Error 0xe0434352 (Unknown error (0xe0434352)) from RpccGetCopyStatusEx4 <BR><BR> 2) The Exchange Admin Center may report HTTP 500 error when checking database copy status | NA | 1) Run the Get-MailboxDatabaseCopyStatus command from Exchange 2016/2019 servers <BR> 2) For Exchange Admin Center issue, make sure the mailbox of admin account is on Exchange 2016/2019 servers.
+After installing [March 2022 Security Update For Exchange Server 2013, 2016, 2019](https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2022-exchange-server-security-updates/ba-p/3247586), the Microsoft Exchange Service Host service may crash repeatedly with Event ID 7031 in system log and Event ID 4999 in application log. <BR><BR>  Event ID 4999 <BR> Watson report about to be sent for process id: 4564, with parameters: E12IIS, c-RTL-AMD64, 15.01.2375.024, M.Exchange.ServiceHost, M.Exchange.Diagnostics, M.E.D.ChainedSerializationBinder.LoadType, M.E.Diagnostics.BlockedDeserializeTypeException, c0e9-dumptidset, 15.01.2375.024.|The issue can occur if there are any expired certificates present on or any certificates nearing expiry on the server| **Update 3/16/2022** <BR><BR> Follow the steps from [KB 5013118](https://support.microsoft.com/kb/5013118) to resolve the issue | NA | 1) Run the Get-MailboxDatabaseCopyStatus command from Exchange 2016/2019 servers <BR> 2) For Exchange Admin Center issue, make sure the mailbox of admin account is on Exchange 2016/2019 servers.
   
 ## Old Issues