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
After half an hour the checking ... updating ... cycle is finished. I restarted transport service. Stopping phase was fine but starting phase had:
The service did start. But mails are stuck in transport queue again.
Checking the version again:
It has been updated to 0098 but is still 21...
Anyway, try to use the automated script.
[PS] C:\Windows\system32>Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
http://go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "N"): Y
[PS] C:\Windows\system32>cd c:\scripts
[PS] C:\scripts>.\Reset-ScanEngineVersion.ps1
Do you want to run software from this untrusted publisher?
File C:\scripts\Reset-ScanEngineVersion.ps1 is published by CN=Microsoft Corporation, O=Microsoft Corporation,
L=Redmond, S=Washington, C=US and is not trusted on your system. Only run scripts from trusted publishers.
[V] Never run [D] Do not run [R] Run once [A] Always run [?] Help (default is "D"): R
[server] UpdateVersion: 2112330098
[server] This server is not impacted. Add -Force to proceed anyway.
The_Exchange_Teamshould I go with the -Force?