Azure-docs: ConnectionFailedAdErrorNoSuchMember and ConnectionFailedNoMappingOfSIDinAD

[XzeroR3]

I came across these two errors with two separate accounts:

• ConnectionFailedAdErrorNoSuchMember
• ConnectionFailedNoMappingOfSIDinAD

These errors came after setting up Windows Virtual Desktop and erroneously using Azure AD credentials for my sign in. Neither error is called out on this article.

Support was able to help me find one of the errors "ERROR_NO_SUCH_MEMBER" @ the following URL: https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--1300-1699-

Thank you.

Powershell detail:

(Get-RdsDiagnosticActivities -TenantName tenantname  -Detailed  -Outcome failure -UserName [email protected] | select-object -Last 1).errors

ErrorSource       : RDAgent
ErrorOperation    : AddUserToRDUGroup
ErrorCode         : -2147467259
ErrorCodeSymbolic : ConnectionFailedAdErrorNoSuchMember
ErrorMessage      : Failed to add user = ≤[email protected]≥ to group = Remote Desktop Users. Reason: Win32.ERROR_NO_SUCH_MEMBER
ErrorInternal     : False
ReportedBy        : RDGateway
Time              : 3/4/2020 3:12:47 PM

(Get-RdsDiagnosticActivities -TenantName tenantname  -Detailed  -Outcome failure -UserName [email protected] | select-object -Last 1).errors


ErrorSource       : RDAgent
ErrorOperation    : ConvertSidToAccount
ErrorCode         : 1332
ErrorCodeSymbolic : ConnectionFailedNoMappingOfSIDinAD
ErrorMessage      : No mapping between account names and security IDs was done
ErrorInternal     : False
ReportedBy        : RDGateway
Time              : 3/4/2020 3:10:33 PM

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cbd503e0-9200-4fb7-4a18-fdf3cf51f8ee
• Version Independent ID: 4b3493f3-ca0e-f64e-a884-0a27b1d18eb1
• Content: Windows Virtual Desktop diagnose issues - Azure
• Content Source: articles/virtual-desktop/diagnostics-role-service.md
• Service: virtual-desktop
• GitHub Login: @Heidilohr
• Microsoft Alias: helohr

[VikasPullagura-MSFT]

@XzeroR3
Thanks for the feedback! We are currently investigating and will get back on this.

[VikasPullagura-MSFT]

@ChristianMontoya Can you please check and add your comments on this.

[ChristianMontoya]

@XzeroR3 : Thanks for reporting this! I'm creating a workitem internally for a docs improvement to include this error in troubleshooting.

@VikasPullagura-MSFT : Feel free to close while we track internally.

[ChristianMontoya]

For tracking purposes, we have created the workitem with ID 25493720 .

[VikasPullagura-MSFT]

@ChristianMontoya Thanks for adding more details on the issue.

@XzeroR3 We will now close this issue, as this is internally tracked as mentioned by the team.