Good day. We deployed the first Exchange 2007 server into our Exchange 2003 org. It has the mbx, cas, and hub roles on it. When it started up for the first time, there was a public folder store already installed but not mounted. When I try to mount it, it says: Exchange is unable to mount the database that you specified. Specified database: servername\zPublic Folder Storage Group\Public Folders Store; Error code: MapiExceptionNoAccess: Unable to mount database. (hr=0 x80070005 , ec=-2147024891 ) I have given the folder for the storage group files and store files full control to the everyone group. I have tried to remove the store and of course it says it cannot be removed because it cannot be checked for replicas. It has never successfully mounted so there should be no replicas. This problem I'm having and the error is the exact same as in the http://support.microsoft.com/kb/313866 article. It says there to check in the configuration container in ADSIEdit for: "CN=Services,CN=Microsoft Exchange,CN=ORGANIZATION ,CN=Administrative Groups,CN=administrative_group ,CN=Folder Hierarchies,CN=Public Folders" and to change the security on CN=Public Folders. When I look in ADSIEdit on my org and the Exch 2007 admin group, I don't have a CN=Public Folders; in fact, I don't have the parent folder CN=Folder Hierarchies either. Under "CN=Exchange Administrative Group (FYDIBOHF23 SPDLT) " I only have CN=Advanced Security, CN=Routing Groups, and CN=Servers" but no CN=Folder Hierarchies. So I can't change the permissions as the folder isn't there. When I look under my Exchange 2003 admin group, there is a CN=Folder Hierarchies and under it a CN=Public Folders. Should I copy these into under the Exchange 2007 CN? Thanx for your help folks. Derrill

KB 313866 seems to be referring to creating Public Folders themselves, not mounting the database.Do you have any errors in the Application Log on the 2007 server?

No, dont move CN=Folder Hierarchies folder. Please use the method in KB 313866 on the CN=Public Folders entry where it was. Check the permissions CN=Services, CN=Microsoft Exchange, CN=ORGANIZATION, CN=Administrative Groups, CN={First Administrative Group}, CN=Folder Hierarchies, CN=Public Folders

How's the issue now? Any update?

Hello , Did you try to see the database if it's in dirty shutdown or not ? please use eseutil /mh on the database to check this. If it's in dirty shutdown state , consider repairing it using eseutil /r or restore from latest backup