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
Ah, yes, your scanner version on the first screenshots show the old version. When the script died from 'divide by zero' error, it was caused from this line:
90: $percentComplete = ($transfer.BytesTransferred * 100 / $transfer.BytesTotal)
It essentially finished the download according to the status bar display. Checking the version on the scanner shows the correct version, and that there is no update needed.
Restarted the transport has mail working, lots of your email was delayed coming in, but everything is flowing...
Engine : Microsoft
LastChecked : 01/02/2022 11:14:40 AM -08:00
LastUpdated : 01/02/2022 10:35:08 AM -08:00
EngineVersion : 1.1.18800.4
SignatureVersion : 1.355.1227.0
SignatureDateTime : 01/01/2022 03:29:06 AM -08:00
UpdateVersion : 2112330001
UpdateStatus : UpdateAttemptNoUpdate