For better understanding of the subject, consider, you as an Exchange Server administrator, are not aware of the fact that resetting the log sequence is necessary, and, you suddenly observe that the Information Store has stopped functioning or is not working correctly for no apparent reason. Additionally, when you view the application log, you receive the below mentioned log:

Event ID: 125
Event Source: ESE97
Event Type: Error
Description:
MSExchangeIS () Unable to create the log. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -519.

Further, when you try to start the Information Store, the following event entry is received in the application log:

Event ID: 7024
Event Source: Service Control Manager
Event Type: Error
Description:
The Microsoft Exchange Information Store service terminated with service-specific error 4294966786.

Thus Information Store is not accessible by any means.

Cause

As mentioned earlier, the above behavior can result if the log file name sequence of Information Store transaction logs has reached the maximum value of Edbfffff.log.

Solution

You can implement any of the applicable methods to isolate the given issue:

1. Check for an offline backup. If present, use it to restore affected Information Store databases
2. If no suitable backup is available, perform hard repair on databases. For this, you need to run eseutil /p, eseutil /d, and isinteg utilities. But keep in mind to backup your database first, as hard repair can delete important pages from your databases.
3. Use a third-party Exchange Recovery Software to repair and restore corrupted Information Store databases. These Exchange Server Recovery software are more effective and safe than Exchange Server repair utilities.

Exchange Recovery Tool is a reliable utility that repairs corrupted Exchange Server databases and restores their mailboxes as PST files to a secure location, which is specified by the user. This Exchange Recovery software supports MS Exchange Server 2007, 2003, 2000, and 5.5.

Corruption of IIS metabase and Exchange Server database is a very serious concern. It can cause several Exchange Server vulnerabilities and make Exchange-related services unusable. In case of metabase corruption, you may encounter the below error message:

“[15:52:34] – The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server. — ID:62145 –
[15:52:34] Prerequisites for Microsoft Exchange Messaging and Collaboration Services failed: The component ‘Microsoft Exchange Messaging and Collaboration Services’ cannot be assigned the action ‘Upgrade’ because:- The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server.”

The above error, in particular, occurs due to missing metabase entries. If various users perform transactions after metabase corruption, the EDB file may encounter several inconsistency issues. In such situations, to bring your Exchange Server in working state, you need to fix this behavior using Microsoft Exchange Recovery Tool.

Resolution

You can use Adsutil.vbs, an inbuilt utility of Microsoft Exchange Server, to locate metabase objects. However, if you encounter the following error while using Adsutil.vbs tool, you have to reinstall Internet Information Service and Microsoft Exchange Server:

“-2147221020 (0×800401e4)
Error trying to enum the object (GetObject failed)”

Although, reinstalling the Exchange Server and IIS may fix this problem, but it can not repair the corrupted Exchange Server database. In order to repair and restore the damaged EDB file, you need to use third-party Exchange Recovery Software.

The applications are particularly designed to carry out systematic scan of entire EDB file (using advanced scanning mechanisms) and to extract all damaged and inaccessible objects. They enable you to perform Exchange Recovery on your own, as they have simple and self-descriptive graphical user interface.

Exchange Mailbox Recovery software repairs damaged EDB file and restores all user mailboxes as individual PST files. The Exchange Database Recovery software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all EDB file objects, such as emails, notes, contacts, tasks, journals, appointments, and attachments.

In a practical scenario, you may see the below even log entries in the Application Event Log of Exchange Server:

“Date: date Source: ESE
Time: time Category: Database Corruption
Type: Error Event ID: 447
User: N/A
Computer: Server name
Description: Information Store (nnnn) A bad page link (error -338) has been detected in a
B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database e:\Program
Files\exchsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).”

The above problem may render your database completely inaccessible. You cannot access your precious emails, notes, contacts, tasks, journal, calendar entries, and other mailbox items. In order to gain access of your data, it is essential to identify the actual cause of this issue and perform Microsoft Exchange Recovery by sorting it out.

Grounds of the issue:

This behavior may occur due to the following possible causes:

• The transactions are not committed to the hard drive by Disk Caching and the Exchange Server is crashed or stopped responding.
• Wrong log files are replayed while restoring the database.
• Exchange Server hard drive is having logical problems, like operating system malfunction, virus infection, file system corruption, and more.
• The database is corrupted due to improper system shutdown, virus infection, application crash, and other such reasons.

Resolution

In order to work around this issue, go through the below steps:

• If your hard drive has logical problems, run ChkDsk utility to detect and fix hard drive related errors.
• In case of database corruption and other database related issues, run DBCC CHECKDB.

However, if the database corruption cannot be fixed by DBCC CHECKDB due to high extent of damage, you need to use third-party Exchange Recovery Software. They work in most of the database corruption situations.

The Exchange Recovery Tools methodically scan entire database and restore all of its inaccessible and damaged components. With read-only conduct and simple graphical user interface, they are totally safe and easy to use.

Exchange Recovery is the most advanced utility for assured recovery of damaged EDB file. The software is able to restore all EDB file objects including emails, notes, contacts, tasks, schedules, attachments, and more. It is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

To depict the probable events, let’s take a related scenario of an Exchange Server 2003 user. When he runs a backup utility to copy the Exchange database, the operation halts with an error that reads:

“Database was not found and could not be backed up. Please make sure database exists and is mounted.”

The logs also consist of errors such as:

“Store_Name is a corrupt file. This file cannot verify.”

Or

“Access is denied. Access denied to database Mailbox Store.”

On exploring the application event log, it shows error -1018.

Cause

The root cause of the above behavior is corruption of Exchange mailbox store, most likely due to hardware issues. These errors cause checksum errors in database pages.

Solution

To resolve the problem:

1. You need to run system hardware diagnostics to find the root cause and then isolate the related issues.
2. User can create a new mailbox store and move the mailboxes from the corrupted store, to correct the database problems.
3. You can also try repairing the corrupted database using Eseutil/p repair utility. However, this command is often unrecommended because it deletes the corrupted database pages and can cause important data to delete.
4. And, for safe database repair, use an Exchange Recovery Tool. Designed to run safe scanning procedures, these Microsoft Exchange Server Recovery software can repair corrupted database and extract valuable data.

Exchange Recovery Software is a professional exchange repair tool built for fixing corruption with Exchange databases created with MS Exchange Server 2007, 2003, 2000, and 5.5. The software recovers deleted mailboxes and includes various advanced options. Compatible with Windows 7, Vista, XP, 2003, and 2000, this Exchange Server Recovery Tool extracts mailboxes in separate *.pst files.

SEO Results

7285b4aa8b33415aa5a6e087d46826c5