Error: 'CreateMailbox first attempt hr= [HR=0x8000ffff]' (NETIQKB46074)

  • 7746074
  • 02-Feb-2007
  • 24-Jun-2008


Exchange Migrator 2.x

Error: 'CreateMailbox first attempt hr= [HR=0x8000ffff]'

Error: 'Create mailbox second attempt failed [CN=Mailbox Store (ServerName),CN=First Storage Group,CN=InformationStore,CN=serverName,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=AdministrativeGroupName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com][HR=0x8000ffff]'

Error: 'ProcessHelperForMdb... failed to migrate object [/o=OrgName/ou=SourceSite/cn=Recipients/cn=mailboxName][HR=0x8000ffff]'


The 8000ffff error code, when returned by CDO for Exchange Management, equates to an error message of 'The specified domain either does not exist or could not be contacted'. With Exchange, this error is typically caused by a Global Catalog server not being available for the domain that the target Exchange server is a member. This can either be a result of DNS not being able to resolve a Global Catalog server or the Global Catalog server being down or unreachable.

To test availability of the Global Catalog server from the Exchange Migrator (EM) console:

Note: This test requires the Windows Support Tools be installed on the EM console.

  1. Open a command prompt
  2. Enter NLTEST /DSGETDC:domain /GC
    • Where domain is the NetBIOS name of the target domain.
  3. If a server is returned, enter ping serverName
    • Where serverName is the name of the DC that is returned as the Global Catalog server.
  4. If the ping is successful, enter ping -a ip.address
    • Where XXX.XXX.XXX.XXX is the IP address that is returned by the original PING. 

Choose one of the following steps to resolve this issue:

  1. Install or join the EM console into the same domain as the target Exchange server.
  2. If the EM console is already a member of the target domain, or you cannot move/install an EM console in the target domain, and you notice issues when trying to contact the Global Catalog server, resolve these resolution issues and try the migration again.
  3. Point the EM console to a DNS server in the same domain as the target Exchange server.

For more information, contact Technical Support at

Additional Information

Formerly known as NETIQKB46074