Sometimes we have to face problem in mounting database or we can’t access Exchange Server mailbox and database. This shows that there are heavily chances that the Exchange Server is corrupt and thereby leading to such an inconsistent state.
Behind this behavior of Exchange, there may be several reasons such as virus infections, database header corruption, hardware issues, etc. In fact in such cases, you should use certain in-built methods to resolve the issue like ESEUTIL and ISINTEG. But if you are not able to understand the reason behind this or you are not able to solve this problem then you must search available option in market for Exchange Server Recovery.
Sometimes when you try to fix this problem you found following errors:-
“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:- Most probably in such cases the mailbox store database has corrupted and, thus, is in an inconsistent state and creates this issue.
Resolution:- This issue can be resolve in two ways. The first one is by the checking the state of the uncountable database and the second one is about repairing the database appropriately after confirming the database problem. To do this, you should perform the following steps:-
Confirm the state of database by entering the following command in Command Prompt: “eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
If the database is consistent, then the following text will be displayed: “State: Clean Shutdown”
Else if the database is inconsistent, then the following text will be displayed: “State: Dirty Shutdown”
Rebuild the database using Eseutil command by entering the following command: “eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
Repair the logical corruption of the database by using the following command: “Isinteg –s exchange_server_name –fix –test alltests”
These steps must be helpful to solve this error but if not then you can install Stellar Phoenix Exchange Server Recovery software. This EDP tool is Microsoft Exchange recovery software that recovers the corrupted EDB files from all instances of corruption. It is supported by Microsoft Exchange Server 2010, 2007, 2003, 2000, and 5.5.
Behind this behavior of Exchange, there may be several reasons such as virus infections, database header corruption, hardware issues, etc. In fact in such cases, you should use certain in-built methods to resolve the issue like ESEUTIL and ISINTEG. But if you are not able to understand the reason behind this or you are not able to solve this problem then you must search available option in market for Exchange Server Recovery.
Sometimes when you try to fix this problem you found following errors:-
“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:- Most probably in such cases the mailbox store database has corrupted and, thus, is in an inconsistent state and creates this issue.
Resolution:- This issue can be resolve in two ways. The first one is by the checking the state of the uncountable database and the second one is about repairing the database appropriately after confirming the database problem. To do this, you should perform the following steps:-
Confirm the state of database by entering the following command in Command Prompt: “eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
If the database is consistent, then the following text will be displayed: “State: Clean Shutdown”
Else if the database is inconsistent, then the following text will be displayed: “State: Dirty Shutdown”
Rebuild the database using Eseutil command by entering the following command: “eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”
Repair the logical corruption of the database by using the following command: “Isinteg –s exchange_server_name –fix –test alltests”
These steps must be helpful to solve this error but if not then you can install Stellar Phoenix Exchange Server Recovery software. This EDP tool is Microsoft Exchange recovery software that recovers the corrupted EDB files from all instances of corruption. It is supported by Microsoft Exchange Server 2010, 2007, 2003, 2000, and 5.5.
0 comments:
Post a Comment