Exchange 2003 Corrupted Databases

Let me start this by saying I’m by no means an Exchange expert.

During our nightly back up two nights ago the power went out. Every since then one of our exchange servers has been down. I did some poking around in the system manager and seen that the mailbox store and the public folder store were down. When I try to mount them, I get the error:

An internal processing error has occurred.
ID no: c1041724

And the event log is getting this error every minute or so (edited the name):

Error 0xfffffb40 starting Storage Group /DC=com/DC=***/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=****/CN=Administrative Groups/CN=***
/CN=Servers/CN=ST10/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

For more information, click

I did some digging on the internet and discovered my databases were in a dirty shutdown state and was missing a required log file (found out via eseutil /mh). I ran eseutil /p on them last night and they all now report as clean shutdown.
I have not run isinteg as I cannot figure it out. The sytax I’m using while in the DB directory is:

C:\Program Files\Exchsrvr\MDBDATA>"C:\Program Files\Exchsrvr\bin\isinteg" -s ST
10 -fix -test alltest

Which fails and just tells me how to use the command.

This morning in the event log a new error is appearing. Its source is ESE and the error is:

Information Store (6548) First Storage Group: Database recovery failed with error -1216 because it encountered references to a database, 'C:\Program Files\Exchsrvr\mdbdata\priv1.edb', which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the "more information" link at the bottom of this message.

The DB is still there and hasn’t been moved.

There is no back up. If someone could point me in the direction to getting this resolved, I would much appreciate it.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

as a start try soft recovery

eseutil /r e00 for example

if it fails you will need to run the hard recovery

eseutil /p priv1.edb
drdingo21Author Commented:
Thanks the /r did fail yesterday.

I have already run the /p on priv1.edb and it completed successfully. But I haven't done anything further as I'm unsure how to proceed.
Shreedhar EtteCommented:

Check the database status by running the command:
eseutil /mh priv1.edb

Refer this:

If it is in Dirty Shut Down then you need repair the database using the commands:

eseutil /p priv1.edb - repair the database
eseutil /d priv1.edb - defrag the database
isinteg -s servername -fix -test alltests - integrity check

Note: Do take the backup of the database file first.

I hope this helps,
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

if you completed /p now please run

eseutil /mh priv1.edb

do you see it is in clean shutdown state ?

if so you can mount it
Confirm that ESM says the database location is 'C:\Program Files\Exchsrvr\mdbdata\priv1.edb', you might be looking at the wrong database.

/P is always a last resort and should not be taken lightly.
drdingo21Author Commented:
I have already ran /p and it completed.

/mh shows all my databases in a clean shutdown state.
ok so try to mount it
drdingo21Author Commented:
And ESM is looking at the correct DBs.
drdingo21Author Commented:
When I try to mount them - I get the error I listed in my original post.
please create a new folder move all log files to it, just keep the .stm and .edb file and then try to mount again
when you do a /MH on the databases, what is the "RepairCount" value?
also ISINTEG command is as follows:
 isinteg -s servername -fix -test alltests

so it looks like you left the "s" off the end of alltests from your original post
drdingo21Author Commented:
To move the log files, do you mean the ones in the MDBDATA (e00.log etc..) or the ones on my c drive that start with 2000xxxx.log?

And the output of /mh
C:\Program Files\Exchsrvr\MDBDATA>cd "C:\Program Files\Exchsrvr\bin"

C:\Program Files\Exchsrvr\bin>eseutil /mh "C:\Program Files\Exchsrvr\MDBDATA\pri

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

Initiating FILE DUMP mode...
         Database: C:\Program Files\Exchsrvr\MDBDATA\priv1.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,11
 Engine ulVersion: 0x620,11
Created ulVersion: 0x620,9
     DB Signature: Create time:04/08/2010 17:30:43 Rand:10177080 Computer:
         cbDbPage: 4096
           dbtime: 444798965 (0x1a8317f5)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 85578
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 2
      Repair Date: 04/08/2010 17:30:43
 Old Repair Count: 0
  Last Consistent: (0x0,0,0)  04/08/2010 17:30:43
      Last Attach: (0x0,0,0)  04/08/2010 17:30:43
      Last Detach: (0x0,0,0)  04/08/2010 17:30:43
             Dbid: 1
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 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: found (1)
Last Bad Checksum Error Date: 04/08/2010 17:30:43
Old bad Checksum Error Count: found (1)

Operation completed successfully in 3.532 seconds.
in C:\Program Files\Exchsrvr\MDBDATA you should have log files of 5 megs each a .chk file of a few kbs a .edb file and a .stm file

keep only the .edb and .stm move all the rest to another folder and try to mount

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
drdingo21Author Commented:

Thank you Akhater! That was the problem. The DB mounted correctly and everything looks good.
drdingo21Author Commented:
please make sure to take backup asap and if you can build a new database and move all your mailboxes to the new one. I don't like running on a db that has been repaired
yep do what Akhater says... Hopefully it will mount, but to be honest you need to run the isinteg to sort out all the logical links within the database.

Since the repair count has gone from 0 to 2, it means that 2 items have been fixed or effectively cut out from the database and that can sometimes mean the whole attachment table... but don't worry too much at this point, I have seen customers with Repair Counts of 13 and no reported missing items...
drdingo21Author Commented:
Thank you both of you.

I started here about 8 months ago and previous admin has 2 exchange box running. One is backed up regularly and the other one is only backed up via the windows back up and only has about 15 mail boxes on it.

It appears they just never migrated the remaining boxes to the new server.

I really appreciate the help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.