Exchange Store - Won't Mount, Repair Failed (DatabaseLogSetMismatch)

Posted on 2009-05-04
Last Modified: 2012-05-06
Hey Everyone,

Not quite sure what is happening... The server blue screened, and Exchange wouldn't mount when it came back up. Traced through the event log and tried to run a soft recovery, here is what it said - I've never seen this before. Any ideas?

Microsoft(R) Exchange Server Database Utilities
Version 6.5
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
    Logfile base name: E00
            Log files: C:\Program Files\Exchsrvr\MDBData
         System files: <current directory>

Performing soft recovery...

Operation terminated with error -539 (JET_errDatabaseLogSetMismatch, Database does not belong with the current set of log files) after 5.0 seconds.
Question by:ryanj1987
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5

Expert Comment

ID: 24301946
try to run eseutil /mh on the db. Is the db in clean or in dirty shutdown.
If it is in dirty shutdown, run eseutil /p on the database. After that remove all transaction log files out of the folder.
The db should mount. After that run eseutil /d on the db.
LVL 49

Expert Comment

ID: 24302046
As  a start try the following

COPY all the files (logs and db and all to another location)

delete all log files from the directory BUT the e00.log

so you should retain only

*.edb *.stm *.chk

Try mounting it again.

If you are lucky it will work.

If not you will have to perform hard recovery and ignore the logfiles

Author Comment

ID: 24302051
Yes, it was a dirty shutdown.

Ran what you requested, said it wasn't up to date (Naurally, dirty shutdown). Said I should only run Repair on a damaged or corrupted dB. Bypassed it, and this is what it had to say...

Operation terminated with error -4001 (JET_errFileIOBeyondEOF, a read was issued to a location beyond EOF (writes will expand the file)) after 65.344 seconds.

Should I continue with your steps, Tompi68?
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 24302060

I'm not too worried about the Log files, any incoming mail that wasn't committed can easily be resent using the Barracuda (I'll just issue a re-mail on anything > crash date / time). How do I go about doing that, if the first suggestion doesn't work?
LVL 49

Expert Comment

ID: 24302103
If it is a dirty shutdown and you do not have logfiles then you are left with 2 options

1) Restore from recent backup (i'd advise you to start with this one)
2) run hard recovery


Author Comment

ID: 24302122

Okay. I'll have my tech load tapes when he gets in (I'm far away from the server, a few hour drive at least). What's the down side to running a hard recovery on one set of the files? (I've made an 'Orignal' copy that I can restore to). Is it just the loss of the inbound mail? How do I start a hard recovery?
LVL 49

Expert Comment

ID: 24302166
hard recovery will take more time than a restore if your database is big, in both cases (restore and hard recovery) you will loose new emails without logfiles

what do you mean by >>I've made an 'Orignal' copy that I can restore to<<

for the repair mode


Author Comment

ID: 24302173
| what do you mean by >>I've made an 'Orignal' copy that I can restore to<<
>> By Orignial, I mean when the server came back up and wouldn't mount. The 'Bad' files, so I can always go back to what the server 'was' when it first came back up.

Again, new e-mails aren't a super huge issue. I can re-deliver them all back to exchange using Barracuda - it keeps all incoming mail for 6 months. We'd really only lose some internal mail, server went down fairly early into a 5/4 work day.
LVL 49

Accepted Solution

Akhater earned 500 total points
ID: 24302250
Try a restore or a eseutil /P


Author Comment

ID: 24302364
Tried a eseutil /P and got this ...

Operation terminated with error -4001 (JET_errFileIOBeyondEOF, a read was issued to a location beyond EOF (writes will expand the file)) after 13.594 seconds.

Author Comment

ID: 24305645
Here's a few things from the Event Log

Information Store (4264) First Storage Group: Corruption was detected during soft recovery in logfile C:\Program Files\Exchsrvr\mdbdata\E00.log. The failing checksum record is located at position 1526:357. Data not matching the log-file fill pattern first appeared in sector 1653. This logfile has been damaged and is unusable.

Information Store (4264) First Storage Group: The log range read from the file "C:\Program Files\Exchsrvr\mdbdata\E00.log" at offset 781312 (0x00000000000bec00) for 512 (0x00000200) bytes failed verification due to a range checksum mismatch.  The expected checksum was 0 (0x00000000) and the actual checksum was 0 (0x00000000). The read operation will fail with error -501 (0xfffffe0b).  If this condition persists then please restore the logfile from a previous backup.

Information Store (4264) First Storage Group: Database recovery/restore failed with unexpected error -4001.

LVL 49

Expert Comment

ID: 24307875
Try restoring from backup it seems the E00 is corupted

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question