Error Message

• 3rd Party Software interference
• Accidental Closure of the Enterprise Vault Admin Console
• Crash of MMC.exe service during the Exporting of PST from Email archives

1. Look in the Folder where you have exported the archives to PST, for any ~TMP files,  this indicates the export is still running.  These ~TMP files indicate that the exports are still successfully running, and should be allowed time to finish.  Time needed depends on the size of the pst being created.
    
2. If no temp files are seen, this indicates that the jobs are completed.  A 6769 event would be thrown in the Enterprise Vault event log. 
3. However, if no 6769 event is thrown after the export has been running longer than expected, follow these steps in Windows Task Manager:
   1. If there were multiple exports running at the same time (with separate Export Archive wizards launched), there will be multiple PID’s for MigratorServer.exe within Task Manager.  Locate each one, and confirm how much CPU is being utilized by them.
   2. If and ONLY if any PID's are using 0 CPU, then manually stop them by right-click and select "End Process." 
   3. Once you end those particular MigratorServer.exe Processes using 0 CPU,  a 6769 Event (Figure 1 and 2) will be generated within the Enterprise Vault Event Log, for Each archive processed by the job.
   4. Any MigratorServer.exe threads still utilizing CPU will need further time to complete work and should not be stopped manually.

Figure 1



Figure 2

NOTE:  If the export(s) did not complete it may be necessary to re-run the export from the beginning as a new export.