Logical corruption of Exchange Server database makes the saved data of Exchange Server totally inaccessible. Exchange Server objects contain data of contacts, e-mail messages, attachments, appointments, journal, tasks, events, and similar more. Exchange Server database gets corrupt or damaged because of faulty hardware, sudden system shutdown, and loss of power supply. In such data loss situation, backup helps you to restore data. If backup is unavailable or falls short to recover the database, then in such situations a third party Exchange Server Recovery tools can be used.
For further clarification of above issue. Let us consider a practical scenario. Suppose, you make a try to mount a mailbox store in a MS-Exchange 2000 server, but fails to mount it. In addition to this, you receive an error message that is:
''The database files in this storage are inconsistent
Id no: c1041739''
In addition to this, whenever you try to mount the database the following events are viewed in the application event log:
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 465
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. Corruption was detected during soft recovery in logfile 4092:203. The failing checksum record is located at position 4117. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable”
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 477
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. The log range read from the file "2095104 (0x00000000001ff800)" at offset 12800 (0x00003200) for -501 (0xfffffe0b) bytes failed verification due to a range checksum mismatch. The read operation will fail with error %7. If this condition persists then please restore the logfile from a previous backup.”
Cause:
Above error message is caused because of inconsistent state of the mailbox store database and public store database.
Solution:
For solving above error message, and to access data of the mailbox store database. You have to follow the below steps:
Confirm the database state by below steps:
1.Open command prompt.
2.Transfer to the Drive:\Program Files\Exchsrvr\Bin folder. This location is the default location for installation of Exchange 2000 server program files.
3.Enter the following command:
“eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_name.edb"
4. Check the output to verify the database state. If the database is not in a consistent state, then you
will receive the below text in the Output:
State: Dirty Shutdown
If the database is in inconsistent state, then you can repair the database by following steps:
If still the backup remains in an inconsistent state, then it is better to go for a third party Exchange Recovery tools. Several third party tools are available in the market that performs Microsoft Exchange recovery instantly. These tools have read-only and are non-destructive conduct.
Stellar Phoenix Exchange Server Recovery is an authentic edb repair tool that performs the Microsoft Exchange recovery and makes the Exchange Server database corruption free, even if it is logically corrupt. It shows compatibility with Windows 7, Vista, Server 2003, XP, and 2000. The interface of the tool is available in English language.
For further clarification of above issue. Let us consider a practical scenario. Suppose, you make a try to mount a mailbox store in a MS-Exchange 2000 server, but fails to mount it. In addition to this, you receive an error message that is:
''The database files in this storage are inconsistent
Id no: c1041739''
In addition to this, whenever you try to mount the database the following events are viewed in the application event log:
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 465
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. Corruption was detected during soft recovery in logfile 4092:203. The failing checksum record is located at position 4117. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable”
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 477
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. The log range read from the file "2095104 (0x00000000001ff800)" at offset 12800 (0x00003200) for -501 (0xfffffe0b) bytes failed verification due to a range checksum mismatch. The read operation will fail with error %7. If this condition persists then please restore the logfile from a previous backup.”
Cause:
Above error message is caused because of inconsistent state of the mailbox store database and public store database.
Solution:
For solving above error message, and to access data of the mailbox store database. You have to follow the below steps:
Confirm the database state by below steps:
1.Open command prompt.
2.Transfer to the Drive:\Program Files\Exchsrvr\Bin folder. This location is the default location for installation of Exchange 2000 server program files.
3.Enter the following command:
“eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_name.edb"
4. Check the output to verify the database state. If the database is not in a consistent state, then you
will receive the below text in the Output:
State: Dirty Shutdown
If the database is in inconsistent state, then you can repair the database by following steps:
- Use a command prompt.
- Transfer the Drive:\Program Files\Exchsrvr\Bin folder.
- Enter the following command:
- eseutil /p "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"
- Defragment and rebuild the database so that the database can be used in a production environment. To do the same, you have to enter the below command:
- eseutil /d /t:x "drive:\program files\exchsrvr\mdbdata\database_file_name.edb
- Check the database status is consistent or not by typing the following command, and can check the output:
- eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"
- State: Clean Shutdown
- To repair the Exchange Server database, you have to execute Isinteg.exe utility. For doing the same, you have to enter the following command:
- Isinteg –s exchange_server_name –fix –test alltests
- Perform the steps 3 to 6 again for each database.
- Mount the databases.
- After the databases are mounted, perform storage group online backup.
If still the backup remains in an inconsistent state, then it is better to go for a third party Exchange Recovery tools. Several third party tools are available in the market that performs Microsoft Exchange recovery instantly. These tools have read-only and are non-destructive conduct.
Stellar Phoenix Exchange Server Recovery is an authentic edb repair tool that performs the Microsoft Exchange recovery and makes the Exchange Server database corruption free, even if it is logically corrupt. It shows compatibility with Windows 7, Vista, Server 2003, XP, and 2000. The interface of the tool is available in English language.
