Error Message

From PSTFileScan_output.log (Example log entry from Veritas Lab):
2023-05-24 18:01:32,219 ERROR [MailFileScan] (18868:null)  File:\\edp-app1-lab\F\Test\Test Email 2\TestSubFolde\PST Files\Test_User\tuser-User,Test.pst has timed out after seconds:3601. Exiting the Scan process with error code -1

Event IDs 2000 and 1000 can be seen in Windows Application Event Log (Examples from Veritas Lab):
Source:  Outlook
Event ID:  2000
Level:  Error
Database corruption was detected and the process was terminated.
Process: "" (65ac.5f1c)
Version: 16.0.10373.20050
File: "\\?\UNC\edp-app1-lab\F\Test\Test Email 2\TestSubFolde\PST Files\Test_User\tuser-User,Test.pst"
Last: "D:\CW\V101\exe\pst\PSTScan.exe"
Database Version: 23 (2)
Context: 10037001
Details: 
BCRead(@9724800): Expected (bid=19A90,cb=8176,dwCRC=E10B44A6,wSig=DBE3), but read (bid=19A90,cb=8176,dwCRC=0B554FCC,wSig=DBE3)

Source:  Application Error
Event ID:  1000
Level:  Error
Faulting application name: PSTScan.exe, version: 0.0.0.0, time stamp: 0x6332b4b3
Faulting module name: mspst32.dll, version: 16.0.10375.20036, time stamp: 0x60b05246
Exception code: 0x80040813
Fault offset: 0x000d196d
Faulting process id: 0x65ac
Faulting application start time: 0x01d98e8b19b97eeb
Faulting application path: D:\CW\V101\exe\pst\PSTScan.exe
Faulting module path: C:\Program Files (x86)\Microsoft Office\Root\Office16\mspst32.dll
Report Id: 9ee277bd-a78d-4a2b-8be8-095081e0bf67
Faulting package full name: 
Faulting package-relative application ID: 

PST file corruption causing Microsoft Outlook to fail throwing event ID 2000 in the Windows Application Event Logs.  This then causes eDP Process called PSTScan.exe to abnormally terminate throwing event ID 1000.

1. Make a backup of the PST file identified in the Event ID 2000.
2. Run Microsoft's tool called scanpst.exe against the identified PST to correct the corruption.
3. When complete rerun Email Checksums support feature tool again.  Running again should get further along to completion or identify another PST with corruption.  Work through each performing steps 1-3 until all corrupted PST files have been fixed and email checksums job completes successfully.

Note 1:  May need to run scanpst.exe against the identified PST file more than once to fully resolve.  Microsoft recommends 5 times because the tool does not always fix every issue in the first attempt.

Note 2:  Microsoft Office 2016 and newer has a new version of the scanpst.exe tool that can be run from command line with parameters making it scriptable.  For more information see https://learn.microsoft.com/en-us/outlook/troubleshoot/data-files/inbox-repair-tool-scanpst-exe-run-multiple-passes

Note 3:  At times scanpst.exe may not be enough to fix the issues with PST files and may require a third party tool such as Stellar Outlook PST File Recovery Tool.  More details about this tool can be found here https://www.stellarinfo.com/outlook-pst-file-recovery.php?msclkid=28c8df0e30301d20a72dbbcdd79224f7