How to solve Error 939586631 in MS Exchange Server ?

Exchange Storage Group any corruption to the EDB file leads to data inaccessibility and creates unavoidable situations of using a backup. If it is not possible to restore from backup, you need to repair the corrupted database using Exchange inbuilt eseutil repair utility or a third-party Exchange Repair tool.

Cause Of the Error:

The Error - 939586631 particularly results when you run Eseutil /CC command using the incorrect file path pointing to Restore.env file.

Note: Eseutil /CC is the restore mode command, which is applied to run hard recovery on a database that has been restored from an online backup. Exchange Server creates Restore.env file while restoring from backup to control the hard recovery process.

Steps to solve the Exchange Error:

   1. Run Eseutil /CC command using the correct file path of Restore.env file.
   2. Check the database consistency. If it is inconsistent, you can use Eseutil /P and then Eseutil /D command for recovering the database.

Eseutil /P is the hard command that deletes the corrupted data, instead of repairing it. So, after using the command, you may find the database with lost pages and deleted information. For this reason, whenever you find your Exchange database in corrupt state, it is recommended to use a safe third party's EDB Repair Tool.

This Exchange EDB Repair application allows you to extract the contained user mailboxes and restore them at a safe location from a corrupted Exchange database. The tools are easy to install and require no prior technical skills to operate them. In any case of logical database corruption, these tools are superb.

Stellar Phoenix Mailbox Exchange Recovery is an advanced MS Exchange Repair software that repairs and restores corrupted Exchange databases. The Exchange Repair Tool extracts all user mailboxes in individual .pst files without modifying its contents and supports Exchange Server 5.5, 2000, 2003 and 2007.

Download the Most trusted free demo version of Exchange Repair Software for MS Exchange Server 5.5, 2000, 2003, 2007 and 2010 !

Troubleshooting the situation when the EDB file gets beyond 16 GB size in MS Exchange Server SP1

If you are using MS Exchange Server 2003 Service Pack 1 in your organization, then you should be mindful about its size and keep archiving the data. Because if you fail to do so, then the EDB (Exchange Database) file may soon cross its 16 GB limit, thereby making it unmountable and, also, corrupt. The Messaging Database (MDB) automatically stops functioning, and becomes unable to mount, when the mailbox reaches this 16 GB limit. But you need not worry as there are several methods that you can perform for Exchange recovery. But when these do not work, then you should surely use a third-party Exchange recovery software.

Consider a scenario in which you are unable to mount MS Exchange Server SP 1. When you check the event log, the following event IDs are logged in it:

“Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 1112
Description: The database "Mailbox Store (Server Name)" has reached the maximum allowed size. Attempting to unmount the database.
Event Type: Warning
Event Source: ESE
Event Category: Space Management
Event ID: 445
Description: Information Store (3160) The database D:\Program Files\Exchsrvr\MDBDATA\priv1.edb has reached its maximum size of 16383 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.”

Cause:

The most probable cause of this issue is that the size of the mailbox has increased 16 GB.

Resolution:

To resolve this issue, there are following methods that you can use to perform Exchange Server recovery and get the Exchange Server back on track:

You should try to upgrade to MS Exchange Server 2003 Service Pack 2 by downloading and installing the Service Pack 2. Restart the system after installing it.

If you are the system administrator in your organization, then you can employ the following steps:

 i.Increase the size limit of the database by 1 GB although temporarily.
 ii.Remove the content that you do not need or take a backup of such items.
 iii.Then, defragment the database to compact it to such an extent that it is under the specified limits of the database size.

You can use the Recovery Storage Group feature to mount the database in the recovery storage group. After that, use the Exmerge.exe tool to retrieve the inaccessible user mailboxes from the database.

If you are still unable to mount the system, then you ought to take desperate measures to recover the Exchange Server. For such cases, a third-party Microsoft Exchange recovery software proves to be the most handy resolution. Such Exchange recovery tools are so efficient and reliable that the databases remain untouched during the Exchange Server recovery.

The most trusted and recommended tool in this respect is Stellar Phoenix Exchange Server Recovery that extracts user mailboxes in the form of separate PST files from damaged EDB files. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange recovery software works on EDB files created for MS Exchange Server 5.5, 2000, 2003, and 2007.

For more visit at: http://www.ms-exchange-server-recovery.com/

How to tackle IIS metabase corruption while performing an in-place upgrade of Exchange 2000 server

Microsoft Exchange Server is a reliable messaging platform which enables an organization to simplify its administration, help protect its communications, and delight its users by providing greater mobility. The Exchange Server highly depends on Microsoft Internet Information Services (IIS) to connect over the Web. Thus, IIS must be running properly to keep e-mail communication flowing. At times, when you upgrade from an older version of Microsoft Exchange server to a newer version, you might experience IIS metabase corruption which doesn't let Exchange setup program to get completed. This situation can also be encountered if you have corrupt EDB files. In such situations, it becomes essential for you to implement appropriate Exchange Server recovery strategies.

Consider a scenario, wherein, you perform an in-place upgrade of Microsoft Exchange 2000 Server to Microsoft Exchange Server 2003, and the upgrade fails. Additionally, the following error messages are logged in the Exchange Server Setup Progress.log file:

"[15:52:34] - The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server. -- ID:62145 --
[15:52:34] Prerequisites for Microsoft Exchange Messaging and Collaboration Services failed: The component "Microsoft Exchange Messaging and Collaboration Services" cannot be assigned the action "Upgrade" because:
- The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server. "

The Exchange Server Setup Progress.log file is typically located in the root folder of the partition where your OS is installed

Cause

The above error message occurs if the Microsoft Internet Information Services (IIS) metabase has become corrupt or if metabase entries are missing. Another possible reason could be corrupt EDB database files.

Resolution

To resolve the issues, you must consider the following steps:

* Use Adsutil.vbs utility by running the following commands:
    cd \inetpub\adminscripts
    cscript adsutil.vbs enum_all
    If you receive the following error message, you must reinstall IIS and Exchange 2000 server
    -2147221020 (0x800401e4)
    Error trying to enum the object (GetObject failed)
* In order to address EDB corruption issues, you must consider using third-party Exchange recovery software.

Such tools are designed to perform thorough scan of corrupt EDB files and extract data from them. You can perform Exchange Server recovery on your own as they come equipped with a simple and graphical user interface.

Stellar Phoenix Mailbox Exchange Recovery is a powerful and reliable application which repairs corrupt .edb files and restores the mailboxes as individual PSTs. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, this Exchange recovery tool recovers all e-mail messages, notes, journals, tasks, contacts and other components.

for more info go here: http://www.ms-exchange-server-recovery.com/

Exchange Recovery Tool - Microsoft Exchange Server Recovery

Exchange Recovery Software

Stellar Phoenix Mailbox Exchange Recovery software is exchange database recovery tool which recovers all edb objects with inaccessible and deleted emails. The EDB recovery software uses advanced scanning algorithms and efficiently converts edb files to pst files that can be easily used with MS outlook.

EDB known as Exchange Database files used by MS Exchange Server to save all emails, attachments, images, contacts, calenders and task. These EDB files gets corrupt due to any of the following reasons:

- Jet errors
- Whole of your EDB file is damaged
- Hard Drive Crash physically
- EDB reaches its maximum limit
- Computer improper shutdown / Dirty shutdown
- Exchange server fails
- Virus attack
- Users Errors
- There are corrupted objects in the database


Some of the most common Exchange database errors due to which the edb file get corrupted and damaged:

• Unable to initialize DAO/Jet db engine
• Exchange Server Error 550
• JET_errInvalidDatabaseId -1010
• Corrupted header information
• Unable to initialize the Microsoft Exchange Information Store service.
• Deleted user mail boxes
• "JET_errRecordNotFound, the key was not found" ,
• "Jet_errRecordDeleted".
• JET_errFileInvalidType -1812
• Improper Exchange Server shutdowns
• JET_errDatabaseStreamingFileMismatch -540
• Duplicate Keys (Identifiers)
• Exchange Dirty Shutdown Errors
• JET_errBadDbSignature -531
• Error -528 initializing the Microsoft Exchange Server Information Store database.
• JET_errDatabaseDirtyShutdown -550
• Exchange Server Error Code 528
• JET_errInvalidDatabase -1028
• JET_errFileInvalidType -1812
• JET_errConsitentTimeMismatch -551
• JET_errDatabaseCorruptedNoRepair -1224
• All types of Jet Engine Errors
• 614. All future database updates will be rejected. Information Store (3420) Unable to rollback operation #65678740 on database C:\EXCHSRVR\mdbdata\priv1.edb.

This Exchange Rcovery Tool scans,repairs & restores the corrupted edb files and extracts all user's mail boxes from the exchange Server 5.5, 2000, 2003, 2007. Through this edb recovery software, all the recovered items can be saved at the user defined hard drive location.

How to Solve Logical Exchange Database Corruption Problem ?

In MS Exchange Server Logical corruption is a  common problem. It could occur due to corruption problems with the following components:

==> Information Store
==> Tables
==> Keys
==> Indexes
==> sometimes to whole database.

Logical corruption is more problematic as it is difficult to identify than the physical database corruption. The Server administrator and users are generally  do not aware of logical corruption incidence. Unluckily Exchange Server also have not any in-built utility to diagnose it.

Causes of Logical Database Corruption:

A) Deletion of Edb.log File
B) Write Back Cache:
C) Repairing EDB using Eseutil /p

Logical corruption in Exchange Server might also take place when you apply Eseutil /p command to perform jet level repair. It may cause loss of data and incompetent space used in database as the repair fixes the EDB by removing the corrupted data.

For the Identification of logical corruption, you need to regularly perform integrity check (Isinteg –fix) or inconsistency check (Eseutil /mh).

Due to logical database corruption, the ultimate result would be the inaccessible Exchange Server database and the loss of your valuable data. To access your valuable data it is very important to perform EDB recovery by using a third party exchange recovery tool like Stellar Phoenix Mailbox Exchange Recovery software, specifically designed to repair and restore your damaged or corrupted exchange database file.

Stellar Phoenix Mailbox exchange recovery tool is the robust EDB repair software, supports Microsoft Exchange Server 5.5, 2000, 2003 and 2007. It can recover deleted user mailboxes and all of the database objects like mails, attachments, calenders, folders and Tasks etc.

Solving Information Store Server Error in MS Exchange Server

Are you facing following error message on your screen?


“The Microsoft Exchange Information Store service returned service specific error 4294966274.”

Due to this Error you can't access your precious data like emails, contacts and notes etc from your Exchange Server as all user mailboxes will become out of your reach.

Causes of the Issue:

- Potential hardware issues
- Corruption issue in Transaction Log file
- EDB File Corrupted

Know How to Resolve it?

==> If problems is due to hardware issue, repair it.

==> If Transaction Log file is corrupted , restart Information Store Service.

==> If it is due to EDB file corruption, perform EDB Repair to solve the issue.

EDB Repair is possible with third party applications known as Stellar Phoenix Mailbox Exchange Recovery software. It perform Exchange Database repair in most of the situations of corrupt EDB file. This EDB Repair software, best ever made, uses advanced scanning algorithm which allows you to have easy and fast .EDB repair in three steps only.

This amazing EDB Repair Tool can repair and restore all of the user mailboxes with all objects including contacts, emails,file attachment, notes,calendar entries and many more. Stellar Phoenix Mailbox Exchange Recovery software supports all file versions of Exchange Server 2007, 2003, 2000 and 5.5.