Exchange Database Repair

This blog describes how to change the location of the message tracking log files in MS Exchange Server 2003. Tracking log position is by default fixed. I.e. when message tracking is enabled on a MS Exchange Server 2003 computer, the tracking logs are written to the following default location: C:\Program Files\Exchsrvr\ServerName.log Here, C:\Program Files\Exchsrvr represents the folder where Exchange Server 2003 is installed and ServerName is the host name of the Exchange Server computer. The size of the message tracking logs increases with increasing email messages and this affects the function of the particular Exchange Server computer in your environment. Because of this increase, you may want to change the location of the message tracking logs. In order to change the location of message tracking logs in Exchange 2003, perform the following steps: Start the Exchange System Manager tool. Expand Administrative Groups, expand your administrative group, expand Servers, right-click your server, and then click Properties. On the General tab, click Change. Type the new path of the message tracking logs, and then click OK. Click OK. If there is corruption in MS Exchange Server user mailboxes .EDB, then you can take help of Kernel for Repair Exchange Database software for repairing corrupted or damaged .EDB database file. Software successfully restores the user mailboxes from corrupt .EDB files to new working .PST files.

The .edb file of Microsoft Exchange Server is not away from flaws. It can be damaged anytime due to physical and logical reasons. Once the database file is damaged, its users need to face data loss. Here, in this article, we tell you how the system administrator can save users from data loss. Following steps help to understand the process of repairing the damaged .edb file:

1. Download the Exchange Database Repair software: The very first step towards the repairing of .edb file is to download the Exchange database repair software. One can search over Google to find the tool.

2. Install the Repair Exchange Database software: Once the software is downloaded, install the software on the computer where the damaged .edb file is available. To install the software, the administrator should follow the on screen instructions.

3. Execute the Repair Exchange Database software: After the software is successfully installed, browse the damaged .edb file. As soon as the damaged .edb file is browsed, the software starts repairing the damaged Exchange database file. After repairing the file, you are prompted to save the file into .pst format on your computer.

4. Save the .pst file: Once the .edb file is repaired and converted into .pst file, you have to save them on your computer. Save the files on your computer’s hard disk.

After saving the files on your computer, you can access them with the supported version of MS Outlook. The Exchange database repair software supports all versions of MS Exchange Server and MS Outlook.

Exchange Server database might get corrupt for number of reasons including accidental system shutdown, corrupt log files, network errors, virus invasion etc. Due to which, the EDB database file might stop and fail to mount. You can try repairing the database using eseutil utility. Still, if the file doesn’t get repaired you are compelled to use a Exchange database repair utility to perform EDB repair. Consider a situation when you come across the following error message while working on MS Exchange Server:

“Database page read failed verification because of no page data.”

Further, it suggests you to move the existing database to a new hardware and gets logged as event 476 within the application event log. This message might occur due to database read operation failure. This error occurs with error 1019 and the reason behind the occurrence of the message might be:

• Specific database page has been reference within the database file is expected to be in use, but Exchange finds them to be empty or uninitialized.

• A page might fail its checksum test with error- 1018. But if the page number field is in use is 0×00000000, the checksum failed page will show -1019 error in place of former message

• EDB file is corrupt and therefore it maps some other pages into database which are not related to it

• Logical links between database pages are incorrect

Check your system for these hardware issues if the database corruption problem occurs repeatedly. Replace the hardware and upgrade your firmware or disk controller if required. In order to repair the corrupt database, you can run eseutil/p command, which is hard recovery option for performing Exchange database repair. Then execute eseutil /d and isinteg –fix commands to perform page-level recovery and deleting pages that it finds to be corrupt. If all this doesn’t works out for your, use Repair Exchange Database tool and repair your Exchange database file in minutes.

Exchange Server databases are designed by Microsoft to work ideally on block level file access via locally attached system. Placing the database on shared network raises chance of corruption and therefore EDB repair might be required. This is because of the reason that when this database is attempted to access using file-sharing protocols, there may be a few file system features that Exchange Server won’t support. However, Exchange 2000 and later versions might exhibit such unmounting issues with the database placed on networked devices.

Although there are some administrative interfaces for changing the database and transaction log file locations resisted by Exchange Server using the database over network. But if the user experiences errors allied to file location or path, then we suggest you to not force it to set some invalid location by playing with the registry. It is so suggested because in the starting, the database runs successfully, but the situation swaps due to heavy traffic or unreliable network. You might also face chances of Exchange database corruption and might receive the following error message:

“An absent, corrupted, or invalid registry entry was encountered. Reinstall Microsoft Exchange Server. [800FF324]”

This error message can be easily resolved and exchange database repair can be performed by redirecting the valid locations for database instead of recommended reinstallation. However, if you face database corruption with the network placed database, you can use repair exchange databases software.

Additionally, Exchange Server comes with in-built Eseutil utility which can be used to curb corruption. But if you don’t want to lose the data in the corrupt pages then look for some third party help. Exchange database repair software will help you retain the feature to impart safe procedure through this read-only conduct. They have this scanning power to offer Exchange Server repair for the corrupt EDB databases.