Circular logging is a Exchange Server feature that implements recycling of logs. Microsoft Exchange Server writes the data to be committed to the database in transaction logs before actually writing it. If circular logging is enabled and four logs have been filled, it assumes that the first log as committed and thus, recycles the logs in order to save disk space. But it comes with a major flaw that prevents disaster recovery. If the database is corrupted while the feature is enabled, Exchange can only restore as far as the last backup is available. In case a suitable backup is unavailable, you are suggested to opt for Exchange Repair [http://www.ms-exchange-server-repair.com/] solutions that are powerful and safe too at repairing a corrupted Exchange database.
For example, you observe an unexpected shutdown with an Exchange database. After this, when you try to start it, an 'JET_errFileNotFound' error is displayed with a numerical value, such as 4294965485, -1811 or 0xfffff8ed. When you view the application event log, it shows events 1120 and 5000.
Cause
Events 1120 and 5000 generally show database inconsistency that prevent the database to start. You should see their description for the exact reason.
One probable cause could be that circular logging is enabled and error lies in checkpoint file, usually Edb.chk file. Since the circular logging is enabled, Exchange deletes the log files immediately after writing the data to the database, for which the information is traced out by Edb.chk file. Now, if a process blocks the Edb.chk file for a considerable period of time and prevents Exchange to update it, the file may get deleted before it could be updated. Thus, the checkpoint gets lost if the database suffers an unexpected stop. When you restart the server, the Edb.chk file points to a log file that doesn't exit anymore and hence, the database doesn't start.
Solution
If the exact cause is known and the errors are occurring only because of Edb.chk file, delete it and database service. But if the cause is different, the database might get damaged.
To achieve recovery, you should not use eseutil /r command without /is or /ds switches. This is because at this point, a new Edb.log file can get created and Exchange may try to repair using incorrect set of log files. Though you can delete the Edb.chk file, but the database remains corrupted.
For getting successful results from a corrupted Exchange database, it is suggested to use MS Exchange Repair products in case if no good backup is there. Exchange Repair tools are high-end and safe database repair utilities that can repair and restore a corrupted Exchange database.
Stellar Phoenix Mailbox Exchange Recovery is a fully-competent tool to perform systematic database repair of damaged Exchange files created with Exchange Server 5.5, 2000 and 2003. It is a reliable Exchange Server Repair tool that extracts all user mailboxes by converting them into individual Outlook usable.pst files. The tool can recover all email messages, notes, journals, tasks and other objects.
For example, you observe an unexpected shutdown with an Exchange database. After this, when you try to start it, an 'JET_errFileNotFound' error is displayed with a numerical value, such as 4294965485, -1811 or 0xfffff8ed. When you view the application event log, it shows events 1120 and 5000.
Cause
Events 1120 and 5000 generally show database inconsistency that prevent the database to start. You should see their description for the exact reason.
One probable cause could be that circular logging is enabled and error lies in checkpoint file, usually Edb.chk file. Since the circular logging is enabled, Exchange deletes the log files immediately after writing the data to the database, for which the information is traced out by Edb.chk file. Now, if a process blocks the Edb.chk file for a considerable period of time and prevents Exchange to update it, the file may get deleted before it could be updated. Thus, the checkpoint gets lost if the database suffers an unexpected stop. When you restart the server, the Edb.chk file points to a log file that doesn't exit anymore and hence, the database doesn't start.
Solution
If the exact cause is known and the errors are occurring only because of Edb.chk file, delete it and database service. But if the cause is different, the database might get damaged.
To achieve recovery, you should not use eseutil /r command without /is or /ds switches. This is because at this point, a new Edb.log file can get created and Exchange may try to repair using incorrect set of log files. Though you can delete the Edb.chk file, but the database remains corrupted.
For getting successful results from a corrupted Exchange database, it is suggested to use MS Exchange Repair products in case if no good backup is there. Exchange Repair tools are high-end and safe database repair utilities that can repair and restore a corrupted Exchange database.
Stellar Phoenix Mailbox Exchange Recovery is a fully-competent tool to perform systematic database repair of damaged Exchange files created with Exchange Server 5.5, 2000 and 2003. It is a reliable Exchange Server Repair tool that extracts all user mailboxes by converting them into individual Outlook usable.pst files. The tool can recover all email messages, notes, journals, tasks and other objects.