How to troubleshoot backups that fail with Error "e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent."

Article:TECH73015  |  Created: 2009-01-31  |  Updated: 2013-06-25  |  Article URL http://www.symantec.com/docs/TECH73015
Article Type
Technical Solution

Product(s)

Issue



How to troubleshoot backups that fail with Error "e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent."


Error



e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer.

UMI :- V-79-57344-3844


Cause



This could happen due to one or more of the following reasons:

1. The server name in the selection list may contain an invalid character.
2. Remote Agent version mismatch.
3. Remote Server is Powered Down.
4. Remote machine is no longer connected to the network or available for backup.
5. Backup Exec is unable to connect with any remote servers.
6. If the Backup Exec Remote Agent Service is stopped or disabled on the Target Machine.


Solution



Scenario 1:  
 
Details :

This can be seen in the XML job log. The item in the selection list is corrupt and needs to be removed and re-selected.
Example of a resource that can fail with the error --  System State.

Solution:

Edit the backup job and remove the selection in Text View of the backup selection list.
Then select the resource again for backup and save the job.

For additional Information on how to edit Selection list , please refer document below :
 
Editing selection lists
www.symantec.com/docs/HOWTO11779

Scenario 2:

Details:  
 
The Remote Agent on the target server is a newer version than the Media Server. This is possible if the Remote Agent was originally installed from a newer version of Backup Exec.

Solution:

Apply all the latest patches for Backup Exec to the media server and make sure the correct version of Remote Agent for Windows System ( RAWS ) is installed on the remote server.

OR

Uninstall the Remote Agent.  Then reinstall the remote agent from the current Media Server.

For Additional information on how to push install the Remote Agent for Windows System ( RAWS ),Please refer document link below:
 
How to push install the Remote Agent for Windows Servers (RAWS) from the Backup Exec Media Server Console
http://www.symantec.com/docs/TECH127916

How to push install the Backup Exec Remote Agent for Windows Servers in Backup Exec 11d & above
http://www.symantec.com/docs/TECH36546

How to perform a local / manual installation for the Backup Exec 2010 Remote Agent for Windows Servers ( RAWS ) and Advanced Open File Option (AOFO)
http://www.symantec.com/docs/TECH128757


Scenario 3:

Details :

The remote server for which the backup job is failing could be turned off [At times due to power outages] or the Remote Agent for Windows System ( RAWS ) is not started  due to errors .

Solution:
Turn on the remote server and ensure that  Backup exec remote agent service is running, then Re-run the Backup's .
 
Scenario 4:

Details:
 
The machine will not be shown in the Backup Exec Graphical User Interface (GUI) or in graphical selections because it is no longer displaying itself on the network.  The error is generated because the job definition still contains a reference to the data on that particular machine. To resolve this, edit the backup job definition to delete the entry for this machine manually from the "View Selection Details".
 
  
 
 1. From the Job Setup tab, right-click on the backup job.
 2. Select Properties
 3. Select the Selections option.
 4. Click on "View Selection Details."
 5. Locate and delete all entries referring to the machine generating the error and submit the changes.

 WARNING: Media servers cannot completely protect remote Windows-based servers or workstations unless the Backup Exec Remote Agent is installed and running on each remote Windows-based server or workstation to be protected. Data loss can occur if the Remote Agent is not running while backing up remote Windows-based computers.
www.symantec.com/docs/TECH64229

Scenario 5:

Details:

Verify this scenario by creating a new backup selection list. The list might be empty with a connection error.

Solution:
-Check the backup Exec System Logon Account credentials.
-Review the Technote TECH139808 linked below in the related articles.


Supplemental Materials

SourceUMI
ValueV-79-57344-3844
Description

The media server was unable to connect to the Remote Agent on machine Server Name. The media server will use the local agent to try to complete the operation. Remote Agent not detected on \\ServerName


SourceError Code
Valuee000846b
Description

The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer.



Legacy ID



329201


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


Terms of use for this information are found in Legal Notices