Process msexchangeadtopology. when updating security for a remote procedure call
In a day to day scenario most of the Exchange Administrator see common error message “Exchange failed to start”, with error message “Process STORE. Topology discovery failed due to LDAP_SERVER_DOWN error”.
To Isolate such scenarios below are the steps that have to checked. 2: Obviously they must all be pointing to an internal DNS server, also we need to confirm that all exchange servers and domain controllers have a single NIC.
Only run these commands on your Exchange 2010 server if you are sure that there is a Active Directory Domain Controller in the same Active Directory site as your Exchange 2010 server and the Exchange 2010 server is able to communicate with the Active Directory domain controller.
Ensure you diagnose all other possible resolutions first such as network/storage/cpu/memory bottlenecks.
If this is the case, you need to make sure that the policy that is responsible for applying the right grants the Exchange Servers (or Exchange Enterprise Servers) group the right, or edit the Group Policy Links for you Domain Controllers OU so that the Default Domain Controllers Policy is applied. 4: Right side or middle of the page find Manage Auditing and security Log in the properties we need add “Exchange Servers” Group, need to add if it’s not present.
The site monitor API was unable to verify the site name for this Exchange computer – Call=Hr Search Error code=80040a01.By default, the Exchange Servers (Exchange 20) group and Exchange Enterprise Servers (Exchange 2003) group are added to this right in the Default Domain Controllers Policy. In Exchange 2003, this is done during the setup /domainprep process.In Exchange 20, this is done during setup /preparedomain process.The site monitor API was unable to verify the site name for this Exchange computer - Call=Hr Search Error code=80040934.When this issue was occuring I verified that the Exchange 2010 server was successfully talking to a domain controller in the same Active Directory site by issuing the following command from a command prompt: This resolved the problem.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.