Please Read: Significant Update Planned, Migrating Forum Software This Month

See more
See less

MSEchangeAL 8026 0x51 LDAP error

  • Filter
  • Time
  • Show
Clear All
new posts

  • MSEchangeAL 8026 0x51 LDAP error

    Hi all

    Hope you can help me with this one.

    First of all some backgound:-

    This is a windows 2003 enterprise server running 2003 exchange enterprise. The server has been running fine for 6 months. It is also the DC. (Only server on the network)

    I receive hundreds of the error below and the server has to be restarted to get back up and running again.

    Event Type: Error
    Event Source: MSExchangeAL
    Event Category: LDAP Operations
    Event ID: 8026
    Date: 17/09/2006
    Time: 00:15:03
    User: N/A
    Computer: VIKING
    LDAP Bind was unsuccessful on directory viking.medigoldhealth.mhl for distinguished name ''. Directory returned error:[0x51] Server Down.

    Event Type: Error
    Event Source: MSExchangeDSAccess
    Event Category: Topology
    Event ID: 2104
    Date: 17/09/2006
    Time: 00:15:18
    User: N/A
    Computer: VIKING
    Process MAD.EXE (PID=4000). All the DS Servers in domain are not responding.

    Event Type: Error
    Event Source: Userenv
    Event Category: None
    Event ID: 1030
    Date: 17/09/2006
    Time: 00:15:06
    Computer: VIKING
    Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

    Now this is what I have done so far:-

    I have ran netdiag and dcdiag both passing ok.
    I have checked the receipient update policy in system manager and the domain/exchange server/ and windows domain controller all appear to be correct.

    Any help would be greatly appreciated.

    Many thanks


  • #2
    Re: MSEchangeAL 8026 0x51 LDAP error

    In addition check the followings:

    1. DNS and network connection to the DC.
    2. Try to reboot the DC or DCs.
    3. Check that the Microsoft Exchange Site Replication Service is running.
    4. Check that there is no FW or port blocking on the DC / Exchange.
    5. Check the recipient update service is configure with the right DC.
    CNE 5, CCA, MCSE NT4.0-2003, MCSE 2003 messaging, Exchange Server MVP.
    Tzahi Kolber - IT Supervisor
    Polycom Israel.