Disaster recovery orchestration for the Enterprise (formerly Veeam Availability Orchestrator)
Post Reply
davis_b
Enthusiast
Posts: 31
Liked: never
Joined: Jan 03, 2017 3:11 pm
Full Name: Brent Davis
Contact:

Failed to install via Admin Share

Post by davis_b »

I am building out some test plans and I am attempting to test an IIS website but I am getting the failure "Failed to install via Admin Share" It's been a while but I have gotten this test to work before but now I can't. I have a domain controller and dns server in the test plan as well since it's an AD service account that runs the IIS web site. Anyone else seen this and resolved? If not, I'll have to get a case opened.


Thanks!
Alec King
VP, Product Management
Posts: 1495
Liked: 382 times
Joined: Jan 01, 2006 1:01 am
Contact:

Re: Failed to install via Admin Share

Post by Alec King »

Hi, my first guess is that VRO is trying to upload the test script via ADMIN$ and failing. Can you check for the existence of that share and the permissions?
davis_b
Enthusiast
Posts: 31
Liked: never
Joined: Jan 03, 2017 3:11 pm
Full Name: Brent Davis
Contact:

Re: Failed to install via Admin Share

Post by davis_b »

I can confirm the share is there and permissions are correct. The account I am using to connect is a local admin.
davis_b
Enthusiast
Posts: 31
Liked: never
Joined: Jan 03, 2017 3:11 pm
Full Name: Brent Davis
Contact:

Re: Failed to install via Admin Share

Post by davis_b »

Correct if I am wrong, but isn't the VRO server supposed to automatically add routes of the masqueraded IP's to the data lab helper proxy to then connect to the associated endpoint in the bubble network?
TWuser
Enthusiast
Posts: 36
Liked: 6 times
Joined: Sep 07, 2021 5:37 pm
Full Name: TW
Contact:

Re: Failed to install via Admin Share

Post by TWuser »

Did you solve this?

I'm getting this error pretty often lately too. Unfortunately it's a bit random, as I can run a Plan and have 2 VMs have the issue, and then run it again and have several others have the issue.
I wish I had a better answer than bad luck/timing. I've added delay timers to give the VM more time to boot before the custom script/tests run, but that still isn't 100%. Sometimes Windows Update or VMware Tools may be a cause, other times I just have no good reason.

If your tests have the same error EVERY time, then that's preferable as it could be something simple like credentials. Can you try a more basic test on a "normal" VM first, then try it on the DC? Running a powershell script on a DC I'm pretty sure would require Domain Admin privileges and would be a common hangup.
Post Reply

Who is online

Users browsing this forum: Bing [Bot], mwisniewski and 1 guest