We help IT Professionals succeed at work.

Decommissioned Exchange 2010 Server too soon

awsic
awsic asked
on
I've been given a project that has me a little confused.  A client has an Exchange Server 2010 (part of SBS 2011) that was decommissioned a little too soon as part of a server migration.

The final SBS 2011 server is still looking for public folders on the previous SBS 2011.  The old SBS 2011 is online (powered on) but no longer hold any AD roles.

I've tried making a new public folder database, told Exchange to not mount it, copied the missing public folder logs and DB to their respective folders, attempted to re-mount in EMC but it fails (error message below).  Tried then to move the *.EDB files where Exchange is expecting them to be and keeping only the log files in place, but that fails too.

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

Public Folder 03292015
Failed
Error:
Couldn't mount the database that you specified. Specified database: Public Folder 03292015; Error code: An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=1011)
. [Database: Public Folder 03292015, Server: <server host name>].

An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=1011)
. [Database: Public Folder 03292015, Server: <server host name>]

An Active Manager operation failed. Error Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=1011)
. [Server: <server host name>]

MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=1011)


Any ideas on where to go with this now?
Comment
Watch Question

Senior Solution Architect
Most Valuable Expert 2015
Top Expert 2015
Commented:
I would highly recommend using Kernel Data Recovery for this siutation. You can recover/restore any database offline and restore them back into production. This also works for all Exchange versions as well.

Kernel Data Recovery for Exchange Server.
http://www.kerneldatarecovery.com/exchange-server-recovery.html

Will.

Author

Commented:
Thank you for your suggestion.