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
evasse Unfortunately we cannot deploy to Validation ring because the machine fails to join the domain. We are using the same script as to deploy to prod ring (which has no issues to join the domain) with the only difference being the
15:10:25 - Resource Microsoft.Compute/virtualMachines/extensions 'rmrvwval4-0/joindomain' failed with message '{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'joindomain'. Error message: \"Exception(s) occured while joining Domain '{sanitized}.com'\"."
}
]
}
}'
Please review our troubleshooting guide for domain join issues: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-set-up-issues
evasse It's been 2.5 weeks now. Can you get some ETA on the fix for this problem? Neither validation or production environment works!!
TenantGroupName : Default Tenant Group
HostPoolName : MyTest_HostPool
FriendlyName : My Test Host Pool
Description :
Persistent : False
CustomRdpProperty :
MaxSessionLimit : 999999
LoadBalancerType : BreadthFirst
ValidationEnv : True
Ring :Still getting the same SID 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 ≤rhythmnewt@rhythmnewt.com≥ with Id
85a45a4c-413d-4074-2e41-08d6e4d9abe8. This scenario is not supported - we will not be able to
redirect the user session.
ErrorInternal : False
ReportedBy : RDGateway
Time : 7/16/2019 3:08:54 PMUser activity log
ActivityId : 10dd46a2-4836-49f1-8f89-face053b0000
ActivityType : Connection
StartTime : 7/16/2019 3:08:54 PM
EndTime : 7/16/2019 3:08:54 PM
UserName : rhythmnewt@rhythmnewt.com
RoleInstances : mrs-eus2r0c001-rdgateway-prod::RD2818785C114D;mrs-eus2r0c002-rdbroker-prod::RD2818788A0588;≤rmrvw-0
.rhythmnewt.com≥
Outcome : Failure
Status : Completed
Details : {[ClientOS, ], [ClientVersion, ], [ClientType, ], [PredecessorConnectionId, ]...}
LastHeartbeatTime : 7/16/2019 3:10:26 PM
Checkpoints : {LoadBalancedNewConnection, TransportConnecting, TransportConnected, RdpStackDisconnect...}
Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}
Roop_Kiran_ChevuriMicrosoft
rhythmnewt We would like to understand more about your domain setup. We observe that SID which VM resolves the user to doesn't match the SID we are getting from his AAD token. Can you please give brief overview of your domain setup and how it is connected to AAD? Do you have multiple domains?
Deleted Please review our troubleshooting section under https://aka.ms/wvdpreview. We have articles on that as well.
evasse I looked over the troubleshooting steps but none of it applies, we deploy to a new resource group in the same vnet, same region, same source image as our production ring. If I create the new host pool with -ValidationEnv $False flag then there is no problem with domain join, and the only issue is the SID error on connection.
