Forum Discussion
Cannot create hostpool (or any other ARM WVD 'resource') - Validation failed
Hi,
We are currently running on wvd fall 2019 and it is working perfectly.
I want to create a new WVD environment in the spring update (ARM).
However, if I try to create a host pool, it fails every single time at validation:
Validation failed. Required information is missing or not valid.
Everything is filled in correctly and it does not give me any additional details as to what the issue is. It doesnt matter if i attempt to create VMs and Workspaces or not during the host pool creation wizard - it always fails on validation.
Any ideas?
Raaert Forgot to mention, go to the Resource Group you specified and look in the Deployments blade and see what information is logged there; attached is an example of what you should see
- No errors in rg deployments - because it fails during validation so I never get to deploy it.
Raaert when I try to fill out information incorrectly, I get a different error and I get a red dot above the area that is causing the error, for example if miss a parameter I see the included clip below; I do not see that in any of your images.
I was not able to recreate the error message you see; I noticed that your gallery image looks to be your own and not one from the drop down menu defaults (clip below), try selecting one of those and again see if that gives same error; it may help in troubleshooting and narrow down areas where the issue is not, and if this works it validates the other fields are correct so must be attributed to maybe the image being used in that case. Apologies than other than that I would not know what the issue is; maybe others have further ideas.
Raaert can you provide screenshots of each of the tabs (Basics | Virtual Machines| Workspaces) showing what you selected.
SteveMiles70
Here is a screenshot of each tab.. it doesnt matter if i only try to create the host pool or also VM/workspace in the wizard, it fails regardless without telling it fails.Raaert I will investigate in my lab to see if can recreate failure; be sure to check AD setup and Connectivity such as custom dns set on the VNET so can find Domain Controllers, the domain join account you are using has the correct credentials and permissons.
As a side note, and extra setting/ step you dont need is the 'Specify domain or unit' you can set this to No if the adminstrator account for the ad domain join UPN is in the same domain you are specifying, as it will automatically join to the domain from that taken from the ad domain join UPN; you would only need to say yes if you actually and specifically need to specify a domain other than that from the ad domain join upn, or specify an OU path which you havent. hope that makes sense.
SteveMiles70
I uploaded the picture from the last page (review+create).
The picture is of the most simple stuff i can choose without choosing VM or workspace.
