Article ID: 316780
Article Last Modified on 3/2/2007
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Exchange 2000 Enterprise Server
This article was previously published under Q316780
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SUMMARY
This article describes how to turn on verbose logging for the Exchange resources on a cluster.
MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
For advanced troubleshooting of issues that are related to Exchange 2000 on a Windows 2000 server cluster, it may useful to have the Exchange resources provide verbose logging in the Cluster log.
On a server cluster, all Exchange resources are controlled by a custom resource DLL file (Exres.dll). The Exres.dll files sends its status of IsAlive (and other status checks and failures) output to the %systemroot%\Cluster\Cluster.log file. You can increase the logging level for Exres.dll to help you to identify issues.
To turn on verbose logging for Exres.dll, create the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\Application\MSExchangeCluster\EventLogLevel
Value Type: REG_DWORD
1 = Turned on
0 = Turned off
The increased logging starts immediately, and you do not need to restart (or stop and then restart) the cluster or Exchange services.
WARNING: After you increase the output of the Exres.dll file, the Cluster log fills up very quickly. Because of this, Microsoft recommends that you only use this procedure when you are troubleshooting Exchange-specific issues. Because the Cluster log can fill up very quickly, you may want to increase the size of the Cluster log. To do so, increase the "CLUSTERLOGSIZE" variable. For additional information about how to increase the CLUSTERLOGSIZE variable, click the article number below to view the article in the Microsoft Knowledge Base:
168801 How to Enable Cluster Logging in Microsoft Cluster Server
Note that because Cluster logging is already turned on in Windows 2000, you only need to increase the maximum size of the Cluster log.
Additional query words: MSCS W2000MSCS
Keywords: kbenv kbhowto KB316780
