hundet
asked on
Exchange 5.5 to 2K3 Migration
We are migrating from and Exchange 5.5 server to Exchange 2K3. At the same time, we are moving from Domain A to Domain B. We are saving all our Exchange Mailboxes to PST files using the Exchange Migration Wizard, then importing them into the new domain/exchange structure. We are getting the following error message during the import:
Event Type: Error
Event Source: MSExchangeMig
Event Category: None
Event ID: 8074
Date: 11/11/2004
Time: 2:36:58 PM
User: N/A
Computer: MAILSERVER01
Description:
MAPI Section
E:\export files\Exch.001\00000001.PR I
Line: 5
Failed to connect to the Mailbox. x500:/o=COMPANYX, INC./ou=EP/cn=Recipients/c n=ImaT
For more information, click http://www.microsoft.com/contentredirect.asp.
I researched this error back in March, and found reference to manually adding an X500 address using ADSI edit. But of course now that I finally got the project approved, I can't find that information. My notes mention adding SMTP,X500 to the msExchInterOrgAddress Type under configuration/services/mic rosoft exchagen/active directory connection/users property. I can't locate that users section - I believe it's because I can't get the*!#*%&@# ADC connector working either.
Any words of wisdom or suggestions to get around these errors?
Thanks,
Tim
Event Type: Error
Event Source: MSExchangeMig
Event Category: None
Event ID: 8074
Date: 11/11/2004
Time: 2:36:58 PM
User: N/A
Computer: MAILSERVER01
Description:
MAPI Section
E:\export files\Exch.001\00000001.PR
Line: 5
Failed to connect to the Mailbox. x500:/o=COMPANYX, INC./ou=EP/cn=Recipients/c
For more information, click http://www.microsoft.com/contentredirect.asp.
I researched this error back in March, and found reference to manually adding an X500 address using ADSI edit. But of course now that I finally got the project approved, I can't find that information. My notes mention adding SMTP,X500 to the msExchInterOrgAddress Type under configuration/services/mic
Any words of wisdom or suggestions to get around these errors?
Thanks,
Tim
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This was one of the articles that I had referenced. After your suggestion, I re-read the article. Amazing what you can learn when you actually read the entire article. Appears that you have to create the x500 address to be the same as the OLD organization information, not the new organization. Once I corrected the x500 address, everything worked great.
Thanks for pointing me back to that article.
Tim