Microsoft WVD Error Message Agent cannot connect to broker with error NOT_FOUND. URL: wss://rdbroke

%3CLINGO-SUB%20id%3D%22lingo-sub-1282841%22%20slang%3D%22en-US%22%3EMicrosoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdbroke%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1282841%22%20slang%3D%22en-US%22%3E%3CP%3E%3CBR%20%2F%3EHello%20everyone%2C%3C%2FP%3E%3CP%3Ei%20am%20currently%20testing%20WVD%20on%20Azure%2C%20and%20deployed%20a%20host%20pool%20with%202%20vms%20windows%2010%20multi%20session%20%2C%20i%20installed%20fslogix%20and%20put%20the%20registires%20and%20tested%20it%20and%20its%20working%20fine%2C%20however%20in%20power%20shell%20when%20i%20used%20the%20following%20command%20and%20got%20the%20below%20results%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet-RdsSessionHost%20-TenantName%20%24WVDTenantName%20-HostPoolName%20%24WVDHostPoolName%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESessionHostName%20%3A%20**-WVD-0.ad.testcrayons.com%3CBR%20%2F%3ETenantName%20%3A%20**-Tenant%3CBR%20%2F%3ETenantGroupName%20%3A%20Default%20Tenant%20Group%3CBR%20%2F%3EHostPoolName%20%3A%20**-HostPool%3CBR%20%2F%3EAllowNewSession%20%3A%20False%3CBR%20%2F%3ESessions%20%3A%202%3CBR%20%2F%3ELastHeartBeat%20%3A%204%2F5%2F2020%202%3A41%3A41%20PM%3CBR%20%2F%3EAgentVersion%20%3A%201.0.1800.1300%3CBR%20%2F%3EAssignedUser%20%3A%3CBR%20%2F%3EOsVersion%20%3A%2010.0.18363%3CBR%20%2F%3ESxSStackVersion%20%3A%20rdp-sxs200326004%3CBR%20%2F%3EStatus%20%3A%20Available%3CBR%20%2F%3EUpdateState%20%3A%20Succeeded%3CBR%20%2F%3ELastUpdateTime%20%3A%204%2F5%2F2020%202%3A36%3A39%20PM%3CBR%20%2F%3EUpdateErrorMessage%20%3A%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdbroker.wvd.microsoft.com%2F%2Fapi%2FrdAgent%2Fv1%3C%2FP%3E%3CP%3ESessionHostName%20%3A%20**-1.ad.**.com%3CBR%20%2F%3ETenantName%20%3A%20**-Tenant%3CBR%20%2F%3ETenantGroupName%20%3A%20Default%20Tenant%20Group%3CBR%20%2F%3EHostPoolName%20%3A%20**-HostPool%3CBR%20%2F%3EAllowNewSession%20%3A%20True%3CBR%20%2F%3ESessions%20%3A%201%3CBR%20%2F%3ELastHeartBeat%20%3A%204%2F5%2F2020%202%3A36%3A42%20PM%3CBR%20%2F%3EAgentVersion%20%3A%201.0.1800.1300%3CBR%20%2F%3EAssignedUser%20%3A%3CBR%20%2F%3EOsVersion%20%3A%2010.0.18363%3CBR%20%2F%3ESxSStackVersion%20%3A%20rdp-sxs200326004%3CBR%20%2F%3EStatus%20%3A%20Available%3CBR%20%2F%3EUpdateState%20%3A%20Succeeded%3CBR%20%2F%3ELastUpdateTime%20%3A%203%2F31%2F2020%209%3A38%3A24%20PM%3CBR%20%2F%3EUpdateErrorMessage%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ei%20got%20the%20following%20error%20message%20for%20one%20of%20the%20session%20hosts%20only%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpdateErrorMessage%20%3A%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdbroker.wvd.microsoft.com%2F%2Fapi%2FrdAgent%2Fv1%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Enot%20sure%20what%20is%20it%20causing%20and%20how%20it%20came%20out%20of%20nowhere%20can%20someone%20please%20advise%20on%20this%20%2C%20thanks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1282841%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWVD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1285821%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1285821%22%20slang%3D%22en-US%22%3EThanks%20for%20reporting.%20This%20is%20a%20output%20issue.%20it%20is%20already%20been%20fixed%20recently.%20It%20should%20not%20affect%20any%20connection%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1295895%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1295895%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181812%22%20target%3D%22_blank%22%3E%40Soo%20Kuan%20Teo%3C%2FA%3E%26nbsp%3BAny%20additional%20information%20on%20this%20other%20than%20an%20%22output%20issue%22%3F%26nbsp%3B%20I%20am%20seeing%20this%20as%20well%20on%20a%20single%20host%20and%20trying%20to%20figure%20out%20why.%26nbsp%3B%20It%20does%20not%20seem%20to%20be%20affecting%20anything%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1298833%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1298833%22%20slang%3D%22en-US%22%3Eit%20is%20powershell%20output%20incorrectly.%20a%20fix%20on%20the%20powershell%20output%20is%20already%20on%20the%20way.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1300264%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1300264%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20also%20have%20the%20same%20isseue%20and%20can%20only%20connect%20to%20machine%20throw%20remote%20desktop%20by%20ip%20address%20for%20machine%26nbsp%3B%3C%2FP%3E%3CP%3Eand%20i%20can't%20remote%20from%20web%20portal%20or%20throw%20remote%20desktop%20agent%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1324317%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1324317%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20facing%20the%20similar%20issue%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EError%20%3A%26nbsp%3B%3CSPAN%3EConnection%20not%20found%3A%20RD%20Agent%20does%20not%20have%20an%20active%20connection%20to%20the%20broker.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet-Rdssessionhost%20output%20is%20given%20below%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPS%20C%3A%5CWINDOWS%5Csystem32%26gt%3B%20Get-RdsSessionHost%20***tenant%20***HP%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ESessionHostName%20%3A%20ZDVM-0.***.co.nz%3CBR%20%2F%3ETenantName%20%3A%20***tenant%3CBR%20%2F%3ETenantGroupName%20%3A%20Default%20Tenant%20Group%3CBR%20%2F%3EHostPoolName%20%3A%20***HP%3CBR%20%2F%3EAllowNewSession%20%3A%20False%3CBR%20%2F%3ESessions%20%3A%201%3CBR%20%2F%3ELastHeartBeat%20%3A%204%2F21%2F2020%2010%3A12%3A10%20AM%3CBR%20%2F%3EAgentVersion%20%3A%201.0.1932.3500%3CBR%20%2F%3EAssignedUser%20%3A%20S******.B******%40*****.co.nz%3CBR%20%2F%3EOsVersion%20%3A%2010.0.18363%3CBR%20%2F%3ESxSStackVersion%20%3A%20rdp-sxs200326004%3CBR%20%2F%3EStatus%20%3A%20Unavailable%3CBR%20%2F%3EUpdateState%20%3A%20Succeeded%3CBR%20%2F%3ELastUpdateTime%20%3A%204%2F19%2F2020%207%3A57%3A53%20PM%3CBR%20%2F%3EUpdateErrorMessage%20%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1336225%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1336225%22%20slang%3D%22en-US%22%3EHi%20Snehanshu%2C%20you%20case%20is%20different.%20your%20VM%20status%20is%20unavailable.%3CBR%20%2F%3ECan%20you%20please%20start%20a%20new%20thread%20for%20you%20issue%3F%20This%20way%20other%20readers%20don't%20get%20confused%20about%20your%20issue%20with%20this%20one.%3CBR%20%2F%3EI%20tried%20to%20check%20your%20machine%20status%2C%20I%20don't%20get%20a%20lot%20of%20information%20about%20your%20affected%20VM.%20other%20than%20it%20is%20unhealthy.%20can%20you%20please%20follow%20the%20requirements%20below%3F%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Foverview%23requirements%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Foverview%23requirements%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1372956%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1372956%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181812%22%20target%3D%22_blank%22%3E%40Soo%20Kuan%20Teo%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20we%20have%20a%20new%20thread%3F%20Same%20problem%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1374898%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20WVD%20Error%20Message%20Agent%20cannot%20connect%20to%20broker%20with%20error%20NOT_FOUND.%20URL%3A%20wss%3A%2F%2Frdb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1374898%22%20slang%3D%22en-US%22%3ENot%20that%20I'm%20aware%20of.%20Please%20start%20a%20new%20thread%2C%20and%20share%20the%20output%20of%20Get-Rdssessionhost%2C%20replace%20some%20characters%20with%20'*'%20in%20your%20Sessionhostpool%20name%2C%20tenant%20name%2C%20assigned%20users%2C%20to%20protect%20your%20privacy.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor


Hello everyone,

i am currently testing WVD on Azure, and deployed a host pool with 2 vms windows 10 multi session , i installed fslogix and put the registires and tested it and its working fine, however in power shell when i used the following command and got the below results:

 

Get-RdsSessionHost -TenantName $WVDTenantName -HostPoolName $WVDHostPoolName

 

SessionHostName : **-WVD-0.ad.testcrayons.com
TenantName : **-Tenant
TenantGroupName : Default Tenant Group
HostPoolName : **-HostPool
AllowNewSession : False
Sessions : 2
LastHeartBeat : 4/5/2020 2:41:41 PM
AgentVersion : 1.0.1800.1300
AssignedUser :
OsVersion : 10.0.18363
SxSStackVersion : rdp-sxs200326004
Status : Available
UpdateState : Succeeded
LastUpdateTime : 4/5/2020 2:36:39 PM
UpdateErrorMessage : Agent cannot connect to broker with error NOT_FOUND. URL: wss://rdbroker.wvd.microsoft.com//api/rdAgent/v1

SessionHostName : **-1.ad.**.com
TenantName : **-Tenant
TenantGroupName : Default Tenant Group
HostPoolName : **-HostPool
AllowNewSession : True
Sessions : 1
LastHeartBeat : 4/5/2020 2:36:42 PM
AgentVersion : 1.0.1800.1300
AssignedUser :
OsVersion : 10.0.18363
SxSStackVersion : rdp-sxs200326004
Status : Available
UpdateState : Succeeded
LastUpdateTime : 3/31/2020 9:38:24 PM
UpdateErrorMessage :

 

i got the following error message for one of the session hosts only:

 

UpdateErrorMessage : Agent cannot connect to broker with error NOT_FOUND. URL: wss://rdbroker.wvd.microsoft.com//api/rdAgent/v1

 

not sure what is it causing and how it came out of nowhere can someone please advise on this , thanks.

 

8 Replies
Highlighted
Thanks for reporting. This is a output issue. it is already been fixed recently. It should not affect any connection issue.
Highlighted

@Soo Kuan Teo Any additional information on this other than an "output issue"?  I am seeing this as well on a single host and trying to figure out why.  It does not seem to be affecting anything though.

Highlighted
it is powershell output incorrectly. a fix on the powershell output is already on the way.
Highlighted

i also have the same isseue and can only connect to machine throw remote desktop by ip address for machine 

and i can't remote from web portal or throw remote desktop agent 

 

Highlighted

I am facing the similar issue 

Error : Connection not found: RD Agent does not have an active connection to the broker.

 

Get-Rdssessionhost output is given below

 

PS C:\WINDOWS\system32> Get-RdsSessionHost ***tenant ***HP


SessionHostName : ZDVM-0.***.co.nz
TenantName : ***tenant
TenantGroupName : Default Tenant Group
HostPoolName : ***HP
AllowNewSession : False
Sessions : 1
LastHeartBeat : 4/21/2020 10:12:10 AM
AgentVersion : 1.0.1932.3500
AssignedUser : S******.B******@*****.co.nz
OsVersion : 10.0.18363
SxSStackVersion : rdp-sxs200326004
Status : Unavailable
UpdateState : Succeeded
LastUpdateTime : 4/19/2020 7:57:53 PM
UpdateErrorMessage :

Highlighted
Hi Snehanshu, you case is different. your VM status is unavailable.
Can you please start a new thread for you issue? This way other readers don't get confused about your issue with this one.
I tried to check your machine status, I don't get a lot of information about your affected VM. other than it is unhealthy. can you please follow the requirements below?
https://docs.microsoft.com/en-us/azure/virtual-desktop/overview#requirements
Highlighted
Highlighted
Not that I'm aware of. Please start a new thread, and share the output of Get-Rdssessionhost, replace some characters with '*' in your Sessionhostpool name, tenant name, assigned users, to protect your privacy.