At the time of starting or mounting the databases in Microsoft Exchange Server, users may encounter this error message:
"Error -1216 (JET_errAttachedDatabaseMismatch)"
Causes for the Occurrence:
• Some important files, that are required to work with Exchange Server database, are altered or deleted.
• Some network problems
• Lost or Damaged Exchange database files
What Event Log says?
On reading the event log, user may see the below mention similar message:
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 0
Date: 8/18/2013
Time: 5:10:23 PM
User: N/A
Computer: EXCHANGESVR
Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘C:\exchsrvr\mdbdata\PRIV1.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed)”
After encountering this error, e-mails and other important data stored in the database (.edb) file becomes inaccessible.
How to Fix Error -1216:
Here are some methods that you may use to fix the Exchange Server Error -1216:
• Run Eseutil repair tools, in-built command line utilities to repair and restore the corrupt Exchange databases.
• If these free built-in eseutil tools fail to fix the error, try to restore the databases from an updated and healthy backup.
• In case the updated backup is not available or you are not able to restore data due to any reason, use a third party Exchange Server Repair program. Such tools are developed with strong database analyzing algorithms to fix all kind of issues and make the database error free.
There are many third party applications available on the web. I would suggest downloading their trial version and checking whether it will work for you or not. Here is a most recommended Exchange database repair tool: http://www.recover-computerdata.com/exchange-server-recovery.html
This advance utility ensures maximum recovery of lost or damaged data from logically as well as physically damaged Exchange databases. It also allows users to mount the database directly to MS Exchange Server as well as to export Exchange mailboxes to PST files at user-specified location.
"Error -1216 (JET_errAttachedDatabaseMismatch)"
Causes for the Occurrence:
• Some important files, that are required to work with Exchange Server database, are altered or deleted.
• Some network problems
• Lost or Damaged Exchange database files
What Event Log says?
On reading the event log, user may see the below mention similar message:
“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 0
Date: 8/18/2013
Time: 5:10:23 PM
User: N/A
Computer: EXCHANGESVR
Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘C:\exchsrvr\mdbdata\PRIV1.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed)”
After encountering this error, e-mails and other important data stored in the database (.edb) file becomes inaccessible.
How to Fix Error -1216:
Here are some methods that you may use to fix the Exchange Server Error -1216:
• Run Eseutil repair tools, in-built command line utilities to repair and restore the corrupt Exchange databases.
• If these free built-in eseutil tools fail to fix the error, try to restore the databases from an updated and healthy backup.
• In case the updated backup is not available or you are not able to restore data due to any reason, use a third party Exchange Server Repair program. Such tools are developed with strong database analyzing algorithms to fix all kind of issues and make the database error free.
There are many third party applications available on the web. I would suggest downloading their trial version and checking whether it will work for you or not. Here is a most recommended Exchange database repair tool: http://www.recover-computerdata.com/exchange-server-recovery.html
This advance utility ensures maximum recovery of lost or damaged data from logically as well as physically damaged Exchange databases. It also allows users to mount the database directly to MS Exchange Server as well as to export Exchange mailboxes to PST files at user-specified location.
No comments:
Post a Comment