Forum Discussion
An internal error occurred / can't connect anymore
- Please set-up a validation pool as we have a fix deployed to the validation pools. Learn here how to set those up: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-validation-host-pool We recommend to make use of Azure Service Health Alerts where you will be notified when the fix is available for production: https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-service-alerts
gdglee: thank you for reporting this. We have introduced additional security checks when resolving user identities. In some environments this leads to restricted connectivity due to legacy set-ups. We are reviewing the issue and will update once a solution is available.
Please ensure that you follow as well the following best practice:
- Have a validation host pool set-up to escalate issues before they hit the majority of your users.
- Set-up service alerts to receive health advisories and notification for your subscription.
evasse Is there any news on the fix? We're unfortunately dead in the water here with synced accounts.
evasse
For us its the same as for the others. Only some InCloud accounts are able to access Virtual Desktop. The validation pool is setup. InCloud as well as AAD synced Accounts get the following error:
ErrorSource : RDBroker
ErrorOperation : OrchestrateSessionHost
ErrorCode : -2146233088
ErrorCodeSymbolic : ConnectionFailedUserSIDInformationMismatch
ErrorMessage : OrchestrateAsync: SID value in the database is different than the value returned in the orchestration reply from the agent for user
≤Firstname.Surname@domain.com≥ with Id xxxxxxxx-yyyy-zzzz-xxxx-xxxxyyyyzzzz. This scenario is not supported - we will not be able to redirect the user session.
ErrorInternal : False
ReportedBy : RDGateway
Time : 11.07.2019 10:42:56evasse Any update?
evasse we're having the same issue as well on both existing host pools that were working properly and on a newly deployed host pool.
evasse - so what do you suggest we do with host pools that are experiencing this issue in the meantime? We have a high visibility POC at a very large client that this is interrupting. Telling them their host pool is ruined and needs to be redployed won't go over so well.
Will redeploying even fix this, without intervention on your side?
Additionally, can you provide some more detail on what these security checks are? Any details on what leads to this condition from a "legacy setup" perspective?
We are also having the same issue, Raised ticket to MS Support team, they said "We cannot not provide support for Windows Virtual Desktop because it’s in preview so unfortunately we cannot answer your questions, or assist with issues you are experiencing."
Also, i have received Service alert from Microsoft "Windows Virtual Desktop - East US 2 - Exploring Mitigation" But there is no ETA As of now.
Please set-up a validation pool as we have a fix deployed to the validation pools. Learn here how to set those up: https://docs.microsoft.com/en-us/azure/virtual-desktop/create-validation-host-pool
We recommend to make use of Azure Service Health Alerts where you will be notified when the fix is available for production: https://docs.microsoft.com/en-us/azure/virtual-desktop/set-up-service-alerts
