Forum Discussion
Internal error occurred when connecting to RD
We have set up a WVD tenant but have not been able to logon to the VM.
When connecting we get the error "Internal error occurred".
Please see the output of the get-rdsdiagnosticsactivies below:
PS C:\WINDOWS\system32> Get-RdsDiagnosticActivities -TenantName $myTenantName -UserName "UPN@UPN.com" -Detailed
ActivityId : aa119e5d-cbcf-4a96-a297-bc16f4cb0000
ActivityType : Connection
StartTime : 29/08/2019 14:03:45
EndTime : 29/08/2019 14:03:51
UserName : UPN@UPN.com
RoleInstances : Workstationname;mrs-eus2r1c001-rdgateway-prod-staging::RD0004FFA4C4AF;mrs-eus2r1c001-rdbroker-prod-staging::RD0003FF8BA99A;≤WVDNDI-0
.ndi.nl≥
Outcome : Failure
Status : Completed
Details : {[ClientOS, WINDOWS; 10.0.18362], [ClientVersion, 1.2.246.18950], [ClientType, MSRDC], [PredecessorConnectionId, ]...}
LastHeartbeatTime : 29/08/2019 14:05:23
Checkpoints : {LoadBalancedNewConnection, TransportConnecting, TransportConnected, RdpStackDisconnect}
Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}
ActivityId : 992eed1a-b079-4c2b-91e5-7f0eecedb7a6
ActivityType : Feed
StartTime : 29/08/2019 14:03:36
EndTime : 29/08/2019 14:03:36
UserName : UPN@UPN.com
RoleInstances : rdwebclient;mrs-eus2r1c001-rdbroker-prod-staging::RD0003FF8BA99A
Outcome : Success
Status : Completed
Details : {[ClientOS, Win32 Chrome 76.0.3809.132], [ClientVersion, 1.0.18.5], [ClientType, HTML], [ClientIPAddress, ]...}
LastHeartbeatTime : 29/08/2019 14:03:36
Checkpoints : {}
Errors : {}
Hopefully somebody will be able to guide us in the right direction on this.
5 Replies
- michawetsIron Contributor
Hi Hermanbonnie ,
Could you exec this cmd ?
Get-RdsDiagnosticActivities -TenantName $myTenantName -UserName "UPN@UPN.com" -Detailed | Select-Object Errors -ExpandProperty errors
This will give the details from the errors in this case.
- HermanbonnieCopper Contributor
Hi michawets ,
Please see the result below:
PS C:\WINDOWS\system32> Get-RdsDiagnosticActivities -TenantName $myTenantName -UserName "UPN@DOMAIN.COM" -Detailed | Select-Object Errors -ExpandProperty errors
Errors : {Microsoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo}
ErrorSource : RDAgent
ErrorOperation : AddUserToRDUGroup
ErrorCode : -2147467259
ErrorCodeSymbolic : ConnectionFailedAdErrorNoSuchMember
ErrorMessage : Failed to add user = ≤UPN@DOMAIN.COM≥ to group = Remote Desktop Users. Reason: Win32.ERROR_NO_SUCH_MEMBER
ErrorInternal : False
ReportedBy : RDGateway
Time : 04/09/2019 10:27:45- michawetsIron Contributor
Hi Hermanbonnie ,
Just a small question: is the user available in both Windows AD & Azure AD?
Is it in both cases the same UPN?
And perhaps this could be the issue:
https://docs.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-client-connection#error-o_add_user_to_group_failed--failed-to-add-user--username-to-group--remote-desktop-users-reason-win32error_no_such_member