jd987
asked on
Corruption of .pst Outlook Files with Outlook 2013
Outlook 2013 crashes about once a week. I can usually resolve this by running the Outllok Inbox Repair Tool. I make a copy of my .pst every two days for security. Outlook crahsed this morning, I have run the Repair Tool with apparent success ("Repair Finished"). Outlook will however not restart and continues to indicate that the .pst is corrupt.
Can anyone please suggest either:
1. A long term solution? or
2. A robust utility to repair my current corrupt .pst file?
Thank you.
Can anyone please suggest either:
1. A long term solution? or
2. A robust utility to repair my current corrupt .pst file?
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
How large is your PST file? Normally it is recommende to keep the PST file size <= 10GB. If you have 30 GB data, it is recommended to split the data into 3 files, for example, move some large folders to a separate PST file.
It is not a good practice to repair the PST file frequently, instead, you should prevent the corruption. Below is some tips on how to do this:
http://www.datanumen.com/a
It is not a good practice to repair the PST file frequently, instead, you should prevent the corruption. Below is some tips on how to do this:
http://www.datanumen.com/a
If you are facing problem of PST corruption, then you can take help of PST Repair tool which can quickly recover your all data from PST files. The tool is supported by all versions of MS Outlook. Read more: http://www.pstfix.com
ASKER
Thank you. My .pst is around 5GB.
I found the problem. The .pst was stored on an encrypted partition using Symantic PGP. The encryption utility was corrupting the .pst file. I have temporarily resolved the problem by moving the file to a non-encrypted partition.
I found the problem. The .pst was stored on an encrypted partition using Symantic PGP. The encryption utility was corrupting the .pst file. I have temporarily resolved the problem by moving the file to a non-encrypted partition.
ASKER