BERS 2010 - Remote Procedure Call fails-Error

[conzepta]

hello,

at first i wish you a happy and powerful new year 2011.

now to my problem:

on a windows server 2008 r2 x64Bit machine runs BERS 2010.

BERS 2010 runs for weeks whitout any problem.

now i needed to build in a new HDD to increase the backup storage.

but now i run all the time in the same problem/error...

during the execution of a backup task (near 94%) it shows me all the time the same messages.

at first it seems that the connection to agent it lost. it shows the following message (translated from german to english):

Attachment1:

"The Connection to the Remote-Agent was disconnected - Please close the window"

Attachment2:

the next message, a error msg, shows: "The Remote Procedure Call fails"

Attachment3:

and at the end, the state/status and  performance windows shows me:

Error 800706be during executing task...

what can i do to solve this problem ?

thank you for your support

[NeerThadarai]

Have you checked this

http://www.symantec.com/docs/TECH61566

Also go through below suggestions which might help.

Error 800706BA is a standard Windows error with many causes. It most often refers to Microsoft COM Internet Services (CIS) on the Distributed Component Object Model (DCOM) client call RPC_S_SERVER_UNAVAILABLE; the RPC server is unavailable (Windows Event ID 1722). It is when a RPC query times out and error 800706BA is the result. The following steps have been shown to resolve this issue:

Retry the Recovery Point backup job after a period of time has elapse

 

• The error can occur when the Backup Exec System Recovery system is under high CPU or memory usage by other services or applications. Wait until those applications finish and attempt the backup. For best practice guidelines on performing recovery point creation please refer to Symantec Backup Exec System Recovery User's Guide Best practices for backing up Chapter 3.
  

Verify Distributed Component Object Model (DCOM) settings

 

• 1. Click Start > Run.
  2. In the Open box, type DCOMCNFG.EXE, and then click OK
  3. Expand Component services.
  4. Expand computers.
  5. Right click the local computer and choose Properties
  6. Select the Enable Distributed COM on this computer check box; if not already selected.
  7. From the Default Authentication Level, select Connect.
  8. From the Default Impersonation, select Identify.
  

Restart RPC service

 

• Make sure that the remote procedure call (RPC) services are started on the Backup Exec System Recovery system.
  
  
  1.      Click Start > Run.
  2.      In the Open box, type services.msc, and then click OK
  3.      Do the following:
  �      Make sure the Remote Procedure Call (RPC) Service is started and set to start automatically
  
  • • a.      Right click on Remote Procedure Call (RPC)
      b.      Click Properties
      c.      Select Automatic for the Startup Type field
      d.      Click START (if not started) for Service status.
      e.      Click  OK
      
  �      Make sure the Remote Procedure Call (RPC) Locator service is started and set to start automatically
  
  • • a.      Right click on Remote Procedure Call (RPC) Locator
      b.      Click Properties
      c.      Select Automatic for the Startup Type field
      d.      Click START (if not started) for Service status.
      e.      Click  OK
      

Stop Anti-Virus Services and disk monitoring tools (e.g. OpenView, Insight Manager)
 

• 
  Applications that make continuous read and writes to the drive Backup Exec System Recovery is attempting to backup and or if these applications establish a security level lock to the drive at the time Backup Exec System Recovery is attempting to create its snapshot imaging during the recovery point imaging process could generate this error. Take precautions when disabling security software when using  Backup Exec System Recovery to create a backup.  
  
  

Reboot target server

 

• Prior to next schedule backup by Backup Exec System Recovery, at the next schedule down time of the system, perform a complete shutdown of the system.
  

Verify DNS settings when backing up to a network share location


 

• Backup Exec System Recovery will report this error occurs when DNS servers are not configured properly when backing up to a network share. Possible network connectivity issue usually DNS is not set properly. If the above suggestions do not correct this error, perform the following steps:
  
  
  
  • �      Verify that address for the configured preferred DNS server on Backup Exec System Recovery client system on the client is valid and reachable.
    
    �      Use NSLOOOKUP and IPCONFIG /ALL to displayed DNS Server settings.  Check the TCP/IP configuration for a local incorrect DNS Server settings. Local settings will overwrite settings from the DHCP Server. By deleting the local DNS setting and switching to auto configuration DNS server settings should be corrected.
    
    �      Check if the storage and client systems have DNS entries. If not make sure dynamic updates are enabled on the DNS server and schedule a restart of the netlogon server on each DC.
    
    �      Check for symptoms where new Global Domain Users cannot not be added to a Local Group in Computer Management -> Local Users and Groups -> Groups. Correct this by configuring the network adapters to point to the correct DNS servers on the network.
    
    �      Verify that the Backup Exec System Recovery client is pointing to the DNS server on same domain as the share.
    
    �      Make sure the authoritative time server is set correctly.
    
    �      Verify that the Backup Exec System Recovery client system can ping the storage system by fully qualified domain name if not from a command prompt use the ipconfig /flushdns and /registerdns and try again.
    
    �      Make sure that if the Backup Exec System Recovery client system has multiple adapters, the adapter that resolves to the storage location is listed first in the adapter binding order in the Advanced settings of Network and Dial-up Connections. Otherwise, DNS resolver may use the DNS server for the adapter listed first that may not resolve to the storage location correctly.
    

Below also are Microsoft Articles that may be helpful:

http://support.microsoft.com/kb/197814
http://support.microsoft.com/default.aspx/kb/265340

[Sush--- · Accepted solution]

Please follow these technotes;

http://www.symantec.com/docs/TECH83833 : Backup fails with "the remote procedure call failed" during process of creating new image file

http://www.symantec.com/docs/TECH63088 : One job fails with errors E0BB00B5 and E0BB03F1, while other jobs run correctly 

http://www.symantec.com/docs/TECH62711 : Remote Procedure Call Failed" occurs when attempting to backup to an external USB Drive

http://www.symantec.com/docs/TECH135334 : Backup Exec System Recovery (BESR) hangs up after error EBAB0013 occurs

Thanks,

-Sush...

[conzepta]

thanks to you both for supporting me!!!

this solved my problem:

The offending job was likely corrupted; after deleting it and recreating a new job to replace it, the errors were eliminated.

See:

http://www.symantec.com/docs/TECH63088 : One job fails with errors E0BB00B5 and E0BB03F1, while other jobs run correctly