Article ID: 246178
Article Last Modified on 3/2/2007
APPLIES TO
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q246178
SYMPTOMS
When you try to view cluster log data after upgrading to Windows 2000, no additional entries have been added to the cluster log that was used before the upgrade.
CAUSE
This issue can occur because the cluster log environment variable is enabled by default when Windows 2000 Cluster service is installed on a computer. The environment variable is set as if the set clusterlog=%windir%\cluster\cluster.log command was executed from a command prompt. If an upgrade installation is executed with Windows 2000 Advanced Server, any existing cluster log environment variable will be overwritten with this default setting. Because of this, any new cluster data logged from the first time that cluster service is started after the upgrade will be written to this new default location instead of being added to the existing cluster log located at the location specified manually in a previous version of the operating system.
RESOLUTION
To work around this issue, reset the cluster log system environment variable to the appropriate path by running the following commands from a command prompt:
set clusterlog=<path including file name>
net stop clussvc
net start clussvc
Additional query words: mscs clusterlog
Keywords: kbprb KB246178