MSExchange ADAccess 2103

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 Warning event indicates that the DSAccess component on the server that is running Microsoft Exchange found no global catalogs that are suitable for LDAP queries. This can cause mail flow to stop. It can also affect the address book services. This Warning event should be investigated immediately. This event may be caused by either of the following conditions:

• DSAccess found no suitable global catalogs when initial topology discovery was finished.
• Network problems have made global catalog servers unreachable.

User Action

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

• If you can, make sure that you have at least two domain controllers in a site that is configured by having global catalog servers. This is to account for failover.
• 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.
• If MSExchangeADAccess Event ID 2080 is logged, no suitable global catalogs were found when initial topology discovery was 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 MSExhchangeADAccess Event ID 2070 is logged, a global catalog may be down or unreachable. Review the event to get details about why each domain controller has become unsuitable. ADAccess 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.

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.