You are currently offline, waiting for your internet to reconnect

Numerous "Event ID 1216" Events in Directory Services Event Log

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q246717
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
You may find multiple instances of the following entry in the Directory Services event log:
Event Type: Warning
Event Source: NTDS LDAP
Event Category: LDAP Interface
Event ID: 1216
Date: 11/19/2000
Time: 9:12:58 PM
User: N/A
Computer: Computer
Description:
The LDAP server closed a socket to a client because of an error condition, 1234. (Internal ID c01028c::4294967295).
Note that the Internal ID value varies with each instance.
CAUSE
This event log message occurs when a Lightweight Directory Access Protocol (LDAP) client sends a request to the computer by using User Datagram Protocol (UDP) but does not keep its socket open to listen for the response from the server. When the server tries to send the answer back, the error message is logged to the event log. This is a harmless error that can occur frequently under normal operating conditions. It occurs only if the diagnostic logging level is increased by modifying the level of LDAP logging to 2 or above in the registry.
RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate the LDAP Interface Events value in the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
  3. Set the data value of the LDAP Interface Events value to a lower setting, and then click OK.
  4. Quit Registry Editor.
The default value for this registry value is 0.
Properties

Article ID: 246717 - Last Review: 09/11/2011 06:25:00 - Revision: 4.0

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Datacenter without Hyper-V
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Enterprise without Hyper-V
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Standard without Hyper-V
  • kbenv kberrmsg kbprb KB246717
Feedback