Non-GRT Backup of Exchange Information Store in a Cluster Continuous Replication(CCR) setup fails with 0xe000fe30 - A communications failure has occurred and Remote Agent on Active node crashes due to Monad RPC Timeout error

Article:TECH68770  |  Created: 2009-01-16  |  Updated: 2014-01-16  |  Article URL http://www.symantec.com/docs/TECH68770
Article Type
Technical Solution


Issue



Non-GRT Backup of Exchange Information Store in a Cluster Continuous Replication(CCR) setup fails with 0xe000fe30 - A communications failure has occurred and Remote Agent on Active node crashes due to Monad RPC Timeout error


Error



Attempt to run a non-GRT Backup of Information Store fails with the below error (Figure 1)
 
 Figure 1.
 
 

 

Cause



Observations

1. An attempt to run a non-GRT Backup of Microsoft Exchange Information Store from Passive Copy only fails on First Storage Group and causes Remote Agent to crash on Active Node

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 17/02/2009
Time: 5:43:20 PM
User: N/A
Computer: ServerName
Description:
Faulting application beremote.exe, version 12.5.2213.101, faulting module bedsxese.dll, version 12.5.2213.0, fault address
0x00000000000171f7.

2. Only the First Storage Group in the resource order is not backed up,rest all are backed up.  
3. Changing the resource order for Storage Groups doesn't help resolve this issue.
4. Excerpts from beremote debug log from Active Node shows following information

8204] 03/12/09 17:52:52 Monad RPC timeout 60000
[8204] 03/12/09 17:54:22 ese command 5 timed out
[8204] 03/12/09 17:54:22 GetClusterStatus returned 80004005 -> CLUSTERNAME
[8204] 03/12/09 17:54:22 GetClusteredStatus() state = (null), active = (null), passive = (null), isClus = FALSE, isCCR = FALSE, isHealthy = FALSE
[8204] 03/12/09 17:54:22 Device Name: \\ClusterName\Microsoft Information Store\SG1('ClusterName' '70' '0' '35' '1')

 
Reason:
  
Backup Exec fails to get Cluster Status due to Monad RPC timeout and ESE command timeout.
 

Solution




Workaround

Backup from Active copy of Exchange CCR.


Solution

Apply Hotfix 319699 on Media Server and update the remote agent on both nodes of Exchange Cluster and add following registry entry.

 
1. Add a DWORD value called MonadRpcTimeout in the Registry on the Backup Exec server and the Exchange server into the following location:
 
HKLM\Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Exchange
 
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes
 

2. Set the value of MonadRpcTimeout to 3600 decimal.
 

Supplemental Materials

Value0xe000fe30
Description

A communications failure has occurred


Value0xe00002fe
Description

Cannot log on to MAPI with the specified credentials


ValueV-79-57344-766
Description

Cannot log on to MAPI with the specified credentials



Legacy ID



321060


Article URL http://www.symantec.com/docs/TECH68770


Terms of use for this information are found in Legal Notices