How to Solve Page Checksum Mismatch Error in MS Exchange Server ?

MS Exchange Database files get corrupted or damaged due to many reasons such as abnormal shutdown of Exchange Server, Virus attack, hardware failure and more. When this type of situation occur , the database becomes totally inaccessible and unusable. In case of edb file corruption , you may encounter critical user's data loss situations and at this point, EDB Recovery is the best way to get your data back.

When EDB file gets damaged or corrupted, you would not be able to access your data such as email messages, contacts, notes, tasks, calender entries etc with MS Outlook. This behaviour occurs because MS Outlook will not be able to access your data from the corrupted mailboxes.

Consider a practicle example, when you try to run an online backup of database after corruption, the operation can not be completed and you come across the following error message:

"Database page read failed verification because of a -1018 error" (page checksum mismatch)

You can not access your valuable data from the database after above error and users might face the following problems:

• Cannot send or receive e-mail messages and other items.

• Unable to start MS Outlook.

• Online backups fail to complete with a -1018 checksum error.

• Online defragmentation surfaces a -1018 checksum mismatch error.
  

To gain access of your data in MS Outlook, you need to identify the root of this issue and perform EDB to PST conversion.

Cause:

The root cause of this error is that faulty hardware parts, firmware and device drivers of hard disk subsystem. The error -1018 indicates checksum mismatch and the specific referenced database page within the Exchange store is corrupt.

Solution:

Try the following steps to resolve the issue:

• Test the system for related hardware issues and replace it
• Upgrade the firmware drivers if needed
• Use the last available online backup to restore the exchange database.
• Perform hard recovery using inbuilt eseutil /p utility or use a third-party EDB PST Converter such as Stellar Phoenix Mailbox Exchange Recovery.

The EDB to PST Converter will help you to get your precious data back by performing in depth scanning and repairing of entire EDB (Exchange database file). To Convert EDB to PST, the tool has interactive graphical user interface and there is no need to be technically sound to use it.

Stellar Phoenix Exchange Server Recovery is the most powerful and multi-featured edb to pst conversion tool that ensure complete EDB Recovery in all instances of .edb file corruption. The EDB to PST Converter works well with MS Exchange Server 5.5, 2000, 2003, 2007 and 2010. The tool is compatible with Windows 2000, Windows XP, Windows 2003, Vista and Windows 7.

The free demo version is also available to evaluate the Convert EDB to PST Software that allows users to repair corrupt edb file and extract the user mailboxes. However, it restricts the user from saving the extracted data and required full version to save the same.

Solving Exchange Server Error – 1019 during Hard Recovery

MS Exchange Server is designed to store and serve the data to millians of users. It is quite well known that Exchange database (EDB) files often get damage and corrupted due to various reasons such as Virus attack, Dirty Shutdown, Hardware failure, abrupt application and physical damage to storage media etc. In this situations, when EDB file gets corrupt or damaged, MS Outlook restricts accessing user's emails and other items from it. To solve this issue you need Exchange Repair solution.

Microsoft has availed the users with an inbuilt utility -eseutil/p . This utility provides two modes of recovery : hard recovery and soft recovery. Soft recovery is the process in which transaction logs are replayed and database exist as offline backup. In hard recovery transaction log is replayed and the online backup of database is used.

How to Solve 'Unable to write a shadowed header for the file' Exchange Server Error?

Consider a practical working situation, when you try to carry out the hard recovery of MS Exchange Server, you might come across error -1019 on the screen. After this error message, you may find the following even ids:

Event ID: 0
Source: ESE97
Type: Error
Category: Performance
Description: (252) Unexpected Win32 error: 0x3E6
Event ID: 122
Source: ESE97 How to Solve 'Unable to write a shadowed header for the file' Exchange Server Error?

Type: Error
Category: Logging/Recovery
Description: (252) Unable to read the log. Error -1022.
Event Id: 0
Source: ESE97
Type: Error
Category: Logging/Recovery
Description: (252) error -1019

Above error message and Event IDs and indicate that the database is severely corrupted and it can not be repaired using hard recovery process. After this situation of Server, the Exchange Repair job gets terminated and the last transaction log file, which is replayed, is altered and damaged.

In order to solve this issue you need to repair corrupt exchange database file with the help of third party EDB Repair tools. These Exchange Server repair software are particulary developed with the high end scanning algorithm to retrieve all items of the exchange database file. With interactive graphical user interface and non destructive design, theses tools are completely safe to use and perform fast EDB Recovery.

Stellar Phoenix Mailbox Exchange Recovery is the best and most excellant option to sort out most of the EDB corruption, damage problems. The edb repair software is compatible with Windows 7, Vista, Server 2003, XP, and 2000. This easy to use Exchane server recovery utility supports MS Exchange Server 5.5, 2000, 2003, 2007 and 2010.

Other Related Post:

• How to Solve 'Unable to write a shadowed header for the file' Exchange Server Error? 

• How to prevent physical corruption

Solving “ESE 447 Database corruption” Error in MS Exchange Server

A storage group in MS Exchange Server works as a logical container for databases and transaction log files. Sometimes when you wish to start any of Storage Group,  the error message:  “ESE 447 Database corruption”  appears on the screen. In this situation, when  you try to create a new storage group and move your mailboxes on this, the user mailboxes become inaccessible and you get the same error again.  To resolve the issue it is necessary to look for a Exchange Recovery utility.

Cause:

The reason of this issue may be one of the following:

    * Scanning of Exchange database directory using some antivirus software
    * Some hardware failure problem.

In both of  above causes, You may encounter logical corruption in the exchange database. Due to this corruption the database becomes completely unusable and may shows the below mentioned error message:

“ESE 447 Database corruption”

Resolution:

To fix this issue, you will have to restore your database from the current backup. But if you do not have proper backup, it is recommended to perform Exchange Server recovery with the help of third party tool like Stellar Exchange Recovery, known as EDB recovery software. This exchange database recovery tool perform quick & complete database scanning to repair the .edb file in most corruption cases.

Stellar Phoenix Exchange Mailbox Recovery software is the prominent and comprehensive tool to recuperate the exchange edb file. This powerful  exchange server recovery tool uses advanced technology to scan the corrupt, damaged .EDB file and extract all items from it. 

How to recover EDB database in MS Exchange Server 2010 when you are unable to mount database

Are you facing some sort of problem while trying to access MS Exchange database folder? Such problem can occur if there are some problems with the configuration in Exchange Server settings. You should try to address the settings. If the problem is not resolved, then there is a quite prominent possibility that the EDB (Exchange Database) database file is damaged, which can happen due to various reasons including virus infections, database header corruption, transaction log file corruption, etc. In such cases, appropriate methods should be used to recover corrupt EDB file. If these methods are insufficient, then the use of a third-party EDB recovery software to perform EDB recovery is a must.

Let us discuss a scenario in which you are unable to mount the mailbox database in MS Exchange Server 2010. In such case, the following error message is displayed:

“Failed to mount database 'Mailbox Database'

Mailbox Database
Error:
Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2-ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005,ec=-2147467259).”

In addition, the following report is logged in the Application event log:

“Event ID 9518
Event Type:    Error
Event Source:    MSExchangeIS
Event Category:    General
Event ID:    9518
Date:     date
Time:     time
User:     N/A
Computer:    ServerName
Description: Error 0x80004005 starting Storage Group /DC=com/DC=example/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=335A1087-5131-4D45-BE3E-3C6C7F76F5EC/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=ServerName/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
MDB failed to start.”

Cause:
There could be the following reasons for such erroneous situation:
A) The 'DomainName\Exchange Servers' group is not assigned the 'Manage auditing and security log' user right.
B) The EDB database file is damaged.

Resolution:
To overcome the problem, you can perform either of the following methods:
A) Run Setup /PrepareAD: You should run the 'Setup /PrepareAD' command using the Exchange Server CD. This command restores the original configuration settings of Exchange Server.
B) Add the Exchange Servers group to the "Manage auditing and security log" policy: To do this, you should perform the following steps:
   i)    Click Start | Administrative Tools | Domain Controller Security Policy.
  ii)    Click 'User Rights Assignment' in the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in.
 iii)    Double-click 'Manage auditing and security log'.
  iv)   Click 'Add User or Group' in the 'Manage auditing and security log Properties' dialog box.
   v)   Enter 'DomainName\Exchange Servers' in the 'User and groups names' box.
  vi)   Click OK two times.
 vii)   Quit Default Domain Controller Security Settings MMC snap-in.
viii)    Restart the Microsoft Exchange Information Store service.

If the problem is persisting, then a third-party EDB recovery software is to be used to recover corrupt EDB file. Such EDB recovery tools use fast and sophisticated scanning algorithms to recover EDB file without causing any damage to the original EDB file.

The EDB recovery tool that most of the recovery experts recommend is Stellar Phoenix Exchange Server recovery, which recovers corrupt EDB file created for MS Exchange Server.

Troubleshooting Error 'JET_errKeyDuplicate Illegal duplicate key' in Exchange Server

The Exchange database contains all the contacts, emails, file folders and a lot of other user information. There are some corruption problems can occur in Exchange Database file due to antivirus scanning, hardware failure, log file issues, database shutdown, system dirty shutdown etc. To ensure a speedy EDB recovery and smooth functioning of the the server, You need to use Third party Exchange EDB Recovery tool.