Hi there,I have an odd problem with a CCR cluster we're recently setup. After a few hours of idle time, whenever I open the EMC or use the shell to check the status of a CCR cluster I get the following error..Get-StorageGroupCopyStatus : Microsoft Exchange Replication service RPCfailed:Microsoft.Exchange.Rpc.RpcException: Error e0434f4d fromcli_GetCopyStatusEx atMicrosoft.Exchange.Rpc.Cluster.ReplayRpcClient.GetCopyStatusEx[Guid[]sgGuid,RpcStorageGroupCopyStatus[]& sgStatuses] atMicrosoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.InternalGetCopyStatus[StringserverName,Guid[] sgGuids,RpcStorageGroupCopyStatus[]&sgStatuses,Int32serverVersion] Moving the cluster to another node, or restarting the CMS resolves the issue. But, after another few hours the error happens again until the CMS is moved/restarted.Anyone seen anything similar?Thanks!

Anyone?

Clarify: Got error info whenever run Get-StorageGroupCopyStatus, move or restart CMS can solved the issue temporarily, right? Known cause: Go to each node, check if Remote Registry was started and set as automatically, and correct it if not Troubleshooting: 0. Search for all the warnings or error in the application log during issued period 1. First of all, we need to confirm the replication service is running properly. Go to Active Node and check the database path, then compare it with the Passive Nodes. They need to be same path and size 2. Check if server was installed properly, same symptom will occur if any nodes didnt be installed correctly Cluster Continuous Replication http://technet.microsoft.com/en-us/library/bb124521.aspx Installing Cluster Continuous Replication on Windows Server 2003 http://technet.microsoft.com/en-us/library/aa997144(EXCHG.80).aspx Installing Cluster Continuous Replication on Windows Server 2008 http://technet.microsoft.com/en-us/library/bb629714(EXCHG.80).aspx 3. Did you saw a low virtual memory message before? If so, modify your pagefile setting 4. Go to ADUC->Computers, verify if you can see EVS for CCR [its the CCRs network name for all client], if the object werent there, the same symptom also will occur Advanced troubleshooting: 1. Run Exchange Best Practices analyzer on CCR Cluster and check if theres any error EMC->Toolbox-> Best Practices analyzer 2. Run MPSRPT_Exchange.EXE to generate MPS Reports for exchange on the both Active/passive node and check http://www.microsoft.com/downloads/details.aspx?familyid=cebf3c7c-7ca5-408f-88b7-f9c79b7306c0&displaylang=en

Hi, Djtodd, how's the issue? Does the suggestions help?

Thanks for the recommendations, but unfortunately I am still experiencing the issue. Remote registry is running on both nodes, there are no errors or warnings in any event logs, replication is occuring properly, and the servers were setup properly. I do not experience the issue in any of our lab environments, only the production environment. I'm stumped.

*bump*

Hello there... I know this is an old thread but I wanted to see if this was ever resolved for you and what a good way to post my first thread on this board We're running into the EXACT same issue with Exchange 2007 SP1 CCR cluster on Windows Server 2008.An additional piece of information, when running the ExBPA from the CMS primary node in question it fails with "Exchange server cannot be contacted" and "Exchange server SERVERNAME is down or unreachable. This could be the result of a network or permissions problem."---------------------------------------------------------------------------------------------------The following instructions are provided to correct the error, along with my checks:To correct this error 1. Ensure that the Exchange Server computer has been started and is connected to the network. --- [Done, I'm RDP'ed into the active node when running the command.] 2. Use the Ping command to see if the Exchange Server computer is reachable. --- [Answered in prior check] 3. If there is a firewall in place, check to see if RPC ports are blocked. --- [No internal firewall, and it works SOMETIMES] 4. Ensure that the Remote Registry service on the Exchange Server computer has been started. --- [Remote Registry is started, check!] 5. Check the permissions for the account under which the Exchange Server Analyzer Tool is running to ensure that it has sufficient permissions to read the registry on the Exchange Server computer. --- [Check, I'm running the tool under my account which is a Domain Admin and Exchange Org Admin] --------------------------------------------------------------------------------------------------- This seems to fit the bill as the following, quoted from the ExBPA, references using the SAME RPC service that is mentioned in the Exchange errorThe Microsoft Exchange Server Analyzer Tool uses remote procedure calls (RPCs) to read the CurrentVersion string value from the following registry key on the Exchange Server computer: Does anyone have any thoughts? I see a lot of similar postings with no resolutions

After working with MS support on the issue and checking various permissions on the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg" key (which were getting overwritten by the System Attendant during a failover to that node), amongst many other things, it was determined that we needed to move from E2K7 SP1 Rollup Update 8 to Rollup Update 9. There were apparently issues with geo-clustering RPC calls in RU8 that were corrected in RU9. See the support responses snippet below:------------------------------------------------------------------------Issue:Receives the RPC error intermittent on a CCR running Windows Server 2008 with Hexcode:- e0434f4d Cause: RPC routing issue not allowing the RPC call to the remote registry and remote share to complete (access denied) Resolution: Install RU9 where the RPC call method has been resolved ------------------------------------------------------------------------ I did move to RU9 on both nodes and confirm that the issue was no longer resident after the update was applied. Environment: Windows Server 2008 SP2, Exchange 2007 SP1 RU8 (corrected in RU9), Geo-clustered CCRHope this helps someone out there!

Did you find more information concerning the problem in the Application log?

Did you find more information concerning the problem in the Application log? Part of the problem in troubleshooting the issue was that event-logging was scarce. There was one entry in the System log (shown below) referencing a timeout when waiting for a response from the Remote Registry service.----------------------------------------------------------------------------------------Log Name: SystemSource: Service Control ManagerDate: 12/8/2009 9:49:31 AMEvent ID: 7011Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: Node1.domain.netDescription:A timeout (30000 milliseconds) was reached while waiting for a transaction response from the RemoteRegistry service.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7011</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-12-08T14:49:31.000Z" /> <EventRecordID>5229707</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>Node1.domain.net</Computer> <Security /> </System> <EventData> <Data Name="param1">30000</Data> <Data Name="param2">RemoteRegistry</Data> </EventData></Event>----------------------------------------------------------------------------------------The primary indicator that lead to the resolution was the error that Exchange was throwing (Hexcode:- e0434f4d), basically indicating that the RPC call to the remote registry was denied.