| Microsoft Exchange Server database consists of | | | | You are highly recommended not to use |
| two common databases, known as Priv.edb and | | | | Exchange Server database repair utility against |
| Priv.stm. These database contains all your | | | | problem STM file as it might damage the internal |
| significant emails, notes, contacts, tasks, journal, | | | | structure of STM database file. At the same time, |
| attachments and more. If the Exchange Server | | | | you may receive further error message stating: |
| database come across any sort of database | | | | "Operation terminated with error -1601 |
| inconsistency and integrity problem, Eseutil.exe | | | | (JET_errRecordNotFound, The key was not |
| utility can help you to fix the problem. It can also | | | | found) after 2.354 seconds." |
| be used to repair the damaged database and | | | | What Causes Fragmentation Errors in Exchange |
| defragment it. However, in some cases, this utility | | | | Server ? |
| can not perform the expected tasks successfully | | | | The above problem may occur if any of the |
| and database remains in inaccessible state. In such | | | | below conditions are true: |
| cases, you are required to carry out Exchange | | | | 1. This behavior occurs because the version of |
| Recovery to work around the problem. | | | | Eseutil utility doesn't ensure that you're running the |
| When you attempt to manually defragment the | | | | tool against correct Exchange Server database. |
| STM (streaming) file of Exchange Server | | | | Structure of STM file is different from structure |
| database, you might encounter the below error | | | | of EDB file. Some Eseutil functions might damaged |
| message: | | | | STM file. |
| "Operation terminated with error -2231 | | | | 2. The Exchange Server database is corrupt and |
| (JET_errSLVStreamingFileInUse, The specified | | | | Exchange Server can not read it. |
| streaming file is currently in use) after 0.891 | | | | Solution |
| seconds." | | | | Go through the below steps to fix this problem |
| After the above error, when you check the | | | | and perform Microsoft Exchange recovery: |
| integrity of STM file, you might encounter the | | | | 1. Obtain latest service pack of Exchange Server. |
| below possibly misleading error: | | | | 2. Use third-party Exchange Recovery software |
| "Operation terminated with error -1206 | | | | to repair and restore the damaged Exchange |
| (JET_errDatabaseCorrupted, Non database file or | | | | Server database. |
| corrupted db) after 0.901 seconds." | | | | |