MS Exchange Repair Tool to repair corrupted or damaged edb file

Stellar Information Systems Ltd,<01-09-10>Gurgaon, a leading name in data recovery industry, today declares the launch of Stellar Phoenix Mailbox Exchange Recovery 4.0, a more robust software which repairs corrupt EDB files of Microsoft Exchange Server 2010 in addition to 5.5, 2000, 2003 and 2007 versions.

Developed specifically to address the needs of affected MS Exchange Server administrators, this powerful Exchange recovery application offers to repair corrupt or inaccessible mailboxes and recovers them as individual PSTs. The newly-revived software now incorporates the capability of recovering selective mailboxes.

MS Exchange Server administrators can bank upon this application to derive accurate results in all failure scenarios including corrupt database header, improper database backups, hardware issues, dirty shutdown and others. The free Demo version of the EDB recovery software now has the provision of providing preview of the recoverable mailboxes.

“Version 4.0 of Stellar Phoenix Mailbox Exchange Recovery software comprises unparalleled recovery capabilities with added support for MS Exchange Server 2010. The Mailbox Exchange Recovery upgrade provides tremendous power in the hands of Exchange database administrators with its ability to recover mailboxes in almost all EDB database corruption instances, “ said Sunil Chandna, CEO, Stellar Information Systems Ltd.

“We are sure that the upgrade launch of the EDB recovery software will meet the growing needs and challenges that the MS Exchange database administrators are facing day to day” he concluded.

Key Features Stellar Phoenix MailBox Exchange Recovery 4.0

• Supports Microsoft Exchange 2010, 2007, 2003, 2000 and 5.5
• Repairs and recovers corrupt EDB databases
• Allows selective recovery of mailboxes
• Recovery of Unicode-formatted EDB files also supported
• Recovers deleted mailboxes
• User-friendly and safe application
• Demo version provides preview of mailboxes
• Compatible with Windows 2000/XP/2003/Vista/Windows 7

About Pricing and Availability

Stellar Phoenix Mailbox Exchange Recovery 4.0 is available in three license options including Administrator, Technician and Academic. The Administrator license is available both in CD+Download versions and is priced at $599 plus service and handling charges extra.

About Stellar Information

Stellar Information Systems Limited (established since 1993) is the leading creators and providers of advanced data recovery software and data recovery services for more than 17 years. Holding direct presence in USA, Europe and Asia, Stellar is a name that is trusted for finest solutions to recover lost and inaccessible data.

For more information on the product refer to the official website www.stellarinfo.com and the product micro-site www.ms-exchange-server-recovery.com.

Contact Information :
For more information and product purchase options:
Call : 1-877-778-6083 (TOLL FREE)
Mailto: orders@stellarinfo.com.
Web Address- http://www.stellarinfo.com

Are you unable to mount EDB (Exchange Database) database file on the MS Exchange Server 2007 system that is being used in your organization? If yes, then there is a very prominent possibility that the EDB file is corrupt thereby disabling you from mounting it. In such cases, you should try to find out the exact cause of corruption and try to eradicate that issue. In case, nothing is succeeding then you should use a professional Exchange repair software to recover the trapped data.

Consider a similar situation in which you are unable to mount the database on MS Exchange Server 2007. The following error message is displayed:

“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, when you check the error log the following event is logged:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 486
Description: Information Store (3932) First Storage Group: An attempt to move the file “E:\Program Files\Exchsrvr\mdbdata\E00.log” to “E:\Program Files\Exchsrvr\mdbdata\E000080A.log” failed with system error 2 (0×00000002): “The system cannot find the file specified.” The move file operation will fail with error -1811 (0xfffff8ed).”

Cause:

You may have run the eseutil /p command on the damaged databases. This problem has occurred because the transaction log files were not removed during the process.

Resolution:

First of all, you should check whether eseutil was run on this system at all or not by performing the following steps:
1.Click Start | Run.
2.Enter ‘CMD’ in the ‘Run’ box and press ‘Enter’ key. The Command Prompt window will be displayed.
3.Enter the following command:
4.c:\program files\exchsrvr\bin\eseutil /mh “c:\program files\exchsrvr\mdbdata\name of Exchange database.edb”
5.Check the repair count field. If it is 0, then the eseutil /p command was not run. For a non-zero count, eseutil /p command was run on the database.
Now, you can transfer the transaction log files to another folder if the database is in a clean shutdown state. To check this condition, you should perform the following steps:
1.Click Start | Run and enter ‘cmd’ in the ‘Open’ box and click OK.
2.To check the private information store, enter the following command in the Command Prompt:
3.c:\program files\exchsrvr\bin>eseutil /mh “drive:\program files\exchsrvr\mdbdata\priv1.edb”
4.To check the public information store, enter the following command in the Command Prompt:
5.c:\program files\exchsrvr\bin>eseutil /mh “drive:\program files\exchsrvr\mdbdata\pub1.edb”
6.Analyze the consistency check results. If the database is consistent, then all the transaction log files are moved to the information store.
7.Transfer all the log files from the directories to a backup folder.
8.Now try to mount the database. It should run fine now.

In the event of still unable to mount the database, the only way of resolving this problem is to use a third-party MS Exchange repair software. These tools are highly interactive in nature that do not damage the EDB files while scanning them.

The best Exchange repair software among all the available tools is Stellar Phoenix Exchange Server Recovery that repairs corrupted EDB files integrated in MS Exchange Server 5.5, 2000, 2003, and 2007. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange Server repair tool is able to extract individual user mailbox in the form of separated PST files.

Microsoft Exchange Server provides you with an inbuilt tool, called Exchange System Manager to manage the Exchange Server operations. It is a narrowed MMC console, which is automatically installed during Exchange Server installation. It helps you to mount the Exchange Server database and makes it accessible by the users. However, under some situations, the database can not be mounted using Exchange System Manager and you run across database inaccessibility. This problem is usually caused by corruption of the EDB (Exchange Database) file or Information Store. It leads to data loss and requires Exchange Server repair to be sorted out.

For example, you may run across the below error message after you restore the Exchange Server database from online backup and then try to mount EDB file using the Exchange System Manager tool:

“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”

At the same time, you may see the following entries in application event log of Microsoft Exchange Server:

“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 619
Description:
Information Store (nnnn) Attempted to attach database
‘D:\Exchsrvr\MyStorageGroup\MyDatabase.edb’ but it is a database
restored from a backup set on which hard recovery was not started
or did not complete successfully.
For more information, click

http://search.support.microsoft.com/search/?adv=1.”

When this problem occurs, the database becomes inaccessible and you need MS Exchange repair to access your precious data.

Cause

You may encounter this problem due to any of the below reasons:

* The backup is not valid or Last Backup Set check box wasn’t selected while restoring the backup.

* The Exchange Server database or Information Store is damaged.

Solution

Try using the below methods to work around this behavior:

* Run hard recovery on the database using “eseutil /cc [backup file path]”

* Repair and restore the database using third-party Exchange repair software.

The applications offer easy and secure recovery with interactive user interface and read-only conduct. Such Exchange repair tools use high-end EDB scanning algorithms to ensure absolute recovery.
Stellar Phoenix Mailbox Exchange Recovery is the most efficient utility used to ensure absolute recovery of damaged EDB files. The Exchange Repair Tool works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores emails, contacts, notes, tasks, journals, attachments, and all other EDB file objects.

Are you having MS Exchange Server 2007 in your organization that is giving problems lately? Are you facing problems while mounting the public folder database? It could be possible because of not having sufficient privileges to mount the database. In such cases, you should check the specific options to obtain appropriate user rights. If the issue is not resolved that means the EDB (Exchange Database) file is corrupted, which is disabling you to mount it. In such cases, you should use a third-party MS Exchange repair software to perform Exchange Server repair.

Consider a scenario wherein you are using MS Exchange Server 2007. In this, you are trying to mount the public folder database but you are unable to do so. An error message is displayed in this regard, which is:

“Failed to mount database ‘Mailbox Database’

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

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

“Event ID 9519
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: date
Time: time
User: N/A
Computer: ServerName
Description: Error 0×80004005 starting database “First Storage Group\Mailbox Database” on the Microsoft Exchange Information Store.
For more information, click http://www.microsoft.com/contentredirect.asp.

Data: 0000: 46 61 69 6c 65 64 20 74 Failed t
0008: 6f 20 63 6f 6e 66 69 67 o config
0010: 75 72 65 20 4d 44 42 00 ure MDB.”

Also, when you try to log on to the system it freezes at the ‘Applying computer settings’ screen.

Cause:

There could be the following causes for this erroneous situation:

1.The DomainName\Exchange Servers group does not have the Manage auditing and security log user rights.
2.The EDB database file is corrupted.

Resolution:

To resolve this situation, you can perform either of the following methods:
1. Run Setup /PrepareAD: You should run the Setup /PrepareAD command using the Exchange Server CD to restore the Exchange Server configuration in the Active Directory.
2. Add the Exchange Servers group to the “Manage auditing and security log” policy: You should add the Exchange Servers group to the aforementioned policy. After this, you should restart the Microsoft Exchange Information Store service. The problem would be solved now.

However, if you still are facing the similar errors while mounting the public folder database then you should use a third-party Exchange repair software to repair the EDB database. Such Exchange repair tools are extremely safe to use that do not overwrite the existing EDB files while scanning it.

Stellar Phoenix Mailbox Exchange Recovery is an Exchange Server recovery software that is able to repair corrupted EDB files created in MS Exchange Server 5.5, 2000, 2003, and 2007. It repairs the EDB files and extracts the data in distinct PST files. This MS Exchange repair utility is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

MS Exchange Server is one of the two sides of the client-server application. It is extensively used in numerous organizations to successfully carry out corporate communications. Also, it is now accessible in both mobile- and Web-based browsers. The information of the each of the user is stored in an EDB (Exchange Database) file. In due course of time, the EDB file can get corrupt due to various reasons such as abrupt system shutdown, file system corruption, database header corruption, etc. In such cases, you should try to repair the Exchange Server. If you are not able to perform Exchange repair, then you should use an MS Exchange repair software to do the needful for you.

Consider a scenario wherein you are using MS Exchange Server 2007 Management Pack for Operations Manager, which is used to monitor the MS Windows Application Event logs. While working on the Transport database, you encounter the following error message:

“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 Server does not let you access your database. At this point, you have to verify the cause of this problem and perform Exchange repair by resolving it.

Cause:
The root cause of this erroneous situation is that the specified database in the error message is damaged, which is causing the MS Exchange database services to mount it.

Resolution:

To resolve this problem, you should perform either of the following methods:

1. Delete the database: You should delete the database in question along with the respective transaction logs. After the deletion, a new copy of the database with the transaction logs will be created automatically. However, you would not get the previous data in this case.

2. Repair the database: You should try to repair the database using the Eseutil /P utility on the corrupted database. After the database repair, restart the MS Exchange Transport service to ascertain whether the error has been resolved or not.

However, if the problem is still not resolved then you should use a third-party Exchange Server repair software to do the needful for you. Such Exchange repair tools are read-only in nature that possess fast yet sophisticated scanning algorithms to extract the EDB files in the form of distinct PST files.

Stellar Phoenix Mailbox Exchange Recovery is an MS Exchange repair software that is able to repair corrupted EDB files from all instances of logical corruption. It is specially designed to perform Exchange repair on MS Exchange Server 5.5, 2000, 2003, and 2007. This Exchange repair software is able to extract the EDB file into separate PST files for each user. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Information store is the most vital component of Microsoft Exchange. When the Exchange Server is hit by corruption issues, information store also gets affected. It is made up of four database files viz Priv1.edb, Priv1.stm, Pub1.edb and Pub1.stm. When corruption occurs either Prive1.edb or Pub1.edb falls prey to it. In event of corruption, an Exchange administrator can observe various symptoms including the MS Exchange Information Store service won’t start, or clients cannot send or retrieve e-mails or abrupt error messages. In order to isolate the issues, the administrator must use the updated backup copy of the database. However, if no backup is available, he should immediately switch to MS Exchange Repair solutions.

Consider a scenario, wherein, you, being the administrator, try to mount the mailbox store in Exchange System Manager, and receive the following error message:

“Unable to Mount the Mailbox Store with error c104173c The Information Store is Busy”

Cause

The above error indicates the possible corruption in one or both edb files (Priv1.edb or Pub1.edb) of information store.

Resolution

In order to troubleshoot the issue, you must perform the following Exchange Repair steps:

1. Run eseutil/mh command in order to determine if the database is consistent
2. If you get the following output ‘Clean Shutdown’ , move out all the log files from Exchsvrmbddata folder
3. But if you get ‘Dirty Shutdown’ as output, perform soft recovery by using eseutil/r
4. If database does not come to a consistent state, perform hard repair by using eseutil/p command.
5. If you use the above command, you may lose some Exchange Server data, including the messages that were contained in the log files that were not committed to the information store database. Therefore, it is a wise decision to use a third-party MS Exchange Repair application.

Such tools repair corrupt .edb files safely and employ improved scanning algorithms to recover inaccessible data in a hassle-free manner. Being-read only they do not modify the original content. Therefore, you can use them blindly and isolate the information store corruption issues efficiently.

Stellar Phoenix Mailbox Exchange Recovery is a powerful and reliable application which repairs corrupt .edb files and restores the mailboxes as individual PSTs. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, this Exchange repair software recovers all e-mail messages, notes, journals, tasks, contacts and other components.

When a Microsoft Exchange Server database is corrupt, it is directly reflected when you try to use or start Information Store service. Thus, if you are unable to start the service, one of the possible reasons can be database corruption. The further scenario illustrates one of such problems and then the possible MS Exchange Repair solutions to correct it.

Consider a case when you try to start Information Store service of Exchange Server and it doesn’t proceed as expected. In addition, you receive the below mentioned error message in system log or on screen:

“The Microsoft Exchange Information Store service terminated with service-specific error 4294966277.”

On examining the issue, when you view the Application Event log, the following entry is observed:

Event ID: 0
Source: ESE97
Type: Error
Category: Logging/Recovery

Description: MSExchangeIS ((451)) -1019

Event ID: 1120
Source: MSExchangeIS
Type Error
Category: General

Description: Error 0xfffffc05 initializing the Microsoft Exchange Server Information Store database.

The above symptoms indicate database corruption and thus when you run Eseutil repair utility, the following message is received:

“-1019 0xFFFFFC05 JET_errPageNotInitialized Repair Only: Read an unused page 4294966277”

Consequently, the corrupted database cannot be repaired.

Explanation

JET_errPageNotInitialized error typically indicates a blank page. But, if it occurs when starting the information store, this shows database page corruption. There can be several pages that cannot be initialized. So, Eseutil cannot repair this database.

User Action

Before troubleshooting the issue, you should determine the cause of the error. Generally, these problems are persistent and occur because of failing hardware. Implement the following actions to solve the problem:

Disable all anti-virus applications, file backup programs, and low-level access utilities
Run hardware diagnostics and check system log for hardware-related issues
Restore the database from your previous backup

At times, database backup is not available or exist in invalid state. In such situations, you should use an Exchange Repair Software. Designed to run powerful, yet safe, scanning algorithms, these utilities are competent to restore Exchange database contents, irrespective of the nature of corruption. Also, MS Exchange Repair utilities are easily operable because of their user-friendly design.

Stellar Phoenix Mailbox Exchange Recovery is a comprehensive exchange repair utility designed to retrieve Exchange database mailboxes as individual *.pst files. Supporting MS Exchange Server 2007, 2003, 2000, and 5.5, this Exchange Server Repair tool facilitates you to restore only the required mailboxes. In addition, it can also recover deleted mailboxes.

Information Store in MS Exchange Server database saves all the public folders and mailboxes. These Information Store components further include two files – priv.edb and priv.stm (in Mailbox Store), and pub.edb and pub.stm (in Public Folder). Corruption in either of the four files stops the Information Store service and leads to inaccessibility of all the data stored in the Exchange Server database. Few main causes for file corruption could be improper server shutdown, header corruption, anti-virus scanning, and malicious software like virus. To overcome file damage situations and access the data saved in MS Exchange database, you will need to repair using an inbuilt repair utility named ‘eseutil/p’. This utility, although successful in most cases, can fall short when the database is severely damaged. For such situations, the user is not left with any other option, but to search for a powerful Exchange Repair application.

To elaborate the above situation, consider a real-time scenario wherein you have a MS Exchange database of around 300 GB. The database (priv.edb file) gets corrupted and you also fail to roll back. To resolve file corruption, you run ‘eseutil/p’ utility. The repair process was successfully repairing the file, until it stopped and displayed the below error message:

“Assertion Failed: dPercentage >=0, file G:\ese97\src\eseutil\edbutil.cxx, line 563.”

After the above error message flashes on the screen, the repair process stops, resulting in complete inaccessibility of MS Exchange database. Additionally, the same error message appears every time you use ‘eseutil/p’ utility to repair the database.

Cause:

The root cause for ‘eseutil/p’ utility failure is severe corruption in priv.edb file.

Resolution:

To get past the above error message and to overcome ‘eseutil/p’ utility failure, you will need to follow the below mentioned steps:

1. Use a complete and valid backup to perform restoration of the database.

2. However, in situations where no backup exists or backup falls short in restoring required data, you will need to use a commercial Exchange Server Repair application. Such Exchange Server Repair tools use safe mechanism for repairing the database to maximum possible level. These tools can be used by any computer user, irrespective of its understanding about database repair.

Exchange Repair Software safely repairs MS Exchange database files (priv.edb and pub.edb) after every logical corruption scenario. The read-only MS Exchange Repair tool makes the original database intact. Supported by MS Exchange Server 5.5, 2000, 2003, and 2007, the tool is designed for Windows 7, Vista, XP, 2003, and 2000.

Microsoft Information Store is the core database that consists of both public folders and mailbox store. The store uses a transaction-based technology service to access all its data. To start this services, the user needs to type ’services.msc’ in ‘Run’, and then select ‘Microsoft Exchange Information Store’ service. While in most cases the service starts after you follow the above procedure, there are certain situations wherein the service fails to start. Such situations primarily occur when the Store gets corrupted or damaged. In most situations of Store corruption, the user receives an error message, that does not allow him/her to access the Store records. To overcome any Store corruption scenario and to access its data, the user needs to opt for a valid backup of the Store. However, the solution of restoring from backup fails if the user has not maintained any backup. In these situations, the user needs to repair the database using a commercial Exchange Repair application.

To illustrate the above scenario in detail, consider the below error message that appears when you try to access the records saved in the Information Store:

“Could not start Microsoft Information Service on local
computer, Error 1053: The service did not respond to the start or control
request in a timely fashion”

After the above error message pops up on the screen, the data saved in the Information Store becomes inaccessible.

Cause:

The above error message flashes only when the Information Store gets corrupted due to unexpected system shutdown, header damage, anti-virus scan, log file corruption, or virus attack.

Resolution:

To get past the above error message and to access the records saved in the Information Store, follow the below guidelines:

1. Repair the corrupted .edb file using an ‘eseutil/p’ inbuilt repair command.
2. If the command fails to repair, then restore the file from an updated backup.
3. If backup file is unavailable or corrupted, then use a third-party Exchange Server Repair application to repair the file. Such Exchange Repair applications use effective repair mechanisms to repair any logically damaged MS Exchange database.

MS Exchange Repair software is a comprehensive solution to repair .edb files created in MS Exchange Server 5.5, 2000, 2003, and 2007. The read-only Exchange Server Repair software keeps the original file intact. Compatible with Windows 7, Vista, XP, 2003, and 2000, the user-friendly application is easy-to-operate, and doesn’t require any prior technical knowledge to operate.

Sometimes, when you try to start MS Exchange Server database, you may come across an error message. Reasons for the occurrence of above error message could be lost/corrupt Exchange Server database files, network issues, and more. In most cases of error message occurrence, data saved in the database becomes inaccessible. An ideal alternative to access database in such situations is by restoring it from an updated backup. However, in case the backup is not available or fails to restore data, you need to opt for an effective Eseutil utility that repairs the database. But, there are situations, when the error message persists even after running the above utility. In such cases, the user needs to search for an effective third-party Exchange Server Repair utility to repair your database.

To illustrate the above situation, consider a practical case wherein your Exchange database gets corrupted and the server stops the recovery of the database:

“Error -1216 (JET_errAttachedDatabaseMismatch) ”

On viewing the event log, you encounter the underneath entry:

“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 0
Date: 4/24/2001
Time: 6:20:18 PM
User: N/A
Computer: EXCHANGE1
Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘D:\exchsrvr\mdbdata\PRIV2.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed)”

Cause:

The root cause for the occurrence of the above error message is replacement or deletion of critical files that are used to open and operate Exchange Server database.

Resolution:

To resolve the above error message and to access Exchange Server database, you will need to follow the below mentioned steps:

• Use Eseutil/P repair command to repair the database.
• If the command fails, restore the database from an adequate backup.
• In case of backup unavailability, use a commercial Exchange Server Repair application. An Exchange Repair utility ensures maximum edb repair of logically damaged MS Exchange database and restoration at user-specified location.

Exchange Repair Software is a powerful, yet easy to operate Exchange Repair application that is competent enough to repair any Exchange Server 5.5, 2000, 2003, and 2007 databases. The repair application recovers almost all EDB file objects, including e-mails, tasks, notes, attachments, and appointments. It can be installed on Windows 7, Vista, XP, 2003, and 2000.

Eseutil/p is an inbuilt repair utility of MS Exchange Server that repairs corrupted Exchange Server databases at both table and page level. While the repair utility proves successful in repairing most of the corrupted databases, there are certain situations wherein the command fails to repair a corrupt database. In such situations, it displays an error message. This happens when the database is severely damaged. Since the database cannot be repaired, it remains corrupt, and the data saved in it remains inaccessible. To access database in such situations, a user needs to restore database from a previous online backup. However, in the absence of an updated backup, a user needs to repair the database using a third-party Exchange Server Repair application.

For detailed explanation of the above problem, consider a practical case wherein your Exchange Server database gets corrupted. And, when you try to repair the database using Eseutil/p utility, you encounter:

“Operation terminated with error -1605 (JET_errKeyDuplicate, Illegal duplicate key) after xxx.xxx seconds.”

Data saved in the database becomes inaccessible after the above error message appears. Additionally, the same error message repeatedly occurs when you try to repair your database.

Cause:

The fundamental reason for the occurrence of the above error message is that the repair utility might rebuild B-trees incorrectly. This will change the complete metadata structure of the database, leaving it in a permanently non-repairable state.

Resolution:

To resolve the above error message and to access the records saved in the database, a user needs to obtain the latest service pack of MS Exchange Server 5.5 and perform repair. However, if the repair utility is unable to repair the database even after installing the service pack, then you need to opt for an advanced commercial Exchange Server Repair application.

An MS Exchange Repair software is a powerful utility specifically designed to repair MS Exchange database, that has become corrupted due to logical crash. The read only utility performs repair without making any change in the original database file.

Exchange Repair Tool provides absolute repair of Exchange Server 5.5, 2000, 2003, and 2007 after any logical crash. The repair tool recovers almost all objects of database, such as, emails, notes, appointments, tasks, and attachments. Designed for Windows 7, Vista, XP, 2003, and 2000, the Exchange Repair software comes with an interactive user interface.

A checksum error while creating a backup of MS Exchange database occurs when the checksum values in the page header do not match with the values returned by the ‘READ’ call. The reason for mismatch of the values is corruption of database due to anti-virus scanning, hard disk subsystem damage, and third-party programs. In such cases, the backup stops and the data saved in the database becomes inaccessible. To overcome such error messages and to access data, the user needs to restore database from online backup. However, in case, no online backup is available, then the user needs to opt for a commercial Exchange Repair application.

Consider a practical case, wherein you encounter the below error message while checking the progress of Veritas backup:

“Backup - \\FSNACORP\Microsoft Information Store\First Storage Group Access denied to  database Mailbox Store (FSNACORP). Database or database element is corrupt”

On checking the event viewer, you find the below event ID:

“Event ID:478 Source: ESE Information Store (4004) The streaming page read from the file "D:\Program  Files\Exchsrvr\mdbdata\priv1.stm" at offset 1267851264 (0x000000004b91e000) for 2445  (0x0000098d) bytes failed verification due to a page checksum mismatch.  The expected  checksum was 2928845483 (0xae92a2ab) and the actual checksum was 3806978948  (0xe2e9e384).  The read operation will fail with error -613 (0xfffffd9b).  If this  condition persists then please restore the database from a previous backup.”

Cause:

As described in the error message, Exchange database is corrupt.

Resolution:

To overcome the above error message:

1. Uninstall all the anti-viruses and third-party software.

2. Use a previous online backup to restore the information store.

3. Move all the mailboxes in database to a new server or mailbox store.

4. In case all the above measures fail to resolve your problem, you will have to repair the database using eseutil/p command. However, repairing the database using this command brings the database in unstable state. To avoid any such situation, it is recommended to repair your database using a third-party Exchange Server Repair application. Such MS Exchange Repair software ensure safe repair of corrupted databases without modifying the original database.

Exchange Server Repair Software is a safe EDB Repair application to repair logically damaged Exchange Server 5.5, 2000, 2003, and 2007 databases. The read only utility saves the mailboxes in a PST file format. It can be installed on Windows 7, Vista, XP, 2003, and 2000.

A Microsoft Exchange Server database can get corrupt owing to several reasons, the most common being hardware reasons. In some cases, database corruption may remain undetected until you run a utility like backup software. In such circumstances, a user needs to restore the database from backup or run some Exchange Server Repair measures.

For instance, when trying to perform backup of Microsoft Exchange Server 2000 SP3 public folder store or mailbox store, a user may have an unsuccessful backup procedure. So, each time when he attempts to do so, he may encounter error like:

“WARNING: Portions of “\Mailbox Store (MAIL)” cannot be read. The backed up data is corrupt or incomplete”

Additionally, the application log shows various entries, such as:

Event Type: Error
Event Source: NTBackup
Event Category: None
Event ID: 8012
Date: 13/09/2005
Time: 4:24:08 PM
User: N/A
Computer: MAIL
Description:
The ‘Microsoft Information Store’ returned ‘Error returned from an ESE
function call (d).
‘ from a call to ‘HrESEBackupClose()’ additional data ‘-’

Apart from the above event ID, other entries are event ID 217, 478, 215, and 222.

Cause

The above symptoms is most probably the outcome of Exchange database corruption that doesn’t allow you to backup the database.

Solution

In case of Exchange Database corruption, you can try solutions as given below:

• If you use Enterprise edition of Exchange Server, you can move all the mailboxes from corrupted store to a new one.

• In other cases, the best solution is to restore the database from backup and to replay the log files

• If you don’t have a suitable backup to restore, you can run eseutil /p repair utility to fix database corruption. Keep in mind to backup all the data prior to running this tool as chances are that your important data may get deleted.

• In case, none of the above methods works, you should opt for a third-party MS Exchange Repair utility. An Exchange Server Repair utility can run most effective and safe scanning algorithms to extract all user data from corrupted Exchange databases.

Exchange Repair Software is a professional utility created to repair corrupted or damaged Exchange databases and restore the mailboxes to a user-intended location. This MS Exchange Repair tool supports MS Exchange Server 2007, 2003, 2000, and 5.5 and also recovers deleted mailboxes. Another noticeable feature is its recoverability for STM data.

A Private Information Store (priv.edb) in Microsoft Exchange Server is a copy of data saved in the user mailboxes. Corruption in priv.edb file can occur due to improper server shutdown, log file corruption, virus attack, anti-virus scanning, or human mistakes. Once this file is corrupted, the user receives error message while accessing the database that further results in inaccessibility of stored records. To overcome such cases, the user needs to erase the corrupt priv.edb file and restore an updated file from an online backup. However, if the backup is inaccessible or deleted, then the user needs to opt for advanced third-party Exchange Server Repair software.

To explain the above issue, consider the below error message that appears when you try to access the data saved in your Private Information Store:

“ERROR: page 1004909 checksum failed ( 0×2f906db8 / 0xb0259cd4 )
ERROR: page 1004925 checksum failed ( 0xe2028fbd / 0×4bfa488c )
ERROR: page 1004910 returned page 1337544633
ERROR: page 1004926 returned page 870534172
ERROR: page 1004910 checksum failed ( 0xa0d54f36 / 0×66c8980e )
ERROR: page 1004926 checksum failed ( 0×35d1f641 / 0×8f9622cc )
…
1005074 pages seen
1001748 bad checksums
3324 uninitialized pages
1001748 wrong page numbers
62818 reads performed
3926 MB read
195 seconds taken
20 MB/second
197970362 milliseconds used
3151 milliseconds per read
54141 milliseconds for the slowest read
31 milliseconds for the fastest read
File: e:\exchsrvr\mdbdata\first storage group\priv1.STM
Checksum Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|-|-|-|-|-|-|-|-|-|-|
…
0 pages seen
0 bad checksums
0 uninitialized pages
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non
database file or corrupted db) after 196.109 seconds.”

Cause:

The above error message pops up only when the Private Information Store or your Exchange Server gets corrupted/damaged.

Resolution:

Below are some techniques that help you in resolving the above error message:

• Execute ESEUTIL/D command to defragment your database. This enables you to resolve minor corruption problems in your database.

• If the problem persists, then restore the database from a valid backup.

• If no backup is available, then you need to use a third-party Exchange Server Repair tool to repair your database. These Exchange Repair utilities can be used after any type of logical corruption situation.

MS Exchange Repair is a safe repair application that repairs databases without modifying or overwriting any data. The Exchange Repair tool is easy to understand and restores the recovered user mailboxes in individual PST files. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, the tool supports Windows 7, Vista, XP, 2003 and 2000.

One of the most important objects of Microsoft Exchange that saves all the database files and transaction logs is ‘Information Store’. This component, once corrupted, results in inaccessibility of all the data/information saved in database. Few most common reasons for the information store corruption are improper database shutdown, log file damage, and anti-virus scanning. An easy way to access the information store after its corruption is by using a complete backup. However, if the backup is unavailable or corrupted, then you need to search for an effective third-party Exchange Server Repair software.

As a practical case, you receive the underneath error messages while trying take a backup of your database files, using Veritas software:

“Information Store – is a corrupt file. This file cannot verify.”

On viewing the event log of your Exchange Server, you view the below error message:

“Source : ESE
Category : Database Page Cache
Event Id : 474
Description :
Information Store (2712) First Storage Group: The database page read from the file “E:\Exchange\mdbdata\priv1.edb” at offset 409464832 (0×000000001867f000) (database page 99966 (0×1867E)) for 4096 (0×00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3567500155055337822 (0×31824e7d5639715e) and the actual checksum
was 3711585678364162506 (0×338233827852b9ca). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.”

Resolution:

For complete resolution of the above error message and to access data, follow the below mentioned steps:

• Firstly, take a copy of your raw database and run ‘eseutil /p’ to perform repair.

• Now, take a backup of your repaired database and run ‘eseutil /d’ to defragment your database.

• Next, take a backup of your defragmented database and run ‘Isinteg -fix -test alltests’ to check the integrity.

• In case, you do not receive any error integrity checking, then run ntbackup on exchange server.

• Lastly, try complete backup information store using the Veritas software.

However, if the information store remains corrupted even after following the above steps and you are still not above to perform database backup, then you need to repair the information store by using an effective Exchange Server Repair. An Exchange Server Repair software incorporates high-end scanning methods to repair corrupt Exchange EDB file.

Exchange Repair Software is an efficient Exchange Repair application that repairs corrupt Exchange EDB file(s) created with Exchange Server 5.5, 2000, 2003, and 2007. With recovery of deleted mailboxes, the read-only software saves repaired files in a .PST file format.

New Microsoft 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: Recover Exchange User Profile with this amazing Exchange Recovery software