148Chapter 7 Meridian Mail to CallPilot migration troubleshooting
Diagnostic steps | Resolution | ||
2 | On Meridian Mail, check if the user | F | If the user has a mailbox number that is |
| has a mailbox number that is less |
| less than three digits in length, perform |
| than three digits in length. You can |
| one of the following tasks: |
| also check the migration transaction |
|
|
| log file (MigTransaction.log) in the |
|
|
| D:\nortel\MPCX\Migration\ folder on the |
| • Change the user mailbox number to |
| CallPilot server. |
| a |
|
|
| collect user data from Meridian Mail. |
|
|
| Perform the user migration again. |
Note: CallPilot does not support mailbox
numbers that are less than three digits in
• Use CallPilot Manager to add
length.
system. Refer to the CallPilot Administrator’s Guide.
Check the migration transaction log file.
3Check the migration transaction log file (MigTransaction.log) in the D:\nortel\MPCX\Migration\ folder on the CallPilot server to determine if the user was migrated successfully.
4Check the Meridian Mail log file. View it from the Meridian Mail→Tools menu.
GIf the user was migrated successfully, check the CallPilot system sanity. If the user was not migrated, perform one of the following tasks:
•Again collect user data from Meridian Mail after correcting the user property or any other errors depending on the CallPilot migration log information.
Perform the user migration again.
•Use CallPilot Manager to add
5 | Does the problem still exist? | H Contact your Nortel technical support |
|
| representative for assistance. |
|
|
|
Nortel CallPilot
Troubleshooting Reference Guide
5.026 June 2007