How To Solve Database Could Not Be Upgraded To Version 3.2 In Exchange Server Error? Article

	1888 Articles Home \| Computer Articles \| Data Recovery Articles \| Windows Articles	Data Recovery RSS
How to Solve Database could not be upgraded to version 3.2 in Exchange Server Error?

Microsoft Exchange Server users often upgrade the existing application version to achieve better performance, speed, and features. Since the process directly interacts with the database, you may sometimes observe the process failing because of database corruption, however, there may be other reasons as well.

Author: Axel Culver

Article Tools:

The database may fail to mount and access. If a valid backup is available, you can recover from such situations by restoring from it, otherwise, it is suggested to use EDB Repair tools to repair the database.

For instance, consider a situation when you use Exchange Server 5.5 and upgrade it to Exchange Server 2000. After this, when you try to mount the Private store of Exchange, it fails and gives an error message, similar to below:

“Database "First Storage Group\Private Information Store (NTSRV01)" could not be upgraded to version 3.2. Error 0xfffff9bb.”

This error is associated with event ID 1187 in application event log of Exchange Server.

Cause

The mentioned error indicates that the Setup program has been unable to upgrade the Exchange database in question. It cannot upgrade the database to the specified version. This may occur if:

1. The database in effect is not included in upgrade sequence and is incompatible with the current Microsoft Exchange version.

2. The database is corrupt.

Solution

You should first analyze the error text and try these solutions to recover from this problem:

1. Make sure that the running MS Exchange version is compatible with that of database you are trying to mount. If not, you should try to mount it on a different server installed with required Exchange version.

2. To check if the database is actually corrupted, you should examine the application log for associated events. If it is, restore the database from backup or run eseutil repair utilities. For safe database repair, you are suggested to use third-party Exchange Server Repair software.

3. Sometimes, the described error may result because of failed upgrade, so you should try to upgrade it again.

The EDB Repair Software are commercial products designed to scan and repair corrupted Exchange databases. These utilities provide an interactive interface and are safe to use.

This EDB Repair Tool is a safe and powerful tool that repairs and restores corrupted Exchange database and extracts all mailboxes in individual *.pst files. The advanced Repair EDB utility supports Exchange Server 5.5, 2000, and 2003. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

For More Information: http://www.edb-repair.com

About Author

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

Article Source: http://www.1888articles.com/author-axel-culver-22336.html

How to Solve Database could not be upgraded to version 3.2 in Exchange Server Error?