Blogs >> Technology >>
How to Repair inconsistent EDB database in MS Exchange Server 2000
Are you facing problems in mounting the Exchange Server? Or are you unable to access the Exchange Server? If yes, then there are chances that the Exchange Server database has gone corrupt thereby leading to such an inconsistent state. Such abnormal behavior can occur due to various reasons such as virus infections, database header corruption, hardware issues, etc. In such cases, you should use certain in-built methods to resolve the issue. However, if you are unable to address the problem then you should use a third-party Microsoft Exchange recovery software to perform Exchange Recovery.
Consider a scenario wherein you are not able to mount the Microsoft Exchange Server 2000. An error message is displayed, that is:
“The database files in this storage are inconsistent
Id no: c1041739”
You can also check the Application log to view the following 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.”
Cause:
The root cause of this error message is that the mailbox store database has corrupted and, thus, is in an inconsistent state.
Resolution:
In this case, the repair process involves two stages. The first one involves checking the state of the unmountable database whereas the second one is about repairing the database appropriately after confirming the database problem. To do this, you should perform the following steps:
1) Confirm the state of database by entering the following command in Command Prompt:
“eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"
2) If the database is consistent, then the following text will be displayed:
“State: Clean Shutdown”
3) Else if the database is inconsistent, then the following text will be displayed:
“State: Dirty Shutdown”
4) Rebuild the database using Eseutil command by entering the following command.
“eseutil /d /t:x "drive:\program files\exchsrvr\mdbdata\database_file_name.edb””
5) Repair the logical corruption of the database by using the following command:
“Isinteg –s exchange_server_name –fix –test alltests”
The aforementioned methods should be able to resolve the issue. However, if you are not able to address the issue then you should use a third-party Exchange Server recovery software to do so. Such read-only tools are able to perform Exchange recovery without overwriting the original data.
Stellar Phoenix Mailbox Exchange Recovery is a Microsoft Exchange Recovery software that recovers the corrupted EDB files from all instances of corruption. It is supported by Microsoft Exchange Server 2007, 2003, 2000, and 5.5. This Exchange recovery software is able to extract the mailboxes into separate PST files according to the specific user. In addition, this Exchange recovery tool is able to preserve the formatting of the RTF and html messages. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.
Consider a scenario wherein you are not able to mount the Microsoft Exchange Server 2000. An error message is displayed, that is:
“The database files in this storage are inconsistent
Id no: c1041739”
You can also check the Application log to view the following 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.”
Cause:
The root cause of this error message is that the mailbox store database has corrupted and, thus, is in an inconsistent state.
Resolution:
In this case, the repair process involves two stages. The first one involves checking the state of the unmountable database whereas the second one is about repairing the database appropriately after confirming the database problem. To do this, you should perform the following steps:
1) Confirm the state of database by entering the following command in Command Prompt:
“eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"
2) If the database is consistent, then the following text will be displayed:
“State: Clean Shutdown”
3) Else if the database is inconsistent, then the following text will be displayed:
“State: Dirty Shutdown”
4) Rebuild the database using Eseutil command by entering the following command.
“eseutil /d /t:x "drive:\program files\exchsrvr\mdbdata\database_file_name.edb””
5) Repair the logical corruption of the database by using the following command:
“Isinteg –s exchange_server_name –fix –test alltests”
The aforementioned methods should be able to resolve the issue. However, if you are not able to address the issue then you should use a third-party Exchange Server recovery software to do so. Such read-only tools are able to perform Exchange recovery without overwriting the original data.
Stellar Phoenix Mailbox Exchange Recovery is a Microsoft Exchange Recovery software that recovers the corrupted EDB files from all instances of corruption. It is supported by Microsoft Exchange Server 2007, 2003, 2000, and 5.5. This Exchange recovery software is able to extract the mailboxes into separate PST files according to the specific user. In addition, this Exchange recovery tool is able to preserve the formatting of the RTF and html messages. It is compatible with Windows 7, Vista, Server 2003, XP, and Server 2000.
|
|
