Microsoft Exchange Recovery Tool

Creating backup of Exchange Server database is a very common practice for database administrators. It helps them in restoring the database if any kind of data loss, corruption or other errors occur. But sometimes, after restoring your database from backup, you may find it difficult to access data from it.
One such scenario occurs when you try to start directory server in Exchange Server after restoring from backup. When you try to do this, you may encounter the following error message:
“Error 1067. The process terminated unexpectedly.”
Along with this error message, the following event entries might appear in the Application Even Log:
Event ID: 124
Source: ESE97
Description: MSExchangeDS ((1432 ) ) Unable to read the log header.
Error -530.
Event ID: 1196
Source: MSExchangeDS
Description: Couldn’t recover the restored Microsoft Exchange Server
database (EDB). Cannot continue. Error c8000212.
After this error message, you can not access anything from your Exchange Server database and may fall in need of Exchange Server recovery.
Reason of this issue
This problem generally occurs when Edb.log file, which is created while performing restoration from backup, interfaces with recovery process. It occurs on recovery server.
Due to this problem, the recovery process could not be completed successfully and you might face this behavior of Exchange Server. It cause complete inaccessibility of Exchange Server database.
Work around
To fix this problem, manually delete the existing data from the Dsadata folder before starting restore operation from the backup. It will delete Edb.log file.
Though, it could fix the issue, but it is not a safe method. Deleting Edb.log file might introduce severe errors in the Exchange Server database and may corrupt it.
EDB corruption is the worst scenario for a database user and it might put him/her in need of exchange server repair. Exchange Server repair can easily be carried out using Exchange Server recovery software.
Stellar Phoenix Mailbox Exchange Recovery software is the best ever made Exchange Server repair software to work around all the corruption issues. Using this Exchange Server recovery software, you can perform easy, quick and absolute Exchange Server repair. Phoenix Exchange Server Repair is applicable to all the Exchange Server file versions.

“Error -1216 (JET_errAttachedDatabaseMismatch)”
It is the most common Jet error in Microsoft Exchange Server. Error -1216 shows that the Exchange Server has determined that the files in Exchange Server database’s running set are lost or they have been reinstated with the different file versions.
Error -1216 could also be symbolized hexadecimally as ‘0xfffffb40’. When the error takes place, the Exchange Server aborts the soft recovery of EDB file before doing some changes to database, which may prevent re-integration of missing database files with data set.
When this error takes place, you should attempt to restore the missing database files. When these files are not available, you could use Eseutil for overriding the error and go on with software EDB recovery.
Error -1216 is caused when the comparison of header information in database and the log files shows that the removal or replacement of some critical files has been done. This error message may cause data loss, if the administrator run the soft recovery.

Grounds of the trouble

This problem occurs due to the inconsistency of the database, which might occur due to unexpected shut down of the Exchange Server or the Storage Group service has been stopped improperly. You may find the following entries in the Application Event Log, when the Exchange Server was stopped abnormally:
“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). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.
Nevertheless the cause of this issue, the database inconsistency will ultimately cause EDB corruption and finally the data loss. In such circumstances, you need to perform Exchange Server recovery to recover your lost data. It is feasible using good EDB repair software such as Stellar Phoenix Mailbox Exchange Recovery.
Phoenix Exchange Server repair is extremely powerful EDB recovery product to handle EDB corruption scenarios. It can perform Exchange Server recovery for all of the EDB repair objects including emails, notes, contacts and so forth. Phoenix Exchange Server repair is applicable to all file versions of Microsoft Exchange Server including Exchange 5.5, 2000, and 2003.

Microsoft Exchange Server runs a defragmentation process to rearrange the mailbox store and public folders and stored data more competently, eradicating unused storage space.
You could use Eseutil utility for defragmenting the Exchange Server database. It examines the basic structure of the database and rearrange them. It is required for better performance of the database.
Sometimes when you defragment the database, the process fails half-way though. After the process gets halted, you get a temporary file of Priv1.edb. When you rename this file, it gets disappeared. In such situations, the Mailbox store gets corrupted and you can not mount it. In this case, when you use the Eseutil /MS (to dump the space usage), the operation gets terminated with the following error message:
“Error -2211 (JET_errSLVHeaderCorrupted, SLV file header contains invalid
information)”
After getting this corruption error message, when you use Eseutil /P to repair the database, you will get the further error message stating:
“Checking database integrity. Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 1.912 seconds.”
This behavior results into the inaccessible Exchange Server database. You can not retrieve even a single bit of data from the database and you may fall in the grave situations of data loss.

Cause

As stated in the above error message, this problem takes place due to damaged Exchange Server database. The database corruption could be the possible result of unexpected system shutdown, virus attack, oversized EDB file and so forth.
It does not matter what the reason of data loss is. The only thing which matter is how to retrieve your precious data? The answer of this question is Exchange Server recovery.
Exchange recovery is the process of repairing the damaged database with the help of EDB recovery software and restore it. EDB recovery software are easy to use tools, which help you in all cases of EDB corruption and can recover all of the EDB objects.
Stellar Phoenix Mailbox Exchange Recovery is the most advanced Exchange Server repair software. It supports EDB repair from Exchange Server 5.5, 2000, and 2003. It systematically scans the entire database and ultimately gives you fruitful results of Exchange Server recovery.

MTA or Message Transfer Agent is the e-mail dealing system in Exchange environment. This sends, receives and delivers mails between servers. Also, this proves valuable for addressing and routing information. But, in few of the cases, the service may fail to start with the following error message:

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

Network administrator is experiencing problems with MTA and so, as recommended, if you run MTACHECK to know if the MTA is corrupted or got crashed, another error message may flash out, stating:

“Database contains serious errors and cannot be automatically repaired.”

The application event log is also helpful in getting the descriptive information about the Exchange Server problem. So here you get Event IDs like 2127, 2152, 2155, 2219 and 2187, which directly or indirectly points towards Exchange database corruption as of the Exchange server recovery failure, object accessing errors, failure in reading database and so on.

Exchange database is corrupt and hence is inaccessible. However, you can try out the registry editing way and then specify the correct path to the MTA database files. So locate the following registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Database Path

Type the correct path to MTA database files in Value data box by double clicking the entry. Verify the correct location for the MTA Run directory by locating and

double clicking the following registry.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Run Directory

If you still don’t find Exchange database accessible, this is a sure corruption case which needs correct scanning and hence Exchange server repair to cure. EDB repair is the process, applicable through third party software which have the read-only conduct, interactive interface and great EDB recovery abilities to help the users.

Be sure to have Exchange server recovery through the trusted and reputed source as an insufficient one will bring damages to the database.

Stellar Phoenix Mailbox Exchange Recovery is the most powerful utility to scan and repair the corrupted Exchange database with the efficient scanning EDB repair algorithms. Easy to use and safe to repair, this Exchange server repair application is found to be compatible with Exchange server 5.5, 2000 and 2003.

This EDB repair tool is meant for all the database objects including e-mails, notes, journal, tasks, appointments and others.

Stellar Data Recovery , a leading provider of data recovery software and service, today announced the immediate update for its popular Exchange Server recovery software- Stellar Phoenix Mailbox Exchange Recovery. With the capability to quickly and easily repair and restore all EDB objects, this software is helpful for the affected users.

The new version of Phoenix EDB recovery can also be installed and used on 64-bit computer as well as 32-bit. It is the best method for EDB recovery, helping to reduce downtime and cost of lost productivity.

The new file version has an interactive user interface and performs smooth EDB recovery without demanding any prior and sound technical knowledge. This EDB repair software has a set of powerful features which include:

Ø Can be used with both 32-bit and 64-bit computers

Ø Recovers email addresses from Active Directory storage

Ø Stores recovered file in PST format

Ø Compatible with Windows 2000 / XP / 2003

Ø Recovers notes, contacts, tasks and appointments

Ø Supports Microsoft Exchange Server 5.5, 2000 and 2003

For in-depth knowledge of the product, please visit http://www.ms-exchange-server-recovery.com/ . You can download and use free demo version of this EDB recovery software from Stellar’s website.

About Stellar Data Recovery

Stellar offers technology-driven data recovery software and service to help users recover their precious data. Stellar’s data recovery, email recovery, file recovery software are available for all system and application software. With more than 15 years of wealthy experience, company has over 1,000,000 satisfied customers all across the globe.

When you attempt to start “Information Store Server” of your Exchange Server, you may receive the following error message:

“The Microsoft Exchange Information Store service returned service specific error 4294966274.”
After this exasperating error message, the below given entries are engendered in the Event log:
Event ID: 31
Source: EDB
Type: Error
Category: Logging/Recovery
Description: MSExchangeIS (313). Unable to read the log header. Error -1022.

Event ID: 1120
Source: MSExchangeIS
Type: Error
Category: General
Description: Error -1022 initializing the Microsoft Exchange Server Information Store database.
After this trouble, you won’t be able to access anything from your Exchange Server. All of your mailboxes will become out of your reach.
Grounds of the trouble
There are three following possible reasons of this grave trouble:
Corrupt Microsoft Exchange Server Transaction Log file
Potential hardware issues
Corrupt Exchange Server Database (EDB) file
Regardless the cause of the trouble, the final result is the inaccessibility of your precious data thus resulting into data loss.

Resolution
According to the problems, there are three basic solutions:
If problem is due to Exchange Server Transaction Log file corruption, restart Information Store Service.
If it is due to hardware, repair it.
If the problem is due to EDB corruption, perform Exchange Server Recovery.
Exchange Server Recovery is possible with third party applications known as EDB recovery software. EDB recovery software perform Exchange Server repair is most of the situations of EDB corruption.

Stellar Phoenix Mailbox Exchange Recovery software is the best ever made and the most influential Exchange Server recovery software which allows you to have easy and fast EDB repair.

This outstanding EDB recovery software can repair and restore all of the Exchange Server objects including emails, notes, contacts, calendar entries and many alike. You can have Exchange Server Repair for all file versions of Exchange Server including Exchange Server 5.5, 2000, and 2003.