Solved

Active Directory problem on running data collection

Posted on 2004-09-20
8
306 Views
Last Modified: 2010-08-05
I am installing a Exchange 2003 server and trying to connected it to an existing 5.5 server. In the Active directory connector screen, when trying to run STEP 2 data collection I get the following error

Server <MAILSERVER> :389 is not an Exchange 5.5 server or an SRS service.
Data Collection stopped. Check the ADCTools.log file for the cause. Then repeat Step 2.
0
Comment
Question by:bateman2413
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 

Author Comment

by:bateman2413
ID: 12103289
When I look at the ADCTOOLS.LOG  I see the following

Pass 1 of 4: Resource Mailbox Scan 09/20/2004 11:39:31
      Server mailserver name :389 is not an Exchange 5.5 server or an SRS service.
0
 
LVL 2

Expert Comment

by:fitcher
ID: 12103359
Maybe a dumb question but,

Is LDAP enabled on the 5.5 server is it set to use port 389? Have you run the domain prep and forest prep?
0
 

Author Comment

by:bateman2413
ID: 12103604
I ran forest prep and domain prep. How would someone enable LDAP on a exchange 5.5 site running Windows 2000 server?
0
PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

 

Expert Comment

by:g_2000
ID: 12105509
Hi,
Is there a program on your computer that  behaving a virus like activity........mey be run anti-virus sofwares..........Thanks
0
 

Author Comment

by:bateman2413
ID: 12105533
well I believe that I had to choose create new organization when installing instead of join existing...  trying that now...
0
 

Author Comment

by:bateman2413
ID: 12237329
I had to resort to calling MicroSoft to walk me through the full Installation of Exchange 2003. The problem was I need to change the port to another port cause something else was using port 389.
0
 

Accepted Solution

by:
ee_ai_construct earned 0 total points
ID: 12526955
Question answered by asker or dialog valuable.
Closed, 500 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

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

Suggested Solutions

This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

726 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