Exchange Y2K22 Audit

Find Exchange Assets Affected by Y2K22

With the start of the new year, a bug in the antivirus engine of Exchange 2019 and 2016 has caused messages to get stuck in a queue. The usage of a 32-bit number in suspected to be the culprit. With the change to 2022 the value was too large for the field causing a crash. When an exchange server is stuck due to this issue, it can be identified thanks to the errors logged: Error event 5300 with the description “The FIP-FS “Microsoft” Scan Engine failed to load. PID: 23092, Error Code: 0x80004005. Error Description: Can’t convert “2201010001” to long.” Error event 1106 with the description “The FIP-FS Scan Process failed initialization. Error: 0x80004005. Error Details: Unspecified error.” You can read more about the Y2K22 bug in our Exchange Y2K22 blog post.

COPY

Show

Hide