Exchange 2010 - Unable to mount database. (hr=0x80004005, ec=1105)

Status
Not open for further replies.
M

masafo

Hello,
I'm having an issue when trying to mount a database restored from a " Windows Server Backup"

Scenario: 1 x 2008R2 Domain Controller
1 x 2008r1/sp2 Member server Running Exchange2010(no servicepack) server
I'm able to create the recovery database store using the following cmdlet

New-MailboxDatabase -Recovery -Name " RDB1" -Server EXCH14 -edbfilepath " C:\recovery\Mailbox Database 0997299251.edb" -logfolderpath " C:\Recovery"

Eseutil tells me the database is clean as per below

------------------------------------------------------------------------------------------------------------------------------------------------------------C:\recovery>eseutil /MH " Mailbox Database 0997299251.edb"

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

Initiating FILE DUMP mode...
Database: Mailbox Database 0997299251.edb
DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x140b6bb4
Actual Checksum: 0x140b6bb4

Fields:
File Type: Database
Checksum: 0x140b6bb4
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,17
Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
DB Signature: Create time:09/21/2010 00:31:58 Rand:1720817 Computer:
cbDbPage: 32768
dbtime: 497277 (0x7967d)
State: Clean Shutdown
Log Required: 0-0 (0x0-0x0)
Log Committed: 0-0 (0x0-0x0)
Log Recovering: 0 (0x0)
GenMax Creation: 00/00/1900 00:00:00
Shadowed: Yes
Last Objid: 1670
Scrub Dbtime: 0 (0x0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Old Repair Count: 0
Last Consistent: (0x5,A,193) 11/01/2010 18:30:45
Last Attach: (0x4,9,86) 11/01/2010 18:30:45
Last Detach: (0x5,A,193) 11/01/2010 18:30:45
Dbid: 1
Log Signature: Create time:11/01/2010 18:21:24 Rand:21321550 Computer:
OS Version: (6.0.6002 SP 2 NLS 500100.50100)

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: none
Old bad Checksum Error Count: none
Last checksum finish Date: 00/00/1900 00:00:00
Current checksum start Date: 00/00/1900 00:00:00
Current checksum page: 0
Operation completed successfully in 0.297 seconds.

------------------------------------------------------------------------------------------------------------------------------------------------------------ I can see the online database + the recovery database I created when I run the cmdlet below
C:\recovery>get-mailboxdatabase

Name Server Recovery ReplicationType
---- ------ -------- -------------
Mailbox Database 0137882491 EXCH14 False None
RDB1 EXCH14 True None

However , when I try to mount the Recovery database using the cmdlet below

recovery>mount-database RDB1

I get the following error

Couldn't mount the database that you specified. Specified database: Recovery1; Error code: An Active Manager operation
failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mou
nt database. (hr=0x80004005, ec=1105)
[Database: recovery1, Server: Exch14.cruzit.local].
+ CategoryInfo : InvalidOperation: (recovery1:ADObjectId) [Mount-Database], InvalidOperationException
+ FullyQualifiedErrorId : 50A7D2E2,Microsoft.Exchange.Management.SystemConfigurationTasks.MountDatabase

- What I'm doing is running through a worst-case scenario in which I'm having to rebuild both the DC/Exchange from scratch & am relying on a backup taken using " Windows Server Backup" , so I've rebuild the Domain using the same " Domain name" & installed exchange using the identical " organization names" so I cant for the life of me work out why I'm getting this error,

any help would be greatly appreciated as I'm lost for ideas/solutions.

Thanks in advanced.
 
G

Gulab Mallah

Make sure that there is no log files and checkpoint files at the current collection, if its there is, move them to another location and try to mount it.

Make sure that " This database can be overwritten by resotre is checked."

Cheers,
-Gulab
 
M

masafo

Hi Gulab,
Ok, I'll give that a go and will update this thread with the results
cheers
 
M

masafo

Ok...I'm glad to say that the issue has being fixed.

Gulab, I did try what you suggested but unfortunately the error persisted.

Then I remembered that the Exchange Server from where the database came from had the SP1 for Exchange 2010 installed, but the new Exchange did not...so I decided to apply SP1 to the new exchange server & I can now mount the database (using the same method as posted at the begining of the thread) without getting the error *Unable to mount database. (hr=0x80004005, ec=1105)*.
I can also Restore Mailboxes from the Recovery Database I created using the following cmdlet

Restore-Mailbox -Identity Martin -RecoveryDatabase RDB3 -RecoveryMailbox martin -TargetFolder “Lost and Found”

The above cmdlet allowed me to restore the mailbox belonging to " Martin" which was held in the recovery database " RDB3" into a folder called " Lost and Found" to a newly created mailbox called " Martin" .

I wanted to try this scenario just to be prepared for a worst case scenario (better to be prepared then put false hopes on a non-tested Disaster Recovery scenario).

Thanks Gulab for replying to my thread, appreciate it either way.

Best regards to all.
 
G

Gulab Mallah

Ooopppssss ;) didn't know that it was SP1 and RTM scenario...

End of the what matters is " Issue resolved"

Cheers,
-Gulab
 
S

Shiney

I was getting the exact same 80004005 ec=1105 error on a test install I did. In my case, I had two mailbox servers set up in a DAG, six databases with 3 on each and a copy on the other. I first noticed issues with the second server, the Exchange search service kept killing the processor utilization and none of the databases would fail over to it properly, resulting in a huge copy queue length. Turned out that I never installed SP1 on the second mailbox server so the databases wouldn't mount there without getting that ec=1105 error. So its definitely a lack of SP1 issue.

The oddest thing is that SP1 existed on the first server before I ever installed the second server. Why would it even allow me to add an SP1-less server to a DAG that was built with SP1? And worse yet, how did it ever add copies to the SP1-less server? And still wore yet, how did it let me add copies of an SP1-less database to the SP1 server?

Listen up MS, you have some serious version checking issues with Exchange 2010!
 
Status
Not open for further replies.
Top