Blogs >> Technology >>
Bad Link Page Error and Information Store Corruption in Exchange Server
Is your Exchange Server delivering outgoing mails without attachments?
Are you unable to see attachments in your Exchange Server mailbox? Do
you encounter ESE (Extensible Storage Engine) errors while accessing
the EDB (Exchange Server Database) file? This behavior indicates
Exchange Server database corruption. You need to go for Exchange Server Recovery to get your database repaired, if an updated and complete backup is not in place.
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:
1. The transactions are not committed to the hard drive by Disk Caching and the Exchange Server is crashed or stopped responding.
2. Wrong log files are replayed while restoring the database.
3. Exchange Server hard drive is having logical problems, like operating system malfunction, virus infection, file system corruption, and more.
4. 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:
1. If your hard drive has logical problems, run ChkDsk utility to detect and fix hard drive related errors.
2. 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 Microsoft 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 Mailbox Recovery is the most advanced exchange recovery utility for assured recovery of damaged EDB file. The Exchange Recovery 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.
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:
1. The transactions are not committed to the hard drive by Disk Caching and the Exchange Server is crashed or stopped responding.
2. Wrong log files are replayed while restoring the database.
3. Exchange Server hard drive is having logical problems, like operating system malfunction, virus infection, file system corruption, and more.
4. 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:
1. If your hard drive has logical problems, run ChkDsk utility to detect and fix hard drive related errors.
2. 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 Microsoft 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 Mailbox Recovery is the most advanced exchange recovery utility for assured recovery of damaged EDB file. The Exchange Recovery 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.
|
|
