Document ID: 295041
http://support.veritas.com/docs/295041
E-Mail this document to a colleague
http://support.veritas.com/docs/295041
E-Mail this document to a colleague
Troubleshooting issues with deploying the Backup Exec System Recovery (BESR) agent
Details:
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 or if the Windows Firewall is not configured to allow remote deployment of the agent.
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:
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.
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 unavailable
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 or if the Windows Firewall is not configured to allow remote deployment of the agent.
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 Material:
| System: Ref.# | Description |
| UMI: V-281-211-60352 | Cannot deploy the agent. |
Products Applied:
Backup Exec System Recovery Desktop Edition 6.5, 7.0, 7.0 7.0.1, 7.0 7.0.2, 7.01, 8.0
Backup Exec System Recovery Option 11.0, 12.0
Backup Exec System Recovery Server Edition 6.5, 7.0, 7.0 7.0.1, 7.0 7.0.2, 7.01, 8.0
Backup Exec System Recovery Windows Small Business Server Edition 6.5, 7.0, 7.0 7.0.1, 7.0 7.0.2, 7.01, 8.0
Backup Exec System Recovery Desktop Edition 6.5, 7.0, 7.0 7.0.1, 7.0 7.0.2, 7.01, 8.0
Backup Exec System Recovery Option 11.0, 12.0
Backup Exec System Recovery Server Edition 6.5, 7.0, 7.0 7.0.1, 7.0 7.0.2, 7.01, 8.0
Backup Exec System Recovery Windows Small Business Server Edition 6.5, 7.0, 7.0 7.0.1, 7.0 7.0.2, 7.01, 8.0
Last Updated: April 01 2008 08:01 PM GMT
Expires on: 12-24-2017
Subscribe to receive critical updates about this document
Expires on: 12-24-2017
Subscribe to receive critical updates about this document
Subjects:
Backup Exec System Recovery Desktop Edition
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Option
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Server Edition
Application: Troubleshooting
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Windows Small Business Server Edition
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Desktop Edition
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Option
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Server Edition
Application: Troubleshooting
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Windows Small Business Server Edition
Install / Uninstall: Install/Uninstall
Languages:
English (US)
English (US)
Operating Systems:
Windows 2000
Windows 2000
Advanced Server SP4, Professional SP4, Server SP4
Windows XP
Home 5.1 SP2, Pro 5.1 64 bit SP2
Windows Server 2003
DataCenter, DataCenter (IA64), DataCenter (x64), DataCenter SP1, DataCenter SP1(IA64), DataCenter SP1(x64), DataCenter SP2, Datacenter SP2(x64), Enterprise (IA64), Enterprise (x64), Enterprise SP1(IA64), Enterprise SP1(x64), Enterprise SP2, Enterprise SP2(x64), Enterprise Server, Enterprise ServerSP1, R2, Standard Server, Standard Server SP1, Standard Server SP1 (x64), Standard Server SP2, Standard Server SP2 (x64), Standard Server(x64), Storage Server, Storage Server SP1, Storage Server SP2, Web Server, Web Server SP1, Web Server SP2
Windows Small Business Server 2003
Premium Edition, Premium Edition R2, Premium Edition SP1, Standard Edition, Standard Edition R2, Standard Edition SP1, Standard Edition SP2
Windows Vista
Business (x64) 6.0.6000, Business (x86) 6.0.6000, Enterprise 6.0.6000, Home Basic (x64) 6.0.6000, Home Basic (x86) 6.0.6000, Home Premium (x64) 6.0.6000, Home Premium (x86) 6.0.6000, Ultimate (x64) 6.0.6000, Ultimate (x86) 6.0.6000
Windows Server 2008
DataCenter (x64-64bit), DataCenter (x86-32bit), Enterprise (x64-64bit), Enterprise (x86-32bit), Itanium, Standard (x64-64bit), Standard (x86-32bit), Web Server (x64-64bit), Web Server (x86-32bit)
Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.