Troubleshoot the Exchange Migration Wizard
Topic Last Modified: 2006-09-14
The migration process consists of two key phases:
- Extracting messaging data and recipient information from the source messaging system into temporary migration files You can take a number of steps to increase the chances of a complete and successful migration. Reducing the amount of data to be migrated from the external system before beginning migration is an excellent strategy. Old data can be purged from the Domino environment if users are asked to empty their mail databases and calendars of outdated data. You can also configure the Exchange Migration Wizard to select only data from a more recent time period and only from active user accounts.
- Importing the messaging data from temporary migration files into an Exchange mailbox store and importing recipient information into Active Directory For optimum performance, move the migration files to the hard disk drive of the computer running the Exchange Migration Wizard. If errors occur during the import of migration files, the Exchange Migration Wizard logs errors to the application event log and import might stop. If import continues, the error is written to a recovery file in the Temp directory.
The following problems are typical and can prevent a successful extraction of data from the source system using the Exchange Migration Wizard:
- Insufficient access rights for the migration account For the Exchange Migration Wizard to successfully migrate doclinks from user mail databases, the connector's Notes user ID must have Reader access to all users' mail databases.
- The Exchange Migration Wizard stops responding during data extraction The Exchange Migration Wizard uses Lotus Notes software components to communicate with the source system. Ensure that you use the a proper version (Lotus Notes 6.x) and include the client executable directory in the system search path.
- Source mail databases are corrupted Corrupted items in source mail databases can cause the Exchange Migration Wizard to report problems during the extraction process. It is recommended that you run FIXUP on users' mail databases prior to starting the Exchange Migration Wizard.
The following problems are typical and can prevent the successful import of data into a Microsoft® Exchange Server 2003 organization using the Exchange Migration Wizard:
- Insufficient access permissions To successfully import messaging data and recipient information into an Exchange Server 2003 organization, you must be an Exchange Full Administrator in the target administrative group and an account administrator in the target Active Directory® directory service domain or organizational unit.
- The DLL Mmfmig32.dll cannot be found You might encounter this problem if you install Microsoft Office XP or Outlook® 2002 on the computer that you use to run the Exchange Migration Wizard. Office XP or Outlook 2002 might delete the correct Mmfmig32.dll file and copy an earlier version to the computer. To work around this problem, use one of the following procedures:
Install Outlook before you install the Exchange Migration Wizard. This ensures that the Mmfmig32.dll file is placed in the Program Files\Exchsrvr\bin folder, which is required for the Exchange Migration Wizard to function correctly.
Before you install Outlook on the computer, copy or move the Mmfmig32.dll file from the Winnt\System32 folder to a temporary location on the server. After installation, copy or move the Mmfmig32.dll file that you moved from the temporary location back to the Winnt\System32 folder.
Copy the Mmfmig32.dll file from the Program Files\Common Files\System\Mapi\1033 folder to the Program Files\Exchsrvr\bin folder.
- Install Outlook before you install the Exchange Migration Wizard. This ensures that the Mmfmig32.dll file is placed in the Program Files\Exchsrvr\bin folder, which is required for the Exchange Migration Wizard to function correctly.
- Data inconsistencies in migration files To import data into Exchange Server 2003, the Exchange Migration Wizard reads the packaging list file that is created during data extraction to determine which migration files to process. The following is an example of a packaging list file:
Every pair of primary (.pri) and secondary (.sec) files corresponds to a user who is being migrated. If a migration cycle fails because the Exchange Migration Wizard cannot process a user, you can edit the packaging list file to exclude the primary and secondary files for that user from the migration process. You can also edit the primary file to detect and correct any problems. Both the packing list and the primary files are comma-separated values (.csv) files.
Note: Do not edit secondary files. These files contain the raw data and checksums. Adding or removing even a single character from the secondary file can cause errors when you later import the data.