Directory Service Access (DSAccess) failed to provide a domain controller to use to read configuration with error 0x%1. Proxy address calculation services will not be available on the local Exchange server. %2

Details
Product: Exchange
Event ID: 8364
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_LDAP_DSCONFIG_DSACCESS_GETDC_FAILED
Message: Directory Service Access (DSAccess) failed to provide a domain controller to use to read configuration with error 0x%1. Proxy address calculation services will not be available on the local Exchange server.
%2
   
Explanation

This Error event indicates that Directory Service Access (DSAccess) returned a zero-length name for the configuration domain controller because of error %1. As a result, Microsoft Exchange Server %2 will not be able to calculate proxy addresses. This error is an indication of a much larger problem. Exchange Server cannot contact a configuration domain controller. This error only occurs if DSAccess returns a zero-length name for the configuration domain controller.

   
User Action

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

  • Review the System and Application event logs 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.

  • Verify that the Exchange Server network connection is functioning.

  • Try to contact any domain controller or global catalog in the Microsoft Windows site.

  • Try to contact the configuration domain controller.

  • Run the tools that Exchange offers to help administrators analyze and troubleshoot their Exchange environment. Open the Toolbox node of the Exchange Management Console to run these tools.

If you cannot resolve this error, or you experience other problems or mail flow interruptions in your Exchange environment after attempting to resolve this error, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.

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:

Microsoft Exchange failed to initialize Directory Service Access (DSAccess) with error 0x%1. Proxy address calculation services will not be available on the local Exchange server. %2

Details
Product: Exchange
Event ID: 8363
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_LDAP_DSCONFIG_DSACCESS_INIT_FAILED
Message: Microsoft Exchange failed to initialize Directory Service Access (DSAccess) with error 0x%1. Proxy address calculation services will not be available on the local Exchange server.
%2
   
Explanation

This Error event indicates that Directory Service Access (DSAccess) could not locate a configuration domain controller because of the error specified in the event description. As a result, the Microsoft Exchange Server specified in the event description will not be able to calculate proxy addresses. This error is an indication of a much larger problem. Exchange Server cannot contact a configuration domain controller.

   
User Action

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

  • Review the System and Application event logs 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.

  • Verify that the Exchange Server network connection is functioning.

  • Try to contact any domain controller or global catalog in the Microsoft Windows site.

  • Try to contact the configuration domain controller.

  • Run the tools that Exchange offers to help administrators analyze and troubleshoot their Exchange environment. Go to the Toolbox node of the Exchange Management Console to run these tools.

If you cannot resolve this error, or you experience other problems or mail flow interruptions in your Exchange environment after attempting to resolve this error, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.

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:

Microsoft Exchange couldn’t read the forest GUID from %1. Proxy address calculation services will not be available on the local Exchange server. %2

Details
Product: Exchange
Event ID: 8362
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_LDAP_DSCONFIG_READ_FOREST_GUID_FAIL
Message: Microsoft Exchange couldn’t read the forest GUID from %1. Proxy address calculation services will not be available on the local Exchange server.
%2
   
Explanation

This Error event indicates that Microsoft Exchange Server cannot read the globally unique identifier (GUID) of the configuration naming context in the Active Directory directory service domain %1. As a result, Exchange Server %2 will not be able to generate proxy addresses. This error is an indication of a much larger problem. Default permissions on the configuration naming context in Active Directory may be too restrictive.

   
User Action

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

  • Review the System and Application event logs 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.

  • Verify that the Authenticated Users group has been assigned the List Contents, and Read Property Permission on the configuration naming context in Active Directory.

  • Run the tools that Exchange offers to help administrators analyze and troubleshoot their Exchange environment. Open the Toolbox node of the Exchange Management Console to run these tools.

If you cannot resolve this error, or you experience other problems or mail flow interruptions in your Exchange environment after attempting to resolve this error, contact Microsoft Product Support. For information about contacting support, visit the Microsoft Help and Support Web site.

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:

Microsoft Exchange couldn’t establish an encrypted Kerberos LDAP connection to %1. Please ensure that the domain controller %1 is running Windows 2000 Server SP3 or later. %4

Details
Product: Exchange
Event ID: 8360
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_LDAP_ENCRYPTION_ERROR
Message: Microsoft Exchange couldn’t establish an encrypted Kerberos LDAP connection to %1. Please ensure that the domain controller %1
is running Windows 2000 Server SP3 or later.
%4
   
Explanation

This Error event indicates that the Exchange server could not establish an encrypted Kerberos Lightweight Directory Access Protocol (LDAP) connection to the domain controller specified in the event description because the domain controller was not running the required version of Microsoft Exchange Server.

   
User Action

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

  • Review the System and Application event logs 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.

  • Run the tools that Exchange offers to help administrators analyze and troubleshoot their Exchange environment. Open the Toolbox node of the Exchange Management Console to run these tools.

If you cannot resolve this error, or you experience other problems or mail flow interruptions in your Exchange environment after attempting to resolve this error, contact Microsoft Product Support. For information about contacting support, visit the Microsoft Help and Support Web site.

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:

Microsoft Exchange couldn’t read the registry key ‘%1’ under ‘HKLM\%2’ because the value is not a DWORD.

Details
Product: Exchange
Event ID: 8358
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_SERVICE_REGISTRY_DWORD_FAIL
Message: Microsoft Exchange couldn’t read the registry key ‘%1’ under ‘HKLM\%2’ because the value is not a DWORD.
   
Explanation

This Error event indicates that the registry key %1 in the HKEY_LocalMachine hive %2 is not a DWORD type as expected. This is abnormal as most keys are created by an Exchange server installation.

   
User Action

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

  • Examine the registry key and determine the value type.

  • Check your server change history to determine if and when this registry key was added by an administrator. If the key was added by an administrator, correct the key to a DWORD type.

  • If the key was not added by an administrator, contact Microsoft Product Support Services. For information about how to contact support, visit the Microsoft Help and Support Web site.

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:

Could not establish a signed Kerberos LDAP connection to %1. Please ensure the domain controller %1 is running Windows 2000 SP3 or later. %4

Details
Product: Exchange
Event ID: 8339
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_LDAP_SIGNING_ERROR
Message: Could not establish a signed Kerberos LDAP connection to %1. Please ensure the domain controller %1
is running Windows 2000 SP3 or later.

%4

   
Explanation

This Error event indicates that the Exchange server could not establish a signed Kerberos LDAP connection to domain controller %1 because the domain controller was not running the required version of Windows Server. Microsoft Exchange Server 2007 requires at least one Windows Server 2003 Service Pack 1 global catalog server in every Windows site to support Active Directory change notification.

   
User Action

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

  • Review the System and Application event logs 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.

  • Upgrade the server specified in this error event to the required version of Windows Server.

  • If you cannot resolve this error or if you experience other problems or mail flow interruptions in your Exchange environment, contact Microsoft Product Support Services. For information about contacting support, visit the Microsoft Help and Support Web site.

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:

The service threw an unexpected exception which was caught at %1(%2)

Details
Product: Exchange
Event ID: 8331
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_RUS_UNHANDLED_EXCEPTION
Message: The service threw an unexpected exception which was caught at %1(%2)
   
Explanation

This Error event indicates that the Address List Service cannot stamp Microsoft Exchange attributes on Active Directory directory service objects. When this event is being logged, users may not appear in the global address list (GAL). Additionally, users may not be able to access their Exchange mailboxes. These GAL display problems and mailbox access problems may occur if an internal class incorrectly processes certain threads that run at the same time.

   
User Action

To resolve this Error event, do the following:

  • Review the Application log 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.

If you are having difficulty resolving the issue, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.

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:

The service can’t work properly because Email Address Policy ‘%1’ has an invalid filter rule (PurportedSearch). The error is ‘%2’. Use the Exchange Management Console to correct this problem. New users, contacts, and groups won’t be fully provisioned until this is fixed. %3

Details
Product: Exchange
Event ID: 8325
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_AL_INVALID_PURPORTEDSEARCH_RP
Message: The service can’t work properly because Email Address Policy ‘%1’
has an invalid filter rule (PurportedSearch). The error is ‘%2’.
Use the Exchange Management Console to correct this problem.
New users, contacts, and groups won’t be fully provisioned until this is fixed.
%3
   
Explanation

This Error event indicates that the e-mail address policy specified in the event has an invalid filter rule. While this error exists, new users, contacts, and groups will not receive mail information.

   
User Action

To resolve this error, fix the filter rule. For more information, see How to Create an Address List By Using Recipient Filters.

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:

The Address List Service could not find the Address List Root which is located in the Exchange Service entry under the attribute addressBookRoots. This might have been caused by a permissions problem. %1

Details
Product: Exchange
Event ID: 8284
Source: MSExchangeAL
Version: 8.0
Symbolic Name: MSG_ALDG_NO_ADDRESS_LIST
Message: The Address List Service could not find the Address List Root which is
located in the Exchange Service entry under the attribute addressBookRoots.
This might have been caused by a permissions problem.
%1
   
Explanation

This Error event indicates that the Address List Service, formerly known as the Recipient Update Service, could not find the Address List Root object (addressBookRoots attribute of the MicrosoftExchange object in the Active Directory directory service). This could be because the Address List Service is unable to communicate with a domain controller or global catalog that is no longer available, has been demoted, or has invalid configuration information.

   
User Action

To resolve this error, restart the domain controller.

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:

When initializing session for virtual machine %1, no public folder server was detected in the Active Directory. Free/busy information will not be published to public folders.

Details
Product: Exchange
Event ID: 8280
Source: MSExchangeFBPublish
Version: 8.0
Symbolic Name: evtNoPublicFolders
Message: When initializing session for virtual machine %1, no public folder server was detected in the Active Directory. Free/busy information will not be published to public folders.
   
Explanation

This Warning event indicates that free and busy information will not be published to your public folders because none was found in the server’s Active Directory directory service. This disables free and busy interoperability with messaging clients, such as Microsoft Outlook 2003 and earlier versions, which expect free and busy information to be published to public folders.

   
User Action

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

  • Ensure that you have correctly designated a public folder server for interoperability with Microsoft Exchange Server 2003. Exchange Server 2007 does not require public folders to publish free and busy information. For more information, see Understanding the Availability Service and Managing the Availability Service.

  • Review the Application log for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this warning.

  • If you are still having difficulty resolving the issue, contact Microsoft Product Support. For information about contacting support, visit the Contact Us page of the Microsoft Help and Support Web site.

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: