XADM: Exchange Migration Wizard Fails with 7026 error

Last reviewed: March 20, 1998
Article ID: Q182665
The information in this article applies to:

- Microsoft Exchange Server, version 5.5

SYMPTOMS

When you migrate users from Microsoft Mail to Microsoft Exchange Server, the following event may be logged and the users' data may not be migrated properly:

   Event ID:   7026
   Source:     MSExchangeMig
   Type:    Error
   Category:   None
   Description:   Migration Aborted due to Mapi logon failure.

CAUSE

In Exchange Server version 5.5, when you use the Exchange Migration Wizard to migrate users from Microsoft Mail to Microsoft Exchange Server, the Exchange Migration Wizard creates an address type of "migrate:" for each user it migrates to Exchange.

This is to ensure that the Exchange Migration Wizard can find the user again if the wizard is run in multiple phases against the same user.

If you modify the CSV and remove the "migrate:MS:NET/PO/USER" information from the Secondary-Proxy-Addresses list, the "migrate:" address type is not created, and the second step of the two-step migration fails with the aforementioned Event ID.

WORKAROUND

To work around this problem, do the following: 1. Do not remove the "migrate:MS:NET/PO/USER" information from the CSV. 2. Manually add the proper "migrate:MS:NET/PO/USER" address type for the

   user on Exchange before you run the second step of the two-step
   migration process.


Additional query words: MSMAIL MAILMIG
Keywords : XADM kbusage
Version : 5.5
Platform : winnt
Issue type : kbprb


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.