new1234.jpg
Home > Exchange, Microsoft > Microsoft: Exchange 2007 cannot mount after install Rollup 9

Microsoft: Exchange 2007 cannot mount after install Rollup 9

Today I updated Exchange 2007 SP1 with rollup 6 to (Windows 2008 Standard SP1 64 Bit) rollup 7, 8 en 9. After each installation I rebooted the server en checked if de Database was mounted. After installation of Microsoft Exchange Rollup 9 and restart server I can’t connect my mail database. I receive this error:

Error:

Exchange is unable to mount the database that you specified. Specified database DOMAIN\First Storage Group\Public_Folders; Error code:MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005,ec=-1023)

image

Resolution:

Add the Exchange Servers group to the "Manage auditing and security log" policy

 

To add the Exchange Servers group to the Manage auditing and security log policy, follow these steps:

  1. Log on to a domain controller by using an account that has administrative rights.
  2. Click Start, point to Administrative Tools, and then click Domain Controller Security Policy.
  3. In the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in, expand Local Policies, and then click User Rights Assignment.
  4. In the right pane, double-click Manage auditing and security log.
  5. In the Manage auditing and security log Properties dialog box, click Add User or Group.
  6. In the User and group names box, type DomainName\Exchange Servers, and then click OK two times.
  7. Exit the Default Domain Controller Security Settings MMC snap-in, and then wait for this security setting to propagate across the domain controllers in the domain.
  8. Restart the Microsoft Exchange Information Store service. (I Restarted the server)
    Pfew its online and mounted: 🙂

image

    Source: http://support.microsoft.com/kb/925825

    Twitter Poster sponsor : Sensa weightloss review

    sanderdaems

    Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.

    More Posts - Website

    Follow Me:
    TwitterLinkedIn

    1. Exchnge Newbie
      December 23rd, 2009  (Quote) at 01:27  (Quote) | #1

      I received the same error message two different times with two different resolutions.

      The first time: I created a new database and tried to mount it and received the same error message as you described. I stopped and restarted the information store and was then able to mount the new database.

      The second time: I had created a new database and installed a Microsoft update. I could not mount the new database but assumed that was because I needed to restart the Information Store service. Since I needed to restart the server from the security update I did not bother with restarting the Information Store service. I restarted the server to complete the Microsoft update installation. When Exchange started it mounted my new database and all others except the third one. Restarting the information store service did not resolve the problem. Going through the application event logs I found one event that mentioned I had more than the maximum 5 databases. (This is Exchange Enterprise so I shouldn’t be limited to 5 databases). Since no mailboxes had been moved to the new database I went ahead and deleted it. I was then able to mount the existing third database.

    1. No trackbacks yet.