The anti-malware scan engine encounters an error when converting the value “2201010001” to a long integer value, so that the process in question can no longer be loaded.
When converting the string to a signed integer value, an overflow occurs with the error code 0x80004005. The error description that will be written in the log files under the PID 10816 reads: Can’t convert “2201010002” to long.
A number of people have been reporting this issue, it appears that the problem is occurring under various Exchange Server versions and different patch levels. However, not all on-premises Exchange Servers are affected – it is suspected that the anti-malware scan or mail filtering is not active on unaffected systems.
There are several approaches to solve this problem.
There are several approaches to solve this problem. For Exchange Server, one of these options is a temporary workaround is to disables the scan engine. To do this you have to run the PowerShell script Disable-AntiMalwareScanning.ps1 . After that, some users had to restart the Transport service or even the Exchange server.
Alternatively, the following PowerShell command can be used to temporarily disable mail filtering:
Set-MalwareFilteringServer exch-19 -BypassFiltering $true
Again, the transport service will probably have to be restarted afterwards.
Another way to fix this bug – with the prerequisite of an Exchange Server 2016 with the latest Cumulative Update – is to execute the command Get-TransportAgent “Malware Agent” | Disable-TransportAgent with which mail receiving and sending works again. Microsoft has collected some information about this topic in the article Disable or bypass anti-malware scanning
With XEOX there is a simple solution to solve this problem on all your servers.
After logging in, you need to navigate to your dashboard and select the Scripts directory under “Job Center”.
Afterwards go to the “Script Library” to the script Exchange Y2K22 Bug Temporary Fix 01.Jan.2022
Now use the ” Copy to MyScripts” button to add the script to system.
To run the script go to the “My Scripts” tab, select the appropriate script and press Run. After that a Pup-up window will open. At the function “Selected Hardware” enter #SERVER and press the button Next on the right bottom of the window.
After following all the steps above, you should be able to fix the error temporarily. If you have problems following any of the steps, you can contact us at email@example.com.
Microsoft has already released a signature update to fix the problem. However, other administrators report that this does not solve the problem. An official statement from Microsoft is still pending.
Microsoft delivers another fix for Exchange Y2K22 bug