SOLVED

Cannot provision a host pool

Copper Contributor

When I go to Windows Virtual Desktop - Provision a host pool and click Create I get the following error:

 

Create MultiVm: failed to parse createUIdefinition file. Error: readyState: 4 responseText: responseXML:

 

{ "shellProps": { "sessionId": "ca1f4d2eb8184589b8bac3f624a3b69c", "extName": "Microsoft_Azure_Compute", "contentName": "CreateMultiVmWizardPart" }, "error": { "message": "Create MultiVm: failed to parse createUIdefinition file. Error: readyState: 4\r\nresponseText: \nAuthenticationFailedServer failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.\nRequestId:40a319f2-f01e-0012-44da-6dfb37000000\nTime:2019-09-18T04:34:42.2905937ZAuthentication scheme Bearer is not supported in this version.\r\nresponseXML: \r\nstatus: 403\r\nstatusText: error\r\n", "code": null }}

 

Not sure what to try next? Any help appreciated.

9 Replies

@DannyD300 

 

We are experiencing the exact same error. We are not able to create a new WVD environment. 

Any directions to solve this issue are more then welcome. 

@DannyD300  I am also experiencing this issue, any update would be appreciated.

 

Error: Create MultiVm: failed to parse createUIdefinition file. Error: readyState: 4 responseText: responseXML:

@DannyD300 

 

Hello all, suddenly it is working again. I'm now able to create a new WVD environment. SO Microsoft is fixing at the background I suppose. :)

 

 

I'm Still having issues

@DannyD300 I seem to be having the same issue. 

best response confirmed by Eva Seydl (Microsoft)
Solution

@AttackonAzure : Our Azure Marketplace team is aware of this incident and are tracking it down. We've noticed that not all customers hit this issue, or were originally hitting the issue but now do not. If you are still hitting this issue, please follow the steps to deploy the GitHub ARM template in the meantime.

 

As the teams investigate, we'll continue monitoring for information and report back.

Any Updates

Hi all,

 

The issue should be resolved. Had the same issue yesterday at multiple Tenants, but now, all Tenants are able to deploy using the Marketplace.

Confirming @michawets observation. You should be able to run the Azure Marketplace offering successfully now!

1 best response

Accepted Solutions
best response confirmed by Eva Seydl (Microsoft)
Solution

@AttackonAzure : Our Azure Marketplace team is aware of this incident and are tracking it down. We've noticed that not all customers hit this issue, or were originally hitting the issue but now do not. If you are still hitting this issue, please follow the steps to deploy the GitHub ARM template in the meantime.

 

As the teams investigate, we'll continue monitoring for information and report back.

View solution in original post