Process msexchangeadtopology pid 1212 when updating security for a remote procedure

Posted by / 18-Oct-2017 00:38

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.DNS Priority and Weight for the Global Catalog servers in this forest will be set to the default values %4 (priority) and %5 (weight). Domain controller %3 was not found when DNS was queried for the service location (SRV) resource records for domain %4 The query was for the SRV record for %5 The following domain controllers were identified by the query:%6 Common causes of this error include the following: - The DNS SRV records required to locate a domain controller for the domain are not registered in DNS.Try to resolve this event by restarting the computer that is running Exchange.If this event reoccurs, review the Application log and System log for any corresponding Warning or Error events. The configuration domain controller specified in the registry (%3) was not found in the Sites container in the Active Directory.I had an issue at a customer site where a vitalised multi role Exchange 2010 server was randomly loosing access to Active Directory.There were two Active Directory Domain Controllers with the Global Catalog role in the same Active Directory site as the Exchange 2010 server with highspeed 1gbps LAN between the servers.These records are registered with a DNS server automatically when a domain controller is added to a domain.They are updated by the domain controller at set intervals.

To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error.

After several hours of troubleshooting when we tried to reinstall Exchange, it failed with : Error: The following error was generated when "$error.

Clear(); initialize-Server Permissions -Domain Controller $Role Domain Controller " was run: "Could not find a directory entry for the local host.".

When the issue occured Exchange 2010 would begin spitting the generic errors you receive whenever there is no Active Directory domain controller available.

Some of these errors include: Log Name: Application Source: MSExchange ADAccess Date: 13/08/2012 AMEvent ID: 2114Task Category: Topology Level: Error Keywords: Classic User: N/AComputer: Exchange2010.domain.local Description: Process STORE. Topology discovery failed, error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)).

Process msexchangeadtopology pid 1212 when updating security for a remote procedure-30Process msexchangeadtopology pid 1212 when updating security for a remote procedure-26Process msexchangeadtopology pid 1212 when updating security for a remote procedure-90

Make sure that the Remote Procedure Call (RPC) service is running.