The Exchange server priv.edb and priv.stm databases stores all important users data like contacts, emails, notes, tasks, folders, journals, media files, attachments and others in their individual mailboxes. When a user tries defragment the database file of Exchange Server manually, an error message may appear on the user's screen:
"Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.891 seconds."
Information Store of MS Exchange Server made of two common databases, known as priv.edb and Priv.stm files. These databases store all important user mailboxes data including text and media contents. If this exchage database comes across any inconsistency or integrity issue, the Eseutil.exe, an inbuilt utility can help the users to fix the problems. This built-in tool can also be run to repair, defrag, and restore the damaged databases. However, in some situations, this tool may not perform the planned tasks successfully and the information store database remains in inaccessible state. In such cases, you are required to perform Exchange recovery to solve the issues.
When you try to defragment the STM (streaming) database file of Exchange Server manually, you might encounter the following error message:
"Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.891 seconds."
After the occurrence of above mentioned error message, when user run eseutil tool to check the integrity of the .stm file, you may face fiurther another error:
"Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.901 seconds."
It is highly advised not to ESEUTIL repair utilities in Exchange Server against the issues in STM file as it may damage the internal structure of the .stm database. At the same time, you may encounter further error message indicating:
"Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.354 seconds."
Causes of Fragmentation Errors in Microsoft Exchange Server:
The above said issue can occur if any of the following conditions are match:
1. The Eseutil utility doesn't ensure that user is running the tool against correct version of database. STM file structure is not same as the structure of EDB file. Some features of Eseutil tool may damaged the structure of STM file.
2. The Exchange database is damaged or corrupt and can not be read.
Solution:
Follow the steps, mentioned below to resolve this issue:
1. Get the latest service pack of MS Exchange Server.
2. Use Exchange Recovery tool from third parties to repair, rebuild and restore the corrupted database of Exchange Server.
Such applications are capable to sort out all types of corruption scenarios in databases of Exchange Server. These programs use advanced scanning and repairing techniques to fix the corrupted items in databases. The tools preserve absolute integrity of the database as of their non-destructive and read only behavior. One such advance application can be downloaded from here that effectively work arounds all databases (.edb and .stm) corruption problems. This Exchange tool works well with all versions of MS Exchange Server and can be run on all plateforms of Windows Operating System.
No comments:
Post a Comment