Forum Discussion

Anuradha_Tondam's avatar
Anuradha_Tondam
Level 5
18 years ago

PST Migrator Issue...

Hi, We have been using the PST Migrator to import PST mail to archive vault with no problems until now. This specific PST file, size close to 2 GB is causing errors and is not getting archived. ...
Enterprise Vault
Information Governance
  • TonySterling's avatar
    TonySterling
    18 years ago
    There was a hotfix for sp1 that fixed an issue w/ PST migrator. It was fixed in sp2 and sp3 has the fix as well. Can you upgrade to sp3?

    If not, you can contact support to see if you can get the hot fix.

    Cheers,
Amanda_H_'s avatar
Amanda_H_
Level 4
18 years ago
You can have corrupt messages in a .pst file and still be able to open the .pst. You might not even notice a problem till you tried to access that specific .pst. So I would start by running scanpst on it to check for errors. In my experience scanpst doesn't always catch all the errors so if you have a lab, you can import that pst to a non-production, empty mailstore then run an isinteg on it, then export it back out and return it to production and try again. PST's do some kooky stuff sometimes! I would also check into the MS tool that truncates oversized PST's as I find that 2GB limit isn't really set in stone--- sometimes a PST will do goofy stuff at 1.7GB or higher and truncating it cures it. I can't remember the name of the tool but it's on the MS site, search for PST 2GB (that might even be the name of it) and you'll find it.