process name (process id) nameOnline defragmentation of database ‘error code’ terminated prematurely after encountering unexpected error %5. The next time online defragmentation is started on this database, it will resume from the point of interruption.

Details
Product: Exchange
Event ID: 705
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) nameOnline defragmentation of database ‘error code’ terminated prematurely after encountering unexpected error %5. The next time online defragmentation is started on this database, it will resume from the point of interruption.
   
Explanation
Online defragmentation of a database ended prematurely after encountering an unexpected error. The next time online defragmentation is started on this database, it will resume from the point of interruption.

Event ID 705 generally indicates a problem with information store memory, or

a problem with the ESE (Jet) database itself. There is more than one known

cause for Event ID 705. Look at the Description section in Event ID 705,

and the Description section in other ESE events and MSExchangeIS events in the

application log. The following causes are the most

common for Event ID 705.

  • Look for Error -1069 (0xfffffbd3) = JET_errVersionStoreOutOfMemory in the

    description

    of Event ID 705, other ESE events, and MSExchangeIS events in the application

    log. If the version store runs

    out of memory, online defragmentation may not be able to complete.

  • Look for the following error in the description of ESE and MSExchange IS

    events in the application log: A bad page link (error -327 or error

    -338) has been detected in a B-Tree. Error -327 indicates

    JET_errBadPageLink and Error -338 indicates JET_errBadParentPageLink. A

    bad page link error indicates corruption in the database at the Jet level.

  • Look for the following error in the description of ESE and MSExchange IS

    events in the application log: Error -1018 or JET_errReadVerifyFailure which
    means a checksum error on a database page. -1018 errors also indicate

    database corruption on the Jet level, and are usually caused by hardware,

    controller, or file system level problems related to hardware.

   
User Action

Error -1069 (0xfffffbd3) = JET_errVersionStoreOutOfMemory in the description

of MSExchangeIS events in the application log. In this case, contact

Microsoft Product Support Services for help in troubleshooting this issue.

Here are resolution steps for Errors -327, -338 (table level corruption) and

-1018 (Jet database level corruption).

  1. Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before proceeding to the next step

  2. If the information store database is running, it is suggested that you ExMerge your data to .pst files, delete the database, create a blank database, and then ExMerge your databases to a blank database.

  3. If the database is running, you may also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.

  4. If the information store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the Application Log.

  5. If the information store database will not mount and there is no backup, the last resort is to repair the database using Eseutil /p and then repeatedly run Isinteg -fix until there are no longer any fixes reported. Then ExMerge out the data, create a blank store, and ExMerge the data back in.

Related:

Leave a Reply