MAPI errors during migration (4264496)

MAPI errors during migration

MAPI errors during migration

MAPI retry features expanded: The tool's MAPI retry features, introduced in version 4.6 as a way to improve performance in environments with occasional MAPI communications/connectivity issues, have been expanded to include all ConfigureMsgService calls. These features control MAPI retries when certain errors are encountered, and are configured by program parameters in the [Exchange] section of Task Parameters and Global Defaults:
[Exchange]
MessageRetryCount=<#>
MessageRetryWait=<##>
MAPIErrorsToRetry=<########>

//  integer (number of retries), default=3
//  integer (seconds), default=10
//  string (MAPI error code/s, comma delimited), default=80040115,80040125

The MessageRetryCount parameter tells the Data Migration Wizard how many times to retry the MAPI call, at intervals specified by the MessageRetryWait parameter. If the error persists through all retry attempts, the Wizard will note the error in the log, skip the current message property or element, and move on to process the next item. Depending on the Log level setting (on the Specify Run Information screen), the retry attempts may appear in the program logs with no other documented error or warning. The defaults:
[Exchange]
MessageRetryCount=3
MessageRetryWait=10
MAPIErrorsToRetry=80040115,80040125
... tell the program to retry a MAPI call that returns the error 80040115 or 80040125, to a maximum of three attempts at 10-second intervals. In most cases, the default errors 80040115 and 80040125 will be sufficient to trap all (or nearly all) MAPI connectivity errors.