Error in ExDeploy.log: Could not connect to the Exchange 5.5 server

Posted on 2004-04-18
Last Modified: 2012-08-14
I'm trying to install Exchange 2003 on a W2K3 Server to replace the Exchange 5.5 on W2K SP4. This is for a small company (50 users) with a single domain.

I've upgraded the domain using Adprep and promoted the W2K3 server to a DC. I've also demoted the other DC to must a domain member. And I switched the domain to native mode as the other three servers are W2K and W2K3.

I get the following error in the ExDeploy log:
- Error: Could not connect to the Exchange 5.5 server 'imsnt1'. Tools that require an Exchange 5.5 server will not run.

A couple of threads posted about this error. One thread discussed not having the LDAP protocol configured. But LDAP is one of the protocols on my Exchange Server. <>

Another thread goes in depth about the error, but the domain is much more complicated than mine and I can't figure out what pieces I can ignore: <>

What could be my problem?
Question by:TerrellITC
  • 6

Author Comment

ID: 10855422
I've gone through the diagnostic logs and the only errors I see were in the DCDiag log, but they don't look related or relevent (I'm not going to setup load balancing...)

         Starting test: frsevent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems.
         ......................... IMS-MAIN failed test frsevent

         Starting test: systemlog
         An Error Event occured.  EventID: 0xC0001B58
         Time Generated: 04/18/2004   14:51:24
         Event String: The Network Load Balancing service failed to
         An Error Event occured.  EventID: 0xC0001B72
         Time Generated: 04/18/2004   14:51:24
         Event String: The following boot-start or system-start
         ......................... IMS-MAIN failed test systemlog


Author Comment

ID: 10863680
Okay, let me pump the points up a bit...

Expert Comment

ID: 10865732
If I read this right, you have a 5.5 exch server and you want to migrate all the stuff to the e2k3 server?
After installing the w2k3 domain controller does your 5.5 server work, connect to AD, etc?
Did you check exdeploy.log and orgnamecheck.log files and review the log contents to ensure that SetupPrep didn't encounter any errors?

If all the above is ture did you go this route for the e2k3 server deploy:

Start the Exchange deployment tools by inserting the Exchange 2003 CD-ROM and selecting Exchange Deployment Tools from the Exchange 2003 dialog box.
When the Exchange Server Deployment Tools Wizard starts, click "Deploy the first Exchange 2003 server."
Click "Coexistence with Exchange 5.5," click Next to move to Phase 2 of the wizard, then click Next again to move to Phase 3 of the wizard.
I recommend running SetupPrep to ensure that you've completed all preparatory steps. Select the check box for Step 1 of Phase 3 of the wizard, which this figure shows.
Enter the Exchange 5.5 server name, the Global Catalog (GC) server name, and a log-file path, then click "Run SetupPrep now."
Open the exdeploy.log and orgnamecheck.log files and review the log contents to ensure that SetupPrep didn't encounter any errors.
Move to Step 3 of Phase 3, then click "Run Setup now."
Click Next to move past the introduction page of the Microsoft Exchange Installation Wizard.
Select "I agree" to the license, then click Next.
The installation wizard defaults to selecting a Typical installation. Click Next.
Select "Join or upgrade an existing Exchange 5.5 Organization," then click Next.
When prompted, enter the Exchange 5.5 server name, then click Next.
Click OK to tell the installation wizard to proceed with tests to ensure that the Exchange 2003 server can be introduced into the organization.
After the installation wizard finishes the tests, click "I agree that I have read and will be bound by the license agreements for this product" and click Next.
When prompted, enter the service account password used for Exchange 5.5, then click Next.
Click Next to move past the installation summary.
The installation wizard will begin installing the Exchange 2003 server and display its progress onscreen. After the server installation is complete, click Finish.

Your Exchange 2003 server will appear in the list of servers, and you can start moving mailboxes and services as required. If you follow the remaining steps of the Exchange Deployment Tools Wizard, you should change your connection agreements to replicate to the new Exchange 2003 server, then run the validation tools outlined in step 5 of the wizard.


Author Comment

ID: 10866181
Hi Ans-Ansdenver,

You're reading the situation right. To clarify, the new W2K3 DC is going to be the new W2K3 Exchange Server.

I can create AD users on both DCs. And I created in Exchange 5.5 a new recipient and linked it to the test user. And AD noted the link to the mailbox when I deleted the test user.

And I am following the path you've outlined. The error in the ExDeploy.log comes when I run DSScopeScan in the Phase 1 step.
Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users should you!


Author Comment

ID: 10866416
I was wondering if LDAP was configured to a different port or even running, so I just ran a port scanner against the server. LDAP was found running on port 389.

Where is the LDAP port configured and how do I confirm that it's really running?

Author Comment

ID: 10936659
I figured it out. It was an LDAP port issue with Exchange 5.5. I guess I was supposed to move it to another port during the server upgrade from NT to W2K. I found an article that explained how to switch it to port 390. I then ran setup with the new port and the error disappeared from the ExDeploy.log.

Author Comment

ID: 11105970
I want to thank ans-ansdenver for providing a step-by-step guide. I wish I could award some points for the effort. But I was following several similar guides in my training manuals and textbooks. And the problem was happening during the first phases of the steps, so all hte other steps failed...

Accepted Solution

Computer101 earned 0 total points
ID: 11137102
PAQed, with points refunded (500)

E-E Admin

Featured Post

Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
This video discusses moving either the default database or any database to a new volume.

757 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

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now