Exchange Database Fails to Mount (SBS 2011, Exchange 2010)

I cannot manage to get the database in an Exchange 2010 server to mount.  The system was working correctly until a power failure and the UPS shut the server down.  After restarting the server the database will not mount and several errors are reported in the event log.

I tried going into the EMC and mounting the DB with no success.

Should I run eseutil to fix corruption?

The system is SBS2011 and Exchange 2010

Please advise


--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database 'Mailbox Database'.

Mailbox Database
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)
. [Database: Mailbox Database, Server: Domain.local].

An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)
. [Database: Mailbox Database, Server: Domain.local]

An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)
. [Server: Domain.local]

MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)





--------------------------------------------------------
OK
--------------------------------------------------------



Log Name:      Application
Source:        ExchangeStoreDB
Date:          9/5/2012 10:29:22 AM
Event ID:      231
Task Category: Database recovery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Domain.local
Description:
At '9/5/2012 10:29:20 AM', the copy of database 'Mailbox Database' on this server encountered an error during the mount operation. For more information, consult the Event log on the server for "ExchangeStoreDb" or "MSExchangeRepl" events. The mount operation will be tried again automatically.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ExchangeStoreDB" />
    <EventID Qualifiers="49156">231</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-05T18:29:22.000000000Z" />
    <EventRecordID>317824</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Mailbox Database</Data>
    <Data>e3ccaeb4-ec90-464d-aded-5aa9f07746af</Data>
    <Data>Store</Data>
    <Data>GenericMountFailure</Data>
    <Data>Mailbox Database</Data>
    <Data>Store</Data>
    <Data>There is only one copy of this mailbox database (Mailbox Database). Automatic recovery is not available.</Data>
    <Data>9/5/2012 10:29:20 AM</Data>
  </EventData>
</Event>





Log Name:      Application
Source:        ExchangeStoreDB
Date:          9/5/2012 10:29:20 AM
Event ID:      240
Task Category: Database recovery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Domain.local
Description:
At '9/5/2012 10:29:20 AM', the active copy of database 'Mailbox Database' on this server detected a corrupted log file. The error returned by the recovery actions was "There is only one copy of this mailbox database (Mailbox Database). Automatic recovery is not available.". For more details, consult the event log on the server for other "MSExchangeRepl" and "ExchangeStoreDb" events.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ExchangeStoreDB" />
    <EventID Qualifiers="49156">240</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-05T18:29:20.000000000Z" />
    <EventRecordID>317818</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Mailbox Database</Data>
    <Data>e3ccaeb4-ec90-464d-aded-5aa9f07746af</Data>
    <Data>Ese</Data>
    <Data>RecoveryRedoLogCorruption</Data>
    <Data>Mailbox Database</Data>
    <Data>
    </Data>
    <Data>There is only one copy of this mailbox database (Mailbox Database). Automatic recovery is not available.</Data>
    <Data>9/5/2012 10:29:20 AM</Data>
    <Data>None</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>0</Data>
  </EventData>
</Event>




Log Name:      Application
Source:        ESE
Date:          9/5/2012 10:29:20 AM
Event ID:      465
Task Category: Logging/Recovery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Domain.local
Description:
Information Store (2584) Mailbox Database: Corruption was detected during soft recovery in logfile F:\Exchange Server\Mailbox Database\E00.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 128 (0x00000080). This logfile has been damaged and is unusable.

For more information, click http://www.microsoft.com/contentredirect.asp.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESE" />
    <EventID Qualifiers="0">465</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-05T18:29:20.000000000Z" />
    <EventRecordID>317815</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Information Store</Data>
    <Data>2584</Data>
    <Data>Mailbox Database: </Data>
    <Data>F:\Exchange Server\Mailbox Database\E00.log</Data>
    <Data>END</Data>
    <Data>128 (0x00000080)</Data>
  </EventData>
</Event>



Log Name:      Application
Source:        MSExchangeIS
Date:          9/5/2012 10:28:31 AM
Event ID:      9519
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Domain.local
Description:
While starting database Mailbox Database, the following error occurred: Log file is corrupt.  
Failed to configure MDB.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeIS" />
    <EventID Qualifiers="49158">9519</EventID>
    <Level>2</Level>
    <Task>6</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-09-05T18:28:31.000000000Z" />
    <EventRecordID>317801</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Log file is corrupt</Data>
    <Data>Mailbox Database</Data>
    <Data>Failed to configure MDB</Data>
    <Binary>5B444941475F4354585D00008E000000FFE8230000000000000280000000B7AC0010FE00000091EA40100F010480B7AC00100F01048091EA40100F010480B7AC00100F01048091EA40100F010480B7AC00100F01048091EA40100F010480B7AC00100F01048091EA40100F010480BD5F201000000000222740100BFEFFFFF17040100BFEFFFF130A40100BFEFFFFF31C40100BFEFFFF730D40100BFEFFFF</Binary>
  </EventData>
</Event>
TechAKAsked:
Who is Participating?
 
TechAKConnect With a Mentor Author Commented:
I ended up calling Dell and with the help of one of there MS Exchange Specialist was able to rename the last good log file E00.log and then was able to commit the logs and mount the database.
0
 
josephspreiCommented:
Yes try doing that.
I have had success many times before running the eseutil on the edb file.
Just make sure you have enough space on the harddrive, you need about double the space of the edb file.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Seems like issue with mounting Database ... hope the AV hasnt Quarantined the log file.

Also if still unable to mount the database check with the DB Status.
eseutil /mh "Location of .edb file"

- Rancy
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
TechAKAuthor Commented:
I ran eseutil /mh "DB Path\DB Name" and received the following. State: Dirty Shutdown


Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...
         Database: F:\Exchange Server\Mailbox Database\Mailbox Database.edb


DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x1f4cf74e
  Actual Checksum: 0x1f4cf74e

Fields:
        File Type: Database
         Checksum: 0x1f4cf74e
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,17
 Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
     DB Signature: Create time:02/05/2012 15:26:02 Rand:2510202 Computer:
         cbDbPage: 32768
           dbtime: 22666767 (0x159de0f)
            State: Dirty Shutdown
     Log Required: 25595-25595 (0x63fb-0x63fb)
    Log Committed: 0-25596 (0x0-0x63fc)
   Log Recovering: 25595 (0x63fb)
  GenMax Creation: 09/05/2012 07:02:46
         Shadowed: Yes
       Last Objid: 1804
     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: (0x63FA,8,1F)  09/05/2012 07:02:42
      Last Attach: (0x63FB,9,86)  09/05/2012 10:29:20
      Last Detach: (0x0,0,0)  00/00/1900 00:00:00
             Dbid: 1
    Log Signature: Create time:02/05/2012 15:25:59 Rand:2471006 Computer:
       OS Version: (6.1.7600 SP 0 NLS ffffffff.ffffffff)

Previous Full Backup:
        Log Gen: 24956-24976 (0x617c-0x6190) - OSSnapshot
           Mark: (0x6191,8,16)
           Mark: 08/30/2012 02:39:44

Previous Incremental Backup:
        Log Gen: 25407-25483 (0x633f-0x638b) - OSSnapshot
           Mark: (0x638C,8,16)
           Mark: 09/04/2012 06:01:10

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

Previous Differential 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

  Last checksum finish Date: 00/00/1900 00:00:00
Current checksum start Date: 00/00/1900 00:00:00
      Current checksum page: 0


Operation completed successfully in 0.78 seconds.
0
 
TechAKAuthor Commented:
I ran eseutil /r e00 /d and received the following.

F:\Exchange Server\Mailbox Database>eseutil /r e00 /d

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating RECOVERY mode...
    Logfile base name: e00
            Log files: <current directory>
         System files: <current directory>
   Database Directory: <current directory>

Performing soft recovery...
                      Restore Status (% complete)

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



Operation terminated with error -501 (JET_errLogFileCorrupt, Log file is corrupt
) after 0.343 seconds.

Is there anyway to fix this issue?
0
 
TechAKAuthor Commented:
I ran eseutil /ml e00 and received the following


F:\Exchange Server\Mailbox Database>eseutil /ml e00

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...

Verifying log files...
     Base name: e00

      Log file: F:\Exchange Server\Mailbox Database\E0000006374.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006375.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006376.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006377.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006378.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006379.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000637A.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000637B.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000637C.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000637D.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000637E.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000637F.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006380.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006381.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006382.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006383.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006384.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006385.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006386.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006387.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006388.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006389.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000638A.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000638B.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000638C.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000638D.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000638E.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000638F.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006390.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006391.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006392.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006393.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006394.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006395.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006396.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006397.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006398.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E0000006399.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000639A.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000639B.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000639C.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000639D.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000639E.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E000000639F.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A0.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A1.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A2.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A3.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A4.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A5.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063A9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063AA.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063AB.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063AC.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063AD.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063AE.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063AF.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B0.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B1.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B2.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B3.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B4.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B5.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063B9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063BA.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063BB.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063BC.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063BD.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063BE.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063BF.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C0.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C1.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C2.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C3.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C4.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C5.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063C9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063CA.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063CB.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063CC.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063CD.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063CE.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063CF.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D0.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D1.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D2.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D3.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D4.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D5.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063D9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063DA.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063DB.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063DC.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063DD.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063DE.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063DF.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E0.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E1.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E2.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E3.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E4.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E5.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EA.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EB.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EC.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063ED.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EE.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EF.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F0.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F1.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F2.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F3.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F4.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F5.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063FA.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063FB.log
                ERROR: Log damaged (unusable). Last Lgpos: (0x63fb,A,0). Error -
501.
      Log file: F:\Exchange Server\Mailbox Database\E00.log
                ERROR: Log damaged (unusable). Last Lgpos: (0x63fc,1C,1C5). Erro
r -501.

Operation terminated with error -501 (JET_errLogFileCorrupt, Log file is corrupt
) after 14.55 seconds.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
State: Dirty Shutdown
     Log Required: 25595-25595 (0x63fb-0x63fb)


eseutil /r e00 /d "Database location with .edb" /l "Location where we have the required log files"

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Only keep these logs and try with

      Log file: F:\Exchange Server\Mailbox Database\E00000063E6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063E9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EA.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EB.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EC.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063ED.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EE.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063EF.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F0.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F1.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F2.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F3.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F4.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F5.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F6.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F7.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F8.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063F9.log - OK
      Log file: F:\Exchange Server\Mailbox Database\E00000063FA.log - OK

eseutil /r e00 /d "Database location with .edb" /l "Location where we have the required log files" /a

- Rancy
0
 
TechAKAuthor Commented:
Why only keep 63E6 to 63FA?

What does the /a swith do?
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Why only keep 63E6 to 63FA? - cause the last log file is unusable so no sense keeping it there ... just few files to try and force replay and get the DB into Mounted.

If this doesnt help we might be best to restore from the Last backup and Repair this DB and get data from RDB.

Corruption was detected during soft recovery in the log file
http://technet.microsoft.com/en-us/library/hh343808(v=EXCHG.140).aspx
Somewhat similar for Unusable Logs as the condition is same that they cant be replayed into the DB
Use the Exchange Server Database Utilities (Eseutil.exe) tool with the /R and /A switches to recover a database that has missing log files

- Rancy
0
 
TechAKAuthor Commented:
I ran the following command
eseutil /r e00 /d "Mailbox Database.edb" /a
and received

F:\Exchange Server\Mailbox Database>eseutil /r e00 /d "Mailbox Database.edb" /a

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating RECOVERY mode...
    Logfile base name: e00
            Log files: <current directory>
         System files: <current directory>
   Database Directory: Mailbox Database.edb

Performing soft recovery...


        Recovery has indicated that there might be a lossy recovery option.  Run
 recovery with the /a argument.


Operation terminated with error -528 (JET_errMissingLogFile, Current log file mi
ssing) after 0.140 seconds.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
eseutil /r e00 /d "Mailbox Database.edb" /a - where is the /L ??
How many log files do you have in total ..... also be prepared for Restore.

- Rancy
0
 
TechAKAuthor Commented:
There are 138 log files in the directory

The log file are in the same directory as the DB

I used the /L switch and received the same result


Recovery has indicated that there might be a lossy recovery option.  Run
 recovery with the /a argument.

Operation terminated with error -528 (JET_errMissingLogFile, Current log file mi
ssing)
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Did you move the corrupted .log \ .chk and all other files just apart from the .edb and logs we discussed ?

- Rancy
0
 
Kernel_Recovery_ToolsCommented:
Check and Repair the database,
Check whether the database state is dirty or clean.
If database state is dirty you have to repair database first and it state is clean then you can go directly for mount the database.
May be database state is clean but some of log is creating issue, for that we have to check using chkdsk utility.


How to check the database:

Run eseutil /mh "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"

Look for the following in the output: State: Dirty Shutdown

2 Database is not properly shut down so it should be repiared first.

Before attempting any kind of repiar make sure you have backup of database.


To repairthe database, run the following command:

eseutil /p "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb"

3 Re-run the database check from Run eseutil /mh "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database.edb" and if all goes well, you should see this somewhere in the output: State: Clean Shutdown

 

You can try mounting the database. If it mounts, you are good to go, if it doesn't you have to check the logs:
Check and Repair the database logs

4 Check the exchange logs (don't forget to specify E00 - the starting sequence for the logs)

eseutil /ml "C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E00"

5 There will be a list of logs and depending on their state, you may get an error. (They should all say OK, if the logs are clean) Errors vary, but most likely it is a file corruption and needs a chkdsk to run.
if the database state is Clean Shutdown you can safely remove the logs.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I guess he played the trick to rename the last log files as E00.log and delete as soon as he ran soft recovery and let the ESE engine rebuild and mount the DB or bring it into clean shutdown. - if thats the same have played many a times but cant over remote :(

- Rancy
0
 
TechAKAuthor Commented:
Everyone was very helpful but an Exchange Specialist from Dell was able to get the DB mounted.<br /><br />Thanks to everyone
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.