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

Exchange 2007 Datebase - MapiExceptionJetErrorAttachedDatabaseMismatch

Environment is Exchange 2007 SP2 running on Server 2008 Ent.
CCR cluster between two identical servers.

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Failed to mount database 'Public Folder Database'.

Public Folder Database
Failed
Error:
Exchange is unable to mount the database that you specified. Specified database: Mailbox1\Second Storage Group\Public Folder Database; Error code: MapiExceptionJetErrorAttachedDatabaseMismatch: Unable to mount database. (hr=0x80004005, ec=-1216)

I'm trying to get a CCR cluster running that was already in a poor state (out of sync and no daily backup) after a LUN dropout. The First Storage came up fine after the dropout but the Public Folder's database won't mount anymore.

So far I've tried all combinations of the eseutil.
Made sure 'Database can be overwritten by a restore' is ticked.
Removing all the logs to a different directory.
Restoring a database from last night.
Restarted all Exchange services.

All seem to get a point where I get a MapiExceptionJetErrorAttachedDatabaseMismatch error and can't go any further. Isinteg also fails with the same error in the event logs -
MSExchangeIS (5784) Second Storage Group: Database recovery failed with error -1216 because it encountered references to a database, 'G:\PublicStore\Public Folder Database.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.

Eseutil /MH says that the database is in a clean shutdown state so it should be ready to mount. The database is definately located at the correct path.

Does anyone have any ideas?
Thanks
0
matthewa00
Asked:
matthewa00
  • 7
  • 7
  • 5
  • +2
1 Solution
 
Marc DekeyserSr Premier Field EngineerCommented:
Could you post the output of the eseutil/mh here? That event ID seems to suggest that it cannot be found. The 4005 error in the mounting is an access denied and the apiExceptionJetErrorAttachedDatabaseMismatch usually refers to logfiles.

On a side node, the exchange servers have not been rebuild?
0
 
matthewa00Author Commented:
Nothing has been rebuilt or even restarted yet. A SAN restart brought the LUN's back then I remounted the datastores. First Storage Group was fine but the Second Storage Group never came back up.

[quote]G:\PublicStore>"c:\Program Files\Microsoft\Exchange Server\Bin\eseutil.exe" /m
"Public Folder Database.edb"

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

Initiating FILE DUMP mode...
         Database: Public Folder Database.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,12
 Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:09/22/2010 16:15:57 Rand:141471139 Computer:
         cbDbPage: 8192
           dbtime: 18513474 (0x11a7e42)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Streaming File: No
         Shadowed: Yes
       Last Objid: 33022
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 2
      Repair Date: 09/22/2010 16:15:57
 Old Repair Count: 0
  Last Consistent: (0x0,0,0)  09/22/2010 16:29:16
      Last Attach: (0x0,0,0)  09/22/2010 16:15:57
      Last Detach: (0x0,0,0)  09/22/2010 16:29:16
             Dbid: 1
    Log Signature: Create time:00/00/1900 00:00:00 Rand:0 Computer:
       OS Version: (6.0.6002 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

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: found (108)
Last Bad Checksum Error Date: 09/22/2010 16:14:13
Old bad Checksum Error Count: found (108)

Operation completed successfully in 0.47 seconds.[/quote]


0
 
Marc DekeyserSr Premier Field EngineerCommented:
Reason I asked is it could have been you had to rebuild the server and the database could have had a newer versioning then the server :). It happens.

Looks in clean shutdown indeed. can you move everything BUT the edb file to another location so that only the EDB file resides in the database location?
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.

 
matthewa00Author Commented:
Unfortunately the exact same error message and event logs are generated with only the EDB in the store directory.
0
 
Marc DekeyserSr Premier Field EngineerCommented:
what if you move the edb to another directory aswell? Might be that there is something corrupt in the tables... If exchange cannot find the edb it will create a blank file. If that one mounts we know an isinteg will be required. If it does not you can try removing the public folder in EMC and recreating it.
0
 
matthewa00Author Commented:
Without the EDB in the directory it spits out the same errors and events... weird. It didn't create a new EDB either.

I'll try removing the storage group all together and re-creating, I attempted it before but stopped because its CCR and a bit of a process to remove.
0
 
MegaNuk3Commented:
Does the database exist in 'G:\PublicStore\Public Folder Database.edb' ?

How many databases in the SG with the PF store?
0
 
MegaNuk3Commented:
ignore my first question as I have just re-read the whole question and can see that is where you ran the eseutil /mh from...

How many other stores in the 2nd SG with the PF store?
0
 
matthewa00Author Commented:
It's only single database in that storage group. I think its actually a requirement of CCR that there is only one database per storage group.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Can you please run the command
Setup /prepareAD
Once completed try mounting the store again
0
 
MegaNuk3Commented:
OK, so try this then.
Move all log files and checkpoint for this SG to another directory and then try and mount the PF store.

I know you said you moved all log files, but you didn't say anything about the checkpoint file. This database is in a clean shutdown state so shouldn't require any log files or checkpoint to mount...
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Yes matthew correctly said that CCR's designed for 1 Store per Storage Group .... Also there is an issue where in if you have multiple CCR's you cannot have Public stores on all of them and also replication has issues .... So as per recommendation MS says to have Public Store on a dedicated PF Server ...
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Hello Mega .... not sure if you have seen the complete error info

MSExchangeIS (5784) Second Storage Group: Database recovery failed with error -1216 because it encountered references to a database, ""G:\PublicStore\Public Folder Database.edb"", which is no longer present
0
 
MegaNuk3Commented:
Have you tried failing over(moving resources) to the other node and then seeing if the PF store mounts?
0
 
MegaNuk3Commented:
Rancy is that after moving the checkpoint like I said and trying to mount the database?
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Any which ways even if the Checkpoint file is in the same location you wont get any error for "encountered references to a database" .... ideally -1216 if for Soft recovery with a \i switch ... but we have seen E2K7 issues were one or more stores mount and others do not with the same error ...
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Megha:
Have you tried failing over(moving resources) to the other node and then seeing if the PF store mounts?

If the Database is "Mind-split" would failing over help in mount and if on Node1 there is no DB or mounting option how failing to Node2 would help .... or would re-seeding be possible by any means ??
0
 
MegaNuk3Commented:
Rancy, let the asker try my suggestions, if they don't work then we are no worse off, if they do then problem solved...
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Surely i agree .... no hard feelings wasnt trying anything out here .. so please dont take it otherwise :)
0
 
MegaNuk3Commented:
no problem
0
 
matthewa00Author Commented:
I managed to figure it out, finally.

I removed the database from AD using ADSI Edit and then restarted the Information Store, after that I could remove the storage group.  I re-created the storage group and database then copied in my EDB. It mounted first go and everything is back to normal.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
It would work because you are manually removing all entries of the AD database .... but maybe this problem might re-occour so you can always try the "Set \PrepareAD" if you want you can read more articles or forums about such problem ...
0
 
Alan HardistyCo-OwnerCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.
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.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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