Sign in
 
HomeOnline201020072003LibraryForumsPartnersEHLO Blog
Exchange Server TechCenter > Exchange Server Forums > Admin > Another Public Folder Database won't mount - different error code

Proposed Answer Another Public Folder Database won't mount - different error code

    •  
      Tuesday, January 09, 2007 10:08 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I'm getting a similar problem to another poster, but with different error codes, so I created a new thread.

      I have no public folders, so stopped exchange services and moved the contents of the "second storage group" to another folder, then restarted exchange. The EMC offered to create new, empty database, but this also would not mount.

      Exchange is running using CCR on the mailbox server, with 2 hub/client access servers using NLB, the only other thing that isn't working properly is forms based authentication. The database mounted successfully after Exchange was installed.

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

      Public Folder Database
      Failed
      Error:
      Failed to mount (online) database 4ed58bcb-546c-469b-9e07-fa007ea84c1f. Reason: MapiExceptionADPropertyError: Unable to mount database. (hr=0x80004005, ec=2418)

       --------------------------------------------------------
      OK
      --------------------------------------------------------

      Any suggestions?

      rob

       

    All Replies

    • Tuesday, January 09, 2007 10:22 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Just to clarify what we've tried:

      • setup /PrepareAD
      • setup /PrepareLegacyPermissions
      • restarting all exchange services
      • restarting exchange services one member at a time

      I don't know if it's because the active cluster member won't mount the store, but there are no database or log files created on the passive member (I guess this could be expected until CCR is active on the store).

      the following have been logged:

      Event Type: Error
      Event Source: MSExchangeIS
      Event Category: General
      Event ID: 9519
      Date:  09/01/2007
      Time:  22:14:49
      User:  N/A
      Computer: FRANK
      Description:
      Error 0x972 starting database "Second Storage Group\4ed58bcb-546c-469b-9e07-fa007ea84c1f" on the Microsoft Exchange Information Store.

      For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
      Data:
      0000: 4c 6f 6f 6b 20 75 70 20   Look up
      0008: 6f 66 20 44 42 20 49 6e   of DB In
      0010: 66 6f 20 66 61 69 6c 65   fo faile
      0018: 64 00 5b 44 49 41 47 5f   d.[DIAG_
      0020: 43 54 58 5d 00 00 5e 00   CTX]..^.
      0028: 00 00 ff e4 16 00 00 00   ..ÿä....
      0030: 00 00 00 02 50 00 00 00   ....P...
      0038: fd 79 20 10 00 00 00 00   ýy .....
      0040: fd 79 20 10 00 00 00 00   ýy .....
      0048: fd 79 20 10 00 00 00 00   ýy .....
      0050: fd 79 20 10 00 00 00 00   ýy .....
      0058: fd 79 20 10 00 00 00 00   ýy .....
      0060: cd 4a 20 10 00 00 00 00   ÍJ .....
      0068: fd 79 20 10 00 00 00 00   ýy .....
      0070: 49 63 40 10 72 09 00 00   Ic@.r...
      0078: 68 28 40 10 72 09 00 00   h(@.r...
      0080: 73 0d 40 10 72 09 00 00   s.@.r...

      Event Type: Error
      Event Source: MSExchangeIS
      Event Category: General
      Event ID: 9518
      Date:  09/01/2007
      Time:  22:14:49
      User:  N/A
      Computer: FRANK
      Description:
      Error 0x972 starting Storage Group /DC=com/DC=cynexia/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=cynexia/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=msx/CN=InformationStore/CN=Second Storage Group on the Microsoft Exchange Information Store.
      MDB failed to start.

      For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
      Data:
      0000: 5b 44 49 41 47 5f 43 54   [DIAG_CT
      0008: 58 5d 00 00 ae 00 00 00   X]..®...
      0010: ff e4 16 00 00 00 00 00   ÿä......
      0018: 00 02 a0 00 00 00 fd 79   .. ...ýy
      0020: 20 10 00 00 00 00 fd 79    .....ýy
      0028: 20 10 00 00 00 00 fd 79    .....ýy
      0030: 20 10 00 00 00 00 fd 79    .....ýy
      0038: 20 10 00 00 00 00 fd 79    .....ýy
      0040: 20 10 00 00 00 00 cd 4a    .....ÍJ
      0048: 20 10 00 00 00 00 fd 79    .....ýy
      0050: 20 10 00 00 00 00 49 63    .....Ic
      0058: 40 10 72 09 00 00 68 28   @.r...h(
      0060: 40 10 72 09 00 00 73 0d   @.r...s.
      0068: 40 10 72 09 00 00 bd 44   @.r...½D
      0070: 20 10 00 00 00 00 03 59    ......Y
      0078: 20 10 00 00 00 00 03 59    ......Y
      0080: 20 10 00 00 00 00 cd 4a    .....ÍJ
      0088: 20 10 00 00 00 00 bd 5f    .....½_
      0090: 20 10 00 00 00 00 cd 4a    .....ÍJ
      0098: 20 10 00 00 00 00 bd 5f    .....½_
      00a0: 20 10 00 00 00 00 03 59    ......Y
      00a8: 20 10 00 00 00 00 cd 4a    .....ÍJ
      00b0: 20 10 00 00 00 00 bd 5f    .....½_
      00b8: 20 10 00 00 00 00          ..... 

      rob

       

       
    • Tuesday, January 09, 2007 10:28 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Sorry - forgot to mention - I manually stopped the cluster service on the active node, and attempted to mount the store on the other server, but got the same error. Trying to delete the public folder database gets this error:

      [PS] C:\>Remove-PublicFolderDatabase "MSx\Second Storage Group\Public Folder Dat
      abase" -removelastallowed: $true
      Remove-PublicFolderDatabase : The critical property 'PublicFolderHierarchy' is
      missing in the PublicFolderDatabase object 'msx\Second Storage Group\Public Fol
      der Database'.
      At line:1 char:28
      + Remove-PublicFolderDatabase  <<<< "MSx\Second Storage Group\Public Folder Dat
      abase" -removelastallowed: $true

      rob

       
    • Wednesday, January 10, 2007 2:57 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Rob I am getting the same errors in my event log too. the db mounted fine after the install then bam...I was hoping to migrate off of 03 this weekend but I dont see it happening now :(

      Ken

       

       
    • Thursday, February 08, 2007 3:32 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I was having this problem too.  It started when I removed the Exchange 2003 First Adminstrative Group from Active Directory with adsiedit.  The old EX2003 server was not in the Old Administrative Group, but Ex2007 public folders had a dependency on a "Folders Hierarchies" object in the old Administrative Group.

      The problem was resolved when I restored Active Directory form a SysState backup of the previous day.

      The missing object in AD that caused this is . . .(im my case) . . . 

      CN=Services, Microsoft Exchange, Org5112, Administrative Groups, First Administrative Group, Folder Hierarchies, >>  %deleted object%

       

      This fixed the problem, but I am trying to figure out if the Old Ex2003 Administrative Group must alway be there, or if their is a configuration command that would eliminated this dependency.

       

       
    • Monday, February 19, 2007 3:38 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      I've the same problem. Do I really have to restore my state? Or is there another solution?

      Thanx and regards,

      Jan Bosch

       
    • Tuesday, February 20, 2007 1:07 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      This may or may not be practical for you depending on how many mailboxes there are. . . I have about 15 mailboxes.

      I preferred to get rid of the legacy organizaton dependencies, so I exported all the mailboxes to .pst files, removed everything from Active Directory related to the legacy Exchange 2003 organization (with ADSIEdit) and ran a new clean install of Exchange 2007.  That was two hours well spent.

       

       

       
    • Thursday, February 22, 2007 12:30 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi Jan!

      To avoid this, add new exchange server account to old Exchange Domain Servers security group

      and old exchange server account to new Exchange Servers security group 

      Restart. Enjoy.

      Best regards,

      Alex Nikiforov.

       
    • Friday, September 07, 2007 8:07 PM
       
       Proposed Answer
      Sign In to Vote
      0
      Sign In to Vote

      hi

       

      check this link

       

      http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2112057&SiteID=17&mode=1

       

      thanks

      • Proposed As Answer by Diego Castelli Monday, September 13, 2010 11:00 AM
      •