Windows Remote Desktop Client bug - "failed to subscribe since there is no workspace"

%3CLINGO-SUB%20id%3D%22lingo-sub-1667217%22%20slang%3D%22en-US%22%3EWindows%20Remote%20Desktop%20Client%20bug%20-%20%22failed%20to%20subscribe%20since%20there%20is%20no%20workspace%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1667217%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20had%20a%20couple%20of%20users%20connecting%20to%20RemoteApps%20fine%20using%20the%20Windows%20Remote%20Desktop%20Client.%20It%20started%20throwing%20errors%20saying%20cannot%20refresh%20so%20we%20tried%20unsubscribing%20and%20resubscribing%20and%20this%20is%20where%20the%20fun%20starts%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EClick%20subscribe%20%26gt%3B%20an%20immediate%20error%20pops%20up%20%22We%20failed%20to%20subscribe%20since%20there%20is%20no%20Workspace%20at%20%3CA%20href%3D%22https%3A%2F%2Frdweb.wvd.microsoft.com%2Fapi%2Ffeeddiscovery%2Fwebfeeddiscovery.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Frdweb.wvd.microsoft.com%2Fapi%2Ffeeddiscovery%2Fwebfeeddiscovery.aspx%3C%2FA%3E%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22remote_error.PNG%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F218293i46EC6BFDE5AABCAE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22remote_error.PNG%22%20alt%3D%22remote_error.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ENote%20that%20the%20url%20(I%20believe)%20is%20the%20non%20ARM%20classic%20URL.%20We%20have%20never%20deployed%20using%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20persists%20even%20when%20we%20clear%20personal%20data%20(from%20the%20about%20tab)%20and%20uninstall%20and%20reinstall.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20we%20click%20Subscribe%20with%20url%20%26gt%3B%20does%20not%20recognise%20the%20email%20address%20(even%20though%20we%20have%20email%20discovery%20turned%20on%20and%20the%20user%20accounts%20are%20fine%20as%20they%20worked%20yesterday).%20Add%20in%20the%20ARM%20subscribe%20URL%20and%20it%20is%20not%20recognised%2C%20the%20Confirm%20button%20is%20not%20enabled%20so%20we%20can%20do%20nothing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EClearly%20some%20strange%20bug%20with%20the%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20how%20I%20can%20get%20round%26nbsp%3B%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We have had a couple of users connecting to RemoteApps fine using the Windows Remote Desktop Client. It started throwing errors saying cannot refresh so we tried unsubscribing and resubscribing and this is where the fun starts:

 

Click subscribe > an immediate error pops up "We failed to subscribe since there is no Workspace at https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx:

 

remote_error.PNG

Note that the url (I believe) is the non ARM classic URL. We have never deployed using this.

 

The problem persists even when we clear personal data (from the about tab) and uninstall and reinstall.

 

If we click Subscribe with url > does not recognise the email address (even though we have email discovery turned on and the user accounts are fine as they worked yesterday). Add in the ARM subscribe URL and it is not recognised, the Confirm button is not enabled so we can do nothing.

 

Clearly some strange bug with the client.

 

Any ideas how I can get round  this?

0 Replies