Archive for the ‘Solving Exchange Server Errors’ Category
EDB Corruption and Access Problems in Exchange Server
December 14th, 2009 | 
Author : At times when you try retrieving your data from MS Exchange Server, the process fails and you receive error message mentioned below:
Access denied to database Mailbox Store (SERVER2K3).
WARNING: “\\SERVER2K3\Microsoft Information Store\First Storage Group\Mailbox Store (SERVER2K3)” is a corrupt file.
This file cannot verify.
Database or database element is corrupt
This error message means that you might lose your important data and this condition is the result of one of the following reasons:
EDB Corruption When Defragmentation Fails
Microsoft Exchange Server runs a defragmentation process to eradicate the unused Storage space and rearrange Mailbox store and Public folders and stored data, so that it can become manageable. Eseutil utility is used for defragmentation of Exchange Server database. It scrutinizes the basic structure of the database and rearranges it to enhance the performance of the database.
Using Microsoft Exchange Mailbox Merge Program
Microsoft Exchange Server comes with an apprehensive tool known as Exchange Mailbox Merge tool aka Exmerge.exe. Exmerege.exe tool is used when you want to merge currently working Exchange Server mailbox database to another system’s Exchange Server mailbox database. Moreover, a lot of time is saved throughout the merger process using Exmerge.exe tool.
Exchange database corruption after using Exmerge.exe
Exmerge.exe utility is Microsoft Exchange Mailbox Merge Program. This particular utility helps in merging Exchange data with another Exchange Server mailbox. Database administrators extract the significant data from user mailboxes on the Exchange Server computer. After that they merge the extracted data to same mailboxes on another Exchange Server computer with the help of Exmerge.exe utility.
Exchange recovery in case of Page Checksum Mismatch
Microsoft Exchange Server includes the procedure to become aware about file level damage caused to its pages in Exchange database. Using ESEUTIL utility with /K switch, you can detect errors in databases at both the page level and the file level. If this wonderful utility results into errors, then it is sure that one or more pages of your database are corrupt.
The most common errors and symptoms that are associated with file-level damage to an Exchange database are as follows:
Knowing Exchange Server Corruption and Exchange Recovery
Exchange database administrators can experience Exchange database failure due to physical corruption or logical corruption. Logical corruption is more problematic than physical corruption and requires a lot of expertise to get back the database to a consistent state. Depending on the type of database corruption and symptoms, different tools and techniques are required to diagnose and solve the problem. Let us know more about Physical corruption and logical corruption of Exchange server database:
Posted in Solving Exchange Server Errors | 
Tags: edb repair, exchange server recovery, Kernel for Exchange Server | 
No Comments » 
