Export (0) Print
Expand All
Expand Minimize

System Attendant legacyExchangeDN value is missing

[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: 2007-01-09

The Microsoft® Exchange Server Analyzer Tool queries the Active Directory® directory service to determine the value of the legacyExchangeDN attribute for the System Attendant object for each Exchange Server computer. If the Exchange Server Analyzer does not find a value for the legacyExchangeDN attribute of any System Attendant object, the Exchange Server Analyzer displays an error message.

A missing legacyExchangeDN can result when an administrator modifies Active Directory to recover a database in a failure recovery situation. To resolve this error, you must modify the legacyExchangeDN attribute using an Active Directory editor, such as the LDP (ldp.exe) tool or Active Directory Service Interfaces (ADSI) Edit.

To make sure that the legacyExchangeDN attribute is correct you should also examine other System Attendant objects for this server or another Exchange server that does not generate this error, because they should have a similar value for the legacyExchangeDN attribute.

In a situation where the legacyExchangeDN attribute is missing on a database, probably the attribute is also missing on several other system objects. Therefore, if you use LDP or ADSI Edit to add a new legacyExchangeDN value, you will have to add a new legacyExchangeDN value on all the other system objects also.

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 Exchange Server 2007, or both. Modify Active Directory object attributes at your own risk.
To correct this error
  1. Open an Active Directory editor, such as ADSI Edit.

  2. Expand Configuration [DomainName], expand, CN=Configuration, DC=DomainName, DC=DomainSuffix.

  3. Expand CN=Services, and then expand CN=Microsoft Exchange.

  4. Expand CN=OrganizationName, expand CN=Administrative Groups, and then expand CN=AdminGroupName.

  5. Expand CN=Servers, expand CN=ServerName.

  6. Right-click CN=Microsoft System Attendant and select Properties.

  7. Scroll down to locate legacyExchangeDN, select it, and click Edit.

  8. In the Value field, enter the correct legacyExchangeDN.

  9. Close the Active Directory editor and restart the Exchange Server computer for the change to take effect.

For more information about using ADSI Edit to create a new legacyExchangeDN attribute, see the Microsoft Knowledge Base article 273863, "How to Change the LegacyExchangeDN Attribute in Native Mode with ADSI Edit" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=273863).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft