Events 4107 and 4102 Occur When an LDAP Instance Stops

Article ID: Q195297

The information in this article applies to:

Microsoft Site Server version 3.0

SYMPTOMS

When one of the LDAP instances is stopped, events 4107 and 4102 are generated every ten minutes in the Event Viewer log.

The event message of 4107 and 4102 are similar to the following:

   The Site Server Authentication Service could not do an LDAP bind.

   Error: 81, virtual server number 2. 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.

WORKAROUND

To work around this problem, perform the following steps:

1. Restart the LDAP instance by doing the following:

   a. In the Site Server Microsoft Management Console (MMC), open the
      Personalization and Membership (P&M) snap-in.

   b. Select the LDAP property.

   c. Select Start.

2. 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:

   a. In the Site Server MMC, open the P&M snap-in.

   b. Select the instance property.

   c. Select Delete.

MORE INFORMATION

For additional information, please see the following article in the Microsoft Knowledge Base:

   Q222950 4107 and 4102 Error Messages Occur When LDAP Instance Is Stopped

Additional query words:

Keywords          :  
Version           : winnt:3.0
Platform          : winnt
Issue type        : kbprb
Solution Type     : kbpending