MS Exchange Server databases are namely consists of two databases namely Priv.
stm and Priv.
edb.
These database stores all significant emails, contacts, notes, journals, tasks, attachments and many more.
Since the exchange server is used very often, so its database may come across such situations when any kind of inconsistency and integrity problem can occur in it.
At that point of time Eseutil.
exe utility can be used to fix the problem that occurred.
This utility can also be used for defragmentation and to repair the damaged databases.
However, in some cases somehow this utility does not perform the expected tasks successfully which makes the database in inaccessible state.
To work around the problem in these circumstances you need to carry out Exchange Server Recovery.
Attempt made to perform the defragmentation of STM of EDB file manually, you may encounter below mentioned errors - "Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.
891 seconds.
" Soon after the previous error message is thrown, you may also encounter another misleading error message - "Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.
901 seconds.
" In these circumstances it is highly recommended not to use the Exchange Server database repair utility against the STM file as the internal structure of the STM database might have damaged.
Any attempt made to use the utility will throw an another error message stating - "Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.
354 seconds.
" So, it is quite clear from the error messages that the using of Eseutil utility against the STM file has damaged the file because the STM file structure is different from the EDB file due to which the server can not read it.
In order to resolve this issue you need to obtain and install the latest service pack of the server.
If it does not resolves the issue then you need to use the third-party Exchange Server Recovery software to repair and restore the damaged exchange database.
Sometimes exchange server comes across inconsistency and integrity problem and when Eseutil.
exe utility is used for defragmentation and to repair the damaged database it fails to do so with error messages.
So, in order to resolve this issue Exchange Server Recovery software is used.
stm and Priv.
edb.
These database stores all significant emails, contacts, notes, journals, tasks, attachments and many more.
Since the exchange server is used very often, so its database may come across such situations when any kind of inconsistency and integrity problem can occur in it.
At that point of time Eseutil.
exe utility can be used to fix the problem that occurred.
This utility can also be used for defragmentation and to repair the damaged databases.
However, in some cases somehow this utility does not perform the expected tasks successfully which makes the database in inaccessible state.
To work around the problem in these circumstances you need to carry out Exchange Server Recovery.
Attempt made to perform the defragmentation of STM of EDB file manually, you may encounter below mentioned errors - "Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The specified streaming file is currently in use) after 0.
891 seconds.
" Soon after the previous error message is thrown, you may also encounter another misleading error message - "Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 0.
901 seconds.
" In these circumstances it is highly recommended not to use the Exchange Server database repair utility against the STM file as the internal structure of the STM database might have damaged.
Any attempt made to use the utility will throw an another error message stating - "Operation terminated with error -1601 (JET_errRecordNotFound, The key was not found) after 2.
354 seconds.
" So, it is quite clear from the error messages that the using of Eseutil utility against the STM file has damaged the file because the STM file structure is different from the EDB file due to which the server can not read it.
In order to resolve this issue you need to obtain and install the latest service pack of the server.
If it does not resolves the issue then you need to use the third-party Exchange Server Recovery software to repair and restore the damaged exchange database.
Sometimes exchange server comes across inconsistency and integrity problem and when Eseutil.
exe utility is used for defragmentation and to repair the damaged database it fails to do so with error messages.
So, in order to resolve this issue Exchange Server Recovery software is used.
SHARE
