Details | |
Product: | Exchange |
Event ID: | 9057 |
Source: | CDOEXM |
Version: | 6.5.6940.0 |
Component: | CDO for Exchange Management |
Message: | NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service.New clients will be refused until a Global Catalog is available.After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients. |
Explanation | |
This event indicates that the Name Service Provider Interface (NSPI) Proxy cannot contact any global catalogs that support the NSPI Service. New clients will be refused until a global catalog is available. A domain controller that was recently promoted to a global catalog may not have been restarted. A global catalog must be restarted in order for the NSPI interface to be available. |
|
User Action | |
Check the general health of the global catalog servers. If you have recently promoted a domain controller to global catalog, remember that it must be rebooted in order to support MAPI clients. |
Category: Exchange
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:
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:
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:
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:
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:
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:
ADC cannot replicate to Exchange 5.5. because, on this server, LDAP Client Integrity is set to ‘2’ (always sign.) Exchange 5.5 does not support LDAP signing. To allow this serverto connect to 5.5., set the registry key to 0 (never sign) or 1 (sign if possible)
Details | |
Product: | Exchange |
Event ID: | 8341 |
Source: | MSADC |
Version: | 6.5.6940.0 |
Component: | Microsoft Exchange Active Directory Connector |
Message: | ADC cannot replicate to Exchange 5.5. because, on this server, LDAP Client Integrity is set to ‘2’ (always sign.) Exchange 5.5 does not support LDAP signing. To allow this serverto connect to 5.5., set the registry key <registry key>to 0 (never sign) or 1 (sign if possible)<value> |
Explanation | |
The Active Directory Connector (ADC) cannot replicate to Exchange 5.5. because, on this server, Lightweight Directory Access Protocol (LDAP) Client Integrity is set to 2 (Always sign). Exchange 5.5 does not support LDAP signing. |
|
User Action | |
Exchange 5.5 does not support LDAP signing. To allow this server to connect to Exchange 5.5., set the registry key to 0 (Never sign) or to 1. |
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: | MSExchangeADDXA |
Version: | 6.5.0000.0 |
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 | |
Could not establish a signed Kerberos LDAP connection.
Receiving this event indicates that the Connection Agreement may be stuck. |
|
User Action | |
Please ensure the domain controller is running Windows 2000 SP3 or later. |
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:
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 connect over LDAP to . This domain controller is running . Please upgrade to Windows 2000 SP3 or later.
Details | |
Product: | Exchange |
Event ID: | 8338 |
Source: | MSExchangeADDXA |
Version: | 6.5.6940.0 |
Component: | Microsoft Exchange Active Directory DXA Connector |
Message: | Could not connect over LDAP to <server name>. This domain controller is running <value> <value>. Please upgrade to Windows 2000 SP3 or later.<connection agreement name> |
Explanation | |
Could not connect over Lightweight Directory Access Protocol (LDAP) using the version of Windows that the designated domain controller is running. If you receive this event, this could indicate that the connection agreement is unable to function. |
|
User Action | |
Upgrade to Windows 2000 SP3 or later. |