XADM: The Exchange 2000 Migration Wizard Does Not Work When You Migrate Exchange Server 5.5 users, and an Event ID 7017 or 7048 Error Message Is Logged

Article translations Article translations
Article ID: 318379
This article was previously published under Q318379
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

Symptoms

If you try to migrate users or mailboxes from a Microsoft Exchange Server 5.5 organization to Exchange 2000, the migration may stop working when you supply the Exchange Server 5.5 server name, account, and password. You may receive the following error message:
Invalid server specified or you do not have the permissions required to complete operation.
If you use Exchange 2000 Server Service Pack 1 (SP1), the following error message may be logged in the Application event log:
Event Type: Error
Event Source: MSExchangeMig
Event ID: 7017
Computer: serverName
Description: Could not log onto the Message Store for Account: %1
If you use the Exchange 2000 Server Service Pack 2 (SP2) version of the migration wizard, the following error message may be logged in the Application event log:
Event Type: Error
Event Source: MSExchangeMig
Event ID: 7048
Computer: serverName
Description: Could not log onto the Message Store for Account 'Microsoft System Attendant' on Server 'server-name'.

Cause

This problem may occur if the directory name for the Exchange Server 5.5 organization name contains a comma (,), for example, "Fabrikam, Inc."

Resolution

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: Migration wizard

Collapse this tableExpand this table
File nameVersion
Mlmig32.dll6.0.5770.68

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

Properties

Article ID: 318379 - Last Review: October 26, 2013 - Revision: 4.0
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kberrmsg kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB318379

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com