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
Still stuck with this
Script generates error “WARNING: Unable to process update request because engine metadata is not available. Attempting to synchronize” metadata. Please try to run the cmdlet again later.
- Copy msvcr110.dll from c:\windows\system32 to %ProgramFiles%\Microsoft\Exchange Server\V15\FIP-FS\Bin and %ProgramFiles%\Microsoft\Exchange Server\V15\Bin
- Restart the Exchange server
- Re-run the script
I do not have a proxy and this does not work.
I have downloaded the files to a local drive and tried and also get the same error even when running on elevated prompt.
I am not alone looking at above, has anyone got a solution other than bypassing by disabling the antispam.
I also get this when I run
$env:ExchangeInstallPath\Scripts\Enable-AntimalwareScanning.ps1
WARNING: Unable to process update request because engine metadata is not available. Attempting to synchronize metadata. Please try to run
the cmdlet again later.
Get-ValidEngines : Could not open local universal manifest
At C:\Program Files\Microsoft\Exchange Server\V15\Scripts\Enable-AntimalwareScanning.ps1:47 char:1
+ Get-ValidEngines | ForEach-Object { if($_.Categories[0] -eq "Antiviru ...
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-ValidEngines], EngineMetadataException
+ FullyQualifiedErrorId : Microsoft.Forefront.EngineUpdates.Service.EngineMetadataException,Microsoft.Forefront.Filtering.Management.P
owerShell.Commands.GetValidEngines
Someone must know how to fix this, it only happens on a fully updated Exchange 2019?
All the Exchange 2016 servers worked fine
The_Exchange_Team help
Thanks