Tips to Solve Exchange Sever Error’ -338 (JET_errBadParentPageLink, Database corrupted)

Microsoft Exchange Server is a transaction-based and fault-tolerant system and thus, has much better protection against data loss as compare to other messaging applications. Despite of the fact, Exchange Server databases still get corrupt. The common reasons of corruption are abnormal system or power failure, database oversize issues (16 GB), antivirus scanning, virus attack, and application bugs. Such instances can affect any of the Information Store databases, which are Priv.edb and Pub.edb. As an administrator, your primary concern is to restore the data, which is applicable using the last backup or by repairing the database. There are several EDB Repair software available that may work against if the Exchange repair utilities fail and/or backup is not available.

As one of the instances, suppose you experience an unexpected power outage with your Exchange Server computer. After this, when you start the database, you get some events (such as event 467, 9297 etc.) logging in the Application log. When you run eseutil commands to check the database integrity, it gives an error as below:

Operation terminated with error -338 (JET_errBadParentPageLink, Database corrupted)…”

If you execute isinteg command, this may result no errors.

Cause

The error -338 occurs due to corruption in parent database and is returned by directory manager. It can occur because of unexpected power failure.

Solution

You can solve the above issue by applying these measures:

  1. Check the last online backup. If available and valid, restore from it.
  2. You can create a new mailbox store and move all possible mailboxes to it
  3. If the above solutions don’t work, you can use esesuitl /r (soft recovery) and/or eseutil /p (hard recovery) commands to repair the corrupted database. The latter option can cause data loss as it deletes the corrupted pages. So, it is suggested to backup your database before applying it.

In case, none of these resolutions proves valid, you need a third-party Exchange Repair utility. These software offer safe EDB Repair in each case of database corruption and have high competency to maintain the original database integrity. Moreover, these utilities are quite easy to install and use with self-explaining documentation.

Stellar Phoenix Mailbox Exchange Recovery is a reliable and advanced utility that repairs damaged or corrupted Exchange database. The high-end EDB Repair Tool supports Exchange Server 5.5, 2000, and 2003. The software implements powerful scanning mechanism and restores all the mailboxes in individual *.pst files. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

How to Solve when Exchange Database Fails to Mount with (hr=0×80004005, ec=-528) Error?

Transaction log files record all the modifications to an Exchange Server database and are crucial for the proper functioning of Exchange. If you remove a log file that has not been written to the associated database, it can bring several issues, the most common being that the database may fail to mount. You can solve this problem by removing all the log files, but you first need to check the database consistency. If it exists in inconsistent state, the solution is to restore from backup or apply an EDB Repair technique.

For instance, consider a scenario in Exchange Server. You try to mount a mailbox store, but the operation fails with the below error message:

Exchange is unable to mount the database thay you specified. Specified database: Servername\First Storage Group\Mailbox Database; Error code: mapiExceptionCallFailed: Unabble to mount database. (hr=0×80004005, ec=-528)”

The error occurs each time when you try to mount the store. As a result, all the clients connected to server are disconnected.

Cause

The above error can occur if you remove a (or more) log file, which has not been committed to the database yet.

Solution

To solve this issue, you need to move the transaction log files to a different folder. For this, follow the steps mentioned underneath:

  • Stop Information Store and all databases in the storage group

  • Verify the integrity of database by running esesutil /mh command, followed by database name (for example, for Mailbox Store1 database, name is Mailbox Store1.edb). Examine the ‘State’ value under its header information

  • If the database is in Clean Shutdown (Consistent) state, you can safely remove all the transaction log file and save them to a different folder. Make sure you don’t remove the current transaction log file

  • If the database is in Dirty Shutdown (Inconsistent) state, restore from the last online backup. In case backup is invalid, run eseutil /r command for soft recovery. If this fails, you can run eseutil /p command for hard recovery or use an EDB Repair Software. The former option (hard recovery) causes data loss as it deletes the corrupted pages. An EDB Repair utility can safely repair a corrupted Exchange database and provides secure data restoration.

Stellar Phoenix Mailbox Exchange Recovery is a powerful solution that repairs and restores Exchange database created with Exchange Server 5.5, 2000, and 2003. The advanced EDB Repair Software extracts all user mailboxes into individual *.pst files and provides option for selective mailbox recovery. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

Watch Video: How to Repair EDB File?

Resolving Error 939586631 in Exchange Server

An Exchange Server storage group consists various public and mailbox folder stores, however their number depends on the Exchange Server version in use and requirements of the user. The mailbox store contains all user and system mailboxes and is comprised of two files: Priv.edb and Priv.stm. Any corruption to the data repository EDB file leads to data inaccessibility and creates unavoidable situations of using a backup. If it is not possible to restore from backup, you need to repair the corrupted database using Exchange eseutil repair utility or a third-party EDB Repair software.

For instance, consider a situation when you run Eseutil /CC command. The mailbox store fails to mount and returns an unknown error -939586631. Consequently, the stored mailboxes are inaccessible.

Cause

The above error particularly results when you run Eseutil /CC command using the incorrect file path pointing to Restore.env file.

Eseutil /CC is the restore mode command, which is applied to run hard recovery on a database that has been restored from an online backup. Exchange Server creates Restore.env file while restoring from backup to control the hard recovery process.

Solution

Follow the below mentioned steps to recover from the given problem:

  1. Run Eseutil /CC command using the correct file path of Restore.env file.
  2. Check the database consistency. If it is inconsistent, you can use Eseutil /P and then Eseutil /D command for recovering the database.

Eseutil /P is the hard command that deletes the corrupted data, instead of repairing it. So, after using the command, you may find the database with lost pages and deleted information. For this reason, whenever you find your Exchange database in corrupt state, it is recommended to use a safe EDB Repair Tool.

An EDB Repair application allows you to extract the contained mailboxes and restore them at a safe location from a corrupted database. These software implement safe scanning algorithms, which are effective at repairing the database file. The tools are easy to install and require no prior technical skills to operate them. In addition, you can use these products in any case of logical database corruption.

Stellar Phoenix Mailbox Exchange Recovery is an advanced solution that repairs and restores corrupted Exchange databases. The EDB Repair Tool supports Exchange Server 5.5, 2000 and 2003. It is a secure database repair tool with rich graphic features. The tool extracts all user mailboxes in individual .pst files without modifying its contents.

How to Solve ‘The database page read failed verification..’ Error in Exchange Server?

Exchange Server generates a checksum for a page, which is written to the disk after it writes all the data to the page. This includes writing the page number also. After adding checksum to the page, the Exchange then moves to write pages to the disk. A database page is declared as corrupt if its page number and/or checksum mismatches. In such situations, you should consider repairing the database or restoring from the latest backup. In case when no clean backup is available, you should run an Repair EDB tool

You might come across the below error with your Exchange Server database:

The database page read failed verification because of a -1018 error (page number mismatch)”

Error 1018 is associated with event 475 displaying in the application event log. The error is generally encountered when you try to perform online backup or online defragmentation.

Cause

The above error is a typical symptom of database damage at page level. It occurs when database page read fails verification because of mismatch in a page number. It indicates that the database page that has been referenced in the store file is damaged. Such errors are usually observed because of firmware, hardware or driver issues.

Solution

To solve the problem discussed above, you need to try these methods:

  • You should run system diagnostics to determine the exact root of the problem. You may not come to a definite conclusion if the corruption occurs rarely or occurs while heavy load conditions. If the hardware issues come out as problematic, you should consider replacing them.

  • You can upgrade the disk firmware and controller BIOS to the latest versions available.

  • To repair the corrupted database, you need to run eseutil repair utility. Try to avoid performing hard recovery as this will delete the corrupted pages from database. Instead, you should restore the database from backup if available and is valid.

If all the attempts fail, you need a suitable third-party solution for EDB Repair. These are perfect EDB Repair Software built with safe scanning technology to repair and restore a damaged Exchange database.

Stellar Phoenix Mailbox Exchange Recovery is a powerful and secure tool to perform systematic repair of damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It is a comprehensive EDB Repair tool that extracts all user mailboxes by converting them into individual Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

Exchange Database Verification Failed because of no Page Data

n Exchange Server database can get corrupt for several reasons, which include unexpected power failure, corrupted log files, network errors, virus infection and others. Consequently, the database may stop and fail to mount. You can try repairing the database using eseuitl utility. If this fails too, it compels you to apply the latest backup available or repair the database by an EDB Repair product.

For instance, you might come across the below error when dealing with Microsoft Exchange Server:

Database page read failed verification because of no page data.”

It further suggests to move the existing databases to a new hardware. The error is logged with event 476 in application event log.

Cause

The above error means that the database read operation has failed It generally occurs with error 1019. The causes are:

  1. The specific database page that has been referenced within the database file is expected to be in use, but Exchange finds it empty or uninitialized.
  2. A page may fail its checksum test with error -1018. But if the page number field that is in use is 0×00000000, the checksum failed page will show -1019 error instead.
  3. File is corrupt and as a result, it maps some pages into database file that are not associated with it
  4. Logical links or pointers between database pages are not correct

The event 476 can also be related to -1018 error that indicates checksum mismatch and is caused generally due to hardware issues.

Solution:

You should check your system for related hardware issues if the database corruption problem is persistent. Replace the hardware and upgrade your firmware and/or disk controller if required.

To repair the corrupted database, you can run eseutil /p command, which is a hard recovery option in Exchange database. Later, you need to execute eseutil /d and isinteg -fix commands. Exchange hard recovery performs page-level recovery and deletes the pages that it finds corrupted. So, it is recommended that you use safe EDB Repair Software. These third-party utilities let you perform easy and secure EDB Repair without any changes to database content, structure and metadata.

Stellar Phoenix Mailbox Exchange Recovery is a reliable and advanced recovery tool for repairing corrupted Exchange databases. It repairs and restore individual mailboxes in .pst files. The comprehensive EDB Repair Software supports Exchange Server 5.5, 2000 and 2003. The tool restores all emails and other objects from corrupted database.

Exchange Database Verification Failed because of no Page Data

An Exchange Server database can get corrupt for several reasons, which include unexpected power failure, corrupted log files, network errors, virus infection and others. Consequently, the database may stop and fail to mount. You can try repairing the database using eseuitl utility. If this fails too, it compels you to apply the latest backup available or repair the database by an EDB Repair product.

For instance, you might come across the below error when dealing with Microsoft Exchange Server:

Database page read failed verification because of no page data.”

It further suggests to move the existing databases to a new hardware. The error is logged with event 476 in application event log.

Cause

The above error means that the database read operation has failed It generally occurs with error 1019. The causes are:

  1. The specific database page that has been referenced within the database file is expected to be in use, but Exchange finds it empty or uninitialized.
  2. A page may fail its checksum test with error -1018. But if the page number field that is in use is 0×00000000, the checksum failed page will show -1019 error instead.
  3. File is corrupt and as a result, it maps some pages into database file that are not associated with it
  4. Logical links or pointers between database pages are not correct

The event 476 can also be related to -1018 error that indicates checksum mismatch and is caused generally due to hardware issues.

Solution:

You should check your system for related hardware issues if the database corruption problem is persistent. Replace the hardware and upgrade your firmware and/or disk controller if required.

To repair the corrupted database, you can run eseutil /p command, which is a hard recovery option in Exchange database. Later, you need to execute eseutil /d and isinteg -fix commands. Exchange hard recovery performs page-level recovery and deletes the pages that it finds corrupted. So, it is recommended that you use safe EDB Repair Software. These third-party utilities let you perform easy and secure EDB Repair without any changes to database content, structure and metadata.

Stellar Phoenix Mailbox Exchange Recovery is a reliable and advanced recovery tool for repairing corrupted Exchange databases. It repairs and restore individual mailboxes in .pst files. The comprehensive EDB Repair Software supports Exchange Server 5.5, 2000 and 2003. The tool restores all emails and other objects from corrupted database.

How to Solve Error 1120 and 5000 Starting Information Store Service?

The core repository of data for Exchange Server is its Information Store service, which is consisted of both public folder and mailbox store data. The store service basically implements the Exchange Server store. If Microsoft Exchange Information Store Service (MSExchangeIS) does not start, one of the top reasons is that its database(s) are corrupted. Among other reasons, this behavior primarily occurs as an after-effect of abnormal shutdown of Information Store. At this point, you should perform soft recovery or restore the database from a previous online backup. If this doesn’t work, it is suggested to use EDB Repair tools instead of hard recovery as it can cause data loss.

To exemplify such MSExchangeIS scenarios, consider you try to start the Information Store service in your Exchange Server, but fail to do so. When you view the Event Log with MSExchangeIS as the source, you find events 1120 and 5000 recorded as the failure entries. These errors show that the Exchange databases are in inconsistent state.

Cause

These errors occur when the following conditions are true:

  1. You perform Eseutil.exe hard recovery operation for Priv.edb file to fix its inconsistency errors that occurred due to unexpected shutdown of Information Store.

  2. The earlier transaction log files don’t exit and are deleted

  3. No hard recovery is performed for Pub.edb file

As a result of the above sequence of steps, Priv.edb is consistent, but Pub.edb is still inconsistent due to the absence of transaction log files.

Solution

To solve the described issue, you can use any of the below methods:

  1. Remove the Pub.edb file provided it contains no required data. Make sure you don’t delete Edb.log file that is required by Priv.edb

  2. Execute hard recovery for Pub.edb file using eseutil /p command

  3. Use a third-party EDB Repair Tool to repair it

EDB Repair software provide safe recovery for corrupted or damaged Exchange .edb files. These are feature-rich applications built with advanced technology for database repair. Moreover, you can use these tools without any prior technical skills as they provide an interactive user interface.

Stellar Phoenix Mailbox Exchange Recovery is an advanced and safe Repair EDB utility that employs powerful scanning algorithms to repair a damaged Exchange Server database. It is compatible with Exchange Server 5.5, 2000 and 2003. It is a safe EDB Repair utility with impressive set of features. The tool extracts user mailboxes in individual .pst file format files.

How to Solve Event 465 in Exchange Server?

An Exchange public store or mailbox store of a storage group can be mounted using Exchange Management Console or Exchange Management Shell. This makes the databases ready for use. For any reason, if the process fails, it leads to data inaccessibility. Database mount failure primarily suggests that one or more storage group components are faulty. However, if one or more databases are corrupted, you should use eseutil utility to repair it. Alternatively, you can apply the last good backup or use a powerful EDB Repair Tool to repair the corrupted database.

For instance, suppose you try to mount public or mailbox store in Exchange Server. The operation fails and the application event log reports the below information message:

Event ID: 465
Source: Ese98
Type: Error
Computer: Server1
Information Store (2184) Corruption was detected during soft recovery in logfile C:\Programme\Exchsrvr\mdbdata\E00000E8.log. The failing checksum record is located at position 6531:471. Data not matching the log-file fill pattern first appeared in sector 6600. This logfile has been damaged and is unusable.
For more information, click http://search.support.microsoft.com/search/?adv=1.

Error 465 is usually accompanied with error 477 that informs checksum mismatch and suggests you to restore the logfile from backup.

Cause

The prime cause of error 465 to occur is transaction log file corruption, specifically Edb00000E8.log file.

Solution

You should remove the corrupted log file to achieve recovery. To do so, you must first find out the storage group, which is affected from this corruption and then follow these steps:

  1. Dismount all the databases of affected storage group and perform its offline backup.

  2. Run eseutil /mh tool to make sure if the databases exist in consistent state.

  3. If all the databases report ‘Clean Shutdown’ state, move out all the log files from Exchsrvr\Mdbdata folder.

  4. But if databases exist in ‘Dirty Shutdown’ state, perform soft database recovery using eseutil /r

  5. On unsuccessful attempt of soft recovery, you can restore the database from last Exchange backup

  6. In cases when no valid backup is available, you can try repairing the database using eseutil /p, which performs hard repair.

  7. The hard repair of Exchange database causes corrupted pages to delete. Thus, it is suggested to use a third-party EDB Repair Tool for more effective and safe database repair. EDB Repair software employ advanced scanning algorithms and provide you easy-to-implement user interface.

Stellar Phoenix Mailbox Exchange Recovery is a full-featured tool to perform systematic repair of damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It is a safe EDB Repair Tool that extracts all user mailboxes by converting them into individual Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

Exchange Errors due to Undetected Page Removal while B-tree Split Operation

Microsoft Exchange Server storage groups are consisted of mailbox store and public folder store. Each mailbox store is further made up of database set comprising of two files: Priv.edb and Priv.stm. Similarly, each public folder store database set contains Pub.edb and Pub.stm files. For any reason if Information Store databases get corrupt, you might experience symptoms like slow performance, abrupt behavior while normal operations and most often, JET errors. If an updated data backup is available, you are recommended to restore from it to solve these problems. In case no valid copy exists, try running built-in ESEUTIL /P utility or safe EDB Repair products.

For instance, when using Microsoft Exchange Server, you may observe any of the below symptoms with information store databases:

1. You run ESEUTIL /D to attempt offline defragmentation of the database, but fail with -1601(JET_errRecordNotFound) or -1603(JET_errNoCurrentRecord) error
2. rror -1069 error (JET_errVersionStoreOutOfMemory) while normal database operations
3. Application log reports an error with Event ID: 1101
4. You run ESEUTIL /G /V /X in Exchange Server 5.5 and receive JET Error -1206 (JET_errDatabaseCorrupted).

Cause

The Information Store service might violate access because of encountered corrupt data.

When trying to insert a record in B-tree, the Exchange engine might find a record with same primary key value, marked for deletion. In such cases, it undeletes the node by updating its content with that of new record and might even change the size of record. Now, if this size is too large for the page, the database engine performs b-tree split operation. The information store may become unresponsive or data might get corrupt if Exchange Server tries to re-latch the pages while the record has been actually removed by information store cleanup thread.

Solution

You can recover from such problems by applying these measures:

1. Execute database consistency checker to check for corrupted and/or orphaned LVs
2. For correcting corrupted and orpahned LV errors, you need to run ESEUTIL /P <dbswitch> /X followed by offline defragmentation
3. Perform offline defragmentation if only orphaned LVs are reported
4. In case of corrupted LVs, you should run ESEUTIL /P <dbswitch> /X followed by offline defragmentation

If applying these measures doesn’t fix the database corruption problem, you should restore from the complete database backup or use a EDB Repair Tool in case of valid backup unavailability. EDB Repair utilities are graphically rich tools incorporated with high-end scanning algorithms to repair and restore damaged Exchange databases at a safe location.

Stellar Phoenix Mailbox Exchange Recovery is an advanced EDB Repair Tool that employs high-end scanning algorithms to repair a damaged Exchange database. It supports Exchange Server 5.5, 2000 and 2003. It is a safe EDB Repair Tool with impressive features. The tool extracts user mailboxes in .pst file format.

Transaction Log File Integrity Check Failure May Cause EDB Corruption

In an EDB (Exchange Server Database) file, the transaction log is s history of activities, executed by the Exchange Server to guarantee the ACID properties over hardware failure or system crash. There are mainly helpful in aces of improper system shutdown to rollback the incomplete transaction and to recover the system from inconsistent state. But in some situations, the transaction log itself might get damaged and put your database in an inconsistent or damaged state. These situations cause critical data loss and require EDB Repair to be sorted out.

In order to check the integrity of log files, you can use Eseutil tool with /ml option. But in some cases, the Eseutil utility with /ml option fails in Microsoft Exchange Server 2003 and Microsoft Exchange Server 2000.

In order to test the transaction log file for corruption, you should the below command:

Eseutil /ml Log File Name

If the transaction log file passes the test, you will get below response:

Integrity check passed for log file: Log File Name

If the test fails, you get following message:

CORRUPTION DETECTED in log file: Log File Name
Operation terminated with error -501 (JET_errLogFileCorrupt, Log file is corrupt)”

The database inconsistency might take place due to torn writes, that require Repair Exchange database to resolve it. The torn write is actually an incomplete physical write operation, which is left in E00.log file after database service stops. The torn write results into checksums on affected transaction in log file to be incorrectly calculated and log is detected as corrupted by Eseutil. To resolve the Torn Write situations, when you apply Eseutil /ml, the following event might be logged into Application Event Log of Exchange Server:

Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 465
Date: 12/9/1999
Time: 2:48:48 PM
User: N/A
Computer:
Computer_Name
Description: Information Store (2428) Corruption was detected during soft recovery in log file E:\exchsrvr\THIRD\E00123ab.log. The failing checksum record is located at position 8189:328. Data not matching the log-file fill pattern first appeared in sector 8195.

In such cases, you need to repair and restore the damaged database to retrieve data from it. This is best possible with the help of powerful and advanced third party EDB Recovery software. These applications are capable of carrying out in-depth scan of damaged EBD file and retrieve all of its objects. The Repair EDB software are built-with interactive graphical user interface and thus do not demand sound technical skills.

Stellar Phoenix Mailbox Exchange Recovery is an efficient tool to ensure safe and absolute recovery in most of the EDB file corruption situations. It works well with Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.