Skip to main content

Agent deployment issue - VBR Community edition

  • September 25, 2024
  • 7 comments
  • 303 views
B

Hi,

I’m experiencing issues with deploying VBR Agent on 2 Domain Joined Workstations using VBR 12.2.0.334 Community Edition.

I know that I am on my own here, but maybe someone has a good idea what could cause the problem.

When I try to install the client from the VBR console, it fails with the error: 

 

25-09-2024 17:30:10 Failed Unable to install backup agent: failed to connect to COMPUTER1 Error: Cannot find package version for component EpAgent package Msi platform X86. 

 

I can install the agent manually, but that doesn't help either. 

VBR can see the computer in the console and get’s the OS edition (Windows 10 Pro 22H2) and IP address.

Thanks in advance,

 

Bjorn Dirchsen

Chris.Childerhose
Madi.Cristil
leduardoserrano

7 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • September 25, 2024

The first part of the message indicates it cannot connect to Computer1.  Are you using the correct credentials and can the VBR server resolve (ping) the FQDN of the agent computer you are trying to install on?

 
 
 
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
B
  • bjoernsifi
  • Author
  • Not a newbie anymore
  • September 25, 2024

Ping is OK.

Name resolution works.

Access to Admin$ fileshare is working

Credentials is working (tested)

Firewall is disabled on endpoint (COMPUTER1)

… 

Chris.Childerhose
Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • September 25, 2024

Ok so every test passes which is good.  Trying to determine what else to check, but even though you use CE edition you can open a support case but it is best effort support.  It might be quicker unless others have ideas.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
B
  • bjoernsifi
  • Author
  • Not a newbie anymore
  • September 25, 2024

Ok. I’ll give their support a try then. Thx for the info.

Yeah, I couldn't figure it out myself either using the basic skills :)

 

Best regards,

 

Bjorn Dirchsen

Chris.Childerhose
Chris.Childerhose
Forum|alt.badge.img+21
  • Chris.Childerhose
  • Veeam Legend, Veeam Vanguard
  • September 25, 2024

Ok. I’ll give their support a try then. Thx for the info.

Yeah, I couldn't figure it out myself either using the basic skills :)

 

Best regards,

 

Bjorn Dirchsen

Not a problem.  Keep us posted if you discuss with Support and the resolution so we can mark a best answer for this thread.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 6* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
P
  • PrivUser2025
  • New Here
  • August 21, 2025

I am seeing this issue when I try to back up the Veeam / host server. 

All VMs are backing up fine, but when I try to back up the server, I am getting error: 

Veeam "Error: Cannot find package version for component EpAgent package Msi platform X64"

 

Confirmed DNS is working fine and ADMIN$ share is working. 

 

Did you ever figure this out? 

 

Also found this: 

So I am trying first to do an in-place upgrade and then I will try uninstall / reinstall / restore config. 

P
  • PrivUser2025
  • New Here
  • August 21, 2025

I was able to resolve this by running the latest ISO installer, then clicking modify.

It installed/updated the ‘agent’ components, I removed and re-added my server backup job from Backups and the device from inventory, and when re-added, it successfully deployed the agent.

Chris.Childerhose
Terms & ConditionsAccessibility statement