5.5 to 2K3 issues (ADC - SRS)

I've installed a test platform of migration from 5.5 to 2K3.
My 5.5 organisation contains several sites hosted in different NT4 domains connected through trust relationships.

The test platform simulates 2 sites in 2 domains (NT4 SP6 - Exchange 5.5 SP4). I tried to migrate one of them.

The migration from NT4 to Windows 2003 has been done without any problem (installation of a new machine, promotion as NT4 PDC of the domain, then upgrade to W2K3).

I launched on the Windows 2K3 the Exchange 2K3 wizard, and choosed to install a new Exchange 2003 on a site having a 5.5 server.

The wizard ran without any error in logs, and I could launch post install tests that returned successful logs.
Problems began when I restarted the server : all Exchange services started except the SRS.

There are lots of errors and warning in the Application Event Viewer. Hereafter are first logged just after the reboot (only errors and warning) : some of them were logged several times:

MSExchangeAL (error) - LDAP Operations - 8026 : LDAP bind was unsuccessful on directory dedomc.de.cast.com for distinguished name ''. Directory returned error (0x51) Server Down.

MSADC (error) - LDAP Operations - 8026 : LDAP bind was unsuccessful on directory dedomc.de.cast.com for distinguished name ''. Directory returned error (0x34) Unavailable.

MSExchangeAL (error) - Service Control - 8026 : The WIN32 API call 'DSGetDCNameW' returned error code (0x826). The specified component could not be found in the configuration information. The service could not be initialized. Make sure that the operating system was installed properly.

MSExchangeSRS (warning) - Service Control - 1403 : Site replication service was unable to obtain legacy account details and cannot continue.
...

FYI : de.cast.com is a child domain of the win2000 domain cast.com which had been forest and domain "preped" (from 2K3 CD).

I ran the full test twice from scratch with the same behaviour.

Thanks for your help.

Fred
LVL 1
fhoAsked:
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.

David WilhoitSenior Consultant, ExchangeCommented:
You ran Exchange 2003 forestprep? just checking...
Did you run forestprep on the root DC/GC, and then domain prep on the root and child domains?

D
0
fhoAuthor Commented:
Yes I did.
0
David WilhoitSenior Consultant, ExchangeCommented:
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

fhoAuthor Commented:
I had already tried this.
What is strange is that the SRS doesn't automatically start, but does without any problem when started manually.
Then no more errors are logged in the EV.
I didn't go further in the migration process (move ADC to the SRS, move mailboxes, ...), even if all services start. I want to find the solution to this issue first.
Shoudl I install any service pack of 2K3 (Win and Ex) if any?
TIA
Fred
0
David WilhoitSenior Consultant, ExchangeCommented:
Exchange 2003 has SP1, but then you'd need to upgrade the ADC as well. This could be a simple timeout issue on startup, I haven't seen any other issues with this before. Is that the only service that fails to start in a timely fashion?

D
0
fhoAuthor Commented:
Yes it is the only service that fails. And the server is a Xeon with 1 GB of ram. It has no other application or service installed except those needed as domain controler.
But the root domain controler (a test server as well) is an old PC with Windows 2000. Perhaps is it the cause of the issue (has it something to do with the startup of Exchange ???)
0
David WilhoitSenior Consultant, ExchangeCommented:
Possibly, but not worth your time to track in a test environment.

MSExchangeAL (error) - LDAP Operations - 8026 : LDAP bind was unsuccessful on directory dedomc.de.cast.com for distinguished name ''. Directory returned error (0x51) Server Down.

MSADC (error) - LDAP Operations - 8026 : LDAP bind was unsuccessful on directory dedomc.de.cast.com for distinguished name ''. Directory returned error (0x34) Unavailable.

This event occurs because of differences in the timing between services as they stop and start. You can ignore this event if it occurs during computer shutdown and startup.
0

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
fhoAuthor Commented:
good piece of news. So, the only issue I still have is the SRS. And as soon as it has been started manually, there are no more errors.
0
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
Exchange

From novice to tech pro — start learning today.