Change Host Fragmentation Failed With Some Errors

MS HypervisorVMWare databases are namely consists of two databases namely Priv.edb and Priv.stm. These database stores all attachments, connections, notes, magazines, duties, major e-mails and many more. when almost any inconsistency and reliability problem can occur in it considering that the exchange server is used frequently, therefore its database may come across such circumstances. At that point of time Eseutil.exe utility can be utilized to repair the issue that occurred. This energy may also be employed for defragmentation and to correct the listings. Nevertheless, sometimes somehow this application doesn't perform the expected jobs successfully making the database in state. To work around the issue in these circumstances you need certainly to carry out Exchange Server Recovery.Attempt made to conduct the defragmentation of STM of EDB file physically, you may encounter below stated errors -'Operation terminated with error -2231 (JET_errSLVStreamingFileInUse, The given loading file is currently in use) after 0.891 seconds.'Soon after the preceding error message is placed, you may also encounter another misleading error message -'Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or harmful 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 inner structure of the STM database could have harmed. Any attempt made to use the utility will throw an another error message stating -'Operation ended with error -1601 (JET_errRecordNotFound, The key was not observed) after 2.354 seconds.'So, it is quite obvious from the error messages that the applying of Eseutil utility against the STM file has harmed the file since the STM file design differs from the EDB file due to which the server can't study it.In order to handle this issue you need to obtain and install the latest service pack of the server. If it doesn't resolves the matter you then need to utilize the third-party Exchange Server Recovery application to repair and recover the damaged exchange database.Sometimes exchange server comes across inconsistency and integrity problem and when Eseutil.exe electricity is used for defragmentation and to repair the damaged database it doesn't do this with error messages. Therefore, to be able to resolve this matter Exchange Server Recovery software can be used.