Migration	<<	>>

Troubleshooting Errors

If errors occur during the import of migration files, the Migration Wizard logs errors to an application log and importing may stop. If importing continues, the error is written to a recovery file. A recovery file is created each time files are imported. The recovery files are written into the temp directory of the computer running the Migration Wizard.

Therefore, if an error occurs, first check the application log and the recovery file. One error in the file format can cause multiple or cascading error messages. If the error can't be found in the line with the error report, an error in a previous line might be causing the problem, or there may be an improper offset to the secondary file.

If it's a primary file error, you can edit this file and fix the problem. If it's 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.

File Processing If you understand how the Migration Wizard processes the files, you can troubleshoot problems. The 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.

Section Processing

Directory Every line after the directory header line until the start of the next section is passed to the directory import dynamic link library one line at a time.

PAB Each line of PAB data is read. After all lines are read, a message is created.

MailMessage If the mailbox does not exist, it is created, if possible by custom recipient conversion. If a message is for public folder, it is created if necessary with appropriate permissions.
For each line, a message is created. The secondary file is checked for body and attachments. If body is empty and there is a document, the attachment to mailbox is copied as a free document. If body is empty and there is a schedule file, the body is supplied by the Migration Wizard and the attachment is added.

Section	Processing
Directory	Every line after the directory header line until the start of the next section is passed to the directory import dynamic link library one line at a time.
PAB	Each line of PAB data is read. After all lines are read, a message is created.
MailMessage	If the mailbox does not exist, it is created, if possible by custom recipient conversion. If a message is for public folder, it is created if necessary with appropriate permissions. For each line, a message is created. The secondary file is checked for body and attachments. If body is empty and there is a document, the attachment to mailbox is copied as a free document. If body is empty and there is a schedule file, the body is supplied by the Migration Wizard and the attachment is added.