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 <process name> (PID=<process id>). The Configuration Domain Controller specified in the registry (<distinguished name>)was not found in the Sites container in the Active Directory. DSAccess will choose the Configuration Domain Controller from the list of available Domain Controllers.
|English: Request a translation of the event description in plain English.|
This event occurred after one of our DCs crashed. Appears to be similar to Event ID 2090 from the same source. Solution: In Exchange System Manager drill down to your server, right click, choose Properties and go to the "Directory Access" tab. Pull the drop down to select the category where the missing DC is listed, remove that DC and add one that can be contacted. Repeat for all categories as necessary.
As per Microsoft: "This message indicates that the configuration domain controller specified by the registry key does not exist. DSAccess will revert to the standard mechanism of automatically choosing the configuration domain controller. This event can occur if the Administrator misspells the hostname in the HKLM\System\CurrentControlSet\Services\MsExchangeDSAccess\Instance0\ConfigDCHostName registry key on the Exchange server". See MSEX2K3DB for additional information about this event.
|Private comment: Subscribers only. See example of private comment|
|Links: MSEX2K3DB, Event ID 2090 from source MSExchangeDSAccess|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated