Forum Discussion

Ron_W1's avatar
Ron_W1
Level 3
10 years ago

Agent wont install

I have a vanilla windows 7 x64 professional that I need to get backup exec agent installed on so I can put it into production. I am having trouble getting it installed. If I try to copy over the RAWS64 folder and install the agent locally, I can get the workstation added to backup exec as long as I don't tick the option upgrade when I am adding. However doing it this way the job will not run. It will error out with The job failed with the following error: A communications failure has occurred. Initial searching shows I need to upgrade the agent. 

If I try it by remote push, I get this.

Job started     : Tuesday, December 23, 2014 7:26:44 AM
Job ended       : Tuesday, December 23, 2014 7:28:15 AM
Final error: 0x643 - Fatal error during installation.

Final error category: Other Errors
Completed status: Failed

Really stuck here..

2012
Agents
Backing Up
Backup and Recovery
Backup Exec
Windows 7

16 Replies

Sort By
  • VJware's avatar
    VJware
    Level 6
    10 years ago

    When a local install completes successfully, do verify the remote agent service is started and running under a local system account. If running any AV, set it to exclude from scanning the remote agent service. Lastly, is port 10000 available for use by the remote agent.

  • Ron_W1's avatar
    Ron_W1
    Level 3
    10 years ago

    tasklist /v shows it is running if I do a local install

     

    beremote.exe                  1444 Services                   0     31,908 K Unk
    nown         NT AUTHORITY\SYSTEM                                     0:00:00 N/A

    Port 10000 inbound is open in the windows firewall. 

  • Ron_W1's avatar
    Ron_W1
    Level 3
    10 years ago

    What documentation would that be? Your link just comes back to my post.

  • Ron_W1's avatar
    Ron_W1
    Level 3
    10 years ago

    Laurie, Remote push isn't working at all for me so I can't initiate an upgrade from backup exec, it generates the error you specified in the link. All I can do is a local install but this doesn't work either. The backup job fails with a communication error.

  • Laurie_Downey's avatar
    Laurie_Downey
    Level 6
    10 years ago

    Are you able to ping the Backup Exec server from the remote computer and vice versa. You also may want to confirm a trust has been established by right clicking on the remote server from the Backup Exec console servers list, and selecting the option for "Establish trust".

    Also confirm the following possiblities:

    1. Firewall is blocking the communication.
    2. Antivirus is blocking the Backup Exec services
    3. IPv6 is enabled on one server
    4. The publishing tab of the remote agent has an incorrect entry for the Backup Exec Server name or IP address

     

  • Ron_W1's avatar
    Ron_W1
    Level 3
    10 years ago

    I can ping yes. Both ways, from the workstation to the server and from the server to the workstation. can't establish a trust though..  

  • Ron_W1's avatar
    Ron_W1
    Level 3
    10 years ago

    I forgot to restart the agent :o so I was able to establish a trust but still no go on updating

    Job started     : Tuesday, December 23, 2014 10:24:16 AM
Job ended       : Tuesday, December 23, 2014 10:24:22 AM
Final error: 0x643 - Fatal error during installation.

Final error category: Other Errors
Completed status: Failed

    And running the job gives me communication error.

    No Antivirus on the machine
    IPV6 is enabled on both systems (its not disabled on any of our systems)
    Publishing tab shows the correct server
    Firewall has an inbound port open for TCP 10000

     

  • Laurie_Downey's avatar
    Laurie_Downey
    Level 6
    10 years ago

    Does the publishing tab of the remote agent list the Backup Exec server by name and IP address in the top box, and the name of the remote server in the bottom box?

    Also try logging into the Backup Exec Server with the Backup Exec Service account and updating the agent once more. If you are already logged in with the service account try referring to the following document and confirm all permissions are being met.

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