{"id":678,"date":"2019-02-12T11:12:55","date_gmt":"2019-02-12T11:12:55","guid":{"rendered":"https:\/\/www.mozesoft.com\/blog\/?p=678"},"modified":"2021-06-17T09:28:39","modified_gmt":"2021-06-17T09:28:39","slug":"how-to-fix-the-database-files-in-this-storage-are-inconsistent-error-in-ms-exchange-server","status":"publish","type":"post","link":"https:\/\/www.mozesoft.com\/blog\/how-to-fix-the-database-files-in-this-storage-are-inconsistent-error-in-ms-exchange-server\/","title":{"rendered":"How to Fix \u201cThe database files in this storage are inconsistent\u201d Error in MS Exchange Server"},"content":{"rendered":"\n

Microsoft Exchange Server is the most reliable Email \nServer for storing user mailbox data. Exchange Server stores user data \nin private as well as public information databases. However, due to some\n reasons, the user is unable to mount this database store information \nand reason would be the corruption in the database. While you are unable\n to mount the database you will encounter an error code<\/p>\n\n\n\n

\u201cThe database files in this storage are inconsistent Id no: c1041739\u201d<\/strong><\/p>\n\n\n\n

To encode this error code you need to run Eseutil command which is as follows:<\/p>\n\n\n\n

eseutil \/mh \u201cc:\\\\Mailbox_Storefilename.edb\u201d<\/strong><\/p>\n\n\n\n

After running above command you will find that the status of the \ndatabase in the log is Dirty Shutdown. Now you have to fix this dirty \nshutdown so that you can continue the database mounting. Now let\u2019s know \nwhat is consistency and inconsistency in Exchange database.<\/p>\n\n\n\n

Consistency in Exchange Database<\/strong><\/p>\n\n\n\n

The Consistency in Exchange Database can be defined as the changes \nwhich are done in log files are immediately reflected in Exchange \nDatabase. Like if Exchange Administrators wants to do some changes in \nExchange database or wants to modify the database. So, Administrator has\n to write all the changes in Log files and after that those changes are \nreflected in Exchange database then you can remove or deleted log files \nthen it is called consistency in Exchange database.<\/p>\n\n\n\n

Inconsistency in Exchange Database<\/strong><\/p>\n\n\n\n

The inconsistency in Exchange Database is the process as \nadministrator is doing some changes in the database then first of all he\n has to write the changes in log files and then those changes will be \nreflected in Exchange database. Once the reflection is obtained then you\n can remove log files but if you removed the logs before its changes are\n being reflected in the database then it is called inconsistency in \nExchange database and due to this inconsistency you have to encounter \nmany errors.<\/p>\n\n\n\n

The reason behind the error<\/strong><\/p>\n\n\n\n

There is the main reason behind this error is like there are \ninconsistencies in Exchange database and when you are trying to mount \nthe database it will get fails due to these inconsistencies.<\/p>\n\n\n\n

Workaround to error<\/strong><\/p>\n\n\n\n

You can fix Database inconsistency error manually in two fundamental ways.<\/p>\n\n\n\n

  1. Restores back your database if you have updated your database backup\n store regularly. If you will have any inconsistency issue with the \nExchange database then restoration is the best option to get back all \nyour data.<\/li>
  2. If you don\u2019t have updated database backup then you cannot restore \nit. The last option remains for you is to repair your Exchange database.\n You can repair your database manually so; let\u2019s know what the manual \nprocedure to repair it is.\n
    1. Initially you need to check the status of the database by running \u201ceseutil\/mh\u201d so check whether it is in dirty shutdown or not.<\/li>
    2. If database is in dirty shutdown then perform soft recovery with \n\u201cESEUTIL \/r enn \/L[path to log files] \/s[path to checkpoint file] \n\/d[path to database file] \/I\u201d command.<\/li>
    3. Then perform hard recovery with \u201ceseutil\/p\u201d command to make your database clean.<\/li>
    4. After this repair your Exchange mailbox \u201cNew-MailboxRepairRequest\u201d.
      \nAfter all these commands all your database is successfully repaired.<\/li><\/ol>\n<\/li><\/ol>\n\n\n\n

      Professional solution \u2013 Exchange Server Recovery Tool
      \n<\/strong><\/p>\n\n\n\n

      The EDB to PST Converter<\/a> is specially designed software to resolve all Exchange related issues. It offers a hassle-free solution to all Exchange problems. If you have a damaged Exchange database, then you can quickly repair it with the Exchange Server recovery tool. With this software you can also migrate your EDB files, Live Exchange and Office 365 mailboxes from source to the desired destination. It has more salient features like<\/p>\n\n\n\n