Eseutil

LET OP VOLGENDE ACTIES OP EIGEN VERANDWOORDING !!!!

Het volgende probleem :Exchange mail Store kan niet meer gestart worden.

 Exchange 2003

  • controleer de exchange mail store file : Eseutil.exe /mh  "[drive]:ExchsrvrMDBData[storage group][mail store]MAILSTOREFILE.edb" (Pas pad aan naar eigenomgeving)
  • Indien er dan in beeld komt dat er een State: "Dirty Shutdown" is geweest, dan is er de mogelijkheid de database te repareren.
  • Voer een reparatie uit op het database bestand : Eseutil.exe /p "D:ExchsrvrMDBData[storage group][mail store]MAILSTOREFILE.edb" (DIt kan enige tijd duren)
  • De mail store kan nu weer gestart worden.

 

 

Resutaten van controle.

File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,11
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,11
     DB Signature: Create time:12/16/2007 10:57:25 Rand:6667201 Computer:
         cbDbPage: 4096
           dbtime: 129298116 (0x7b4eec4)
            State: Dirty Shutdown
     Log Required: 3-3 (0x3-0x3)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 84447
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
 Old Repair Count: 0
  Last Consistent: (0x3,4FC,7B)  06/21/2008 22:46:58
      Last Attach: (0x3,517,9B)  06/21/2008 22:47:23
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 3
    Log Signature: Create time:06/21/2008 22:27:04 Rand:7041571 Computer:
       OS Version: (5.2.3790 SP 2)

Previous Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

       ECC Fix Success Count: none
   Old ECC Fix Success Count: none
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: none
Old bad Checksum Error Count: none

Operation completed successfully in 3.0 seconds.

Resutaten van een repair :

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode…
        Database: D:ExchsrvrMDBData[storage group][mail store]MAILSTOREFILE.edb
  Streaming File: D:ExchsrvrMDBData[storage group][mail store]MAILSTOREFILE.STM
  Temp. Database: TEMPREPAIR5676.EDB

Checking database integrity.

The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.

To ensure the database is up-to-date please use the 'Recovery' operation.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|

Rebuilding MSysObjectsShadow from MSysObjects.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
          ……………………………………………

Checking the database.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
          ……………………………………………

Scanning the database.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
          ……………………………………………

Repairing damaged tables.

                     Scanning Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |—-|—-|—-|—-|—-|—-|—-|—-|—-|—-|
          ……………………………………………

Repair completed. Database corruption has been repaired!

Note:
  It is recommended that you immediately perform a full backup
  of this database. If you restore a backup made before the
  repair, the database will be rolled back to the state
  it was in at the time of that backup.

 

Operation completed successfully with 595 (JET_wrnDatabaseRepaired, Database cor
ruption has been repaired) after 244.109 seconds.

Leave a Reply