Resolving JET_errLVCorrupted Error in Exchange Server

Computers & TechnologyTechnology

  • Author Axel Culver
  • Published February 7, 2010
  • Word count 396

Microsoft Exchange Server database engine splits a column into several parts, when it finds it too large and thus, the Long-values (LVs) are created. These structures are stored in a different B-Tree (binary tree) of the associated table, each with a unique long-value ID. Each of these LVs has a specific header, called LVROOT, consisting of information, like reference count and length of LV. In some cases, this LVROOT can get overwritten (usually because of a defective B-split operation), which eventually results into corruption of LV. This can cause Information Store to stop, errors accessing LV and/or database corruption. To repair the database, you should restore from a suitable backup. If no valid backup is present, you need to apply an Exchange Repair solution.

To illustrate such problems, suppose you attempt to perform offline defragmentation of an Exchange database. But the operation fails with an error message as below:

"Operation terminated with error -1526 (JET_errLVCorrupted, Corruption encountered in long-value tree) after seconds"

Further, when you execute eseutil /g command to check the integrity of the database, it reports the database as corrupted.

Cause

The above error occurs due to corruption in LV tree. This can exist in conjunction with orphaned LVs.

Solution

You should first check for the backup. If present and valid, restore from it. In other case, you need to implement the given sequence of steps to solve this issue:

  1. Run eseutil /g with /v and /x parameters for detailed output and examine it for the cause (error, orphaned or corrupted)

  2. If the LVs are corrupted, you can run eseutil /p command. But make sure you backup the database first as this causes corrupted data to delete

  3. If the LVs are corrupted and orphaned both, you should execute eseutil /d to perform database defragmentation after the repair.

Eseutil /p is a hard command. So, for safe EDB Repair, you need to use a third-party database repair tool. An Exchange Server Repair tool uses intensive, yet safe, scanning algorithms to repair and restore a corrupted Exchange database, while providing an interactive user interface.

Stellar Phoenix Mailbox Exchange Recovery is an effective solution that repairs a corrupted Exchange database and restores it to a user-specified location. The safe Exchange Server Repair solution extracts all user mailboxes as individual .pst files. The tool supports Exchange Server 5.5, 2000, and 2003. It is compatible with Windows 7, Vista, XP, 2003, and 2000.

Axel Culver has passion for writing Technical article. He is right now writing articles related to Product like Exchange Repair tool and Exchange Server Repair Software. He is a professional writer and has written many blogs, article, press releasing and content for many websites.

Article source: https://articlebiz.com
This article has been viewed 1,345 times.

Rate article

Article comments

There are no posted comments.

Related articles