MSExchangeDSAccess 2114

Event ID: 2114
Source	MSExchangeDSAccess
Type	Error
Description	Process <process> (PID=<PID>). Topology Discovery failed, error <error code>.
Things to understand	What is the role of the Microsoft Exchange Directory service?
Comments	Joe Richards (Last update 6/10/2005): - Error code: 0x8007077F - This means that no site/subnet has been defined for the Exchange server. Check the IP address of the Exchange server, define a subnet in Active Directory, and assign that subnet to the proper site. Ionut Marin (Last update 6/10/2005): - Error code: 0x80040a02 - This event can be caused by the evaluation version of SharePoint Portal Server. After this evaluation period has expired this event along with others are logged in your event log. See M823722 for more details. As per Microsoft: "This event indicates that new topology could not be generated. If this is NOT the first topology discovery since system startup, the previously discovered topology will be used. However, topology discovery failure is usually a sign of a serious problem and needs to be investigated immediately". See MSEX2K3DB for more details on this event. Marty (Last update 6/10/2005): Check that the "Exchange servers" group has the rights to "manage audit and security logs". On a working DC, go to Start -> Programs -> Admin tools -> Domain controller security -> Local settings -> User Rights and find the manage audit and security logs option. Add the group if necessary. Anonymous (Last update 3/4/2005): We found this event popping up in a system with Windows 2003 Standard Server and Exchange Server 2003 Service Pack 1. It was followed by event 2102 stating that the Exchange server is not able to discover the topology of our AD. To solve it we activated the MSExchangeDSAccess diagnostic logging. We set the Topology section to maximum logging. The next topology discovery cycle revealed that it was trying to get AD information from a public DNS instead of our internal AD DNS servers. This problem appeared because our TCP/IP local configuration included two internal DNS servers and two public DNS and the exchange topology discovery engine took the list and used it in the reverse order, therefore it was searching the Internet for private information. Mauro Patrucco (Last update 9/13/2004): This problem can appear because the service principal name for ldap is not registered for the Exchange virtual server. You can verify this with the setspn utility (Windows 2003 resource Kit). Enter the following command: ”setspn -l [exchange_virtual_server_name]”. If you do not see: ”ldap/[exchange_virtual_server_name]” ”ldap/[exchange_virtual_server_FullQualifiedDomainName]”, then add it manually ”setspn -a ldap/[exchange_virtual_server_name]” ”setspn -a ldap/[exchange_virtual_server_FQDN]”. Elliott Fields Jr (Last update 5/6/2003): No Domain Controllers could be located for Directory Access.