Showing posts with label exchange repair. Show all posts
Showing posts with label exchange repair. Show all posts

Monday, November 21, 2011

Bugged down by Exchange Server Database Corruption, Try EDB Repair Tool

End number of times Exchange Server users are bugged down by the corruption of database (.edb)file owing to several factors. While operating in an exchange server environment, it is imperative that the EDB files remain accessible at all times for MS Outlook users to work on their mailboxes and other Outlook components, such as emails, appointments, tasks, To-do lists, calendars, contacts and much more.

Though designed for high set features and flexibility, Exchange Servers succumb to corruption. Conventional causes of EDB file corruption are:

  • Dirty shutdown
  • Abnormal Outlook termination
  • Virus attack
  • EDB file header corruption
  • Hardware failure
  • JET engine error

A common error message encountered by MS Outlook users when trying to access their mailboxes at the time of a power outage or diry shutdown is:


“database was not shutdown cleanly (dirty shutdown)”

The first resort is the in-built Microsoft utility, such as ESEUTIL or ISINTEG. However, at times of severe corruption, these utilities fail to repair the .edb file. In such delicate situations, when your precious emails and Outlook items are completely inaccessible, seeking the aid of a third party Exchange Server Repair utility becomes exigent. The market is stuffed with multifarious EDB repair tools that efficiently repair and recover all the emails, attachments, calendar items, notes, contacts and other items from the corrupted EDB file.

An excellent and globally used EDB file repair tool is “Stellar Phoenix Exchange Server Recovery”. This utility is capable of recovering selected data from the corrupt EDB file and restores it in the form of separate PST files that can be imported into Outlook directly. Not only the present mailboxes and their items can be recovered, but even the lost or deleted emails can also be recovered using this tool.

A fair deal about the Exchange Server Repair software is that the demo version offers a preview of the items that are recoverable so that it is clear to the user, what he will get after purchasing the software. This utility is designed for high level of flexibility and supports Exchange Server Versions 5.5, 2000, 2003, 2007 and 2010.

The users have the option of saving a log report of Exchange recovery operation. The high level of compatibility of the software can be judged from the fact that it supports Windows XP, 2003, Vista and Windows 7 operating systems. User-friendliness and a highly interactive GUI is the icing on the cake. A free demo version of the software is available for download on the website.

Tuesday, August 31, 2010

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 !

download edb recovery

Tuesday, August 3, 2010

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.

Monday, August 2, 2010

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.

Tuesday, July 13, 2010

Exchange Server Error Codes

Exchange Error Messages Error Code Number Description



JET_wrnNyi -1 0xFFFFFFFF Not Yet Implemented 4294967295
JET_errSuccess - 0 0x00000000 Successful Operation
JET_errFileClose -102 0xFFFFFF9A Could not close DOS file 4294967194
JET_errRfsNotArmed -101 0xFFFFFF9B Resource Failure Simulator not initialized
JET_errRfsFailure -100 0xFFFFFF9C The Resource Failure Simulator failed
JET_errTooManyIO -105 0xFFFFFF97 System busy due to too many IOs 4294967191
ErrBFINoBufferAvailable -254 0xFFFFFF02 No buffer available for immediate use 4294967042
errBFIOutOfBatchIOBuffers -253 0xFFFFFF03 out of Batch I/O Buffers 4294967043
errBFIOutOfOLPs -252 0xFFFFFF04 out of OLPs 4294967044
errBFIPageCached -251 0xFFFFFF05 page already cached 4294967045
errBFLatchConflict -202 0xFFFFFF36 page latch conflict 4294967094
errBFIPageEvicted -250 0xFFFFFF06 page evicted from the cache 4294967046
errBFPageNotCached -201 0xFFFFFF37 page is not cached 4294967095
wrnBFCacheMiss -200 0x000000C8 page latch caused a cache miss 200
JET_errDatabaseBufferDependenciesCorrupted -255 0xFFFFFF01 The buffer dependencies were set improperly and there was a recovery failure 4294967041
wrnVERRCEMoved -275 0x00000113 RCE was moved instead of being cleaned 275
errBTMergeNotSynchronous -336 0xFFFFFEB0 Multiple threads attempting to perform merge/split on same page (likely OLD vs. RCEClean)
wrnBTShallowtree 335 0x0000014F BTree is only one or two levels deeps
JET_errNTSystemCallFailed -334 0xFFFFFEB2 A call to the operating system failed 4294966962
wrnBTMultipageOLC 333 0x0000014D needs multipage OLC operation 333
errSPOutOfOwnExtCacheSpace -332 0xFFFFFEB4 unable to make update to OwnExt tree since in-cursor space cache is depleted 4294966964
errSPOutOfAvailExtCacheSpace -331 0xFFFFFEB5 unable to make update to AvailExt tree since in-cursor space cache is depleted 4294966965
errBTOperNone -330 0xFFFFFEB6 Split with no accompanying
wrnBMCleanNullOp 329 0x00000149 BMClean returns this on encountering a page // deleted MaxKeyInPage [but there was no conflict]
JET_errBadBookmark -328 0xFFFFFEB8 bookmark has no corresponding address in database 4294966968
JET_errBadPageLink -327 0xFFFFFEB9 next/previous page link page does not point back to source 4294966969
errBMMaxKeyInPage -326 0xFFFFFEBA used by OLC to avoid cleanup of parent pages 4294966970
errDIRInPageFather -325 0xFFFFFEBB sridFather in page to free
JET_errKeyBoundary -324 0xFFFFFEBC Reached Key Boundary
JET_errPageBoundary -323 0xFFFFFEBD Reached Page Boundary
JET_errPreviousVersion -322 0xFFFFFEBE Version already existed. Recovery failure
JET_wrnRemainingVersions -321 0x00000141 The version store is still active
errNDNoItem -320 0xFFFFFEC0 Item not there
wrnNDDuplicateItem -319 0x0000013F Duplicated Item
errNDFirstItemNode -318 0xFFFFFEC2 First node of item list
errNDLastItemNode -317 0xFFFFFEC3 Last node of item list
errNDGreaterThanAllItems -316 0xFFFFFEC4 Greater than all items
errNDOutItemRange -315 0xFFFFFEC5 Item out of range
errNDOutSonRange -314 0xFFFFFEC6 Son out of range
wrnNDNotFoundInPage -314 0x0000013A for smart refresh
wrnNDFoundGreater -313 0x00000139 Found Greater
errNDNotFound -312 0xFFFFFEC8 Not found
wrnNDFoundLess 312 0x00000138 Found Less
errSPConflict -311 0xFFFFFEC9 Device extent being extended
wrnDIREmptyPage 310 0x00000136 Moved through empty page
errDIRNotSynchronous -309 0xFFFFFECB May have left critical section
errDIRFDP 308 0x00000134 On an FDP Node
errDIRTop -307 0xFFFFFECD Cannot go up
errDIRCannotSplit -306 0xFFFFFECE Cannot horizontally split FDP
errDIRNoShortCircuit -305 0xFFFFFECF No Short Circuit Avail
wrnBMConflict 304 0x00000130 conflict in BM Clean up
errPMTagsUsedUp -303 0xFFFFFED1 Tags used up
errPMRecDeleteded -302 0xFFFFFED2 Record deleted
errPMItagTooBig -301 0xFFFFFED3 Itag too big
errPMOutOfPageSpace -300 0xFFFFFED4 Out of page space

Are you facing any of the above ERROR, then see if  we can help!  Helpline No. 1-877-778-6087 - Stellar Information Systems Ltd., India's No. 1 Data Recovery Company