Use the information in this section to identify and solve problems with migration by scrutinizing the migration files. For more information on specific problems you may encounter running Migration Wizard with respect to your specific messaging system, search the Microsoft Support Knowledge Base, or use Exchange troubleshooters.
Migration Wizard stops when importing migration files.
If it is a primary file error, you can edit this file and fix the problem. If it is a secondary file error, you get a pointer to the problem, which you can attempt to fix. If you must edit the secondary file, make a backup first. Be careful not to change the offsets of later sections. After all problems are fixed, you can create a new packing list file that lists the primary and edited (not original) secondary files.
If you understand how Migration Wizard processes files, it will help you troubleshoot problems. Migration Wizard first reads the packing list file and then starts processing the first primary file. The following table describes how each primary file is processed.
|DIRECTORY||Every line after the directory header line, until the start of the next section, is passed to the Migration Wizard, one line at a time.|
|PAB||Each line of PAB data is read. After all lines are read, a message is created with the PAB attached to the message and some text.|
|MAILMESSAGE||If the mailbox does not exist, it is created, if possible by conversion of a contact. If a message is for a public folder, it is created with appropriate permissions. For each line, a message is created. The secondary file is checked for body and attachments. If the body is empty and there is a document, the attachment to mailbox is copied as a free document. If the body is empty and there is a schedule file, Migration Wizard supplies the body and the attachment is added.|
This section contains the following topics: