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

URGENT! ID no: c1041724 when trying to mount PRIV DB!

Had to rebuild my exchange server and restored from older databases.  At first when I tried to mount them I got an error saying that the databases were corrupt.

Ran Eseutil /p and /d and now I get

"An internal processing error has occured.  Try restarting the Exchange System Manager or the MS Exchange Information store service, or both."

ID no: c1041724
Exchange System Manager

I ran the eseutil /p with /i on both....

Also, the priv is showing dirty shutdown.

I have gotten the Public to mount, but I can not get the priv1.edb to mount.  I get the c1041724 error I put above.

Anyone?
0
lttech
Asked:
lttech
  • 6
  • 4
  • 2
  • +1
1 Solution
 
mkumar23Commented:
Can you check your event log for any event you may have received after trying to mount the store?

Also check if there some disk space issue as mentioned in this MS article

http://support.microsoft.com/kb/294318/en-us
0
 
lttechAuthor Commented:
We are getting:

Event ID: 9175 MSExchangeSA
Event ID: 9519 MSExchangeIS
Event ID: 1133, 1000, 1217 on MSExchangeIS Mailbox Store

There is plenty of diskspace.  The DB's are pretty small.



0
 
december41991Commented:
ID no: c1041724
Exchange System Manager
The above error is very generic
What is the status of the database file. Is it clean shut down

eseutil /mh path of edb file
This command will dump the header and will let you know the status of the database.
Event ID is required by all means....

Dominic
0
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!

 
lttechAuthor Commented:
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:06/07/2006 13:29:34 Rand:2489956 Computer:
         cbDbPage: 4096
           dbtime: 777 (0x309)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
   Streaming File: Yes
         Shadowed: Yes
       Last Objid: 9
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
  Last Consistent: (0x1,1F51,95)  06/07/2006 16:22:05
      Last Attach: (0x1,1F50,1AC)  06/07/2006 16:22:05
      Last Detach: (0x1,1F51,95)  06/07/2006 16:22:05
             Dbid: 2
    Log Signature: Create time:06/07/2006 13:44:57 Rand:625512 Computer:
       OS Version: (5.2.3790 SP 1)

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

Operation completed successfully in 3.15 seconds.

-------------------------------------------------------------------------------

0
 
december41991Commented:
While I check other option that you might have try mounting the store after removing .chk files to a different location.
Also past the description for 1133 and 1000 events.

Thanks
Dominic
0
 
mkumar23Commented:
0
 
lttechAuthor Commented:
December:

Moving the .chk files changes nothing.


Mkumar:  Regarding your post, I am not sure what the .env file is and what it is regarding.  
0
 
december41991Commented:
Disable AV software. Rename the mdbfolder and use fresh one. We don't need .chk or for that matter any file apart from .edb and .stm and the log file location empty.


Dominic
0
 
december41991Commented:
Mkumar:  Regarding your post, I am not sure what the .env file is and what it is regarding.  

This is not related. Its restore.env file and is created when you restore from a online backup. IGNORE.
0
 
lttechAuthor Commented:
We have no AV on the server.  

So rename the MDBDATA folder to something else and create a new one and dump the EDB and STM files in it or no?
0
 
december41991Commented:
yes

first find out the log file location..... if there are any log files in it the remove it. ( back it up ) easiest way rename that folder as well.
a clean shut down database does not require any log files and is self sufficient to get mounted.

try mounting with a blank store to know if we have a issue with the edb file itself.

Dominic
0
 
december41991Commented:
If you a env file then delete it ( if you have done  a online restore.  
"restore.env"
0
 
questionforrajaCommented:
Have tried running ISINTEG.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

  • 6
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now