Discussion Locked

Exchange server database corruption

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,

Our exchange server got the following application event log:

Source: ESE
Category: Database Corruption
Type: Error
EventID: 447
User: N/A
Computer: VOYAGER

Description:
Information Store (2624) A bad page link (error -338) has been detected in a B-Tree (ObjectId: 2283, PgnoRoot: 213598) of database E:\Exchsrvr\MDBDATA\priv1.edb (3253654 => 3304833, 3253654).

Right we can still send plain text email using OUTLOOK, but attachments can't be sent, OUTLOOK will say "The operation failed".

The interesting thing is, attachments can be sent and received without problems if using web access: http://ip/exchange, instead of OUTLOOK.

Any input would be appreciated. Already stuck here for 4 days. Reboot didn't solve the problem, by the way.

Thanks!
max

3 replies

by jz_nj

Ok. Restore works. We had a Symantec backup for D and E drives 3 weeks ago. I used ExMerge to export the emails for all users during those 3 weeks and then restored both drives. After restore is done, merge the exported .pst files to every user's mailbox. This way, only a few email with attachments were lost. Everything is back to normal now.

The trick is, we not only need to restore E drive which contains priv1.edb, but need to restore D drive which contains transcation logs. Both need to be consistent with each other.

Using eseutil might damage the whole page and make it unusable any more, if it's attachment table, then it's not accessible any more, even if using web access. So I didn't take the risk. Restoration is the best way.

Thanks for reply.

This discussion is closed to new replies.