?
Solved

Event ID: 2114 installing Exchange 2007 LDAP error

Posted on 2008-01-27
5
Medium Priority
?
14,713 Views
Last Modified: 2008-07-03
While installing Exchange 2007 receive and error during the Exchange Transport HUB install.  In the server event log we receive the following errors:

Event Type:      Error
Event Source:      MSExchange ADAccess
Event Category:      Topology
Event ID:      2114
Date:            1/27/2008
Time:            11:55:33 AM
User:            N/A
Computer:      MAIL
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1196). Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Event Type:      Error
Event Source:      MSExchangeTransportLogSearch
Event Category:      General
Event ID:      7005
Date:            1/27/2008
Time:            11:52:48 AM
User:            N/A
Computer:      MAIL
Description:
Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server localhost did not return a suitable domain controller.
   at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)
   at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts()
   at Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext()
   at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
   at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId)
   at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
   at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)
   at Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindServerByFqdn(String serverFqdn)
   at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindLocalServer()
   at Microsoft.Exchange.Transport.LocalServerConfiguration.<>c__DisplayClass2.<TryLoadLocalServer>b__0()
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

We have verified that DNS is pointing to active directory servers.  We can ping the FQDN names on the network between all servers.  I think the issue is with the LDAP error, however, the only reference to this error is with windows 2000 server and applying the latest updates and patches to correct it.

Additional information.

This is a single domain with all windows server 2003 servers.  The new Exchange 2007 server is Server 2003 64 bit.  There is currently one Exchange 2003 server installed on the domain and we are trying to install Exchange 2007 on the new server.  Before we installed Exchange 2007 we successfully completed all the prerequisite tasks.  Now if we try to modify the install it says the Exchange server is in an inconsistent state and we must use the Recovery command line option.  However when we do this it still fails during the Hub Transport installation.
0
Comment
Question by:exsabier
  • 3
5 Comments
 
LVL 15

Expert Comment

by:JimboEfx
ID: 20758234
I recommend extracting the tail end of the exchange installation log files which are often more useful than the events they generate.

http://technet.microsoft.com/en-us/library/bb125254.aspx
0
 
LVL 23

Expert Comment

by:Stacy Spear
ID: 20760688
Check to see if ports 389 and 390 are open between the hub server and your AD servers. If they are, then check for port 3268 which is the Global catalog port.

If your servers are set to require a secure connection on the other hand, the LDAP port then becomes 636 and global catalog becomes 3269
0
 

Author Comment

by:exsabier
ID: 20765110
Here is the end of the Exchange setup log.

[1/26/2008 10:50:59 PM] [2] Current service status query time is '1/26/2008 10:50:59 PM'.
[1/26/2008 10:50:59 PM] [2] Generated Watson report with dump for the service MSExchangeTransport
[1/26/2008 10:50:59 PM] [2] [ERROR] Unexpected Error
[1/26/2008 10:50:59 PM] [2] [ERROR] Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.
[1/26/2008 10:50:59 PM] [2] Ending processing.
[1/26/2008 10:50:59 PM] [1] The following 1 error(s) occurred during task execution:
[1/26/2008 10:50:59 PM] [1] 0.  ErrorRecord: Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.
[1/26/2008 10:50:59 PM] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.
[1/26/2008 10:50:59 PM] [1] [ERROR] Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.
[1/26/2008 10:50:59 PM] [1] Setup is halting task execution because of one or more errors in a critical task.
[1/26/2008 10:50:59 PM] [1] Finished executing component tasks.
[1/26/2008 10:50:59 PM] [1] Ending processing.
[1/26/2008 10:50:59 PM] [0] The Exchange Server Setup operation did not complete. For more information, visit http://support.microsoft.com and enter the Error ID.
[1/26/2008 10:50:59 PM] [0] End of Setup
[1/26/2008 10:50:59 PM] [0] **********************************************
0
 

Author Comment

by:exsabier
ID: 20765113
Here is the log parsed for errors only via the Exchange Power Shell:

[WARNING] Please exit Powershell to complete the installation.
        [WARNING] Please exit Powershell to complete the installation.
        [WARNING] The following service restart is required for the chan
        ge(s) to take effect : MSExchangeTransport
        Ending processing.
        Service 'MSExchangeADTopology' failed to start. Check the event
        log for possible reasons for the service start failure.
        [ERROR] Unexpected Error
        [ERROR] Unexpected Error
        [ERROR] Service 'MSExchangeADTopology' failed to start. Check th
        e event log for possible reasons for the service start failure.

        Ending processing.
    0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceFailedToS
    tartException: Service 'MSExchangeADTopology' failed to start. Check th
    e event log for possible reasons for the service start failure.
    [ERROR] Service 'MSExchangeADTopology' failed to start. Check the event
    log for possible reasons for the service start failure.
    Setup is halting task execution because of one or more errors in a criti
    cal task.
        The maximum wait for the operation is set to '00:15:00'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='0'- Current checkpoint='0'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:13:30'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:12:00'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:10:30'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:09:00'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:07:30'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:06:00'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:04:30'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        The remaining time for service status change is '00:03:00'.
        [WARNING] Service checkpoint has not progressed. Previous checkp
        oint='1'- Current checkpoint='1'.
        Previous service status query time is '1/26/2008 10:38:58 PM'.
        Generated Watson report with dump for the service MSExchangeTran
        sport
        [ERROR] Unexpected Error
        [ERROR] Unexpected Error
        [ERROR] Service 'MSExchangeTransport' failed to reach  status 'R
        unning' on this server.
        Ending processing.
    0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotRea
    chStatusException: Service 'MSExchangeTransport' failed to reach  statu
    s 'Running' on this server.
    [ERROR] Service 'MSExchangeTransport' failed to reach  status 'Running'
    on this server.
    Setup is halting task execution because of one or more errors in a criti
    cal task.
0
 

Accepted Solution

by:
exsabier earned 0 total points
ID: 20810872
So I opened a case with Microsoft.  They had several different techs working on this but here is what I know about what they did.  They had me run a netdiag and noted that it would error out with the net logon test.  See output below.  I did not actually get to talk to the technician who fixed this issue but I believe the issue was that the "Access this computer from the network" had the "Authenticated User" removed from this.  I had checked this at the "Domain Controller" policy level, however, not at the "Default Domain Policy" level.  After fixing the Netlogon error I was able to uninstall the current installation and do a clean install.

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Default-First-Site-Name\COMPANY
      Starting test: Connectivity
         ......................... COMPANY passed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\COMPANY
      Starting test: Replications
         ......................... COMPANY passed test Replications
      Starting test: NCSecDesc
         ......................... COMPANY passed test NCSecDesc
      Starting test: NetLogons
         * Warning BUILTIN\Administrators did not have the "Access this computer
         *   from network" right.

         [COMPANY] An net use or LsaPolicy operation failed with error 1, Incorrect function..
         ......................... COMPANY failed test NetLogons
      Starting test: Advertising
         ......................... COMPANY passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... COMPANY passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... COMPANY passed test RidManager
      Starting test: MachineAccount
         ......................... COMPANY passed test MachineAccount
      Starting test: Services
         ......................... COMPANY passed test Services
      Starting test: ObjectsReplicated
         ......................... COMPANY passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... COMPANY passed test frssysvol
      Starting test: frsevent
         ......................... COMPANY passed test frsevent
      Starting test: kccevent
         ......................... COMPANY passed test kccevent
      Starting test: systemlog
         ......................... COMPANY passed test systemlog
      Starting test: VerifyReferences
         ......................... COMPANY passed test VerifyReferences
   
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
   
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
   
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
   
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
   
   Running partition tests on : accent-inc
      Starting test: CrossRefValidation
         ......................... accent-inc passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... accent-inc passed test CheckSDRefDom
   
   Running enterprise tests on : accent-inc.com
      Starting test: Intersite
         ......................... accent-inc.com passed test Intersite
      Starting test: FsmoCheck
         ......................... accent-inc.com passed test FsmoCheck
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Question has a verified solution.

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

In this post, we will learn to set up the Group Naming policy and will see how it is going to impact the Display Name and the Email addresses of the Group.
Let us take a look at the scenario, you have a database that is corrupt and you run the ESEUTIL command only to find you are unable to repair it. How do you now get the data back?
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
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 anti-spam), the admin…
Suggested Courses
Course of the Month3 days, 9 hours left to enroll

599 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