Troubleshooting issues with deploying the Backup Exec System Recovery (BESR) or Symantec System Recovery (SSR) agent

Article:TECH56222  |  Created: 2008-01-01  |  Updated: 2014-02-06  |  Article URL http://www.symantec.com/docs/TECH56222
Article Type
Technical Solution


Subject

Issue



When deploying a Backup Exec System Recovery (BESR) or Symantec System Recovery agent an error message from the list below occurs and the deployment fails.


Error



The following errors might appear in the pushlog.txt file or in the product interface while deploying the BESR agent.
  • Attempt to connect to remote computer failed
  • Attempt to copy RemoteCmdSvc.exe to remote computer failed
  • Attempt to access the remote Service Control Manager failed
  • Attempt to create the RemoteCommand Service on the remote computer failed
  • Attempt to start service on the remote computer failed
  • Attempted connection to RemoteCmdSvc on remote computer failed
  • Attempt to push package to remote computer failed due to an invalid environment
  • Attempt to copy package failed
  • Attempt to communicate with RemoteCommand Service on remote computer failed
  • Remote command failed to start
  • Attempt to restart remote computer failed
  • Attempt to delete package failed
  • RPC server is unavailable

Solution



 


Attempt to connect to remote computer failed

The product was unable to establish a network connection to the requested computer. This error is usually reported when the current user does not have administrative privileges on the remote computer. This error might also occur if network communication problems exist, the two systems are not sharing the same version of NTLM authentication, or if a software/OS/hardware Firewall between the system and the console is not configured to allow remote deployment of the agent. To verify connectivity Please review Troubleshooting Communication Issues With Backup ExecSystem Recovery (BESR) : www.symantec.com/docs/TECH55824

Attempt to copy RemoteCmdSvc.exe to remote computer failed

The product was unable to copy the remote service executable (RemoteCmdSvc.exe) to its destination on the remote computer. This error is usually reported when the product cannot find the RemoteCmdSvc.exe source, or it is unable to write to the destination computer's Admin$\temp directory.

Attempt to access the remote Service Control Manager failed

The product was unable to connect to the Service Control Manager on the remote computer. This error is usually reported when the current user does not have administrative privileges on the remote computer. This error might also occur if network communication problems exist.

Verify that the current user has appropriate administrator privileges on the remote computer.

Attempt to create the RemoteCommand Service on the remote computer failed

The product was unable to connect to the RemoteCmdSvc service on the remote computer. This error is usually reported when the RemoteCmdSvc is already running on the remote computer.

To correct the problem, either restart the remote computer or manually stop and remove the RemoteCmdSvc service from the remote computer.

Attempt to start service on the remote computer failed

The product was unable to start the RemoteCmdSvc service on the remote computer. This error is usually reported when the RemoteCmdSvc is already running on the remote computer.

To correct the problem, either restart the remote computer or manually stop and remove the RemoteCmdSvc service from the remote computer.

Attempted connection to RemoteCmdSvc on remote computer failed

The product was unable to start the RemoteCmdSvc service on the remote computer. This error is usually reported when the RemoteCmdSvc is already running on the remote computer.

To correct the problem, either restart the remote computer or manually stop and remove the RemoteCmdSvc service from the remote computer.

Attempt to push package to remote computer failed due to an invalid environment

The product was unable to copy the package files to the remote computer. This error occurs under the following circumstances:
 
  • Corrupted package files:  Correct this problem by reinstalling the product.
  • Poor connection to the RemoteCmdSvc service on the remote computer: To correct this problem, restart the remote computer. Then, try again to do the operation.

Attempt to copy package failed

The product was unable to copy the package files to the remote computer. This error is usually reported when the package files are left open on the remote computer from a previously failed copy.

To correct this problem, restart the computer. Then, try again to deploy the agent.

Attempt to communicate with RemoteCommand Service on remote computer failed

The product was unable to communicate with the RemoteCmdSvc service.

To correct this problem, restart the remote computer or manually stop and remove the RemoteCmdSvc service from the remote computer.

Remote command failed to start

The product was unable to run the specified remote command. This error occurs when the remote installation package encounters an error.

To correct this problem, restart the remote computer, or manually stop and remove the RemoteCmdSvc service from the remote computer.

Attempt to restart remote computer failed

The product was unable to force the remote computer to restart. This error occurs when the current user does not have the SE_SHUTDOWN_NAME privilege enabled. It can also occur when the current user on the remote computer does not have the SE_REMOTE_SHUTDOWN_NAME privilege enabled.

Attempt to delete package failed

The product was unable to delete all of the package files that it copied to the remote computer. This error occurs when a file that is running stops responding.

To correct this problem, restart the remote computer.

RPC server unavailable

If a computer name is longer than 14 characters, you must shorten the computer name while adding it to the Computer List.

If the computer name is no longer unique on the network, you must rename the computer in Windows Properties.

Supplemental Materials

ValueV-281-211-60352
Description

Cannot deploy the agent.



Legacy ID



295041


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


Terms of use for this information are found in Legal Notices