Dear All, We are maintaining backend & frontend exchange 2003 servers. The backend exchange configured clustering ( 2 nodes). We are facing issue whenever i clickany one database right click go to properties and then click database(both nodes also). I received this error: Access is denied. Facility:Win32 ID no:c0070005 Exchange system manager Please give good solution.. Regards, Santh

Santh: I am assuming that you have tried the basic stuff such as closing the Exchange Systems Manager and logging out and then back in. Is the Remote Registry Service running on your clustered nodes? That might cause this problem. Also, is your Active Directory health (no down or problematic issues with any domain controllers). Jim

Jim: In frontend exchange server this service running. But i am able to open database propertises for the frontend server. But whenever i try backend server (click servername - click first storage group - right click mailbox database- then click database tab) Here only showing that error. Regards, Santh

Santh, Have you reviewed this article? http://support.microsoft.com/kb/323915 Thanks ~Brian

Hello, I already read this article. This article what are all the steps mentioned, i followed and alsoi have given this rights. But still this error is coming...... Regards, Santh

Is the Remote Registry service running on your cluster nodes? You only mentioned that it was running on the FE server.

Clarify: Got error info when you want to access the Properties of the database in the ESM, right? If Brians solution is still not working: 1. try to add LOCAL SERVICE account and gave it the "Read permissions on all three keys, then try to restart ESM and check HKEY_LOCAL_MACHINE\software\Microsoft\Exchange\language HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurePipeServer\Winreg HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SecurePipeServers\winreg 2. Try to logon with another admin account and check Another known resolution: Change the password of the user account facing this issue to be 15 characters long [KB 828861] which can solve similar issue

Hello, This service running both clustering nodes & also restarted this service..... Regards, Santh