Hi to all, i have the Problem after an crash of my E2K7 the public database didn't exist anymore in the filesystem (and there is no backup) so i deleted the configuration of the public database via ADSI Edit. Then i was able to create a new public database but unable to mount this database. See the print of Exchange console wizard: Error Exchange is unable to mount the database that you specified. Specified database: MYEXC1\Third Storage Group\MYSERVER; Error code: MapiExceptionADNotFound: Unable to mount database. (hr=0x80004005, ec=2417) I didn't check the mountbox in the wizard, i waited a few minutes after creating the new database and then i tried to mount the database. Result: above Any godd advices are very welcome thx in advance Best regards Simo

Clarify: Original public folder database disappeared after an exchange server crash, and then you deleted the public folder database related attributes from ADSIEditor. Issue is, new public folder database is unable to mount after created with error window, right? Error: Exchange is unable to mount the database that you specified. Specified database: MYEXC1\Third Storage Group\MYSERVER; Error code: MapiExceptionADNotFound: Unable to mount database. (hr=0x80004005, ec=2417) Cause: AD configuration appeared to be uncompleted or changed according to the error info and symptom Resolution: 1. Go to the location of the Exchange setup files folder 2. Run Setup.com /PrepareAD Related articles: How to Prepare Active Directory and Domains White Paper: Preparing Active Directory for Exchange 2007 Permission Considerations Insufficient Permissions to Prepare Active Directory Collect info: Please also post the error info from servers application log

I had this very same Error Message, I couldn't find something back in the eventviewer neither.However my Public Database was still intact. I just couldn't mount my "Mailbox Database 2" which I tried to mount on a new Storage Group called 'Third Storage Group". Finally, a server reboot did the trick, database is mounted now.

Hi, Simo, I assume your question has been answered, and I'd like to change the status to "Marked as answer", please feel free to post here if you have any update

this work for me in a similar case: When Itry to create and mount a mailbox database I receive this error: "Error code: MapiExceptionADNotFound: Unable to mount database. (hr=0x80004005, ec=2417)". The solution for me was to remove the limits imposed by default when the db was created. 1.Right click on the db; select properties; on the second tab "Limits" remove all three checks on "Storage limits"; click OK. 2.Right click on the db and mount it. 3.Re-apply tthe storage limits that you desire.

i have tried this fix, didn't work. it use to resolve itself, sometimes a reboot i could mount the database again, now nothing seems to work to mount the database. any other ideas?

I had a similar problem a few days ago and had tried the resolution proposed by James-Luobut without any luck. I triedMihaiA's idea less than half an hour later and it seemed to do the trick. I'm not sure whether there was some sort of propagation delay to the first resolution but I wanted to thank both for the assist. :)Many thanks,

Unchecking the Storage limits worked for me, also. I had created the new PF so we could move all replicas from the First E2K7 server, and then decomm, but the new PF DB wouldn't mount.It's kind of a bizarre fix, though . . .??Thanks

Just wanted to chime in that when I got the error mentioned all I needed to do was wait 10 minutes and I could then mount the DB.I'm guessing that it was some sort of propagation issue.

this work for me in a similar case: When I try to create and mount a mailbox database I receive this error: "Error code: MapiExceptionADNotFound: Unable to mount database. (hr=0x80004005, ec=2417)". The solution for me was to remove the limits imposed by default when the db was created. 1.Right click on the db; select properties; on the second tab "Limits" remove all three checks on "Storage limits"; click OK. 2.Right click on the db and mount it. 3.Re-apply tthe storage limits that you desire. This worked for me.. Thank you so much!!

I had the same issue and Mihaia's fix worked for me. Thanks!Mike luebbers