MSExchange ADAccess 2084

Letztes Änderungsdatum des Themas: 2011-03-24

Thank you for clicking the link that brought you to this page. We do not currently have an article to resolve this specific issue. Your attempt to get to this event article helps us prioritize the event articles for which we will be providing detailed explanations and user actions.

Although there is as yet no supplementary content specifically written to help resolve this Exchange 2010 event, here are some recommended next steps to learn more about this alert:

• Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.
• Research your issue by using self-support options. From the navigation pane of the Exchange Server Solutions Center page, click Self Support Options to use the following and other self-help options:
  • Search the Microsoft Knowledge Base. For example, search the Knowledge Base for the Event Source and event ID you are getting, as well as any other key words in the text of the event message.
  • Search the Exchange 2010 Forum. You can also post a question there.
  • Search the Exchange Server Community Web site.
• Research your issue by using other resources. From the navigation pane at the Exchange Server Solutions Center page, click Key Resources to learn about other resources.
• Resolve your issue by using assisted support options. From the Exchange Server Solutions Center page, click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Technical Support, be sure to reviewing your organization's guidelines first. If you do contact support, have the event ID information available. Also, if possible, be prepared to send your application and system logs to the support professional.

Details

Explanation

This event indicates that no suitable domain controllers exist in the local site. DSAccess will use out-of-site domain controllers, but they may respond more slowly. This can cause message queuing and network saturation. This event may be logged when the following conditions are true:

• No domain controllers exist in the local site.
• All in-site domain controllers are down.
• Network problems are preventing the Microsoft Exchange server from contacting the domain controllers.
• Permission problems exist.
• Configuration errors exist.

User action

To resolve this problem, do one or more of the following:

• Make sure that at least one domain controller in the local site has been promoted to a global catalog server, and that enough time has passed for this server to synchronize with other global catalog servers.
• If a global catalog server is expected to be present, verify that it is running and is reachable over the network from the Exchange server.
• Use the nltest /dsgetdc: /site:<local site name> command to verify that a global catalog server can be located in the local site. Look for the global catalog server flag in the nltest output. The NLTest tool is installed together with the Windows support tools.
• Suchen Sie im Anwendungsprotokoll nach verwandten Ereignissen. Die Details in weiteren MSExchange ADAccess-Ereignissen und anderen Ereignissen können dabei helfen, die Hauptursache für diese Warnung zu ermitteln. Erhöhen Sie den Diagnoseprotokolliergrad für die Kategorie "MSExchange ADAccess\Topologie" auf Niedrigste oder höher. Weitere Informationen zur Erhöhung des Protokolliergrads finden Sie unter Verwalten der Diagnoseprotokolliergrade.
• To review the current MSExchangeADAccess service diagnostic logging settings, type Get-EventLogLevel MSExchangeADAccess in the Exchange Management Shell.
• To change the logging level for the Topology category, type Set-EventlogLevel MSExchangeADAccess\Topology -Level Minimum in the Exchange Management Shell.
• If MSExchangeADAccess Event ID 2080 is logged, no suitable global catalogs may have been found when initial topology discovery finished. Review that event to determine which domain controllers have been contacted and whether they are unsuitable for any reason. Correct any problems as indicated by the event description. For more information, see Microsoft Knowledge Base article 316300, Event ID 2080 from MSExchangeDSAccess.
• If MSExchangeADAccess Event ID 2070 is logged, a global catalog may be down or unreachable. Review the event for more information about why each domain controller has become unsuitable. DSAccess found no suitable global catalogs when initial topology discovery was finished.
• Verwenden Sie das Befehlszeilentool Ping oder PathPing zum Testen der grundlegenden Konnektivität. Verwenden Sie Ping, um Netzwerkhardwareprobleme und inkompatible Konfigurationen zu isolieren. Verwenden Sie PathPing, um Paketverluste bei Routen mit mehreren Hops zu ermitteln. Weitere Informationen finden Sie im Microsoft Knowledge Base-Artikel 325487 Behandlung von Problemen mit der Netzwerkverbindung.

For more information about diagnostic logging commands, see Get-EventLogLevel and Set -EventLogLevel in the Exchange 2007 Help.

Note   Wenn dies nicht bereits der Fall ist, sollten Sie die Exchange-Tools ausführen, die für die Analyse und Problembehandlung der Exchange-Umgebung erstellt wurden. Mit diesen Tools kann sichergestellt werden, dass Ihre Konfiguration die bewährten Methoden von Microsoft einhält. Sie tragen zudem zur Identifikation und zur Lösung von Leistungsproblemen bei, und können die Nachrichtenübermittlung verbessern. Sie können diese Tools über den Knoten Toolbox in der Exchange-Verwaltungskonsole ausführen. Weitere Informationen zu diesen Tools finden Sie unter Verwalten von Tools in der Toolbox.