Overcome Exchange Server Fragmentation Fails With Errors Issues

Exchange server database includes two database namely Priv.edb and Priv.stm. EDB files contains huge amount of data such as notes, attachments, emails, journals etc. If you are facing any type of integrity issue or inconsistency problems, you can take the help of eseutil.exe utility, which comes inbuilt with exchange server. This tool can be also used for repairing the corrupted database and defragment it. However, in some cases this tool fails to do the expected tasks and you may see that Exchange server fragmentation fails with errors thereby making your edb database inaccessible.


In some cases, if you manually try to defragment Exchange server STM file, you will come across 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 this error message, when try to check the integrity of STM file, you may encounter the below given misleading error:

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

If you are facing these errors with your edb files, it has been strictly recommended to not to take the help of Exchange Server database repair utility for resolving STM file problems as it can cause considerable damage to STM database file internal structure. The very same time, you will get other error messages too.

Why Exchange Server fragmentation fails with errors?


Exchange server fragmentation fails when the eseutil utility version is not being used for appropriate Exchange server database. STM file structure is quite different from EDB file structure and as such some of the eseutil functions can damage the STM file. Exchange server fragmentation failure also occurs if edb database is corrupted and Exchange server is unable to read it.


How to overcome Exchange server fragmentation fails with errors issues:


In order to overcome the Exchange server fragmentation failure issues, you will have to go for the latest Exchange server service pack and try to resolve the edb issues. If this does not resolves the problem and you are still facing the same situation, you can go for third-party Edb Recovery Software for repairing and restoring the corrupted Exchange server database files.