Microsoft Exchange Server is getting popular now days due to enhanced requirement of email communication using MS Outlook and MS Outlook Express. To cater the need of increasing email communication, Microsoft has provided a set of client-server architecture i.e. Outlook and Exchange Server using which organizations and home users keep communicating with their friends, colleagues, and relatives.
The prime reason behind the popularity of Exchange Server is its speed, security, and availability (does not get down easily). Although, Exchange Server has lots of features that go in its favor and make it popular amid users, there is a thing that sometimes create mountainous hurdle in front of Outlook users and IT administrators. Sometimes, Exchange Database gets damaged leading into inaccessibility of users’ mailboxes stored on Exchange server. This is a case when there is major corruption in Exchange Server but in case corruption is minor then issues like users are not able to send attachments with email occur.
Let us consider a practical scenario in which you are trying to send an attachment – a small attachment to your colleague but you are not able to send an email with attachment. However, email without attachment is getting delivered successfully. When you are trying to send the email with attachment, you get the following error message:
“The operation failed.”
Now, just by viewing the above error message, you cannot just make it sure about the reason behind this. To get the exact reason behind the aforementioned error, you explore the Application Event Log of Exchange Server and get the following information listed in the event log:
Source: ESErnCategory: Database CorruptionrnType: ErrorrnEvent ID: 447rnUser: N/ArnComputer: XXXXXrnDescription: Information
Store (2624) A bad page link (error -338) has been detected in a B-Tree (Object Id: 2283, Pgno Root: 213598) of database E:\Exchsrvr\MDBDATA\priv1.edb (3253654 => 3304833, 3253654).
By viewing the Category section in the Event log, you come to know that Exchange Server database has been damaged demanding
Exchange Recovery. Here, you might be thinking that if Exchange database has been damaged then how the user is able to send email without attachment. The user shall not be able to deliver any kind of email. You are right with your perspective about database damage but as discussed above EDB corruption can be major or minor.
In case of major corruption, users cannot access their mailboxes on Exchange Server leading into halt in the communication process. But, in case of minor corruption, issues as described above in this article occur. Now, when you know that database has been damaged, you have to repair EDB file in order to restart email communication.
Kernel for Exchange Recovery enables IT administrators to repair Exchange database file with full accuracy. The file so repaired using Exchange Recovery tool can be saved as .edb file or individual mailboxes can also be saved in .pst file. If you save the file in .edb format then you can directly mount it on Exchange Server to send email with attachment and if you save the file in .pst format then you can directly access the file with MS Outlook. Kernel for Exchange Recovery tool allows repairing EDB file created using Exchange Server 2010, 2007, 2003, 2000, 5.5, and 5.0.