Blogs >> Technology >>
Exchange Server Database Fragmentation Fails with Misleading Errors
Microsoft Exchange Server database consists of two common databases, known as Priv.edb and Priv.stm. These database contains all your significant emails, notes, contacts, tasks, journal, attachments and more. If the Exchange Server database come across any sort of database inconsistency and integrity problem, Eseutil.exe utility can help you to fix the problem. It can also be used to repair the damaged database and defragment it. However, in some cases, this utility can not perform the expected tasks successfully and database remains in inaccessible state. In such cases, you are required to carry out Exchange Recovery to work around the problem.
When you attempt to manually defragment the STM (streaming) file of Exchange Server database, you might encounter the below error message:
“Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.891 seconds.”
After the above error, when you check the integrity of STM file, you might encounter the below possibly misleading error:
“Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.901 seconds.”
You are highly recommended not to use Exchange Server database repair utility against problem STM file as it might damage the internal structure of STM database file. At the same time, you may receive further error message stating:
“Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.354 seconds.”
What Causes Fragmentation Errors in Exchange Server ?
The above problem may occur if any of the below conditions are true:
1. This behavior occurs because the version of Eseutil utility doesn't ensure that you're running the tool against correct Exchange Server database. Structure of STM file is different from structure of EDB file. Some Eseutil functions might damaged STM file.
2. The Exchange Server database is corrupt and Exchange Server can not read it.
Solution
Go through the below steps to fix this problem and perform Microsoft Exchange recovery:
1. Obtain latest service pack of Exchange Server.
2. Use third-party Exchange Recovery software to repair and restore the damaged Exchange Server database.
The Exchange Server Recovery applications are capable of handling all types of Exchange Server corruption scenarios, using advanced scanning techniques. The software preserve absolute integrity of your database as of their read-only and non-destructive conduct.
Stellar Phoenix Exchange Mailbox Recovery is a powerful, yet easy to use application that effectively handles all EDB corruption problems. This Exchange Recovery Tool works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all inaccessible objects of Exchange Server database, including emails, contacts, notes, tasks, journal, and more.
When you attempt to manually defragment the STM (streaming) file of Exchange Server database, you might encounter the below error message:
“Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.891 seconds.”
After the above error, when you check the integrity of STM file, you might encounter the below possibly misleading error:
“Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.901 seconds.”
You are highly recommended not to use Exchange Server database repair utility against problem STM file as it might damage the internal structure of STM database file. At the same time, you may receive further error message stating:
“Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.354 seconds.”
What Causes Fragmentation Errors in Exchange Server ?
The above problem may occur if any of the below conditions are true:
1. This behavior occurs because the version of Eseutil utility doesn't ensure that you're running the tool against correct Exchange Server database. Structure of STM file is different from structure of EDB file. Some Eseutil functions might damaged STM file.
2. The Exchange Server database is corrupt and Exchange Server can not read it.
Solution
Go through the below steps to fix this problem and perform Microsoft Exchange recovery:
1. Obtain latest service pack of Exchange Server.
2. Use third-party Exchange Recovery software to repair and restore the damaged Exchange Server database.
The Exchange Server Recovery applications are capable of handling all types of Exchange Server corruption scenarios, using advanced scanning techniques. The software preserve absolute integrity of your database as of their read-only and non-destructive conduct.
Stellar Phoenix Exchange Mailbox Recovery is a powerful, yet easy to use application that effectively handles all EDB corruption problems. This Exchange Recovery Tool works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all inaccessible objects of Exchange Server database, including emails, contacts, notes, tasks, journal, and more.
|
|
