We have addressed the issue causing messages to be stuck in transport queues of on-premises Exchange Server 2016 and Exchange Server 2019. The problem relates to a date check failure with the change ...
Updated Jan 11, 2022
Version 36.0
Blog Post
AhmadBilal We got the same problem. Unfortunately your solution/workaround did not work for us.
On our server the installation path is: D:\ExchangeServer\
We placed the msvcr110.dll in the following directories:
C:\Program Files\Microsoft\Exchange Server\V15\bin (we created the folder bin, since that one did not exist before)
D:\ExchangeServer\Bin
D:\ExchangeServer\FIP-FS\Bin
After restart still the error:
[PS] D:\exchangeserver\scripts>.\Update-MalwareFilteringServer.ps1 *fqdn*
Wird als "*Domain\Admin" ausgeführt.
--------
Verbindung mit "*fqdn*" wird hergestellt.
WARNUNG: Unable to process update request because engine metadata is not available. Attempting to synchronize
metadata. Please try to run the cmdlet again later.
Remotebefehl gesendet. Start-EngineUpdate -UpdatePath http://amupdatedl.microsoft.com/server/amupdate
--------
[PS] D:\exchangeserver\scripts>Get-EngineUpdateInformation
Engine : Microsoft
LastChecked : 01.03.2022 10:29:47 +01:00
LastUpdated : 03.20.2020 01:55:31 +01:00
EngineVersion : 1.1.16800.2
SignatureVersion : 1.311.1596.0
SignatureDateTime : 03.20.2020 07:24:29 +01:00
UpdateVersion : 2003200003
UpdateStatus : UpdateAttemptFailed
Does anyone have a solution?
Happy new year 🙂