Exchange Server Forums

Win 2K Exchange server database corruption

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Information Stores >> Win 2K Exchange server database corruption

Page: [1]

Message

<< Older Topic Newer Topic >>

Win 2K Exchange server database corruption - 28.Apr.2005 10:30:00 PM

madmax

Posts: 1
Joined: 28.Apr.2005
From: austin, tx
Status: offline

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 now 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

Post #: 1

Featured Links*

RE: Win 2K Exchange server database corruption - 29.Apr.2005 12:52:00 PM

marcn

Posts: 23
Joined: 5.Aug.2004
From: Dallas, Tx
Status: offline

You need to run isinteg. Dismount the database and run the following command from the exchsrvr\bin folder:

isinteg -fix -s servername -test alltests

where servername is your exchange server. Once this is complete mount the store back up and test.

(in reply to madmax)

Post #: 2

RE: Win 2K Exchange server database corruption - 1.Jan.2012 9:33:08 AM

Ellinor

Posts: 105
Joined: 24.Oct.2011
Status: offline

The bad page link error -338 is occurs due to the corruption in parent database and it could be solved by using any of the following methods:

I) Restore the damaged database from the last online backup, if that is available and valid.
II) Create a new mailbox and move all likely mailboxes into a the new mailbox
III) Use esesuitl /r (soft recovery) or eseutil /p (hard recovery) tool to repair the corrupted database. You are recommended to backup your database before using the methods.

If the Exchange database still could not be repaired, you require to use a third party appliction. The best known tool for this purpose is:recover-computerdata.com/exchange-server-recovery.html . This advanced Exchange server recovery software will definitely repair and recover the corrupted database file. This tool is very easy for you to use and to repair the damaged .edb files without harming the original data. It supports Exchange Server 5.5, 2000, 2003, 2007 and 2010 versions.

(in reply to madmax)

Post #: 3