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
MAPI Section

E:\export files\Exch.001\00000001.PRI

Line:  5

Failed to connect to the Mailbox. x500:/o=COMPANYX, INC./ou=EP/cn=Recipients/cn=ImaT

For more information, click

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/microsoft 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?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you read this kb:

XFOR: Migration Wizard May Not Work with Events 8074, 8124, and 8002;en-us;256199

Michael Lundgren

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
hundetAuthor Commented:

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.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.