If event 5003 is logged after a server restart and the Exchange information storage service (MSExchangeIS) cannot be started, the cause is usually that the time between the DC and the Exchange server is too different.
In vmWare environments, this can be caused by the time being synchronized with the ESX host and not with the DC. This behavior can be switched off in the vmWare tools
After the check mark has been removed, the time can be synchronized from the DC with the following command:
Net time \\DCNAME /Set
Danach muss noch der Dienst „Microsoft Exchange Active Directory-Topologie“ neugestartet werden. Wenn noch nicht geschehen kann dann der Dienst „Microsoft Exchange Informationsspeicher“ gestartet werden.