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.
Process EMSMTA.EXE" (PID=2640). An LDAP search call failed - Error code=<error code>. Base DN=CN=SERVER,CN=SERVERS,CN=FIRST ADMINISTRATIVE GROUP,CN=ADMINISTRATIVE GROUPS,CN=M2D,CN=MICROSOFT EXCHANGE,CN=SERVICES,CN=CONFIGURATION,DC=M2D,DC=LOCAL, Filter=(objectClass=RFC1006Stack), Scope=2.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Directory service?
What is LDAP?
Peter Van Gils
- Error code: 80040957 - From a newsgroup post: "I have this exact problem and there seems to be no fix. What I have done is manually entered the GCs into the Exchange Server. To do this, open ESM and drilldown to your server, and open the properties. Click the Directory Access, under the Show header, click the down arrow and you will see three options: Configuration Domain Controller, Domain Controllers, and Global Catalog Servers. Take a note of each server in the 3 options. For each of the options clear the tick for “Automatically discover servers”, click OK to the message box, and then click the Add button. Enter your DCs/GCs in the AD Search box and click OK".
I have also seen this error on an Exchange 2003 SP2 cluster based on Legato CSBSAA 5.1. After contacting both Legato and Microsoft, the only solution was a complete reinstallation of the cluster.
As per Microsoft: "This error indicates that the DSAccess process in Exchange received an error when it made a Lightweight Directory Access Protocol (LDAP) call to a domain controller. This event might occur if the domain controller being used by the Exchange server is in a Child Domain. Such a domain controller would return a referral if the object being searched for (in the LDAP call) is not present in the Child Domain. However, DSAccess does not support referrals. This problem can also be caused by intermittent network problems or permissions issues". See MSEX2K3DB for more details.
Error code: 8004090a. This error is occuring on a clustered Exchange 2000 Server. ME309175 deals with a possible fix. They say that if the DS is looking to a domain controller in a child domain, that DC returns a referral, and DSAccess doesn't accept referrals. If DSAccess looks to a local domain controller, the proper LDAP query takes place and the request is answered. They say it's fixed in SP2 for Exchange 2000 Server. E2KS SP2 makes the Exchange Server look at Global Catalog servers for directory information, instead of any DC.
Error code: 8004090a. As per ME329166, this issue occurs because the Directory Services tab in Exchange System Manager lists only the domain controller and the configuration domain controllers that are in the site where you are currently located. Domain controllers and configuration domain controllers that are in other sites are not included in the search filter.
Error code: 80040952. This issue can occur because the carrier_some_users account should only exist on Mobile Information Server Carrier Edition servers. See ME313956.
Error code: 80040957. No info.
|Private comment: Subscribers only. See example of private comment|
|Links: ME309175, ME313956, ME329166, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (2) - More links...|
Send comments or solutions
- Notify me when updated