Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Faulting application name: MigratorServer.exe

Created: 17 Oct 2012 • Updated: 09 Nov 2012 | 8 comments
This issue has been solved. See solution.
Yesterday, I completed a migration from 9.0.3 to 10.0.2 on new 64-bit hardware. I have been chasing down various error messages, but this morning, I got the following in the event log:
 
Log Name:      Application
Source:        Application Error
Date:          10/17/2012 11:44:27 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxx
Description:
Faulting application name: MigratorServer.exe, version: 10.0.2.1112, time stamp: 0x5050ef0d
Faulting module name: EVPstApi.dll, version: 10.0.2.1112, time stamp: 0x5050ee54
Exception code: 0xc0000005
Fault offset: 0x00023a99
Faulting process id: 0x3124
Faulting application start time: 0x01cdac7e2190aaff
Faulting application path: C:\Program Files (x86)\Enterprise Vault\MigratorServer.exe
Faulting module path: C:\Program Files (x86)\Enterprise Vault\EVPstApi.dll
Report Id: 87f271b5-1871-11e2-8374-00155d010300
 

Any ideas what would cause this?

Thanks

Doug

Comments 8 CommentsJump to latest comment

ManishN's picture

If you are not using Migration Wizard then probably it's vault cache.

We need to understand the reason for this crash and if you could collect a dump using ADPlus it would help you alot.

You can use the following article for ADPlus

http://support.microsoft.com/kb/286350

Regards,

MN

dglasgow's picture

Any idea what mode to run the adplus? The crash only happened once this morning. I have not seen it again yet.

Rob.Wilcox's picture

Another question ... which version of Outlook (and service pack) have you got on the EV server?

Rob.Wilcox's picture

You'll need to run it in -crash mode.  But in order to do that you'll need the process to be running... and it's not always running.

JesusWept3's picture

use DebugDiag and set it to look for c0000005, then just set it and forget it, and once it occurs it will have produced the memory dumps, but even then you are going to have to open a support case with symantec

SOLUTION