Troubleshooting Common Error Codes Related To Enterprise Vault (EV) .PST Migration

Problem

Troubleshooting Common Error Codes Related To Enterprise Vault (EV) .PST Migration

Solution

The following is a list of the 4 different PST migration methods used to import PST's from an environment into Mailbox archives:

  1. Server-side Locator, Collector and Migrator Tasks
  2. Server-side PST Migration wizard
  3. Client-driven PST migration
  4. Enterprise Vault Policy Manager (EVPM)

Below is a list of common error codes that span different root causes.
 


I - 0x8004011D - The server is not available.
     Often occurs when any of the following conditions are true
 

  1. Partial Outlook synchronization with Exchange - http://support.microsoft.com/kb/289971/EN-US
     
  2. DNS issues: As a test, add an entry to the 'hosts' file on the computer hosting the PST file for the Exchange server, see if that solves that problem. If it does, then troubleshoot DNS.
                   Note: If name resolution is affecting only one machine, just leave the entry in the hosts file just as a backup until the issue is resolved.
     
  3. Latency problems on LAN or VPN connections: The ping and traceroute commands are widely used to identify latency problems on networks.
                   Note: Investigate Ethernet duplex modes at the port on the switch and NIC card on the machine hosting the PST.
     
  4. Profile problems: To delete the Exchange profile in Outlook and then recreate it sometimes will correct the problem. You can also try recreating the entire Windows user profile.
     
  5. Local computer firewall: If active try to disable the local firewall on the machine where the PST file is located and attempt the migration again.
     
  6. Local computer antivirus program: Try to exclude real-time scanning on the directory where the problem PST file is located
  7. Insufficient resources on the vault server.  This includes memory, paging file and/or sufficient space available in the TEMP directory.

II - 0x80070005 - Access is denied.
 

  1. "Read-Only" attribute: Change the Read-Only restriction on the problem PST files - http://support.microsoft.com/kb/326549
     
  2. Permissions issue: The Vault Service Account, or the service account set for the EV PST Migrator Task to run under might lack sufficient permissions to the PST owner's mailbox or to the PST file itself. The required permissions are listed in the EV Installation and Configuration or Administrators Guides under document 277782 at the bottom.
     
  3. Other Outlook issues: Such as mailbox over the quota limit or try to re-enter the password. 
     

III - 0x80070020 or 0x800CCC0F - Sharing violation.
 

  1. Timing issue: Can occur if another program or application is interfering with the EV PST Migrator process. For example; antivirus programs that use real-time scanning, antispam scanners, Windows Update, real-time backups of system files, e.t.c. Temporarily disable or modify the intrusive application settings accordingly. Restart the computer hosting the problem PST files.
  2. Incorrect PST tagging or marking: Can occur if the problem PST files were incorrectly tagged or marked and therefore, the destination archive would be wrong so the migration process fails on them. This can be manually corrected by matching them to the true owner's mailbox label. Sometimes simply waiting for the intrusive program to release the handles on the PST files and then attempt migration later could solve the problem.

    Note: For more information on PST marking please refer to the EV Installation and Configuration or Administrators Guides
     

IV - 0x80040600 - MAPI_E_CORRUPT_STORE.
 

  1. Incorrect PST tagging or marking: Refer back to point III(b) above.
     
  2. File access restricted: The problem PST file could be either encrypted or password protected.
     
  3. These errors are sometimes caused by the 2GB limit which applies to ANSI format PST files created using Outlook 2002 and earlier. To work around the issue, the content of the PST file that is failing must be exported to a Unicode PST so that the 2GB limit no longer applies. The Unicode PST can then be migrated by any PST migration methods mentioned at the top.
     
  4. File corruption: Clear the "Deleted Items" folder and use the "Inbox Repair tool" to analyze and repair the problem PST file - http://support.microsoft.com/kb/814441

Note: At the time of writing this document, the existing Inbox Repair tool version does not work on PST files larger than 2 GB (gigabytes).
 

V - 0x80040119 - MAPI_E_EXTENDED_ERROR. 
 

  1. Misplacement: Often occurs because a PST was moved and the EV Migrator process will attempt to follow the earlier specified file path, hence the error. Manually reconcile the problem PST location path in Outlook or use PST repair tools to automate this task - http://www.pstfilerepair.com/0x80040600.php  and http://support.microsoft.com/kb/814441

 

VI - 0x80040111 - MAPI_E_LOGON_FAILED
 

  1. This is a very rare MAPI error during PST migration. Can be caused if there is a duplicate mailbox alias (Mixed or Pure Exchange environments).Investigate the issue further via Exchange diagnostic logging tools and correct the duplicate mailbox aliases. If no duplicate mailbox aliases found then concentrate on permissions related issues on Exchange.
 

 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)