Document ID: 291747
http://support.veritas.com/docs/291747
E-Mail this document to a colleague
http://support.veritas.com/docs/291747
E-Mail this document to a colleague
Attempting to deploy an agent from Backup Exec System Recovery (BESR) Console/UI resulted in error, 'Attempt to push package to remote computer failed due to an invalid environment.'
Exact Error Message
"Attempt to copy package failed"
"Cannot deploy the Agent to <ComputerName>
Attempt to push package to remote machine failed due to an invalid environment"
Error: "Cannot deploy the agent...exception occurred: Attempt to push package to remote machine failed due to an invalid environment.
"Attempt to copy package failed"
"Cannot deploy the Agent to <ComputerName>
Attempt to push package to remote machine failed due to an invalid environment"
Error: "Cannot deploy the agent...exception occurred: Attempt to push package to remote machine failed due to an invalid environment.
Details:
This error can occur for the following reasons.
Not enough disk space on the computer.
Ensure that the following available space is available:
Firewall is enabled preventing access to the target computer.
Uninstall and reinstall .NET 2.0 on client system
Agent setup files on console/UI are corrupted.
This error can occur for the following reasons.
- No access the Admin$ and C$ share with the currently logged in user on the BESR console/UI system.
Ensure there is access to this share by doing the following:
- 1. Verify the IP address of the computer the Agent.
2. Go to START | RUN open field, type: <IP address of the machine you are trying to deploy the Agent to>\admin$
3. Click OK
NOTE: If an error occurs or a request for credentials and the credentials provided does not allow access; correct the network/permission issues first before re-attempting agent deployment.
Not enough disk space on the computer.
Ensure that the following available space is available:
- - Agent install requires: 60 MB.
- .NET Framework 2.0: 280 MB of hard disk space is required for 32-bit computers, and 610 MB is required for 64-bit computers
Firewall is enabled preventing access to the target computer.
Ensure that the ports needed by BESR console/UI are available and open between the console and agent systems. For more information on the ports used by Backup Exec System Recovery please refer to the appropriate Related Document technote below.
- - Check if the File and Print Sharing for Microsoft Networks service in enabled in the network card properties on the agent system.
- Be sure Simple File Sharing is turned off (XP clients) to prevent authentication issues.
Uninstall and reinstall .NET 2.0 on client system
- Before re-attempting to install agent from the management console do the following
- 1. Reinstall .NET 2.0 on the client system
2. Reboot
Agent setup files on console/UI are corrupted.
- 1. Uninstall and reboot Backup Exec System Recovery management computer.
2. Reinstall and reboot Backup Exec System Recovery management computer.
3. Reattempt the Agent deployment to client system(s).
Related Documents:
http://support.veritas.com/docs/290775
http://support.veritas.com/docs/293215
http://support.veritas.com/docs/293846
http://support.veritas.com/docs/294526
http://support.veritas.com/docs/295041
http://support.veritas.com/docs/290775
http://support.veritas.com/docs/293215
http://support.veritas.com/docs/293846
http://support.veritas.com/docs/294526
http://support.veritas.com/docs/295041
Products Applied:
Backup Exec System Recovery Desktop Edition 6.5, 7.0
Backup Exec System Recovery Server Edition 6.5, 7.0
Backup Exec System Recovery Windows Small Business Server Edition 6.5, 7.0
Backup Exec System Recovery Desktop Edition 6.5, 7.0
Backup Exec System Recovery Server Edition 6.5, 7.0
Backup Exec System Recovery Windows Small Business Server Edition 6.5, 7.0
Last Updated: September 29 2008 12:40 PM GMT
Expires on: 09-25-2018
Subscribe to receive critical updates about this document
Expires on: 09-25-2018
Subscribe to receive critical updates about this document
Subjects:
Backup Exec System Recovery Desktop Edition
Install / Uninstall: Install/Uninstall
Backup Exec System Recovery Server Edition
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 Server Edition
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, Advanced Server Windows Powered, Datacenter Server, Professional, Server
Windows XP
Pro 5.1
Windows Server 2003
DataCenter, Enterprise Server, Standard Server, Storage Server, Web Server
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.