Error Message

From PST_Retriever_output.log:
2023-07-24 11:48:59,172 [8996] ERROR BufferManager null - Message writing to PST store failed with Unknown Exception: esa:pst/*:\\edp-lab-server\d\Case Data\TestData\Mike Brown\Archive\Exported_Data_01.pst:00000000433f9dd8ef3aa04fbe9403076c12dafd645e2200: ::0700853dc5a1969df91480cab79060e74c758cbfd07899e31662aada6dfb879ecf74 setting error code:14928

PST File corruption. 

1.  Go to the Clearwell logs folder.  Usually D:\CW\V###\logs. 

Example:

2.  Open the PSTRetriever_output.log file
3.  Search for the term ERROR
4.  If an error is found similar to the above saying "ERROR BufferManager null - Message writing to PST store failed with Unknown Exception" followed by a path to a PST file path/file name, then run the Microsoft tool called scanpst.exe against the reported pst file path/file name listed in the error.
5.  Rerun the export.

Note 1:  You may need to run scanpst.exe against the identified PST file more than once to fully repair it..  Microsoft recommends 5 times because the tool does not always fix every issue on 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

Note 4:  After the PST file(s) mentioned in the log is corrected and running the export again, the job could get further along and may run into another corrupted PST file and the steps above will then need to be repeated.