Sometimes a PST file is uploaded to PST Flight Deck and processed by the repair or the extraction module, but it fails with an error that would stop the file from further processing. Generally the setup is that the file skips the repair module, and the first failures are in the extraction module.
The extraction module has an automatism that will send certain failure types through the repair automatically. If the file is not repairable, the failure will be indicated in the extraction module. In the extraction module, typical failure events are:
In the repair module typical events are:
In both the cases the operations team need to decide what to do with the file.
The normal response from the operation team is look at the file. Some files have .PST extension but are not really PST files. If the file appears to be a real PST file, it should be sent through the repair module. The repair module uses Microsoft’s ScanPST tool to repair the file. In most cases the file cannot be repaired – typical numbers from production environments will show that typically +90% of all files deemed corrupt by the extraction module couldn’t be repaired. A very small percentage (typically below 1%) of corrupt files can be opened by Outlook. It may seem strange that the Microsoft repair tool cannot repair it, but Outlook can open it. There are generally two reasons for this:
In the case where the customer wants the data ingested, some options are available. Before use the options:
If the conclusion is that the file needs to be ingested, the options are:
This requires purchasing a third party repair tool and install that to do the “repairs.”
In some cases the file can be opened in Outlook, which allows an export into a new file.
Move the file to a repair directory, or better to an alternate computer as repair load can be significant.