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 recover 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.

Source: http://www.edb-repair.com/

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.

Source: http://www.edb-repair.com/

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 Exchange Server Recovery.

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 0x80040605.

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.

Stellar Phoenix Mailbox Exchange Recovery 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.

source: http://www.edb-repair.com/

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 . 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

è An incorrect value exists in the registry for the location of MTA database path.

è 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).

Source: http://www.edb-repair.com/