XADM: "The System Cannot Find the Path Specified" Event ID 5007 Message is Logged by the Microsoft Exchange System Attendant

Microsoft Exchange System Attendant may log the following event ID message:

This behavior can occur because the msExchDataPath attribute on the server object is the base folder where the system attendant writes the tracking log files. However, it appends the ServerName.log. For example, if the server has the name Server7890, the value for the msExchangeDataPath attribute is drive name:\Exchsrvr. The actual path to which the tracking logs are written is similar to the following example: This event ID message is common on Cluster Servers; however, it is not restricted to Cluster Servers.

To resolve this behavior, make sure that the msExchDataPath attribute is pointed properly, and that the msExchDataPath attribute contains a folder ServerName.log

To modify the msExchDataPath attribute, start ADSI Edit from the Windows 2000 Support Tools.

WARNING: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Exchange 2000 Server, or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

1. In ADSI Edit, click to expand the Configuration container.
2. Click to expand each of the following:
   CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=YourOrganization, CN=Administrative Groups, CN=YourAdministrative Group, CN=Servers, CN=ServerName
3. Right-click ServerName, click Properties, and then in the Select Property to View list, click the msExchDataPath attribute.
4. Type the correct path in the Edit Attribute box, and then click Set.
5. Restart the Exchange 2000 Server computer.

For additional information about changing the location for the tracking logs, click the article number below to view the article in the Microsoft Knowledge Base: