Microsoft KB Archive/246864

{|
 * width="100%"|

XADM: How to Change the Location of Log Files for Message Tracking

 * }

Q246864

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS
When tracking is enabled on a Microsoft Exchange 2000 Server computer, the tracking logs are written to the location %Exchsrvr%\ServerName.log where %Exchsrvr% represents the directory in which Exchange 2000 is installed. The log file names are in the format, yyyymmdd.log (where y is the year, m the month, and d the day). No user interface exists to change the location of tracking logs.

WORKAROUND
To change the location of tracking logs, you must make the location change to the registry:

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).


 * 1) Start Registry Editor (Regedt32.exe).
 * 2) Locate the LogDirectory value under the following key in the registry:
 * 3) On the Edit menu, click String, and type the new path for the log directory, and then click OK.
 * 4) Quit Registry Editor.
 * 5) Stop and restart the system attendant service so that the change can take effect.

STATUS
Microsoft has confirmed this to be a problem in Exchange 2000 Server ..

Additional query words:

Keywords :

Issue type : kbbug kbprb

Technology :