Let us take an instance in which you are unable to mount on an MS Exchange Server 2000 database. The following error message is displayed:

“The database files in this storage are inconsistent

Id no: c1041739”

In addition, the following error is logged in the Application event log for MS Exchange Server 2000:

“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 problem is that either the public store database or the mailbox store database is in an inconsistent state.

Resolution:

To resolve the situations, you should either restore or repair the corrupt EDB file. This could be done using the following methods:

1. Restore the backup: Restoring the backup can be done by performing the following steps:
   1. Move or rename the E00.log file. By default, it is stored in the Drive:\Program Files\Exchsrvr\MDBDATA folder.
   2. Restore the storage group and the log files from the backup file.
   3. Mount the database when the storage group is restored.
2. Repair EDB database file: To repair the EDB database file, you need to perform the following steps:
   1. Click Start | Run, and enter ‘cmd’ in the ‘Open’ box.
   2. Press the ‘Enter’ key to open Command Prompt.
   3. Move to the Drive:\Program Files\Exchsrvr\Bin folder.
   4. Type the following command and press the ‘Enter’ key:

   eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

   5. Type the following command and press the ‘Enter’ key to defragment and rebuild the EDB database file:

   eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb

   6. Verify the state of the database by using the following command:

   eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

   7. If the database is consistent, then the following text is displayed:

   State: Clean Shutdown

   8. Use the ‘isinteg’ tool with the following switches to repair the logical corruption:

   Isinteg –s exchange_server_name –fix –test alltests

   9. Mount the database and check if the error is appearing again or not.

If the problem is still there, then you need to use a third-party EDB recovery software to recover EDB database file. The use of extremely safe scanning algorithms in a highly interactive user interface are some of the striking features of these EDB recovery tools.

Stellar Phoenix Exchange Server Recovery is one the best EDB recovery software that works well on Windows 7, Vista, Server 2003, XP, and 2000. With the ability to recover corrupt EDB files created for MS Exchange 5.5, 2000, 2003, and 2007, this EDB recovery utility extracts distinct PSTs from various user mailboxes.



Consider a scenario, wherein, you may come across the following error with your Microsoft Exchange 2000 or 2003 server computer:

The information store won’t start and you may receive the following error:

‘1067 The information store terminated abnormally’

When you go for online defragmentation, the following event is generated in the application log:

Date:      date        Source:   ESE
Time:      time        Category: Database Corruption
Type:      Error       Event ID: 447
User:      N/A
Computer:  Servername

Description:
Information Store (nnnn) A bad page link (error -338) has been detected in a
B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database e:\Program
Files\excshsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).

In case of Event ID: 447, you are not able to mount the information store and the crucial .edb files goes inaccessible. To troubleshoot the problem, you must have a thorough understanding of the exact causes. Then only, you can decide upon relevant Recover EDB steps.

Cause
The Even ID 447 clearly indicates that the logical structure of the database has become corrupt. The reasons behind corruption could be:

1. The server suffered a crash as disk caching has not committed transactions to the hard disk
2. During a database restoration, incorrect log files were replayed
3. Or if a server has a defective hard disk controller

Also, as seen in the application log, a bad page link error means logical corruption at the Jet level in the database.

Resolution
In order to troubleshoot the problem, you must consider the following steps:

1.If possible, restore the database using a backup which was created before this error
2.If no backup exists, perform hard repair by using eseutil.exe / p command.
3.After the hard repair, perform an offline defragmentation by running the eseutil.exe / d command
4.Finally run, the isinteg -s servername -fix -test alltests command on the database
5.If you are still not able to mount the database, then grab a third-party EDB recovery software

Such applications, being read-only are absolutely safe to use and perform EDB file recovery in a hassle-free manner.

Stellar Phoenix Mailbox Exchange Recovery is an advanced software which repairs corrupt edb files and recovers mailboxes as separate PSTs which can be directly imported in Outlook. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, the Exchange recovery software also performs recovery of deleted mailboxes.

Consider a scenario wherein you are unable to mount the Exchange Store in Exchange Server 2007. An error message is displayed, that is:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager”

In addition, if you check the Application log you may find the following error entry:

“Event Type: Error
Event Source: Antivirus_Program_Name
Event Category: None
Event ID: 5
Description: The description for Event ID ( 5 ) in Source ( Antivirus_Program_Name ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Virus Found! Virus name: W32.Netsky.P@mm!enc in File: E:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_216f566e01c43c76000002af.EML by: Realtime Protection scan. Action: Clean failed : Quarantine failed : Access denied.”

Cause:

One possible cause of this problematic situation is that an antivirus is deleting or quarantining the existing Exchange log file.

Resolution:

To resolve this error, you should perform the following steps:

1. Check the antivirus configurations: You should check whether the antivirus is configured to scan the Exchange Server directories.
2. Review the log files: You should check whether the log files were deleted or quarantined by the antivirus.
3. Recover the log file: You should attempt to recover the log file.

The problem will be resolved using aforementioned steps and you would be able to mount the database. However, if you are not able to address the situation then you should use a third-party EDB recovery software to do so. Such read-only tools recover EDB files using fast yet sophisticated scanning algorithms.

Stellar Phoenix Mailbox Exchange Recovery is an Exchange recovery software that repairs corrupt EDB file by converting it into different PST files. It is designed to support EDB file recovery for MS Exchange Server 2007, 2003, 2000, and 5.5. This EDB recovery tool is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

In a practical scenario of this problem, Microsoft Exchange Server database, which circular logging enabled, may not start after an improper shut down. Furthermore, you may run across a JET_errFileNotFound error in one of the below given forms:

• -1811
• 0xfffff8ed
• 4294965485

In the Exchange Server Application Event Log, events 5000 and 1120 are logged in hexadecimal version of this error. The events are generic Exchange Server database startup errors. You should interpret the error code in descriptions for understanding exact cause of the problem and then fix it through EDB recovery solutions.

Root of the problem

You may come across this behavior of Microsoft Exchange Server due to any of the below reasons:

• There is some problem in the checkpoint file of Microsoft Exchange Server database. The file may get damaged due to unexpected shut down of Exchange Server computer.
• Exchange Server removes transaction log files after the data is written to main database file, if the circular logging option is enabled.
• Another database process is having an open Edb.chk file. It prevents MS Exchange Server from modifying checkpoint file when checkpoint advances.
• The Exchange Server database is severely damaged.

Solution

Try out any of the Microsoft Exchange recovery methods to fix the problem:

• Locate and remove Edb.chk file from your Exchange Server database. However, you should play safely while doing this.
• If problem is caused due to critical Exchange Server database corruption, repair and restore the database using powerful third-party applications.

The EDB recovery tool are particularly designed to scan entire Exchange Server database, to recover edb and extract all inaccessible data from it. They are incorporated with rich and interactive graphical user interface to offer easy recovery.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced EDB recovery solution to effectively fix all your database corruption issues. The Corrupt EDB File recovery software is designed to repair corrupt databases of Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all inaccessible items from EDB file, such as emails, notes, tasks, contacts, journal, and attachments.

Here is an example illustrating how an upgrade process can fail in MS Exchange Server. Let’s say, you try to upgrade to Exchange Server and the process fails. On each attempt of doing so, you receive the below mentioned error message:

“An unexpected error has occurred.
ID No. c106fdda”

This error won’t allow you to upgrade Microsoft Exchange Server. However, if you apply a fault-tolerant setup, the given error pops up:

“Your upgrade did not complete successfully. Please restart your Microsoft Exchange services and your system will behave as it did before the upgrade was attempted.”

Such problems specifically occur when Exchange Server setup during upgrade finds a database that is not consistent. Since an inconsistent database cannot be upgraded, the setup exits with a failure error message, as above.

User Action

If you encounter the problem that has been discussed above, you need to perform the below sequence of steps:

• Quit the Exchange setup program

• If you didn’t choose the fault-tolerant upgrade at start, you need to check the consistency of all databases using commands as follows:

drive:\Winnt\System32\eseutil /mh file_path\priv.edb

drive:\Winnt\System32\eseutil /mh file_path\pub.edb

However, in case the fault-tolerant upgrade was chosen. The following commands will help:

drive:\exchsrvr\bin\edbeutil /mh file_path\priv.edb
drive:\exchsrvr\bin\edbeutil /mh file_path\pub.edb

• Execute the below mentioned command for the inconsistent database:

<drive>:\Winnt\System32\eseutil /r /ispriv

<drive>:\Winnt\System32\eseutil /r /ispub

If the database doesn’t become consistent again, you should restore it from the last available backup or run a third-party EDB Recovery Tool. An Corrupt EDB File recovery software can scan a corrupted Exchange database file and extract its data in readable form, accessible by normal means.

Stellar Phoenix Mailbox Exchange Recovery is a comprehensive recover edb solution designed for repairing a corrupted Exchange EDB file and restoring the mailboxes as *.pst files. This EDB Recovery Software supports MS Exchange Server 5.5, 2000, and 2003 and provides advanced options to aid recovery. In addition, it can also recover deleted mailboxes.

Suppose you are an Exchange Server administrator with a mailbox store that contains hundreds of user mailboxes. Since the store contains critical information required for uninterrupted working of the organization, its consistency cannot be compromised. But you observe that the below mentioned event ID is repeatedly observed in application event log:

Event Type: Error

Event Source: MSExchangeIS Mailbox Store

Event Category: Rules

Event ID: 1148

Date: date

Time: time

User: N/A

Computer: Computer_Name

Description:

A rule synchronization error (Read verification error) has occurred.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This error occurs irrespective of the fact that all Exchange Server services are working without any issue.

Cause

Exchange database is corrupt.

Note: The same error can also occur if required data is missing.

Solution

Following are the possible solutions that can help you recover from such database corruption issues:

1. Run ‘Eseutil’ with ‘/r’ switch for soft database recovery

2. Restore database from the last available backup

3. Execute ‘Eseutil’ with ‘/p’ switch to repair the database. But make sure to backup the database before running this command. This prevents data loss.

4. Use a third-party EDB Recovery Tool to repair and restore the corrupted Exchange database

EDB Recovery Software are exclusive tools built to scan and repair the damaged EDB database file safely and effectively. One of the best utilities is Stellar Phoenix Mailbox Exchange Recovery software with deleted mailbox recovery capability, this EDB Recovery Tool supports MS Exchange Server 2007, 2003, 2000, and 5.5 and can extract individual mailboxes as *.pst files.

]]> http://www.edb-recovery.com/blog/resolving-event-1148-with-rule-synchronization-error/feed/ 0 http://www.edb-recovery.com/blog/fixing-%e2%80%9c-1605-0xfffff9bb-jet_errkeyduplicate%e2%80%9d-exchange-server-error/ http://www.edb-recovery.com/blog/fixing-%e2%80%9c-1605-0xfffff9bb-jet_errkeyduplicate%e2%80%9d-exchange-server-error/#comments Fri, 09 Apr 2010 09:52:47 +0000 admin http://www.edb-recovery.com/blog/fixing-%e2%80%9c-1605-0xfffff9bb-jet_errkeyduplicate%e2%80%9d-exchange-server-error/ Microsoft Exchange Server is a popular application for creating collaborative messaging environment. It is a server-side application of client-server environment. It stores all your valuable data, such as emails, notes, contacts, tasks, appointments etc., in EDB (Exchange Database) file. In some situations, the database gets damaged and you encounter Jet errors while accessing the database. This behavior of Exchange Server database leads to significant data loss and requires EDB Recovery Software to be sorted out.

The Jet errors generally occur when Exchange Server database gets damaged beyond repair capabilities of the Eseutil.exe and other EDB Recovery Tool. A number of Jet errors are quite difficult to handle.

In a practical scenario, you may receive the below Jet error while working on Exchange Server or trying to repair the database using Eseutil utility:

“-1605 0xFFFFF9BB JET_errKeyDuplicate Illegal duplicate key 4294965691”

When the above error message is encountered, you can’t continue using the Exchange Server database. This error indicates that EDB file is severely damaged and thus immediate recovery of corrupted database is required.

Microsoft Exchange Server offers an inbuilt utility to handle database inconsistency and corruption. But, this error can not be fixed using Eseutil.exe tool. If you keep running the Eseutil.exe tool after receiving this error message, it may cause a bigger headache, lost data, and lost time,in other words, it would merely aggravate the problem.

When you run the Eseutil.exe, it seems that the changes are not committed to Exchange Server Information Store or database, but the program may modify the database without displaying any sort of verbose information. It can apply changes to database even if it shows that database is not repairable.

In such circumstances, an absolute backup of your Exchange Server database proves a great help. You can easily restore your database from the backup and save your time and data. However, if the backup is either not updated or is damaged, severe problems occur.

This implies, you face critical data loss and need advanced and powerful third-party Recover EDB file tools. The applications are powerful enough to systematically scan the damaged EDB file using advanced scanning techniques and extract damaged data from it.

Stellar Phoenix Mailbox Exchange Recovery software repairs and restores damaged Exchange Server database in all cases of corruption. This EDB Recovery application does not demand sound technical skills to repair and restore the damaged database as it has simple and interactive user interface. It preserves the integrity of data owing to its read-only and non-destructive conduct. The software is usable with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all EDB file objects, such as emails, notes, contacts, tasks, calendar entries, attachments, and more.

Microsoft Exchange Server indicates Information Store corruption with a number of symptoms, which include:

1. You can not start Microsoft Exchange Server Information Store Service.

2. The Information Store Service can not be stopped.

3. The CPU (Central Processing Unit) usage level reaches at 100% and Information Store stops responding.

4. Clients can not send or retrieve emails. The problem persists even if you stop and restart Information Store service.

5. If you attempt to restore Microsoft Exchange Server database from offline backup and run Isinteg (Information Store Integrity) utility, you come across the below error message:

“Error 4294966746: JET_errDatabaseInconsistent”

How to Fix Information Store Corruption?

To rectify the Information Store damage and recover the private and public information stores:

1. Start the Information Store service.

2. Check the consistency of Information Store using Eseutil.exe tool.

3. Remove all .chk and .log files in ExchSrvr\Mdbdata folder.

4. Verify that Exchange Server databases are working, by starting Information Store service. If it starts successfully, stop the service.

5. Defragment the Exchange Server database that you repaired. You can defragment the database using Eseutil utility.

6. Run Isinteg.exe utility to repair the databases.

7. Restart Microsoft Exchange Server Information Store Service.

8. Run the DS/IS (Directory Service/Information Store) Consistency Adjuster.

If the above method can not help you to Recover EDB file, you need to restore database from the most recent backup. However, if the backup is either damaged or not updated, you need to repair and restore the database using third-party applications.

The EDB Recovery Software work in all cases of database corruption and successfully restore database in original state, without modifying the original data.

EDB Recovery Tool is the most advanced recover edb utility for assured recovery of your damaged EDB file. The software effectively repairs Corrupt EDB File and restores all EDB file objects, such as emails, notes, contacts, tasks, notes, calendar items, and journals. It is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

You must complete the hard recovery after restoring the database from an online backup. It is primarily a log replay process. In hard recovery, the below operations are performed:

1. Patch information is applied to database during the log file replay.

2. Checkpoint is ignored. The Restore.env file is used in place of checkpoint to consider for which file the recovery needs to be started.

3. If EDB is restored to different file path than from which the file was backed up, the replay process of log file completes successfully, ignoring database paths that are listed in log files.

4. Replay the restored transaction log files from temporary folder designated by administrator prior to restore.

5. Hard recovery process doesn’t fail if other Exchange databases in storage groups are not available.

The database files, which are restored from online backup, are stored to normal paths set for database. The restore process starts by overwriting the existing Exchange Server database files. If you need existing database in future, you should back it up before restoring the database from backup.

You must consider that the restore process may fail due to any reason. Even if existing EDB file cannot be played at the moment, the files are possibly still repairable, and you can salvage the data.

The Corrupt EDB File recovery through hard recovery is possible in the majority of Exchange Server database corruption scenarios. However, you must have complete backup of the database to carry out this task. In case,the backup is either not available or not updated, you need to go for third-party Exchange recovery solutions.

In such situations, EDB Recovery Software come for your rescue. They are particularly designed to carry out in-depth scan of entire Exchange Server database and extract all mailboxes and their objects. The EDB Recovery Tool is totally easy to use with simple and self-explanatory graphical user interface. The applications preserve integrity of your database due to their read-only conduct.

EDB Recovery Software is the most advanced solution tor Recover EDB and handle all types of EDB corruption situations. It works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. The software restores emails, notes, contacts, tasks, calendar entries, appointments, attachments, and other objects.

As an example, MS Exchange Server 2007 Management Pack for Operations Manager supervises the MS Windows Application Event log on systems, which are running MS Exchange Server 2007 and returns the below event:

“Product Name: Exchange
Product Version: 8.0 (Exchange Server 2007)
Event ID: 17003
Event Source: MSExchangeTransport
Alert Type: Critical Error
Description: A Transport database operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required.”

After the above error, Microsoft Exchange Server does not let you access your database. At this point, you have to verify the cause of this problem and perform EDB File Recovery by resolving it.

Cause:

The error message below indicates that specified ESE (Extensible Storage Engine) database is damaged. It is preventing MS Exchange Server services from starting.

- ESE, also called JET Blue, is an ISAM (Indexed Sequential Access Method) data storage technology intended by Microsoft. The ESE is particularly used as a key component of the Microsoft Exchange Server and the Active Directory.

How to Fix ESE Corruption:

You can carry out following things to sort out this issue-

1. Delete the defined database and corresponding transaction logs. You must not remove the database if you have significant data in the database.

2. Repair the damaged database using Isinteg.exe tool or restore it from backup.

However, if none of the above methods helps you to work around the problem, EDB Recovery Tool is the only option to go for. They carry out in-depth scan of entire EDB file using high-end scanning techniques and restore all database objects such as emails, notes, contacts, tasks, and more.

The software enable you to recover corrupt EDB file in a quick and easy way as they are incorporated with simple and self-descriptive graphical user interface. The integrity of your database is always preserved by these tools.

EDB Recovery Software is the most preferred recover EDB solution to repair and restore EDB files in all cases of corruption. The EDB Recovery is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

Know More: How to Recover EDB File?

The following scenario will help you understand such problems better. Consider you deploy a Unified Messaging system in your Exchange Server environment. You observe that the UM utility cannot start. Later, you observe that Microsoft Exchange database is also unable to mount and reports an error, such as below:

The database files in this store are corrupted.
ID no: c104173b
Exchange System Manager.

You cannot mount the Exchange database at even further attempts.

Cause

The prime reason for the above error to occur is corruption of Exchange Server database.

This issue can also occur due to presence of old transaction log files in the folder.

Solution

You should try these solutions to overcome the existing problem:

• Execute Eseutil /R command to replay the transaction log files and perform soft recovery

• Remove the transaction logs from the folder and try to mount the database again. You can successfully rerun the UM utility once the database mounts

• Check for the database backup. If available, restore

• Run Eseutil /P command, followed by Eseutil /D and Isinteg commands. But this command deletes data and hence, is less recommended

• Use an EDB Recovery Software to repair the corrupted database and extract the valuable data

An Recover EDB application uses a powerful, yet safe, set of algorithms to repair the corrupted Exchange database. These repair applications are easy to install and use with interactive user design. You can use these utilities in any case of Exchange database corruption.

EDB Recovery Tool is an advanced utility that repairs corrupted or damaged Exchange database and restores the mailboxes in *.pst files. The EDB Recovery Software supports Exchange Server 5.5, 2000, 2003, and 2007. The software is easy to operate and can also recover deleted mailboxes. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

More Exchange Server Resources

Exchange 2007 Recovery:
Exchange 2007 Recovery software recovers e-mails and other related items from the corrupted or damaged EDB and STM database of MS Exchange Server and restores mailboxes in distinct *.pst files.

Exchange 2003 Recovery: Exchange 2003 Recovery tool is an advanced Exchange database recovery utility and can recover all of the objects of EDB file in each and every case of corruption.

Exchange Mailbox Recovery: Exchange Mailbox Recovery software repairs corrupt .edb and .stm files of MS Exchange Server and recover user mailboxes with their respective emails and related items.

Exchange Database Recovery: Exchange Database Recovery software is designed and developed to recover emails from corrupted or damaged database files of MS Exchange Server.This tool restores individual mailboxes in Outlook-usable PST files.

Exchange User Profile Recovery: Exchange User Profile Recovery software Recover user Profile that is comprised in Exchange EDB file.

Stellar Phoenix Mailbox Exchange Recovery v3.0 recovers STM data in e-mail body itself, which is a considerable improvement over its previous releases that used to recover it as an e-mail attachment. Also, the exchange recovery software now allows users to manually select the root Exchange Server version at ‘Select EDB File’ dialog-box with the added ‘Select Server Type’ option. The free demo version of the exchange server recovery product is available for download from company’s website that lists the mailbox(es) it can recover.

“Stellar Phoenix Mailbox Exchange Recovery v3.0 is the unified package that delivers full versions’ compatibility, accidental deleted mailbox recovery, and multilingual data recovery support . Together with several conforming features, the update helps administrators to achieve long-term database control.”said Sunil Chandna, CEO of Stellar Information Systems Limited. “This release provides organizations a way to lessen the operational losses while Exchange database corruption. With several reworked features, Exchange Recovery v3.0 is designed as a cost-effective and time-saving solution”

New Features of Mailbox Exchange Server Recovery v3.0:

1. Supports MS Exchange Server 2007

2. Recovers deleted mailboxes

3. Supports Unicode-formatted EDB files

4. Recovers STM data as e-mail body for Exchange Server 2003, 2000, and 5.5

5. Allows to select Exchange Server type- a new ‘Select Server Type’ option

Pricing

Stellar Phoenix Mailbox Exchange Recovery v3.0 is an affordable edb recovery solution, available in three different license options- Administrator, Technician, and Academic. The product range starts at $499 for Academic License.

Stellar Information Systems

Stellar Information Systems Limited is industry’s leader in providing data recovery software, e-mail recovery tools, database repair solutions, file repair utilities, data safety products, and data recovery services. Certified with ISO 9001:2000 standard, Stellar has more than 1,100, 000 satisfied customers worldwide.

Contact Information

For more information and product purchase options:

Call : +1-866-554-2512 (TOLL FREE)
Mailto: orders[at]stellarinfo.com.
Web Address- http://www.edb-recovery.com

Exchange single-bit errors are most likely to be reported while online backup or defragmentation. This is because while these operations, database is read at page-level and corruption also exists at page-level. For instance, you might encounter the below error message:

The database page read from the file ‘file_name’ at offset ‘offset’ (database page) for ‘number’ bytes failed verification. Bit ‘bit’ was corrupted and was corrected but page verification failed with error ‘error’. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.

This error is usually associated with -1018 error and is logged under event 398.

Error Explanation

The error suggests that the specific database page that has been referenced in Exchange database file such as Priv.edb is damaged. It occurs when CRC of a database page mismatches with that contained in this page. Exchange reports a fatal error when there is a multibit error.

Solution

You need these measures to solve the given problem:

1. Perform all system diagnostic tests and take the corrective measures

2. Use a different set of hardware if required

3. Upgrade the firmware or BIOS to the latest versions available

4. Perform EDB Recovery using eseutil /P and eseutil /D commands

eseutil /P is an unsafe command with respect to database integrity as it deletes corrupted pages. However, if you use an EDB Recovery Software that proves much safer to repair the corrupted database and extract the lost data.

EDB Recovery Software is an efficient utility that repairs corrupted Exchange databases and restores the mailboxes in individual *.pst files. The EDB Recovery Tool also recover deleted mailboxes. The tool is compatible with Exchange Server 5.5, 2000, 2003, and 2007. The software recovers STM data in e-mail body.

As an instance, you might receive the below error message with your Exchange Server database:

“msgidJetDatabaseCorrupted.”

This error is transient and under its description, you see the below error statement:

“Non-database file or corrupted database.”

Exchange Server logs this error in application event log with Event ID 9511.

The error suggests that Information Store service of MS Exchange Server is trying to read some data from a corrupted database or a non-database file. The database is logically or physically corrupted.

To solve the above described issue, you should check for more ESE events logging in Application log to determine the specific roots of this issue. You can also run Database Recovery Management tool, which is a part of Toolbox in Exchange Management Console, to get more assistance in this regard.

In order to solve corruption issues with Exchange database, you need to perform these steps:

1. Dismount the database that is affected from corruption

2. Backup the database

3. Perform database integrity check using eseutil /g command

4. Repair the database using eseutil /p command

In case, performing the above method results data loss or proves unable to repair the database, you need an third-party product for recover corrupt EDB file. The EDB Recovery software perform thorough database scan and result safe repair in each instance of database corruption. The software are easy to install and implement with self-explaining nature.

EDB Recovery Software is an advanced utility that repairs and restores corrupted Exchange databases. It is a safe database repair tool with highly rich graphic features. The EDB Recovery Tool supports Exchange Server 5.5, 2000 and 2003. This tool extracts all user mailboxes as *.pst files without modifying the original contents.

To illustrate such scenarios with Calendaring agent, suppose you try to save few appointments in MS Exchange Server. Your observe that Calendaring agent fails to function properly. Some or all of the calendar information are lost. Additionally, you receive the similar entries logging in application event log of Exchange Server:

Event ID: 8206
Source: EXCDO
Description: Calendaring agent failed with error code 0×80040229 while saving appointment

and

Event ID: 1160
Source: MsExchangeIS
Description: Database resource failure error First Storage Group\Mailbox Store (MAIL) occurred in function JTAB_BASE::EcPrepareUpdate while accessing the database “0xfffffc0d”.

You may also encounter Event IDs: 2 and 7200 describing the failure of Exchange Calendaring agent.

Cause
Exchange Server exhibits the above described behavior when a file-level antivirus software is installed and is configured to scan the Exchange Server directory (EXCHSRVR) structure.

Solution

The solution to this problem is to reconfigure your antivirus software and not to include EXCHSRVR directory and drive ‘M’ in this scan.

A file-level antivirus software locks and scans the file that is currently being tried to access by Exchange Server. Thus, the Information Store fails to lock this file and eventually, the file may become corrupt and unusable. When this occurs, your first recommendation is to restore the database from a previous backup or apply eseutil repair utilities (/p and/or /r switches) for the affected database(s).

However, if none of the database restore method works, you need to use an EDB Recovery Software that can scan and repair the corrupted database effectively. The EDB Recovery utilities are exclusively designed and simple products that allow to repair and restore the damaged Exchange database.

The EDB Recovery Tool is an excellent working utility that repairs corrupted Exchange Server database and restores the individual mailboxes as *.pst files. The advanced EDB Recovery Software supports Exchange Server 5.5, 2003, and 2003. The tool provides an easy and safe mailbox restoration with an interactive user interface.