EDB Corruption After Attaching Mismatched Database Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles	Data Recovery RSS
EDB Corruption after Attaching Mismatched Database

When you start Microsoft Exchange Server database, you might come across Error -1216. This error shows that the Microsoft Exchange Server has concluded that that files in EDB (Exchange Server Database) file’s running set are lost or the files have been reinstated with different versions.

Author: Bob Luis

Article Tools:

In such situations, the EDB file may get damaged and you need to go for Exchange Server Recovery to sort out the issue. Error -1216 may be shown in the following format:
“Error -1216 (JET_errAttachedDatabaseMismatch)”.

This error can also be symbolized in the hexadecimal format as ‘0xfffffb40’. When you encounter this error, Microsoft Exchange Server aborts the soft recovery process on EDB file, prior to make some changes in the database that might prevent you to re-integrate the missing database files with data set.

When this error occurs, you should try restoring the missing database files. When such files are not available, use Eseutil tool to override the error and continue with Exchange Server Repair. When this error occurs, you might find the following entries in the application event log of Exchange Server:

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

This behavior of Exchange Server generally occurs when the assessment of header information in database and log files indicates that the replacement or deletion of some vital files has been done. If you run soft recovery, entire database might get damaged.

No matter what the cause of this issue is, the ultimate result would be the loss of your mission critical data. In such situations, Exchange Server Recovery is required to repair and restore damaged database. This is best possible using powerful and advanced third party tools, known as Exchange Server Repair software.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective tool to retrieve data from damaged Exchange Server. This software can repair and restore EDB files of Exchange Server 2003, 2000 and 5.5. It is compatible with Microsoft Windows 2003, XP and 2000.

About Author

Bob Luis is writing articles related to software like Exchange Recovery Software and MS Exchange repair software. His expertise extends too many different fields and blogs about many different topics and niches. Mailbox Exchange recovery and repair are the main focus of most of his sites.

For more information, visit: http://www.ms-exchange-server-recovery.com

Article Source: http://www.1888articles.com/author-bob-luis-22336.html

EDB Corruption after Attaching Mismatched Database