AVD start on connect issue

Question

AVD start on connect issue

djenkins 1

hello, looking for some help with a minor AVD issue.

I have a host pool with a single VM. Start on connect was setup a few months ago and has been working fine up until yesterday.

Now, my user is getting an error when trying to connect:

"we couldn't connect because there are currently no available resources. Try again later or contact tech support for help if this keeps happening".

Error code: 0x3000046
Extended error code: 0x0
Timestamp (UTC): 2021-10-05T14:15:38.138Z
Activity ID: 65d0e152-11e2-4884-b730-90433c510000

Saw something that suggested recreating the host pool, but would like a more streamlined solution rather then jumping through that hoop.

KarishmaTiwari-MSFT 20,772 Reputation points Microsoft Employee Moderator

2021-10-06T00:50:24.237+00:00

This error usually indicates that the VM in the host pool which you are trying to connect to, has issues.

Can you please check and confirm if the VM show as Healthy in the Azure Portal/PowerShell?
If the VM is unavailable and there is still a user session on it, please try to logoff the stale session and try to connect again.
Cajethan Ehumadu 1 Reputation point

2022-09-23T06:56:58.937+00:00

The solution is to assign the DESKTOP VIRTUALIZATION POWER ON CONTRIBUTOR ROLE to the AVD service principal, but be sure to do it at the Subscription level.

https://learn.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect?tabs=azure-portal#create-a-custom-role-for-start-vm-on-connect

2 answers

Your answer

KarishmaTiwari-MSFT 20,772 Reputation points Microsoft Employee Moderator

2021-10-06T00:50:24.237+00:00

This error usually indicates that the VM in the host pool which you are trying to connect to, has issues.

Can you please check and confirm if the VM show as Healthy in the Azure Portal/PowerShell?
If the VM is unavailable and there is still a user session on it, please try to logoff the stale session and try to connect again.
Cajethan Ehumadu 1 Reputation point

2022-09-23T06:56:58.937+00:00

The solution is to assign the DESKTOP VIRTUALIZATION POWER ON CONTRIBUTOR ROLE to the AVD service principal, but be sure to do it at the Subscription level.

https://learn.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect?tabs=azure-portal#create-a-custom-role-for-start-vm-on-connect

Answer 1

we also see this on occasion and I'm looking for a way to prevent. We typically see the disconnected/stale session and the VM will show its still stopped/deallocated as shown above. We do what was said above - start the vm and logoff the disconnected session and then the host will show available again. Sometimes you can see in Boot Diagnostics that Windows didn't start successfully and the screenshot shows it's waiting for a response to continue or not (which obviously no one can respond to), so we end up stopping and starting the VM again.

Trying to understand if there is something to do to prevent the situation - there wasn't an session for the host before the user tried to connect (typically first thing in the morning). We make sure all sessions are logged off at the end of the day and stop their VMs, so in the morning when they connect, it should start on connect and most times it works successfully. On the Windows not loading, is there a Windows setting that would have Windows automatically try to restart again vs. prompting for response? Trying to find ways to handle these few exceptions. Also, we've never had to recreate the Host Pool - just get the VM up in a good state again, and end any disconnected sessions if they exist after the initial attempt to start on connect....

Kanishka Dobhal | Redington 41 Reputation points

2022-01-04T10:05:11.113+00:00

Hi @Shannan Shapiro @djenkins Were you able to resolve this?

I am seeing the same problem for months now on multiple hostpools since we have enabled Start VM On Connect.
Hostpool has approx 10 users and the automation works fine for say around 5-6 users and the error pops up for the rest 4.
I even have group policy enabled to disable any stale sessions when the machine is in idle state for an hour, which ensures the VMs are logged off when the users is done for the day.
Only way to fix it is Starting the VM from Azure portal manually aka getting it into a healthy state, but that workaround is a pain when you have multiple hostpools and more than 2 affected users.

Any help would be appreciated.

Thanks
Kanishka

Answer 2

Robert Mahon 1

I have been running into issues of late with the first attempt of connecting, getting "error occurred while accessing this resource"

On second attempt, its work correctly then. Its like the first connection timeouts while the the VM is starting up.

Just wondering has anyone else come across this?

Rob

Share via

AVD start on connect issue

2 answers

Your answer