Process (PID=). All Global Catalog Servers in use are not responding:

Product: exchange
Event ID: 2103
Source: msexchangedsaccess
Version: 6.5.6940.0
Component: Microsoft Exchange Directory Access Service
Message: Process <process name> (PID=<process id>). All Global Catalog Servers in use are not responding:<fully qualified domain name>

This event indicates that DSAccess was not able to find any global catalogs suitable for Lightweight Directory Access (LDAP) queries. This can result in the halting of mail flow and interruption of Address Book services, so it should be investigated immediately.

Causes can include all intra- and extra-site global catalogs being down or network problems hindering communication with them.

User Action

One possibility is that DSAccess could not find any suitable global catalogs when it did its initial topology discovery (whenever DSAccess starts, such as at Exchange server boot-up).

In this case, check the event log for DSAccess Event ID 2080 (may need to increase the DSAccess logging level to record this event). The detail in that event will allow one to determine if global catalogs have been contacted that are unsuitable for some reason. They can then be corrected.

Another possibility is that global catalogs already in use have become unsuitable (for example, by having lost contact due to network problems, LDAP port problems, and so on). Look for DSAccess Event ID 2070 in the event logs. These events will detail why each global catalog has become unsuitable. Correct as necessary.


Leave a Reply