Clicky

Articlesalley.com - Articles Directory

Browse Articles | Submit an Article | Search Articles | Most Viewed Articles | Latest Articles | FAQ
Article Directory
Articles Area
Home Login / Register Get RSS Feeds Add Free Article Content Article Ratings Go Daddy Coupon Codes
Guidelines
Authors Publishers
Home | Computers | Data Recovery | Exchange Repair - Ti ...

Exchange Repair - Tips to Resolve Error -1216

Submitted by Axel and viewed 945 times
Total Word Count: 433  
Author Rating: NA

Rate this article Rate this article | Publisher Publisher | Print Print
Error message “Error -1216 (JET_errAttachedDatabaseMismatch) ” occurs due to replacement or deletion of critical files that are used to open and operate Exchange Server database
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 ncountered 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:

1.Use Eseutil/P repair command to repair the database.
2.If the command fails, restore the database from an adequate backup.
3.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 application that is competent enough to repair any Exchange Server 5.5, 2000, 2003, and 2007 databases. The MS Exchange 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.
ArticleSource: ArticlesAlley.com
Additional articles about Error -1216
About the author
Axel Culver has passion for writing technical article and right now writing articles related to Product like MS MS Exchange Repair Software and Microsoft Exchange Recovery software to repair & recover edb file.
Please Rate This Article

Number of ratings: 0
Rating: 0

© Copyright dd ArticlesAlley.com - All Rights Reserved Worldwide. About Us | Contact Us | Site Map | Exchange Links | Privacy Policy | Terms of Use