Event ID 4999 and mailbox transport delivery service won't start with Exchange Server 2019

Question

Hi,
After an upgrade to Microsoft Exchange Server 2019 CU11, I noticed that the Exchange mailbox transport delivery service was unable to start showing error 1068 "dependency service or group failed to start". Additionally, Microsoft Exchange Server Extension for Windows Server Backup starts and stops and returns the following event id 4999.
I followed this link and upgraded to CU 12 but to no avail.
https://support.microsoft.com/en-us/topic/event-id-4999-and-mailbox-transport-delivery-service-won-t-start-with-exchange-server-2016-cu7-installed-95162a31-715d-8115-36ad-52af4b22dd54
Can you help?
Thank you in advance.
Kind regards,
Kristian

Answer 1

@LangeMuller ,

1. Please ask if you have downloaded the corresponding security update. if not, please install the security update for Exchange 2019 CU12 and see if can help with this issue.
2. Second，please check the setup log to see if there is issue with the installation.
3. Because event id 4999 is a common error that cannot be analyzed at the moment, if you can, please provide a complete error report so that I can analyze the problem more accurately.

Besides, based on your description, the reason the Exchange mailbox transport delivery didn't start was due to the failure of the dependency service or group to start. The reason for the failure may be due to the fact that the Windows service is not started, it is recommended that you manually open the desired service. Additionally, you may receive Error 1068 if you try to open a network connection sharing. For specific solutions, please refer to the following link:

Depending on your description, whether you mean to stop immediately after Microsoft Exchange Server Extension for Windows Server Backup starts and returns event ID 4999? If the service stops, it is recommended that you manually start the service and check. Additionally, the following link is similar to yours for that issue and may be helpful to you.

Answer 2

I have found similar threads. I hope, it will help you:
https://social.technet.microsoft.com/Forums/en-US/e7e3d0e7-049e-415e-9b83-f7d486465a9d/event-id-4999?forum=Exch2016Adm
https://social.technet.microsoft.com/Forums/en-US/de390af9-d7b9-4f6d-97e2-0b9da20e43a8/exchange-2013-event-id-4999-ms-exchange-common-watson-report-about-to-be-sent-for-process-id?forum=exchangesvradmin

Also check this blog for help - How to Fix the Exchange Error 4999?