Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You receive LDAP bind errors after you run Dcpromo to install the first Windows Server 2003 computer in a domain

You receive LDAP bind errors after you run Dcpromo to install the first Windows Server 2003 computer in a domain

View products that this article applies to.

Symptoms

After you run the Dcpromo.exe tool to install the first Microsoft Windows Server 2003 computer in a domain, and then you restart the computer, you may receive Lightweight Directory Access Protocol (LDAP) bind errors.

When you run the Dcdiag utility on the computer, you may receive the following error message:
LDAP search failed with error 55.
The specified network resource or device is no longer available.
When you run the Netdiag.exe diagnostic utility on the computer, you may receive the following error message:
Cannot do un-authenticated ldap_search to 'ServerName.DomainName.com': Unavailable.
[WARNING] Failed to query SPN registration on DC 'ServerName.DomainName.com'.


Additionally, the following events may be logged in the system event log:

Event Type: Error
Event Source: NTDS
Event Category: Inter-site Messaging
Event ID: 1824
Date: 12/8/2003
Time: 3:34:15 PM
User: N/A
Computer: Server Name
The Intersite Messaging Service requested to perform an LDAP bind operation. The operation was unsuccessful. The error message is as follows: The specified server cannot perform the requested operation. Additional data Error value: 58



Event Type: Error
Event Source: NTDS Inter-site Messaging
Event Category: Inter-site Messaging
Event ID: 1473
Date: 12/8/2003
Time: 3:34:15 PM
User: N/A
Computer: Server Name
The Intersite Messaging service could not read the intersite transport objects from Active Directory. As a result, the Intersite Messaging service has stopped. The Knowledge Consistency Checker (KCC) will be unable to calculate intersite topology without this service. User Action Verify that LDAP queries function properly on this machine. Restart the Intersite Messaging service to continue intersite communication. Additional Data Error value: 58 The specified server cannot perform the requested operation.



Event Type: Error
Event Source: NTDS LDAP
Event Category: LDAP Interface
Event ID: 2046
Date: 12/8/2003
Time: 3:34:15 PM
User: N/A
Computer: Server Name
All of Active Directory's LDAP send queues are full. This can be caused by clients that continue to send requests faster than they are processing the results. In order to prevent the server from becoming unresponsive as a result of this condition Active Directory has closed number connections that are not bound as Administrators. Active Directory will continue to close connections until enough send queue space has been recovered to operate normally.



Event Type: Error
Event Source: NTDS KCC
Event Category: LDAP Interface
Event ID: 1312
Date: 12/8/2003
Time: 3:34:15 PM
User: N/A
Computer: Server Name
A call to the Intersite Messaging service that specifies the following transport failed. Transport: CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=Domain Name,DC=com As a result, the Knowledge Consistency Checker (KCC) cannot configure a correct intersite replication topology. User Action Verify that the Intersite Messaging service is running.



If you increase the LDAP Interface NTDS diagnostics to 5, the following event may be logged in the Directory Services event log:

Event Type: Warning
Event Source: NTDS LDAP
Event Category: LDAP Interface
Event ID: 1216
Date: 12/23/2003
Time: 3:34:15 PM
User: N/A
Computer: Server Name
Description: Internal event: An LDAP client connection was closed because of an error.

↑ Back to the top

Cause

This problem may occur if the value of the MaxReceiveBuffer attribute in the LDAP policy is greater than 10737418. To determine the value of the MaxReceiveBuffer attribute in the LDAP policy, follow these steps:
  1. Click Start, click Run, type ntdsutil, and then click OK.
  2. At the Ntdsutil prompt, type ldap policies, and then press ENTER.
  3. At the LDAP policy prompt, type connections, and then press ENTER.
  4. At the server connections prompt, type connect to server ServerName, and then press ENTER.
  5. At the server connections prompt, type quit, and then press ENTER.
  6. At the LDAP policy prompt, type show values, and then press ENTER.
  7. Make sure that the MaxReceiveBuffer attribute is set to the default value of 10485760. If the value is greater than 10737418, follow the steps that are in the Workaround section to change the MaxReceiveBuffer attribute to the default value of 10485760.
  8. At the LDAP policy prompt, type quit, and then press ENTER.
  9. At the Ntdsutil prompt, type quit, and then press ENTER.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
   Date         Time   Version            Size    File name   Platform
   -------------------------------------------------------------------
   26-Jan-2004  18:17  5.2.3790.121    1,055,232  Esent.dll   x86
   26-Jan-2004  18:17  5.2.3790.124    1,527,296  Ntdsa.dll   x86
   26-Jan-2004  18:17  5.2.3790.121    2,605,056  Esent.dll   IA-64
   26-Jan-2004  18:17  5.2.3790.123    4,037,120  Ntdsa.dll   IA-64

↑ Back to the top

Workaround

To work around this problem, lower the value of the MaxRecieveBuffer attribute in the LDAP policy. To do this, follow these steps:
  1. Click Start, click Run, type ntdsutil, and then click OK.
  2. At the Ntdsutil prompt, type ldap policies, and then press ENTER.
  3. At the LDAP policy prompt, type connections, and then press ENTER.
  4. At the server connections prompt, type connect to server ServerName, and then press ENTER.
  5. At the server connections prompt, type quit, and then press ENTER.
  6. At the LDAP policy prompt, type show values, and then press ENTER.
  7. At the LDAP policy prompt, type set maxreceivebuffer to 10485760, and then press ENTER.
  8. At the LDAP policy prompt, type commit changes, and then press ENTER.
  9. At the LDAP policy prompt, type quit, and then press ENTER.
  10. At the Ntdsutil prompt, type quit, and then press ENTER.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More information

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kbautohotfix, kbhotfixserver, kbwinservds, kbactivedirectory, kbbug, kbfix, kbqfe, kbwinserv2003presp1fix, kbqfe, KB834317

↑ Back to the top

Article Info
Article ID : 834317
Revision : 11
Created on : 7/24/2007
Published on : 7/24/2007
Exists online : False
Views : 793