Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Exchange data path in Active Directory does not match cluster registry

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2006-04-28

The Microsoft® Exchange Server Analyzer Tool queries both the cluster registry (HKEY_LOCAL_MACHINE\Cluster) and the Active Directory® directory service to determine if the paths for Exchange data files (for example, message tracking log files) are the same in both places. Exchange Server configures these values in the registry and in Active Directory when the Exchange Setup program is used to install Exchange on a node in a Microsoft Windows® server cluster.

The registry value created by Exchange Setup and read by the Exchange Server Analyzer is:

HKLM\Cluster\Resources\<Resource GUID of Information Store resource>\Parameters\DestPath

The Active Directory value created by Exchange Setup and read by the Exchange Server Analyzer is: msExchDataPath. This value is an attribute of the Exchange Server computer object in Active Directory, which is found at:

CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=OrganizationName=Administrative Groups, CN=AdministrativeGroupName, CN=Servers, CN=ServerName

If the Exchange Server Analyzer finds that the values for DestPath and msExchDataPath do not match, an error is displayed.

A common cause for these values to be different is when the location of some or all Exchange data files changes after Exchange has been in production. For example, if hardware is upgraded, message tracking log files are moved, and a drive letter is changed, the change is reflected in the cluster registry but not in Active Directory. After such a change has been made, service startup errors, database mounting issues, and other problems may result, especially when applying an Exchange service pack or installing a roll-up package.

noteNote:
You should resolve this discrepancy as soon as possible. Do not install any service packs or updates to Exchange Server until this problem is corrected.

To perform the following procedure, you will need to use an Active Directory editor such as Active Directory Service Interfaces (ADSI) Edit or the LDP (ldp.exe) tool.

CautionCaution:
If you incorrectly modify the attributes of Active Directory objects when you use ADSI Edit, the LDP tool, or another Lightweight Directory Access Protocol (LDAP) version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003, or both. Modify Active Directory object attributes at your own risk.
  1. Modify the affected Exchange Virtual Server (EVS) value for msExchDataPath so that it matches the value in the cluster registry for DestPath. The msExchDataPath attribute can be found at:
    CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=OrganizationName=Administrative Groups, CN=AdministrativeGroupName, CN=Servers, CN=ServerName

  2. Restart the virtual server's Exchange System Attendant resource for the change to take effect.

For more information about modifying Active Directory with the LDP tool, see the Microsoft Knowledge Base article 260745, "XADM: Using the LDP Utility to Modify Active Directory Object Attributes" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=260745).

For more information about how to use ADSI Edit to modify the msExchDataPath attribute, see the Knowledge Base article 288362, "XADM: "The System Cannot Find the Path Specified" Event ID 5007 Message is Logged by the Microsoft Exchange System Attendant" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=288362).

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.