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.

Solving Exchange Server Error- “The information store terminate abnormally”

Information Stores is the most important component of Microsoft Exchange Server. It is responsible for managing and controlling Exchange Server Database (EDB) file, mailboxes, public folders and all other database objects. But in some cases, this vital Exchange Server objects gets damaged and thus you can not access your critical data from Exchange Server. This behavior lead to critical data loss and require EDB Repair to be sorted out.

In a practical scenario, when you try to access data from Microsoft Exchange Server 2003 or 2000, you may come across any of the below given symptoms:

  • The Exchange Server Information Store service might not start and underwritten error message may occur:
    1067 The information store terminated abnormally.

  • While performing online defragmentation of EDB file, the following event is logged in Application Event Log:
    Date: date
    Source: ESE
    Time: time
    Category: (12)
    Type: Error
    Event ID: 447
    User: N/A
    Computer: Server name
    Description: Information Store (nnnn) A bad page link (error -327) has been detected in AB-Tree (ObjectId: 19, PgnoRoot: 113) of database E:\Program Files\Exchsrvr\mdbdata\priv1.edb (3440582 => 3443648, 3443232).

Root of the issue

This issue generally takes place due to antivirus scanning of database file directory or hardware failure. The Event ID 447 shows that the database is logically corrupted. It might happen due to any of the following causes:

  • Incorrect log files were replayed while database restoration was going on.

  • Database log files have removed, which weren’t fully committed to database.

  • Virus has infected the database and has damaged its logical structure.

No matter what the cause of this problem is, the ultimate result would be the loss of your critical data. When it occurs, all of your valuable emails, notes, contacts, tasks, and personal folders becomes unusable. At this point, you are required to carry out Repair EDB by sorting out this issue.

You can repair and restore damaged Exchange Server database using third party tools, known as EDB Recovery software. These software effectively scan the corrupted EDB file using efficient scanning mechanisms and retrieve all of its inaccessible and damaged objects. These applications are completely easy to use and always perform safe and original EDB Repair.

Stellar Phoenix Mailbox Exchange Recovery is the most advance EDB Repair tool to repair and restore EDB file from Exchange Server 2003, 2000 and 5.5. It is compatible with Microsoft Windows 2003, XP and 2000. This software is capable of retrieve all of the EDB file objects, user mailboxes and public folders.

EDB Corruption Due to Improper Termination of Information Store Service

The common reasons of EDB (Exchange DataBase) file corruption are improper system shutdown due to operating system malfunction, system crash, and hardware failure or power outage. If Exchange Server’s Information Store Service gets terminated inappropriately, the EDB file may get corrupt and become inaccessible. This behavior makes all your critical data inaccessible and result as serious data loss. You need to go for EDB Recovery tools to solve this issue.

When you try to start Microsoft Exchange Server, you might encounter any of the below given symptoms:

è The Exchange Server Information Store Service might not start and you might get the following error:
”1067 The information store terminated abnormally”

è While performing online fragmentation, following event is logged into the Application Event Log of Exchange Server:
Date: date Source: ESE
Time: time Category: (12)
Type: Error Event ID: 447
User: N/A
Computer: Server name
Description: Information Store (information store name) A bad page link (error -327) has been detected in a B-Tree (Object Id: 19, Pgno Root: 113) of database E:\Program Files\Exchsrvr\mdbdata\priv1.edb (3440582 => 3443648, 3443232).

After this behavior of Microsoft Exchange Server, you can not mount the Information Store and thus EDB file becomes inaccessible. To fix this problem, you need to find out the cause of the problem and perform EDB Repair.

Grounds of this issue

This problem generally occurs due to Exchange Server database corruption after improper termination of Information Store Service. The Event ID 447 indicates that the logical structure of the EDB file is damaged and Microsoft Exchange Server can not recognize it.

The logical database corruption is generally undetectable by the database repair utilities like Eseutil. This problem appears only when you try to access the EDB database file.

Resolution

To solve this issue, you need to repair and restore the EDB file. It is best possible with the help of EDB Recovery software. These are powerful third party applications, which are capable of thoroughly scanning the entire EDB file and repair all its objects as emails, notes, contacts, journals, tasks and more.

These are user-friendly software as they come equipped with simple and interactive graphical interface. With read-only and non-destructive design, these EDB Repair tools are completely safe to use and perform absolute recovery.

Stellar Phoenix Mailbox Exchange Recovery is the foremost EDB Repair tool to revamp the corrupted EDB Files. It supports Exchange Server 2003, 2000 and 5.5. The software is compatible with Microsoft Windows XP, 2003 and 2000.

EDB Corruption Due to Integrity Errors

Sometimes, you can not access data from private stores of Exchange Server 2003 that use active/passive clustering. It may cause serious problems of data loss and thus you need to perform EDB Repair.

When you try to backup the private storage group, the backup may fail and you may see the following entries in Application Event Log:

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 217
Date: 14/09/2005
Time: 2:16:59 PM
User: N/A

Computer: CALEXNODE01

Description:

Information Store (3280) SG2 – Edmonton: Error (-4001) during backup of a database (file K:\EXCHSRVR\SG2\SG2-Store4.edb). The database will be unable to restore.

For more information, click http://www.microsoft.com/contentredirect.asp.

In these situations, when you run “eseutil /g” on the EDB file to check its integrity, you get the following result:

“Integrity check completed.

Database is CORRUPTED, the last full backup of this database was on 09/13/2005 23:23:16

Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 271.110 seconds.”

This entire behavior of Exchange Server results into serious data loss situations and you need to recognize the cause of the problem and carry out EDB Repair to save your data.

Grounds of this issue

As stated in the above error messages, you may encounter this problem due to corruption to the EDB file. Corruption could be the result of virus attack, unexpected system shutdown, application malfunction and other similar reasons.

Nevertheless the cause of this problem, the ultimate result would be the loss of your mission critical data. To save your precious data and your business, you are required to perform EDB Recovery.

You can carry out this process using third party applications. These software are powerful enough to methodically scan your entire EDB file and extract as much data as possible from it.

With graphical user interface and interactive design, these software are very easy to use and allow you to have Do IT Yourself EDB Repair. These software keep the integrity of data intact as they have read-only design.

Using Edb Repair Software, you can easily repair all your emails, notes, contacts, journals and other EDB objects easily, safely and completely. The repaired EDB file can directly be used with Exchange Server without reconfiguring the user profiles.

Stellar Phoenix Mailbox Exchange Recovery is the most comprehensive and advanced software that can recover your EDB file and all its objects in most of the corruption scenarios. It works well with Exchange Server 2003/2000/5.5. It is compatible with Windows 2003/XP/2000.

EDB Corruption Due to Compressed NTFS Volume

Compression, as the name suggests, is the way to reduce required disk space for a particular file, folder or the entire volume. The one, which is available and done on NTFS formatted volumes, is termed as NTFS compression. NTFS allows compressing of files, folders or the entire volume and thus decreasing their size. Volume compression advantages users to decrease used space of all the contained files and folders in a single go.

Adverse effects of NTFS volume compression have been seen with respect to Exchange Server Information Store which is repository of all user mailboxes and other data. The Information Store service is like the soul of Exchange Server, but NTFS compressed volume may introduce corruption in it. The corruption is specific when the compressed volume of information store reaches the size of 4 GB and hence requires EDB repair.

  • Exchange Server attends many users at a time. It helps processing different user requests and writes and so should not be blended in NTFS compressed volume. Compressed volumes can’t handle heavy write traffic for compression and hence doesn’t support heavy loaded servers such as Exchange Server.
  • Exchange Server supports transaction logging i.e. all the data is written to log files prior to disk. Now, if you have configured it to store its files on NTFS compressed volume and Exchange Server modifies data via mapped section in a compressed file, corruption may result. The application may create bad pages in database.
  • If Exchange Server is using NTFS compressed volumes, the insufficient CPU capacity can fetch problems to EDB. It should have enough CPU capacity which can host compress/decompress operations of compressed volume.

In situations like when CPU utilization gets increased or there exists large NTFS directory, the results may come out as decreased server performance and eventual Information Store failure.

About EDB Recovery

In case, EDB gets corrupted due to the mentioned problems, EDB recovery becomes mandatory to be done. Exchange Server in-built utility, Eseutil, helps removing corruption scenarios, but may fail in several cases and delete those pages which it can’t comprehend. For safe EDB repair, use commercial EDB recovery software . These are the read-only and non-destructive EDB repair utilities which scan and repair corrupted EDB completely.

Stellar Phoenix Mailbox Exchange Recovery is the best quality EDB recovery application. This uses the powerful scanning algorithms to examine and repair Exchange databases. The application is compatible with Exchange Server 5.5, 2000 and 2003 and comes equipped with interactive interface. This EDB repair software repairs all the database objects.

EDB Recovery after Registry Corruption

When you start your Windows computer with Exchange Server installed, you might be notified by the Server Control Manager that Information Store Service won’t start. In this case, your data can not be accessed by EDB file and you need to carry out EDB Repair to access .edb file .

The Service Control Manager of Microsoft Exchange Server may give you the following error message at startup:

“At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

The Exchange Microsoft Exchange Information Store will not start. As a result, all services that depend on Information Store service will not be able to start.”

Along with this error message, you might see the following error events in the Application Even Log of Exchange Server:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Description:
The Microsoft Exchange Information Store service terminated with service specific error 0.

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 5000
Description:
Unable to initialize the Microsoft Exchange Information Store service. Error 0×80040605.

This entire behavior of Exchange Server cause data loss and you need to identify the root cause of the problem and fix it by performing Exchange Repair Software.

Grounds of this issue

This behavior of Exchange Server generally takes place due to missing or inaccessible Services string type value placed in following registry key:

“HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Setup”

The missing registry key corrupts Exchange Server Database File (EDB) and results into data inaccessibility and data loss.

Resolution

You can fix this problem by repairing the corrupted EDB file. It is possible by achieving Exchange Server Recovery that can easily be performed using EDB recovery software.

These software are particularly designed to thoroughly scan the entire EDB file, repair the corrupted EDB file and then restore it. Most of these software have interactive and graphical user interface and thus allow you to have easy and trouble-free Edb Repair Software.

With read only and non destructive design, these recovery software carries out safe and original recovery of all the EDB objects including emails, notes, contacts, calendar entries, journal and personal folders.

EDB Repair Tool is most powerful and result-oriented tool that ensures safe and absolute extraction of all the EDB objects. It can repair EDB files of Microsoft Exchange Server 2003, 2000 and 5.5. This EDB repair software is compatible with Microsoft Windows 2003, XP and 2000.

Microsoft Exchange MTA: EDB Corruption Due To MTA Errors

Sometimes when you start MTA (Message Transfer Agent), you are getting an error message:

“Could not start the Microsoft Exchange Message Transfer Agent service on <ServerName>. Error 2140: An internal Windows NT error occurred.”

To solve this problem, you run Mtachecker.exe, then again you are getting an error message. Database contains serious errors and cannot be automatically repaired.”

Along with these error messages, you might see several events in Application Event Log of the Windows NT Event Viewer, like the following:

Event ID: 2152:
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Operating System


Description: MSExchangeMTA – A fatal database error occurred, the database recovery operation was not successful and manual correction will be required. Details can be found in the file: drive: \Exchsrvr\Mtadata\.\MTACHECK.OUT\MTACHECK.LOG. Please contact Microsoft Product Support Services. [DB Server MAIN BASE 1 14] (16)

Main causes of this type of errors:

You are facing these errors because of the following conditions are

  1. An incorrect value exists in the registry for the location of MTA database path.
  2. If might be possible that edb file is corrupted and Ms Exchange Sever can not read data from the edb file.

This will be the loss of your important data like your e-mails, contacts, tasks, journals and etc. If you want to do recovery of your important data, you can do these two different methods:

  1. If window registry is incorrect, then you have to edit the Window registry to correct the invalid references by exact location reference.
  2. Another method is that you can use EDB Repair software to scan the corrupted EDB file for correction and then you can recovery your crucial data.

Basically EDB Repair software is a third party tool which repair or recover you edb files. This software is very easy to use and no technical knowledge required.

Phoenix EDB Recovery software is powerful enough to systematically scan the whole EDB file and extract your emails, notes, contacts, calendar entries and other data from it. Another important feature of EDB Repair software is that it supports Exchange Server 5.5, 2000, 2003 and also this software is compatible with Windows Vista, XP, 2003, 2000 and NT4 (SP6).

How to Diagnose and Cure Logical Exchange Database Corruption

Logical corruption to Exchange Server is a very common problem. It could occur due to corruption problems with Information Store, Tables, Keys, Indexes or sometimes to whole database.

Logical database corruption is more problematic and difficult to identify than the physical database corruption. The database administrator and users are generally unaware of logical corruption incidence. Unluckily Exchange Server does not contain any in-built utility to diagnose it.

There are so many reasons due to which the logical corruption can take place. Some major causes of logical corruption are as underwritten:
. Deletion of Edb.log File: Some records in Edb.log (log file) might contain changes to the pages, which have been flushed out to the Exchange Server database. If this file is removed, it may cause incomplete transaction. Incomplete transactions might result into internal inconsistency of the database.
. Write Back Cache: When you run unprotected write back caching against log drive, the logical corruption might take place. Unprotected write back cache is one in which the database gets lost, if the any hardware failure or power failure occurs. When the write operations is completed, ESE (Extensible Storage Engine) commits a transaction and makes the information durable on disk.

Once the write operation is complete on the log disk, ESE is free to flush the particular page on the database. If the write operation was unsuccessful, the same problem of logical corruption strikes. Problems occurred while using write back cache don’t prevent the user from using the write back caching.

. Repairing EDB using Eseutil /p: Logical database corruption might also take place when you apply Eseutil /p command to perform jet-level repair. It may cause data loss and incompetent space used in database as the repair fixes the EDB by removing the corrupted data.
If any of the above situations occurs to your database, it may cause logical database corruption. To identify the logical corruption, you need to regularly perform integrity check (Isinteg –fix) or inconsistency check (Eseutil /mh).

Regardless of the cause of logical database corruption, the ultimate result would be the inaccessible Exchange Server database and the loss of your valuable data.
Due to the importance of Exchange Server database for your organization, it is very important to perform Exchange Server recovery. You can easily carry out EDB recovery using the Exchange Server repair software. These are the third party tools, specifically designed to repair and restore your damaged database.

Exchange Server recovery software is a powerful tool to systematically scan the entire database and extract each and every bit of your valuable data. EDB repair software are easily obtainable from Internet and here you may also find the free demo versions of these software to check them out before purchasing.

Stellar Phoenix Mailbox exchange recovery software is the robust EDB recovery software, which is applicable to all file versions of Microsoft Exchange Server and can recover all of the database objects. Interactive user interface, powerful scanning procedures, Live Update and read only design are some major features which make this software world class. To know more about the product, download free demo version from Stellar’s website.

Information Store Inconsistency and Corruption Problems in Exchange Server

You may encounter inconsistency problem or corruption in Microsoft Exchange Server 2000 Information Store Service in Jet database. The problem is indicated by the event ID 448. At this point of time, the database will become inaccessible and you may see the following entries in Application Event Log:

Date: Date
Source: ESE
Time: Time
Category: Database Corruption
Type: Error
Event ID: 448
User: N/A
Computer: Server Name
Description: Information Store (2412) Data inconsistency detected in table Msg of database E:\Program Files\exchsrvr\mdbdata\priv4.edb (0, 524957). For more information, click http://search.support.microsoft.com/search/?adv=1

. Event ID 448 shows that there is an inconsistency or corruption problem in a table of the Jet database.

After this error, when the Exchange Server starts, all the services related to Exchange 2000 might start, but the mailbox stores would not be mounted. Thus, the users will not be able to access data from the database and will face the nightmare of data loss.

After coming across this problem, when you bear out the integrity of EDB file by running Eseutil /g command, it will be unsuccessful attempt and you will get the further error message stating:

“The Database is corrupted.”

Such problems might take place if the hard drive of your Exchange Server is defective or the hard drive is having any defective controller. It could also occur due to incomplete or corrupted restore operation or due to virus attack.
Regardless of the cause of EDB corruption, the main thing is your data and which is at stack of loss. It becomes mandatory here to search for a powerful Exchange Server recovery solution.

Exchange Server recovery is best possible with the application of third party software known as Exchange Server repair software. These software are very powerful to scan the damaged EDB file and end up at perfect EDB recovery.

Stellar Phoenix Mailbox Exchange Recovery is the ultimate solution of all your EDB repair related worries. Having a great scanning capability, this Exchange Server recovery is the best for perfect Exchange Server repair. This EDB recovery software can be used to recover all of the Exchange Server objects from Exchange Server 5.5, 2000, and 2003.