An internal error occurred / can't connect anymore

Deleted
Jul 09, 2019
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
JanPijnacker
Copper Contributor
Jul 08, 2019
evasse

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.
- sbuntun
  Brass Contributor
  Jul 08, 2019
  JanPijnacker evasse This is true for us as well.
  - rmaddron
    Copper Contributor
    Jul 09, 2019
    evasse - anything new on this? All of my client's IDs are sourced from on-prem AD > AADC > AAD. The error remains on my existing pools, and based on the feedback here - suspect it will with a validation pool deployment. Moving to cloud only IDs isn't really an option
    
    Can you provide any more detail on what leads to this condition?
Deleted
Jul 03, 2019
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
-ValidationEnv $True flag on the new-rdshostpool command.

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'\"."
}
]
}
}'
- evasse
  Former Employee
  Jul 14, 2019
  Please review our troubleshooting guide for domain join issues: https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-set-up-issues
  - rhythmnewt
    Copper Contributor
    Jul 16, 2019
    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 PM
    
    User 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}
- evasse
  Former Employee
  Jul 03, 2019
  Deleted Please review our troubleshooting section under https://aka.ms/wvdpreview. We have articles on that as well.
  - Deleted
    Jul 03, 2019
    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.
gdglee
Copper Contributor
Jul 03, 2019
Hi evasse that is good to know. I changed my hostpool to a validationenvironment. The agent is upgraded: AgentVersion : 1.0.833.5
Unfortunately I see the same behaviour still. Not able to connect, same error.
- gdglee
  Copper Contributor
  Jul 04, 2019
  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

Forum Discussion

An internal error occurred / can't connect anymore

Resources