Microsoft KB Archive/279433

= XADM: You Receive Misleading Error Messages When You Run Eseutil =

Article ID: 279433

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q279433





SYMPTOMS
If you try to run a manual offline defragmentation against a streaming file, you may receive the following error message:

Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.891 seconds.

If you run an integrity check against an .stm file, you may receive the following potentially misleading error message:

Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.901 seconds.

IMPORTANT: Do not run Exchange 2000 database repair against the .stm file because database repair corrupts the internal structure of the .stm file, and you receive the following error message:

Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.354 seconds.



CAUSE
The Exchange 2000 database is made up of two databases, Priv*.edb and Priv*.stm. Exchange 2000 contains a utility named Eseutil.exe. You can use Eseutil.exe to perform many tasks on an Exchange 2000 database, such as repair, integrity checks, and defragmentation.

This problem occurs because the released version of Eseutil does not make sure that you are running Eseutil against the correct database file. The structure of the .stm file (streaming file) is different from the structure of the .edb file (Rich Text). Some of the functions of Eseutil actually damage the streaming file.



RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.



MORE INFORMATION
These commands must always point to the Messaging Application Programming Interface (MAPI) rich database file (.edb). The command is performed on both the .edb file and the corresponding the .stm file.

In Exchange 2000 Server Service Pack 1 (SP1), if you run database repair against an .stm file, you do not damage the .stm file. The Exchange 2000 SP1 version of Eseutil checks to make sure that the file is a MAPI rich .edb file before Eseutil starts a repair.

Keywords: kbbug kberrmsg kbfix KB279433

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.