Process msexchangeadtopology pid 1212 when updating security for a remote procedure
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions. Exchange Active Directory Provider failed to obtain DNS records for forest %3.
For information about correcting this problem, %6%7 Process %1 (PID=%2).Set event logging level for Validation category to Expert to get additional events about each failure. A cache hash table that stores DSAccess information ran out of memory.This event can be caused by internal memory issues.Microsoft Exchange Server 2010 generates MSExchange ADAccess events in Event Viewer so that you can troubleshoot and verify the ADAccessfeatures, and services.Event Viewer tracks the following kinds of events in the given order, based on importance: Process %1 (PID=%2).This event may be caused because of internal memory issues.
You may be able to resolve this event by restarting the Microsoft Exchange Active Directory Topology service.
Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers. Exchange Active Directory Provider received a request to connection to domain controller %3 but that domain controller is not available.
Run the Dcdiag command line tool to test domain controller health. Internal error - A hash table that stores DSAccess information is damaged and cannot be used.
In addition, make sure that the network ports that are used by RPC are not blocked by a firewall. Exchange Active Directory Provider could not find an available domain controller in domain %3.
This event may be caused by network connectivity issues or configured incorrectly DNS server.
A request to Directory Server %3 did not return a result within %4 seconds and is being abandoned. The search that failed has the following characteristics: Base DN=%5, Filter=%6, Scope=%7. DSAccess did not register an Active Directory shutdown notification with the local server, error 0x%3 (%4).