The common reasons of EDB (Exchange DataBase) file corruption are improper system shutdown due to operating system malfunction, system crash, and hardware failure or power outage. If Exchange Server’s Information Store Service gets terminated inappropriately, the EDB file may get corrupt and become inaccessible. This behavior makes all your critical data inaccessible and result as serious data loss. You need to go for EDB Recovery tools to solve this issue.
When you try to start Microsoft Exchange Server, you might encounter any of the below given symptoms:
è The Exchange Server Information Store Service might not start and you might get the following error:
”1067 The information store terminated abnormally”
è While performing online fragmentation, following event is logged into the Application Event Log of Exchange Server:
Date: date Source: ESE
Time: time Category: (12)
Type: Error Event ID: 447
User: N/A
Computer: Server name
Description: Information Store (information store name) A bad page link (error -327) has been detected in a B-Tree (Object Id: 19, Pgno Root: 113) of database E:\Program Files\Exchsrvr\mdbdata\priv1.edb (3440582 => 3443648, 3443232).
After this behavior of Microsoft Exchange Server, you can not mount the Information Store and thus EDB file becomes inaccessible. To fix this problem, you need to find out the cause of the problem and perform EDB Repair.
Grounds of this issue
This problem generally occurs due to Exchange Server database corruption after improper termination of Information Store Service. The Event ID 447 indicates that the logical structure of the EDB file is damaged and Microsoft Exchange Server can not recognize it.
The logical database corruption is generally undetectable by the database repair utilities like Eseutil. This problem appears only when you try to access the EDB database file.
Resolution
To solve this issue, you need to repair and restore the EDB file. It is best possible with the help of EDB Recovery software. These are powerful third party applications, which are capable of thoroughly scanning the entire EDB file and repair all its objects as emails, notes, contacts, journals, tasks and more.
These are user-friendly software as they come equipped with simple and interactive graphical interface. With read-only and non-destructive design, these EDB Repair tools are completely safe to use and perform absolute recovery.
Stellar Phoenix Mailbox Exchange Recovery is the foremost EDB Repair tool to revamp the corrupted EDB Files. It supports Exchange Server 2003, 2000 and 5.5. The software is compatible with Microsoft Windows XP, 2003 and 2000.


August 26th, 2009 at 12:34 am
tedemo…
Office 2003 Serialz …