Use Exchange Recovery tool for problematic Exchange Server database service
Posted on Feb 16 2011 at 04:48:02 AM in Software
Sometimes Exchange Server database service simply refuses write access to the Exchange Server database files or checkpoint files. When database service exhibits the same behavior, it makes all the data of Exchange Server database inaccessible and unusable. You lose your access of important data. Behind such peculiar behavior, you can find numerous issues. Well, such data loss situation can be handled by an updated backup. If backup falls short too weak, then try to use a third party Exchange recovery software.
Let us take an instance to depict the above stated problem. Suppose Exchange Server database service denies write access to the EDB or CHK file, and you will come across the below event ID's:
“Event Type: Error
Event Source: ESE97
Event Category: General
Event ID: 145
Time: 1:57:34 PM
Description: (1996) The database engine could not access the file called E:\exchsrvr\mdbdata\tmp.edb.”
“ Event Type: Error
Event Source: ESE97
Event Category: Logging/Recovery
Event ID: 158
Time: 4:40:20 PM
Description: MSExchangeIS (1628) Unable to write a shadowed header for file D:\exchsrvr\MDBDATA\edb.chk.
(Microsoft Exchange Server 5.5 error format. In Microsoft Exchange Server 4.0, the Event ID for this error is 61; in Microsoft Exchange Server 5.0, the Event ID is 63.)”
These event ID's do not occur each and every time. Such kind of behavior occurs when there are some issues in Exchange Server. Valuable data of the Exchange Server database cannot be accessed.
Some of the causes that are responsible for the occurrence of above error message are as follows:
a)File has been stolen by some other process, such as a virus checker. Access has been denied by backup process.
b)Occurrence of disk and controller failure.
c)Removal of the permissions from the folder where file has been kept.
d)Marked file as a read-only.
e)Deletion of file that is contained in the folder.
f)Corruption of Exchange Server database is one of the reason.
Above problem can be overcome easily by following methods:
i.If disk or controller failure occurs, then try to check the errors related to system log for I/O or drive errors.
ii.Use a suitable backup to restore permissions.
However, corruption of Exchange Server database file can be handled with a third party Exchange Server Recovery tools. Such third party tools easily perform Microsoft Exchange recovery effectively and efficiently. Valuable data of the Exchange Server database, such as contacts, attachments, journal, tasks, calendar entries can be easily recovered.
Stellar Exchange Server Recovery is a reliable tool used to perform MS Exchange recovery. It recovers data from the corrupt Exchange Server database. Additionally, it repairs Unicode formatted EDB files. It works well with operating systems, such as Windows 7, Vista, Server 2003, XP, and 2000. You can download a demo version of the software to recover exchange server data and check its overall functionalities.
About the Author:
The author of this article has a strong background in computer technology; She has been a technical writer and blogger for over 5 years. She is writing articles related to topics like Exchange Server Recovery and EDB PST Converter to repair and convert .edb to .pst file.