FIX Not Able to Connect to AVD Personal Desktop VM Issue Error 0x3000046

Let’s see how to FIX Not Able to Connect to AVD Personal Desktop VM Issue Error 0x3000046. This issue is experienced with the latest release of AVD. I have explained about AVD v2 ARM model architecture in the last blog post.

I have shared the experience of creating new host pools, Workspaces, and Session Hosts in the following post. AVD v2 Admin Experience Create New Host Pool | Workspace | Session Host.

Problem Statement – Not Able to Connect to AVD

FIX Not Able to Connect to AVD Personal Desktop VM Issue  Error 0x3000046
FIX Not Able to Connect to AVD Personal Desktop VM Issue Error 0x3000046

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 0x3000046

Patch My PC

Extended Error Code 0x0

FIX Not Able to Connect to AVD Personal Desktop VM Issue
FIX Not Able to Connect to AVD Personal Desktop VM Issue

Troubleshooting AVD Issues Error 0x3000046

The user is not able to connect to the personal virtual desktop (with the direct assignment) when I create a host pool and session host from the new portal for AVD (a.k.a WVD v2). 

Everything works ok with the old WVD process of creating a host pool, adding session hosts, etc… using PowerShell. And the user is part of the Desktop App group as I explained in the above post.

FIX Not Able to Connect to WVD Personal Desktop VM Issue
FIX Not Able to Connect to AVD Personal Desktop VM Issue

The following are the errors Microsoft support engineer retrieved for the issue.

ActivityId env_name env_time ErrorSource ErrorCode ErrorMessage ReportedBy ErrorInternal
3ff94fe9-2995-48df-a938-8fe4b467800000 ##Microsoft.RDInfra.Monitoring.Events.DiagErrorInfo 2020-05-22 23:21:21.0788537 RDBroker -21678388 Host pool = ≤WVD2≥ is a PersonalDesktop pool with Direct assignment type. In order to connect to this pool, user = ≤[email protected]≥ has to have a SessionHost pre-assigned! RDGateway False
Returning error '{
"Code": "E_PROXY_ORCHESTRATION_LB_NO_SESSIONHOST_AVAILABLE",
"Message": "UserId = ≤[email protected]≥ should have a pre-assign SessionHost to connect to. The host pool = ≤WVD-v21≥ is a PersonalDesktop pool with Direct assignment. The administrator needs to assign the SessionHost prior to user connecting to this host pool.",
"Target": null,
"Details": null,
"InnerError": null
}' HttpCode=400 ContentType='application/json; charset=utf-8'
Update-AzWvdSessionHost_UpdateExpanded: ActivityId: 419fdfb-480c-4da9-9d5f-kajskljaasbc77bcec8 Error: SessionHost does not exist

Fix AVD Error 0x3000046 PowerShell Way

As per Microsoft documentation and Microsoft support engineer, we need to use the PowerShell command to fix this issue. There is a PowerShell command to assign this user to a personal desktop.

NOTE! – I couldn’t find the option to assign a personal desktop to a user from AVD’s new portal experience (a.k.a AVD v2). This was the situation when I worked on this issue with a Microsoft engineer.

Update-AzWvdSessionHost -HostPoolName $hostpoolname -Name $sessionhostname -ResourceGroupName $resourcegroupname -AssignedUser $userupn

AVD Portal Experience

Microsoft AVD black belt Tom Hickling shared a tweet to confirm, that there is an option to assign a personal desktop to a user from AVD’s new portal (a.k.a WVD v2).

  • Login to portal.azure.com
  • Search with “Azure Virtual Desktop“.
  • Click on the Azure Virtual Desktop icon.
  • Select Personal Host Pool.
  • Select personal desktop Session Hosts.
  • Navigate to the right until you see the Assigned user column.
  • Click on the (Assign) link and select the user (direct assignment).
direct assignment - FIX Not Able to Connect to WVD Personal Desktop VM Issue
Picture Credits to Tom Hickling – direct assignment – FIX Not Able to Connect to WVD Personal Desktop VM Issue

Resources

Categories AVD

7 thoughts on “FIX Not Able to Connect to AVD Personal Desktop VM Issue Error 0x3000046”

  1. For me, I had the ‘Max session limit’ set too low on the host pool. That can be modified in the ‘Properties’ section of the host pool.

    It would have been nice if the error message said something like “We couldn’t connect because the max session limit of 4 has already been reached”.

    Reply
  2. Hi Anoop, Thanks for your article.
    When I am trying to connect avd machine, it gives me an error saying that username and password is incorrect but I can use the same username and password to login office portal. It’s a personal avd desktop and it’s joined to our Azure AD
    Do you know where I am doing wrong?

    Error message : Oops, we couldn’t connect to “AVD-Demo01”
    Sign in failed. Please check your username and password and try again.

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.