Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The Site Server Authentication Service could not do an LDAP bind. Error: <error code>, virtual server number '<number>'. 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.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is an authentication protocol?
What is LDAP?
- Error code: 81 - This problem occurs when you attempt to connect to the SQL Server computer using a SQL Server alias name and you have Microsoft Data Access Components version 2.1 SP2 installed on your Site Server computer. See ME239855 to solve this issue.
- Error code: 49 - This problem occurs if the computer name is greater than 11 characters. See ME193375 for details on this issue.
Error code 81: As per ME222950, these errors are known to occur if you have multiple Lightweight Directory Access Protocol (LDAP) instances and one of them is stopped. See the above mentioned article for more details.
Error 32: no info
It appears in the application log along with a warning Event ID 4102. It happens if you have more than one instance of LDAP running on the same server and one of them is stopped. The solution is to start the stopped instance or delete it if you don't need it anymore. See article ME222950.
|Private comment: Subscribers only. See example of private comment|
|Links: ME193375, ME222950, ME239855|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated