Error: 'Warning--failed in bindToMailbox' (NETIQKB1820)

  • 7701820
  • 02-Feb-2007
  • 02-Oct-2007


Exchange Migrator 1.x

Exchange Migrator 2.x

Error: 'Warning--failed in bindToMailbox'


The main issue occurs when migrating more than one mailbox. After Exchange Migrator creates the object in the Active Directory it returns the error, "failed in bindtomailbox", in the EMApplog.txt file when trying to copy mailbox data on some of the newly created mailbox objects. You will find that Exchange Migrator can bind to other previously migrated mailboxes without error and copy the data successfully.

On investigation of the user objects that generate a "failed in bindtomailbox" error, you will find that the mailbox has not been completely created. The following two tests can be used to prove this:

  1. Send an email with a delivery receipt to the mailbox, no receipt will be returned.
  2. Try logging onto the mailbox. This also will fail.

Errors logged in EMApplog.txt

  • +++(2723) Created object
  • ---(2781) Updating the properties of migrated objects
  • ---(3304) Migrating mailbox messages
  • +++(3432) Succeeded - Creating local Custom Recipient for mailbox [xusery][HR=0x00000000]
  • ***(3472) Warning--failed in bindToMailbox
  • ***(3473) ERROR - Failed using target profile. Validate profile by using it to log into Microsoft Outlook [HR=0x8004011d]
  • ***(3476) ERROR - Failed attempting incremental migration of mailbox messages

Possible Scenarios this issue may manifest itself in.

  • Microsoft Exchange 5.5 site to site migration on a Microsoft Windows 2000 SP2 OS and later.
  • Microsoft Exchange 5.5 to Exchange 2000 migration on a Microsoft Windows 2000 SP1 OS and later.

Noted possible causes:
  1. Microsoft Exchange 2000 to Global Catalog to Active directory replication issue. This is most likely the problem in the environment. The "failed in bindtomailbox" error can occur when Exchange Migrator tries to connect to the mailbox to stream the mailbox messages before the mailbox is actually completely created. The reasons for this may be as follows:
    • When a mailbox is created in Exchange 2000 the action is not initiated in Exchange 2000 but in Windows 2000 AD. This request for mailbox creation can be made on any domain controller (DC) but can only be passed to the Exchange 2000 server by a Global Catalog (GC) server as this is the only type of AD server Exchange 2000 communicates with for directory information. Therefore, if there is a sufficient lag between the creation of the object, by Exchange Migrator, in the AD and the AD GC passing this to the Exchange 2000 server, Exchange Migrator will not be able to connect to a mailbox as it does not exist yet. This can happen very easily due to replication cycles with the AD site structure.
    • The issue may involve the Microsoft Exchange Recipient Update Service (RUS) not replicating at the same time and thus causing a lag. Please see the following Microsoft KB article for more information about the RUS.
      • Q246127: XADM: How to Check the Progress of the Recipient Update Service (Q246127)
  2. Memory Leak issue.
    • Please see Microsoft KB article Q293150: FIX: Leak in Repeated Calls to MAPILogonEx (Q293150)
  3. Target OU has been manually typed in and extra spaces have been included in the LDAP path.
  4. Target Server is running out of space.
  5. Possible conflict between Exchange Migrator and Microsoft Exchange Service Pack 1.
  6. The path to the object is incorrect in the Exchange Migrator database due to the object being moved or renamed.
  7. Permission requirements have not been met. 

  1. NetIQ Development may modify the code in a future release to increase the wait-time and compensate for this lag.  However, no decision has been made at this point.
  2. NetIQ Development will include code to minimize memory leak issues.  This code will be contained in the next full release.
  3. NetIQ Development will include code to handle extra spaces in an LDAP path.  This code will be contained in the next full release.  
  4. NetIQ recommends that you allow for enough disk space to accommodate the size of the migrated objects plus a 20% buffer.
  5. Although no conflict between Exchange Migrator and Microsoft Exchange 2000 SP1 has ever been solidified, you may want to consider using an Exchange Migrator console that does not have Microsoft Exchange 2000 SP1 installed. Try this only if all else fails.
  6. Using SQL Enterprise Manager to update the path and/or name in the Object table (for source accounts), or the MigrationInfo table (for target accounts), to reflect the actual object.
  7. Review and Implement NETIQKB2202 : What are the software and configuration requirements for Exchange Migrator?

Additional Information

Formerly known as NETIQKB1820