Forum Discussion
An internal error occurred / can't connect anymore
We've been running WVD succesfully for a few months, but since this morning my users cannot login anymore. Not through the desktop and not through the webclient. The desktop client returns 'An internal error occurred' after logging in. The webclient has a cannot connect message (in Dutch). I've traced the connection failure via Powershell to below two errors. It seems my SID has changed somehow, but I cannot understand how:
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 ≤PRIVATE≥ with Id PRIVATE. This scenario is not supported - we will not be able to redirect the user session.
ErrorInternal : False
ReportedBy : RDGateway
Time : 28-6-2019 12:42:44
ErrorSource : Client
ErrorOperation : ClientRDPConnect
ErrorCode : 2147965400
ErrorCodeSymbolic :
ErrorMessage : Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance.
ErrorInternal : True
ReportedBy : Client
Time : 28-6-2019 12:42:44
I've tried removing an RdsAppGroupUser and re adding it, but the same error remains.
- 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
- evasse
Microsoft
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 - 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.
- evasse
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
- evassePlease 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
Maybe relevant to know from our setup. Users created in the Azure AD as cloud only are able to connect, users synchronized from our on-premise AD are not.
JanPijnacker evasse This is true for us as well.
evasse I created a new hostpool as validationenvironment, to see if that would make difference. The agent is 1.0.833.5 but the error remains the same. In an earlier reply you mentioned a legacy setup. Could you elaborate on that? What could we setup differently to make this work again?
Thanks, Gerrit
evasse This is still not working for us in either validation pool or production pool. These are the agent versions installed on my VM.
Remote Desktop Services Infrastructure Agent Microsoft Corporation 1.0.833.5
Remote Desktop Services SxS Network Stack Microsoft Corporation 1.0.1904.29002
Remote Desktop Agent Boot Loader Microsoft Corporation 1.0.0.0
Remote Desktop Services Infrastructure Geneva Agent Microsoft Corporation 42.3.9
Remote Desktop Services Infrastructure Agent Microsoft Corporation 1.0.0.1462
- Can I just move my pool to validation pool instead or cretaing new POOL , i found that I can switch the POOL to validation pool using command below Set-RdsHostPool -TenantName MVPPOC -Name POCHOST1 -ValidationEnv $true
Do we know if there is a fix for this yet. I have installed a new Validation Pool and still the same error. My agent is 1.0.833.5
Roop_Kiran_Chevuri
Do we know if there is a fix for this yet. I have installed a new Validation Pool and still the same error. My agent is 1.0.833.5
