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 description for Event ID ( 2048 ) in Source ( MSExchangeDSAccess ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Excessive LDAP Timeouts occured. Process/PID/DC/PLDAP/MsgId/CLdapConnection*:, INETINFO.EXE, 1584, <host name>, 0xe82058, 0x390d, 0xbfbe177c.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a DLL?
What is causing the “The description for Event ID ( … ) in Source ( …. ) cannot be found… “?
What is the role of the Microsoft Exchange Directory service?
What is LDAP?
This behavior can occur if the \MSExchangeDSAccess\Instance0:MaxMemory registry key is set to less than 2 megabytes (MB). Attributes are not cached. The 2-MB value is used for DSAccess at a minimum. See ME309179 for more details.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated