Good morning. I have been having some trouble getting PST files to import into EV 10.0.3 that got exported from our old Mimosa NearPoint system. We contracted with a 3rd party company called Archive1024 that has a stable of former NearPoint engineers. Their product does a mass export of all of the data from NearPoint and is creating 5 GB PST files of user archived. For example, my own export has 3 PST files.
What I am seeing is that older e-mails (those before 2/2/11) are making the PST import function crash within EV. When I import, it will first pop up a box that says "The PST Migration Server on ServerName has unexpectedly shut down. Click Next to restart migration". It then restarts and crashes again, etc.
The event log will show a few errors such as:
Enterprise Vault could not migrate an item from a PST to an archive. Check the migration report once the migration has completed.
Subject: Mail Log summary created on Thu Jan 27 04:02:03 EST 2011.
Archive Name: David
Archive ID: 1C858A7A00D52314197B806D11C277D241110000servername
Error: Catastrophic failure (0x8000ffff)
I found that our NearPoint system was updated on 2/2/11 to a new version, and there appears to have been some kind of encoding bug in the prior version of the archive. I can see that some of the older items have "Chinese-like" characters in the "from" field. There are also other e-mails that fail to import even though they appear to be normal and don't have those characters. I've been going back and forth with Archive1024 on a solution and now they are wanting to know if there is a way to get more detail as to why EV is crashing on import. I get those catastrophic errors, but they want to know if we can get what MAPI properties would be causing the crash. Any thoughts on what I could look for on the EV side?