Error 0xfffff05b Post Applying Exchange Server 2000 Sp3 Or Later

A compressed NTFS partition can cause several problems

, if is made to store Information Store databases. Some of them are high CPU usage, delays when enumerating large NTFS directories and performance issues with many files. It can even corrupt the Information Store and prevent it from starting when it reaches to about 4 GB in size. Also, Exchange Server 2000 SP3 and Exchange Server 2003 do not support compressed Information Store. So, if you upgrade to any of these versions and store Information Store databases are stored on compressed NTFS partition, odds are that they might fail to mount. However, if the database are corrupted due to compression, you will need to restore them from backup or apply soft recovery commands. At times, when it doesn't work, you need a powerful Exchange Server Recovery solution to repair the corrupted databases.

Consider you upgrade Exchange Server 2000 SP2 or earlier to Exchange Server 2000 SP3 or later. After you install the upgrade, when you try to mount the Information Store databases, the operation fails. When you view the application log of Event Viewer, it shows error 0xfffff05b with Event IDs 505 o r 9519.

Cause

As discussed, this issue occurs when you apply Exchange Server SP3 or any later version to a compressed NTFS partition containing Information Store databases. These versions automatically decompress database files, which are equal to or smaller than 128 MB in size, but prevent them from starting if are of greater size.

Exchange Server database files require sector independence to achieve log-based recovery after any disaster. But if you compress these files, the condition is invalidated, which can corrupt them.

Solution

To solve the existing issue, following steps are recommended:

1.You should dismount all the Exchange databases

2.You need to decompress the root folder of Exchange databases and log files

3.You should defragment the databases and remount them

However, if the databases are corrupted because of NTFS compression, you need to restore them from backup or run Eseutil /r to perform soft recovery. Also, there are various Exchange Recovery products that can work for correcting database corruption. Exchange Server Recovery are high technology based tools that incorporate safe scanning algorithms to repair a damaged Exchange database.

Stellar Phoenix Mailbox Exchange Recovery is a fully-featured and secure tool to perform systematic repair of damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It is a comprehensive Exchange Recovery tool that extracts all user mailboxes by converting them into individual Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

by: axel culver

POST COMMENT

Resolving your Database May Be Corrupt Error Message Tips To Resolve mysql Server Has Gone Away Error Message Tips On Resolving A Virus Attack What Is Media Surface Contamination Usb Disk Files Recovery Combating The Developing Energy & Environmental Costs Of Data Centres Recover Lost Data From Canon Eos 50d Supported Memory Cards Pictures Lost From Ibm Microdrive Warning Message After Ms Sql Database Corruption Windows Xp Does Not Detect Hard Drive When Using A Boot Disk Data Recovery Solutions For Common Computer User Hard Drive Recovery To Resolve hard Disk Not Found Error Canadian Address Database Helps Immigrants Better Adapt To The Country