Veeam Backup Transport -- Error 1723

What account are you using to add the Hyper-V host?  It has to be local administrator or group.

using a domian admin account, Veaam is not on the domain, i have 2 standalone hosts same os (2022), same network, on the same domain, same hardware one host works fine added a test backup job completed fine, the other host fails to install transport components when add in to infrastructure.

If using a domain admin but not on the domain that will not work.  You need to use a local admin account on the server.

Hi,

I encountered similar issues when trying to add a Hyper-V host or cluster with a user who was not the built-in local admin or a domain admin. This was due to UAC being triggered, which prevented Veeam from installing the packages.

One possible solution is to manually install the packages on the host and then add the host to Veeam.

The packages you need to install are:

• VeeamHvintegration.msi
• VeeamInstallerSvc.msi
• VeeamTransport.msi

You can find these files on the Veeam ISO under “D:\packages” or on the veeam Server under “C:\Program Files\Veeam\Backup and Replication\Backup\Packages”

Actually UAC is another good call out here and getting that turned off as it causes many issues.  You can also try the MSI files too.

I think I have to disagree for the first time ​@Chris.Childerhose but please correct me again.

As from my experience you can add a domain joined Hyper-V (both host and cluster) as part of an AD domain even if the Veeam server is not part of the domain.

As Chris mentioned just the service account (credential object you use in Veeam) for the connection has to have the required rights on the target (Hyper-V). Please try to add the account you are using to the local admin group of the Hyper-V servers and try again. Even if the account is a domain admin it doesn’t automatically indicate that it has the required rights on a server.

If that doesn’t work either please try to temporarily disable the Windows firewalls on the systems (both Veeam and Hyper-V) just to not run into firewall issues.

Best

Lukas

Yes you can add a domain joined machine - the issue here was using a domain admin account for a non-domain joined Hyper-V server.  I never stated you cannot use a domain joined Hyper-V host. 😉

I have to refresh the pages before, didn’t see the whole conversation.

Ok ​@Chris.Childerhose, I understood that the Hyper-Vs are both members of the AD. My bad.

No worries at all.  It is hard to keep up some times and the refresh of posts and replies.  😂

Hi Guys, 

thank you for your replies.

just to recap,

i have a Veeam server not domain joined 

2 hv hosts domain joined (not Clustered just replicas)

credentials added to the Veeam server to use to connect to hv hosts are ad domain admin i have added individually to the local admin group on the host not working too.

one host added to Veeam and a backup taken all good

the second host won’t attach to Veeam,

i thought i found something regarding Visual C++ needing to be 2015-2022 but on the non working host it was 2012 for some reason, i have updated still same.

when you say run the msi do you mean copy those msi to the host and run from there ? then go back to the veeam run gui add server or would that have been added then ?

thank you for your assistance.

Hi ​@MI101,

Yes this is exactly what i ment.

1. Copy and Install the *.msi packages directly on the HyperV Host
2. try to add HyperV server from veeam gui

Regards

Chalid

i have tried to install locally 

VeeamIntegration.msi - installed ok

VeeamInstallerscv.msi - fails same as GUI error

VeeamTransport.msi - fails same as GUI error, 

can you try the package on another Server?

Can you try to install the msi packages with the local Admin User?

Maybe download the veeam ISO again and take the Packages from there. 

Hi,

after installing Veeam this was the first Host server i tried it failed so i went to the second host server that worked and then i went back to the first host it still fails. when manually installing i took the files from the ISO, so i would assume files are ok as i downloaded the image fresh during installation of the Veeam server yesterday.

Thank you

Have you tried to reboot the Host before installing the packages?

Are there any Patches pending?

It seems to mee that there is an issue with the Host and not with veeam.

ok will try reboot and advise.

patches seem similar, updates last installed 11 /4 /25, last checked 03:00 today, non pending

Also check permissions again as the error coming up from the MSI installers that are not working are indicating permissions.  Yes I know you have checked but the warning still shows it is checking for admin rights.

Also check this page about permissions - Permissions - User Guide for Microsoft Hyper-V

i have checked permissions, also logged in as .\administrator still same issue. 

I have also run into this issue today.

Hi ​@MI101 ,

Then i think it would be the best to Open a Case with veeam Support to figure Out the what the issue ist.

Maybe you can keep us posted about the outcome. 

Regarda

Chalid

This should work so as noted open a ticket and get support involved now as we have probably given as much help as we can.

I got this back from support:

It appears that the issue you're encountering is a known one related to the upgrade to version 12.3.1.1139, based on the feedback we've received from other customers as well.

The root cause is associated with the WDAC Policy on the Cluster Nodes.

To attempt resolving this issue, please disable the policy during the upgrade of the Cluster Nodes and then re-enable it afterward.

Just logged onto a node and ran the PS command

Enable-AsWdacPolicy -Mode Audit

Attempted to run the update again from Veeam. this time it was successful, then I re-enabled WADC.

Dan

Great to hear you got an answer to this issue and shared the solution to help others.