The "eseutil /cc" command does not work on cluster server

Article translations Article translations
Article ID: 266689 - View products that this article applies to.
This article was previously published under Q266689
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

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:
Error returned from a callback function call (0x8004010F). Operation terminated with error -107 (JET_errInternalError, Fatal internal error)
The following event error message may also be logged in the application event log:
Event Type: Error
Event Source: ESE BACKUP
Event Category: Callback
Event ID: 904
Description:

Information Store (1728) Callback function call ErrESECBRestoreOpen ended with error 0x8004010F

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.

Properties

Article ID: 266689 - Last Review: October 26, 2013 - Revision: 4.0
Applies to
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kberrmsg kbpending KB266689

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com