Event ID 4107 and 4102 Error Messages Occur Every 10 Minutes (222950)


The information in this article applies to:

  • Microsoft Site Server 3.0
This article was previously published under Q222950

SYMPTOMS

You may receive one or more of the following error messages in Event Viewer:
Event ID: 4107
Source: LDAPSVC
Description: The Site Server Authentication Service could not do an LDAP bind. Error: 81, virtual server number 'X'. If this happened during a reboot of the machine and the LDAP server is on the same machine, it is not critical. The Authentication Service will automatically recover from this problem when the first authentication happens.
Event ID: 4102
Source: LDAPSVC
Description: The Site Server Authentication Service could not connect to the LDAP server. Error: 81, virtual server number 'X'. If this happened during a reboot of the machine and the LDAP server is on the same machine, it is not critical. The Authentication Service will automatically recover from this problem when the first authentication happens.
where X is the number representing a specific Personalization and Membership instance.

NOTE: These errors may occur in 10 minute intervals.

CAUSE

These errors are known to occur if you have multiple Lightweight Directory Access Protocol (LDAP) instances and one of them is stopped.

RESOLUTION

To resolve these errors, restart the stopped LDAP instances and optionally delete the unused instances. To restart the LDAP instance, do the following:
  1. In the Site Server Microsoft Management Console (MMC), open the Personalization and Membership (P&M) snap-in.
  2. Double-click to expand the server and double-click to expand the instance.
  3. Right-click the LDAP object for the instance.
  4. Click Start.
If the LDAP instance is not used, you may need to delete the instance to avoid events 4107 and 4102. To delete the unused LDAP instance, do the following:
  1. In the Site Server MMC, open the P&M snap-in.
  2. Double-click to expand the server and right-click the instance.
  3. Click Delete.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Site Server version 3.0.
Modification Type:MajorLast Reviewed:6/25/1999
Keywords:kbbug KB222950
©2002 Microsoft Corporation. All rights reserved.