Article ID: 266689
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q266689
SYMPTOMS
If you run the eseutil /cc command, the command may not work with Exchange 2000 Server running on a cluster server, and you may receive the following error message:
The following event error message may also be logged in the application event log:
CAUSE
This problem can occur if the Eseutil utility is using the local computer name instead of the cluster name.
WORKAROUND
To work around this problem, set the following environment variable:
SET _CLUSTER_NETWORK_NAME_=cluster_name
For example, in a two-node cluster that is composed of SERVER1 and SERVER2, with the cluster visible to network clients as CLUSTER1, type the following command:
SET _CLUSTER_NETWORK_NAME_=CLUSTER1
Note The SET _CLUSTER_NETWORK_NAME_=cluster_name variable is always a user variable. Do not attempt to set it manually to be a system variable. If you set it to be a system variable, it can cause failures and, in extreme cases, the inability to log on.
RESOLUTION
To resolve this problem, obtain the latest service pack for MIcrosoft Exchange 2000 Server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
STATUS
Microsoft has confirmed that this is a problem in Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.
MORE INFORMATION
Hard recovery is the process through which you apply transaction logs and database patch files to a database that has been restored from online backup.
Usually, you click to select the Last Backup Set check box in Microsoft Windows NT Backup to start hard recovery. If you forget to select this check box, you must either restore the backup again and this time click to select the Last Backup Set check box, or run the eseutil /cc command.
Run the eseutil /cc command from a command prompt in the temporary folder where the Restore.env file exists.
Additional query words: exch2kp2w XADM
Keywords: kbbug kberrmsg kbpending KB266689
