• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 326
  • Last Modified:

SBS 2003 Exchange Database won't Mount

I have an old sbs 2003 box that has been running email for ever. The power went out with a bang and now the Exchange is toast.  I have been able to run the eseutil on the database but I still cannot mount it. I can't run the Isinteg as it cannot initiate the verification process.

This is in the application error log;
Error 0xfffffc01 starting Storage Group /DC=local/DC=EganIT/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=EGANIT/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN=GATEWAY/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

When I try to mount the database I get an error saying an internal processing error had occurred and to restart the services. This makes no difference. It gives an error number C1041724. I would like to get this running if poss.
  • 3
  • 2
1 Solution
Check if this helps you fix the problem.


Do you have backup of the database? You might need to restore the database from backup.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Okh do this

eseutil /mh "Location of .EDB" (What is the Status) ?
Did you remove all other files apart from .EDB and .STM ...... out of the default folders ? If not please do so and try to mount the database ?

- Rancy
Todger66Author Commented:
Thanks guys. The logs are on a different drive. I had to swap out the drive they were on and they got a different drive letter say S:\Exchange\Logs for instance.
I have gone in and in the properties of Exchange Manger changed this path to the logs folder.

I ran the eseutil /mh;

C:\>eseutil /mh "C:\program files\exchsrvr\mdbdata\priv1.edb"

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,11
     DB Signature: Create time:05/14/2013 11:19:57 Rand:3607782
         cbDbPage: 4096
           dbtime: 1774017 (0x1b11c1)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 1266
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 4
      Repair Date: 05/14/2013 10:14:04
 Old Repair Count: 4
  Last Consistent: (0x0,0,0)  05/14/2013 11:37:18
      Last Attach: (0x0,0,0)  05/14/2013 11:19:58
      Last Detach: (0x0,0,0)  05/14/2013 11:37:18
             Dbid: 2
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Comput
       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.

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Perfect the database is Cleno :)

Now ensure that no .LOG .RES .CHK .TEMP .TMP ...... or anything apart from EDB and STM are there and then try to mount

- Rancy
Todger66Author Commented:
Thanks guys. The log file header had a different path for the "log files".
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So didnt my comments help even a bit ?

- Rancy
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.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now