cancel
Showing results for 
Search instead for 
Did you mean: 

PST migrator is shutting down

rasobey
Level 5

Hiya

I'm trying to import a PST but after having made around six attempts, including creating a new PST (from New-MailboxExportRequest in Exchange 2010 SP1) I'm getting frustrated with the migrator shutting down without a hint of why.

The new PST I created at least got more than 50% through before it stopped.

Is there anything I can do to find out where the problem lies? I note there is no dtrace option for PST migration issues.

The only thing in the logs is as follows:

 

Faulting application name: MigratorServer.exe, version: 10.0.1.1171, time stamp: 0x4f63aff9
Faulting module name: mspst32.dll, version: 12.0.6606.1000, time stamp: 0x4e2f95b5
Exception code: 0xc0000005
Fault offset: 0x00017b7a
Faulting process id: 0x37e0
Faulting application start time: 0x01cd7155e26a857b
Faulting application path: C:\Program Files (x86)\Enterprise Vault\MigratorServer.exe
Faulting module path: C:\Program Files (x86)\Microsoft Office\Office12\mspst32.dll
Report Id: b9edf701-dd4b-11e1-b42b-0022642a7920
 
Cheers
 
Richard
1 ACCEPTED SOLUTION

Accepted Solutions

JesusWept3
Level 6
Partner Accredited Certified
So it's actually outlook that is faulting You can DTrace the migratorserver through the command line DTrace utility You could try scanpst to check the integrity of the PST file, you could also try a repair on outlook Otherwise you might need a DTrace a long with a memory dump through ADPlus or DebugDiag etc and pass along to support
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

5 REPLIES 5

JesusWept3
Level 6
Partner Accredited Certified
So it's actually outlook that is faulting You can DTrace the migratorserver through the command line DTrace utility You could try scanpst to check the integrity of the PST file, you could also try a repair on outlook Otherwise you might need a DTrace a long with a memory dump through ADPlus or DebugDiag etc and pass along to support
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

rasobey
Level 5

Hmm. Scanpst did the job (the dtrace wasn't conclusive). Never seen a corrupted PST straight out of a mailbox export before. 

What's the easiest way to clean up the user's archive from all the failed import attempts? I was going to sync the archive using Vault Cache, delete what I don't want, and let it sync back to the server but it there a better way?

Cheers for the help!

JesusWept3
Level 6
Partner Accredited Certified

hmmm your best bet is to use the duplicate cleaner if you can
what version of Enterprise Vault are you on?

https://www.linkedin.com/in/alex-allen-turl-07370146

rasobey
Level 5

10.0.1. That sounds handy.

JesusWept3
Level 6
Partner Accredited Certified

http://www.symantec.com/business/support/index?page=content&id=TECH154803

https://www.linkedin.com/in/alex-allen-turl-07370146