Article Content King

You are viewing: Error 1216 Logs when One or More Database Files are Inconsistent
By Axel Culver

Error 1216 Logs when One or More Database Files are Inconsistent

Articles - Computers - Data-Recovery - View Article



Publish this article

Exchange Server database files are the most important recovery elements, required to be rebuilt after information store crash. If you can successfully restore them from the last backup and all required transaction log files are available, you should replay them to get the database to the state that existed before the crash occurred. In case of any issues, eseutil repair utility can help, but can cause data loss. For safe database repair, use of Exchange Server Recovery software is recommended. These tools can diagnose and repair all database contents using advanced procedures.

For instance, you might observe that Exchange Server storage group stops unexpectedly. If this leaves few database files unavailable for the server, you encounter the below error marked in the Application event log:
"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."
The corresponding event is logged with Event ID '0'.
Cause
All or few database files of storage group are inconsistent.
Solution
You can check the database file consistency by running Eseutil /mh command. If you find any database inconsistent, you should apply these methods to recover:
  • Restore from backup. You can determine the logs required by executing eseutil /mh database_name | find /i "log required command. Play the log files, if available
  • Perform hard repair using eseutil /p command, followed by eseutil /d and isinteg -fix commands
  • If the database contains no important information, you can simply delete it and create a new one
  • Corrupted database files can be safely repaired using Exchange Recovery products. Exchange Server Recovery applications are powerful tools that employ high-end scanning algorithms to repair damaged Exchange databases and provide you interactive interface to work with.
Stellar Phoenix Mailbox Exchange Recovery is a fully-features Exchange Recovery tool to safely extract all the mailboxes from damaged databases created with Exchange Server 5.5, 2000 and 2003. It is a non-destructive Exchange Server Recovery product that can restore all objects including emails, email properties, tasks, drafts and more.
See All articles From Author

Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like Exchange Recovery Tool and Inbox Repair Tool for MS Outlook. He is a professional writer and have written many blogs, article, press releasing and content for many websites.

Article Source : http://www.articlecontentking.com

Tags: Exchange recovery software Exchange Server Recovery Exchange recovery Microsoft Exchange Recovery Exchange 2003 Recovery Exchange recovery tool Edb Recovery Exchange Mailbox recovery.

Word Count Appx. : 448 | Article Views 272 Published 14-11-2009


Related articles
Data Recovery
By: Russell Phillips | 05-11-2008
Memory storage has witnessed a technological revolution in the last few years, from the big sized floppy disks that allowed nothing over a mere megabyte of data to the gigabytes that we can easily store on a Flash today. (read entire article)
Boot Sector Corruption and File Loss Due to Power Off/Shutdown in Windows
By: Richard Dawson | 06-10-2009

Sometimes you may face boot sector corruption issues on a Windows NT-based operating system computer, if you've installed the operating system on a FAT file system formatted partition. In such situations, the computer might not start properly, when you (read entire article)

Hard Drive Recovery Is Not For the Faint of Heart
By: Tom Stabler | 29-06-2009
I went to work and during lunch I purchased a new hard drive. When I got home I told my wife that everything was under control. I installed the new hard drive and using my most recent backups (six months old) and the recovery disks, I was able to get & (read entire article)
How to Recover Data From a Failed Hard Drive
By: Stephen Drummonsy | 09-05-2010

This article will help you to recover hard drive data before it is too late.

(read entire article)
Logical Corruption and Bad Page Error in Exchange Server Database
By: Axel Culver | 25-10-2009

Logical corruption in Microsoft Exchange Server database (EDB) is very problematic and quite difficult to identify and repair than physical damage. The administrators and users are generally unaware of logical corruption to EDB file.

(read entire article)
Data Recovery and Your Computer
By: Clive Haman | 11-12-2009

Data recovery for your computer

(read entire article)
Easy way for removing duplicate Outlook contacts
By: mac nicolson | 04-10-2010

Contacts imported to PST file results in duplicity of contact information. But duplicate Outlook contacts are easy to remove from PST file using manual methods. Also, there is an efficient tool to remove duplicate contacts in much easier way.

(read entire article)
The Fix Computer Problems Virus Scan Guide
By: Bryon Zirker | 20-12-2009

Downsides to ineffective repairs and loading the OS new include having...

(read entire article)
How to Solve MAPI call "OpenMsgStore" failed Error?
By: Axel Culver | 30-12-2009

For Exchange Server, MAPI uses different interface methods. The OpenMsgStore is the method associated with IMAPISession interface that is used to open a message store.

(read entire article)