Process %1 (PID=%2). DSAccess could not discover the Fully Qualified Domain Name (FQDN) of local server with Exception %3. The local name that was used to look up the server is %4. This event may be caused by an incorrectly configured DNS server. It may also occur if the local server was renamed but DNS records were not updated. To resolve this error, see “Troubleshooting DNS servers” in the Microsoft Windows Server TechCenter. In addition, if the name of the server that logged this event was changed, make sure that the computer was restarted.

Details
Product: Exchange
Event ID: 2075
Source: MSExchange ADAccess
Version: 08.01.0107.000
Symbolic Name: DSC_EVENT_FIND_LOCAL_SERVER_FAILED
Message: Process %1 (PID=%2). DSAccess could not discover the Fully Qualified Domain Name (FQDN) of local server with Exception %3. The local name that was used to look up the server is %4. This event may be caused by an incorrectly configured DNS server. It may also occur if the local server was renamed but DNS records were not updated. To resolve this error, see “Troubleshooting DNS servers” in the Microsoft Windows Server TechCenter. In addition, if the name of the server that logged this event was changed, make sure that the computer was restarted.
   
Explanation

This Error event indicates that the Fully Qualified Domain Name (FQDN) of the local computer could not be discovered. This event generally occurs when the Exchange server that logged this event runs on a domain controller. This event occurs if one or more of the following conditions are true:

  • The DNS server is not correctly configured.

  • The name of the computer that logged this event was changed. However, DNS records were not updated to reflect that change.

   
User Action

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

  • Make sure that the server the logged this event is correctly registered on the DNS server. For more information about how to troubleshoot DNS issues, see Troubleshooting DNS servers in the Microsoft Windows Server TechCenter.

  • If the name of the computer that logged this event was changed, make sure that the computer was restarted.

  • Review other related events in the Application log and System log for Warning events and Error events. These related events may provide more information about the root cause of this error.

Note  If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Leave a Reply