John Yassa's Blog

Home » Posts tagged 'Clean Shutdown'

Tag Archives: Clean Shutdown

Unable to mount any mailbox store in a storage group (event id 9518 + event id 454 + event id 494)

yesterday one fo our servers got hang , so we had to hard restart the server

once the server got up again we found that all mailbox stores under one storage group failed to brign online

and we found that the below 3 event log appeared in the event viewer :

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 494
Date:  6/24/2012
Time:  1:46:51 AM U
ser:  N/A Computer: server1
Description: Information Store (8676) Storagegroup1: Database recovery failed with error -1216 because it encountered references to a database, ‘G:\EXCHSRVR\StorageGroup1\MAilboxstore1.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.
————————————————————————————————-
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date:  6/24/2012 Time:  1:46:51 AM
User:  N/A
Computer: server1
Description: Information Store (8676) storagegroup1: Database recovery/restore failed with unexpected error -1216.
————————————————————————————————-
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date:  6/24/2012 Time:  1:46:51 AM
User:  N/A
Computer: server1
Description: Error 0xfffffb40 starting Storage Group /DC=com/DC=domain/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=name/CN=Administrative Groups/CN=First Administrative Group/CN=Servers/CN=server1/CN=InformationStore/CN=storagegroup1on the Microsoft Exchange Information Store. Storage Group – Initialization of Jet failed.
————————————————————————————

we have tried to do soft recovery for mailbox store mailboxstore1 by running command eseutil /r “logbase” /l “Log path” /d “Database path”

but it failed and could repair the Database softly

the problem here was because the path of the DB and the path of the Logs wasn’t the same, so we moved the DB files to the same path as the logs and try the command one more time, and it success and could mount the all mailbox stores

Can’t mount Database with error ,Unable to mount database. (hr=0x80004005, ec=-550)

Couldn’t mount the database that you specified. Specified database: DB2; Errorcode: An Active Manager operation failed. Error: The database action failed. Error: An error occurred while trying to select a database copy for possible activation. Error: The database ‘DB2’ was not mounted because errors occurred either while validating database copies for possible activation, or while attempting to activate another copy. Detailed error(s):

An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)

Before you can mount a database restored from a backup, it needs to be in a clean shutdown state. You can use the Eseutil tool to check whether a database is in a clean shutdown state – if it is not in a clean shutdown state you can perform a repair to get the database into consistency.

Soft Recovery using Eseutil

The first thing you want to do is verify that the database is in a dirty shutdown state. We can do this using the eseutil /mh command. For example:

the output should be as below:

as long as you can it shows that the DB is closed dirty shut down
also you can see the logs that is missing
we can replay the log files into the DB (if they only exist) using the command eseutil /r /l /d

For example, my log file prefix is E03, and my database and logs are stored in G:\E_\Program Files\Microsoft\Exchange Server\V14\Mailbox\DAGDB1

after it finsihed you can the first command eseutil /mh to confirm that the DB is now in clean shut down state

if after these steps , you try to mount the DB  if it fails to mount then you will have to do a hard repair using the command  eseutil /p

after it finsihed you can the first command eseutil /mh to confirm that the DB is now in clean shut down state , then try to mount the DB , it should mount with you with no problem

%d bloggers like this: