How to temporary fix your on-premise exchange servers for the Y2K22 Problem

At the turn of the year, numerous Exchange servers around the world go on strike because the FIP-FS scan engine is getting hung up on the year. All the same, there is a temporary workaround.

Converting the date value goes wrong

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.

Workaround: Disable Antimalware Scanning

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

How to fix it using XEOX

With XEOX there is a simple solution to solve this problem on all your servers.

  1. The first thing you need to do is log-in with your XEOX account.
  2. After that you have to select the appropriate script from the library and copy it to your “My Scripts”.
  3. Finally you have to run the script on your servers.
Step by step explanation:

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 support@xeox.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.

Read also:
Microsoft delivers another fix for Exchange Y2K22 bug

BLACK WEEK Special at XEOX!

This is your chance to make the most of our special deal and transform your experience with our services. 

Our Black Week Special at XEOX kicks off today!

20% Discount

 on your First Year Subscription!

From November 20th to November 27th, we are offering an incredible 20% off on all new subscriptions for the first year.

Whether you’ve been considering joining the XEOX family or looking for an opportunity to save, now is the perfect time.

Subscribe to our newsletter!

Get all latest news, exclusive deals and updates + free 30 day XEOX trial.