NM: List of Migration Initialization Failures with Autodiscover Connectivity (B305011)

A Migration Initialization Failure status is reported on a migration account due to Autodiscover connectivity failures. 

To check for the reason for an Initialization failure open the migration log for an account that reported the failure. This can be done through clicking on the Open Log button on the Notes document or though the OS logs folder on the controller or the worker.

The default logs path for the controller is C:\Program Files\Binary Tree\CMT for Exchange\Logs

The default logs path for the worker is C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker\Logs

Within the log the issue causing the failure will be recorded as an Error and this error can be checked in this knowledge base article or searched for in the knowledge base itself.

Note that if logging is set to Minimal or Normal on the Migration Profile then you may need to run the migration again with a Migration profile that is set to Verbose logging on the Source Option tab.

If migration logging is set to minimal or normal, you may see the following errors:

! Error: log on Failed 8004011

Or

! Error: Failed to initialize

To find the exact error, change the Migration Profile logging to Verbose, and run the migration again. We have listed the most common Autodiscover errors. Click the link for more information.

Scenario 1: DNS Autodiscover is not configured for the SMTP Domain

@ 10:44:51 10:44 AM: [Error] Exception in BTLogonHostedExchange:

@ 10:44:51 10:44 AM: [Warning] Warning connecting to default folder: Not logged on. Please log on first

@ 10:44:51 10:44 AM: [Error] Invalid input for CreateRDOSession

@ 10:44:51 10:44 AM: [Error] Unable to logon to Hosted Exchange Mailbox:

See the following article for cause and resolution: NM: 4.6 O365 Migration error: ! Error: log on Failed 8004011

Scenario 2: Autodiscover username or password is incorrect: NM: 8004011[Error] Invalid input for CreateRDOSession 

Scenario 3: Autodiscover username is not set:  NM: 80040111 [Error] Invalid Parameters for Server/Archive

Scenario 4: SMTP address for the migration account in Notes does not match the Exchange SMTP address: NM: 80040111 [Error] Exception in BTLogonHostedExchange:

Scenario 5: Incorrect Outlook version installed: NM: 80040111 [Warning] Warning connecting to default folder: Default path to inbox is incorrect for user

Scenario 6: CAS server cannot connect: NM: 80040111 [Error] Exception in DoProfileGeneration: GetAutodiscoverForEmailAddress

Scenario 7: Outlook does not have all the required patch levels: NM: 80004002 AutoDiscover Response for Archive not found

Scenario 8: Hybrid configuration causes a DNS lookup fault with Autodiscover: NM: 80040111 [Error] Exception in DoProfileGeneration: SCP lookup did not locate autodiscover objects in the AD - Fixed in version 4.6.3 

Scenario 9: Damaged Outlook Installation: NM: 80040111 Unable to MAPIAdminProfiles(), intending to delete existing profile 'CMT Temp Migration Profile'

Scenario 10: MAPI Disabled on Target Mailboxes: NM: 80004002 Error: AutoDiscover Archive MdbDN not found

Scenario 11: Account contains both the tenant.onmicrosoft.com and the tenant.mail.onmicrosoft.com aliases: NM: Log on Failed 80040111 - Error: AutoDiscover Mailbox LegacyDN not found

Related articles:

NM: Migration failed with the following Status: AutoDiscover Failure