Process %1 (PID=%2). No Domain Controller server was found in the local site %3. Exchange Active Directory Provider will try to find Domain Controller servers in other sites.

Details
Product: Exchange
Event ID: 2086
Source: MSExchangeADAccess
Version: 8.0
Symbolic Name: DSC_EVENT_NO_LOCAL_DC_FOUND
Message: Process %1 (PID=%2). No Domain Controller server was found in the local site %3. Exchange Active Directory Provider will try to find Domain Controller servers in other sites.
   
Explanation

This Informational event indicates that Microsoft Exchange Active Directory Provider could not find any suitable domain controllers in the local Active Directory site. Domain controllers in the other Active Directory sites will be discovered. Using domain controllers from remote Active Directory sites can slow down the performance and may cause message queuing and network saturation.

This event may occur if one or more of the following conditions are true:

  • Network connectivity problems prevent this server that is running Exchange Server from contacting the domain controllers in the local Active Directory site.

  • All the domain controllers in the local Active Directory site are not working.

  • The domain controllers have not been configured correctly.

  • There are permission problems that prevent this Exchange server from using the available domain controllers.

   
User Action

To resolve this issue, follow these steps:

  • Make sure that the Active Directory site where this Exchange server is installed has at least one working domain controller.

  • Use the Ping or PathPing command line tools to test basic connectivity. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

  • Use the nltest /dsgetdc: /site:<local site name> command to verify that a domain controller can be located in the local Active Directory site. The nltest tool is installed with the Microsoft Windows support tools.

  • Make sure that all the domain controllers in local Active Directory site are registered correctly on the DNS server. For more information, see the following Microsoft Knowledge Base articles:

  • Determine which attributes or properties contain invalid values.

    1. Increase the diagnostic logging level on the Validation counter of the MSExchangeADAccess performance object. You can increase logging by running the following Exchange Management Shell cmdlet: Set-EventLogLevel MSExchangeADAccess\Validation -Level High. For detailed information about how to increase logging, see Changing Process Logging Levels.

    2. Review the additional MSExchangeADAccess events in the Application log to determine which attributes or properties contain invalid values.

      Important   After you have completed troubleshooting this issue, return logging to the default level by running the following cmdlet: Set-EventLogLevel MSExchangeADAccess\Validation -Level Lowest.

  • If you find MSExchangeADAccess Event ID 2070 in the Application log, it indicates that Exchange Active Directory Provider lost contact with one or more domain controllers. For more information about how to resolve Event ID 2070, visit Events and Error Message Center.

  • Run the Dcdiag command line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview.

Related:

Leave a Reply