Comprehensive data protection for all workloads
Post Reply
ssdn108
Influencer
Posts: 14
Liked: 1 time
Joined: Mar 15, 2024 7:05 am
Full Name: Aman Nangia
Contact:

Installing VBR v12.3.2.4165 (latest build) in Azure win2022 VM; failing to start veeamtransport service

Post by ssdn108 »

hi,
Brand new install of VBR v12.3.2.4165 on win2022 in azure, and it's failing with below.

failed to start veeamtransportsvc service. click retry to attempt to stop the service again. click cancel to exit setup.

It's a non-AD joined VM (workgroup call BCDR).
All Ports are open.
Defender Firewall is off.
It fails in the end during module 8 of 8 load with the above msg.
I did retried few times, and it still fails after 3 or 4 mins.

any clue?
petesteven
Veeam Vanguard
Posts: 15
Liked: 4 times
Joined: May 08, 2018 7:34 am
Full Name: Peter Steffan
Contact:

Re: Installing VBR v12.3.2.4165 (latest build) in Azure win2022 VM; failing to start veeamtransport service

Post by petesteven »

Hi,

This installation error in is typically related to service account (i normally use local service instead of service account), permissions, or system environment issues.
Does your VM has the required system requirements? (CPU, RAM..)
Does the VM has any hardending?
Is UAC disabled? (https://learn.microsoft.com/de-de/troub ... estriction --> localaccounttokenfilterpolicy)
Peter Steffan - My Blog: petersvirtualworld.de; VMCE2024, VMCA2024, Vanguard
ssdn108
Influencer
Posts: 14
Liked: 1 time
Joined: Mar 15, 2024 7:05 am
Full Name: Aman Nangia
Contact:

Re: Installing VBR v12.3.2.4165 (latest build) in Azure win2022 VM; failing to start veeamtransport service

Post by ssdn108 »

yeah..it's local a/c. Apparently, i don't know what it was. We did cancel and knowing it did not installed fully, i removed the registry contents from HKLM for Veeam, to retry install after removing Veeam. Then noticed that several pkgs were successfully installed in control panel>programs and they failed to get uninstalled when i tried to uninstall VBR as registry components were partially removed. So, it was in a messy state.

Finally, we rebuild that same VM in azure, and interestingly, this time no error came up in the install; so, all good with the install. Never had this issue in past.

Only thing i can think of is time-out but we did tried retry several times prior to cancelling (just not manual start of service or all services)

I do have the svc.veeambackup.log file saved from prior failed session if someone is interested to see.

all good for now though.
Thx
Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests