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 NameThe 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 NameAll
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 NameA 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 NameDescription:
Internal event: An LDAP client connection was closed because of an error.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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