Troubleshooting the Exchange Migration Wizard

  • Article

 

The Exchange Migration Wizard is the primary tool for migrating users and data from non-Exchange messaging systems to Exchange 2003.

Important

For more information about troubleshooting guidance for interoperability between Lotus Notes R5/R6, Exchange Server 2003, and Windows Server 2003 Active Directory, see Resources for Moving to the Microsoft Collaboration Platform.

As explained in Understanding Interoperability and Migration in Exchange Server 2003, the migration process consists of two key phases:

  1. Extracting messaging data and recipient information from the source messaging system into temporary migration files   You can take a number of steps to increase your 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 files can be purged from the foreign system, and users can be asked to empty their mailboxes 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.

  2. 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.

Troubleshooting the Data Extraction Process

The following are typical problems that 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 extract messaging data from user mailboxes, the migration account that you use to access the source system must be granted appropriate access rights. For example, GroupWise users must grant all appropriate proxy access rights to the GroupWise migration account and the account must be local to the post office that you are migrating. Some messaging systems, such as Microsoft Mail for PC Networks, grant the post office administrator full access to all mailboxes.

  • The Exchange Migration Wizard stops responding during data extraction   The Exchange Migration Wizard uses non-Microsoft software components to communicate with the source system. For example, you must have a Novell GroupWise client installed on the local computer when migrating Novell GroupWise users. Ensure that you use the proper versions of the software, and include the client directory in the system search path.

  • Source mailboxes are corrupted   Corrupted items in source mailboxes can cause the Exchange Migration Wizard to report problems during the extraction process. It is recommended that you check the source mailboxes using the database tools provided with the source messaging system prior to starting the Exchange Migration Wizard. For example, when you are migrating from Novell GroupWise, run the GroupWise messaging database repair tool, GroupWise Check (GWCheck), available from Novell.

Troubleshooting the Data Import Process

The following are typical problems that can prevent the successful import of data into an Exchange 2003 organization using the Exchange Migration Wizard:

  • Insufficient access permissions   To successfully import messaging data and recipient information into an Exchange 2003 organization, you must be an Exchange Full Administrator in the target administrative group and an account administrator in the target Active Directory 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.

  • Data inconsistencies in migration files   To import data into Exchange 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:

    ! CodePage
1252
! HeaderLine
Filename,Filetype
Directory.PRI,Primary
00000001.PRI,Primary
00000001.SEC,Secondary
00000002.PRI,Primary
00000002.SEC,Secondary

    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. The following is an example of a primary file for a Novell GroupWise user:

    ! Migration Type

    MAILMESSAGE,GWise:CONTOSO_DOM.CONTOSO_PO.admin,admin

    ! HeaderLine

    Folder,Sender,To,Cc,Bcc,Subject,Send-Date,Received-Date,Priority,Unread,Unsent,Body,Level,Position

    Inbox,,,,,,,,,,,,0,0

    Inbox,Exchange Test[GWISE:Exchange.First Administrative Group.Administrator],NGWAPI,,,API Gateway Test,20031119172100,20031119172100,0,FALSE,FALSE,#00000001.SEC(66),0,0

    Inbox,Ted Bremer[GWISE:CONTOSO_DOM.CONTOSO_PO.Ted],admin[GWISE:CONTOSO_DOM.CONTOSO_PO.admin]; Administrator[GWISE:Exchange.First Administrative Group.Administrator],,,This is a message,20031119210624,20031119210624,0,TRUE,FALSE,#00000001.SEC(532),0,0

    Inbox,,,,,,,,,,,,0,0

    Inbox,,,,,,,,,,,,0,0

    Documents,,,,,,,,,,,,0,0

    Work In Progress,,,,,,,,,,,,0,0

    Cabinet,,,,,,,,,,,,0,0

    Sent Items,admin,Exchange.First Administrative Group.Administrator[GWISE:Exchange.First Administrative Group.Administrator],,,API Test Message,20031119172104,20031119172104,0,FALSE,FALSE,#00000001.SEC(717),0,0

    Sent Items,admin,Ted Bremer[GWISE:CONTOSO_DOM.CONTOSO_PO.Ted]; Administrator[GWISE:Exchange.First Administrative Group.Administrator],,,Re: This is a message,20031119210701,20031119210701,0,FALSE,FALSE,#00000001.SEC(967),0,0

    Sent Items,,,,,,,,,,,,0,0

    Inbox,GroupWise,,,,Migrated Calendar Information,,,0,TRUE,FALSE,#00000001.SEC(1235),0,0

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.