Home > Ask the Microsoft Exchange Experts > Peter terSteeg: Deployment and Migration Questions & Answers > Error: 'Tools that require an Exchange 5.5 server will not run'
Ask The Exchange Expert: Questions & Answers
EMAIL THIS

Error: 'Tools that require an Exchange 5.5 server will not run'

Peter terSteeg EXPERT RESPONSE FROM: Peter terSteeg

Pose a Question
Other Exchange Categories
Meet all Exchange Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 01 March 2006
I am trying to install Exchange 2003 Enterprise Edition on a Windows Server 2003 Standard Edition (member server). My ExDeploy log runs this error: "Could not connect to the Exchange 5.5 server. Tools that require an Exchange 5.5 server will not run." What's going on?


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Peter terSteeg: Deployment and Migration
Mailbox viewing problems after migrating to Exchange 2007
Migrating mailboxes across domains with the Exchange Management Console
Recovering deleted items after an Exchange 2003 migration
Installing Exchange Server 2003 and a domain controller on the same hardware
Reinstall an Exchange Server 2007 cluster continuous replication node
Outlook Web Access issues after an Exchange 2003 migration
Migrating new users onto Exchange Server 2003
Can Exchange 2003 and Exchange 2007 live on the same domain?
Keeping the old server name after migrating to Exchange Server 2003
Troubleshooting a 64-bit Exchange Server 2007 installation

Exchange Server Deployment and Migration Advice
Exchange Server 2007: Email archiving tips and hosted services trends
Exchange Insider e-zine
ExMerge gotchas to watch for when migrating Exchange 2003 mailboxes
Mailbox viewing problems after migrating to Exchange 2007
Migrating mailboxes across domains with the Exchange Management Console
Recovering deleted items after an Exchange 2003 migration
Linking two Exchange 2003 servers in different forests
Installing Exchange Server 2003 and a domain controller on the same hardware
Outlook Web Access issues after an Exchange 2003 migration
When to use Move Mailbox Wizard or ExMerge to move Exchange mailboxes

Microsoft Exchange Server 2003
Changing email address formats in Exchange Server 2003
Should you remove .STM files from Exchange Server 2003?
Troubleshoot 'System Attendant' error messages in OWA
Configuring the default recipient policy in an Exchange 2003 environment
Removing old disclaimers from Exchange Server 2003
ExMerge gotchas to watch for when migrating Exchange 2003 mailboxes
Recovering deleted items after an Exchange 2003 migration
Linking two Exchange 2003 servers in different forests
Microsoft Exchange Server virtualization tutorial
Installing Exchange Server 2003 and a domain controller on the same hardware
Microsoft Exchange Server 2003 Research

RELATED GLOSSARY TERMS
Terms from Whatis.com − the technology online dictionary
rehoming  (SearchExchange.com)

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


VIEW MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A.

My initial guess is that you have one of these components installed that only work with Exchange 2000/2003:

cc:Mail Connector
Chat
Conferencing Server
Instant Messaging
Key Management Service
Mobile Information Server
MSMail Connector

Could it be that you are trying to install an Exchange 2003 server into your existing Exchange 5.5 implementation to continue on with an intra-organizational migration? If so, just ensure those components are removed prior to the install.


MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A:

The named error could also occur if the Exchange 5.5 server has its LDAP protocol turned off, if the default LDAP port number from 389 has been changed, or the Exchange 5.5 server is on a Windows 2000 domain controller resulting in an LDAP port conflict.

Some ExDeploy tools, such as the Active Directory Connector (ADC), will use this port in communicating with Exchange 5.5; you can change the LDAP port and the authentication method in the ExDeploy configuration setup.

It would seem an unintentional misstatement that the listed components only work with Exchange 2000/2003. The listed components work with Exchange 5.5 and Exchange 2000, but are obsolete in Exchange 2003. They can continue running in a mixed Exchange 5.5/2000/2003 organization as long as they are not on the Exchange 2003 server.

Also, it is not necessary to ensure the listed components are removed prior to the install of the Exchange 2003 server into the Exchange 5.5 site. Removal would be required if the user planned to upgrade an Exchange 2000 server to an Exchange 2003 server with these installed.
—Keith G.


Do you have comments on this Ask the Expert Q&A? Let us know.

Related information from SearchExchange.com:

  • 11 tips in 11 minutes: Migrating from Exchange 5.5 to Exchange Server 2003
  • Learning Guide: Exchange Migration
  • Reference Center: Migration tools
  • Reference Center: Migration advice



  • Search and Browse the Expert Answer Center
    Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
    Browse our Expert Advice



    Outlook Web Access (OWA) Tips and Advice
    HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
    About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
    SEARCH 
    TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

    TechTarget Corporate Web Site  |  Media Kits  |  Site Map




    All Rights Reserved, Copyright 2004 - 2009, TechTarget | Read our Privacy Policy
      TechTarget - The IT Media ROI Experts