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.
LDAP Search Initial Page on directory <directory name> at base '<value>' with filter '<value>' was unsuccessful. Directory returned the LDAP error:[0x<error code>] <error code>
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is LDAP?
What is the role of the Microsoft Active Directory Connector (MSADC) ?
This event is logged if LDAP errors occur during replication between Active Directory and the Exchange Server 5.5 directory. The ADC creates duplicate objects in the Exchange Server 5.5 directory when LDAP connectivity is lost when the ADC searches for objects in the Exchange Server 5.5 directory and LDAP connectivity is restored when the ADC tries to create new contacts because of the unsuccessful search for a matching object in the Exchange Server 5.5 directory. See ME837968 for a hotfix applicable to Microsoft Exchange Server 2003.
See ME837165 for a hotfix applicable to Microsoft Exchange 2000 Server.
As per Microsoft: "The Connection Agreement may be requesting too many objects based on the configuration setting of the target directory or the target server may have failed". See MSEX2K3DB for more details.
Check network connectivity. Verify the user name, password, and port address are correct, and try again. If the problem persists, verify that the remote Exchange server is configured to support LDAP.
|Private comment: Subscribers only. See example of private comment|
|Links: ME837165, ME837968, MSADC Events, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated