Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

5.5 to 2K3 issues (ADC - SRS)

Posted on 2004-11-16
8
Medium Priority
?
1,427 Views
Last Modified: 2011-10-03
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
0
Comment
Question by:fho
  • 4
  • 4
8 Comments
 
LVL 24

Expert Comment

by:David Wilhoit
ID: 12596913
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
 
LVL 1

Author Comment

by:fho
ID: 12601212
Yes I did.
0
 
LVL 24

Expert Comment

by:David Wilhoit
ID: 12604755
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
LVL 1

Author Comment

by:fho
ID: 12605454
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
 
LVL 24

Expert Comment

by:David Wilhoit
ID: 12605757
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
 
LVL 1

Author Comment

by:fho
ID: 12605872
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
 
LVL 24

Accepted Solution

by:
David Wilhoit earned 2000 total points
ID: 12605968
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
 
LVL 1

Author Comment

by:fho
ID: 12606509
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

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
Stellar Exchange Toolkit: this 5 in 1 toolkit comes loaded with mega-software tool. Here’s an introduction to tools’ usage and advantages:
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question