SOLVED

An internal error occurred / can't connect anymore

%3CLINGO-SUB%20id%3D%22lingo-sub-727771%22%20slang%3D%22en-US%22%3EAn%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727771%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20been%20running%20WVD%20succesfully%20for%20a%20few%20months%2C%20but%20since%20this%20morning%20my%20users%20cannot%20login%20anymore.%20Not%20through%20the%20desktop%20and%20not%20through%20the%20webclient.%20The%20desktop%20client%20returns%20'An%20internal%20error%20occurred'%20after%20logging%20in.%20The%20webclient%20has%20a%20cannot%20connect%20message%20(in%20Dutch).%20I've%20traced%20the%20connection%20failure%20via%20Powershell%20to%20below%20two%20errors.%20It%20seems%20my%20SID%20has%20changed%20somehow%2C%20but%20I%20cannot%20understand%20how%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EErrorSource%20%3A%20RDBroker%3CBR%20%2F%3EErrorOperation%20%3A%20OrchestrateSessionHost%3CBR%20%2F%3EErrorCode%20%3A%20-2146233088%3CBR%20%2F%3EErrorCodeSymbolic%20%3A%20ConnectionFailedUserSIDInformationMismatch%3CBR%20%2F%3EErrorMessage%20%3A%20OrchestrateAsync%3A%20SID%20value%20in%20the%20database%20is%20different%20than%20the%20value%20returned%20in%20the%20orchestration%20reply%20from%20the%20agent%20for%20user%20%E2%89%A4PRIVATE%E2%89%A5%20with%20Id%20PRIVATE.%20This%20scenario%20is%20not%20supported%20-%20we%20will%20not%20be%20able%20to%20redirect%20the%20user%20session.%3CBR%20%2F%3EErrorInternal%20%3A%20False%3CBR%20%2F%3EReportedBy%20%3A%20RDGateway%3CBR%20%2F%3ETime%20%3A%2028-6-2019%2012%3A42%3A44%3C%2FP%3E%3CP%3EErrorSource%20%3A%20Client%3CBR%20%2F%3EErrorOperation%20%3A%20ClientRDPConnect%3CBR%20%2F%3EErrorCode%20%3A%202147965400%3CBR%20%2F%3EErrorCodeSymbolic%20%3A%3CBR%20%2F%3EErrorMessage%20%3A%20Your%20computer%20can't%20connect%20to%20the%20Remote%20Desktop%20Gateway%20server.%20Contact%20your%20network%20administrator%20for%20assistance.%3CBR%20%2F%3EErrorInternal%20%3A%20True%3CBR%20%2F%3EReportedBy%20%3A%20Client%3CBR%20%2F%3ETime%20%3A%2028-6-2019%2012%3A42%3A44%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20removing%20an%20RdsAppGroupUser%20and%20re%20adding%20it%2C%20but%20the%20same%20error%20remains.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-727860%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727860%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368211%22%20target%3D%22_blank%22%3E%40gdglee%3C%2FA%3E%26nbsp%3BWe've%20exactly%20this%20same%20issue%2C%20we%20tried%20to%20open%20a%20case%2C%20but%20it's%20not%20supported%20for%20preview%20services%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-727883%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727883%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368220%22%20target%3D%22_blank%22%3E%40P_haem%3C%2FA%3E%26nbsp%3Bgood%20to%20know%20we're%20not%20the%20only%20ones.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-727894%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727894%22%20slang%3D%22en-US%22%3EIt's%20seem's%20to%20be%20cause%20by%20the%20agent%20upgrade%20(yesterday%20around%2010PM%20for%20us)%20%3A%20New%20agent%20version%20%3A%201.0.833.4%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-727896%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727896%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368220%22%20target%3D%22_blank%22%3E%40P_haem%3C%2FA%3E%26nbsp%3BSo%20were%20you%20able%20to%20resolve%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-728468%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-728468%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20also%20experiencing%20this%20issue.%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368211%22%20target%3D%22_blank%22%3E%40gdglee%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-731346%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-731346%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368211%22%20target%3D%22_blank%22%3E%40gdglee%3C%2FA%3E%26nbsp%3B-%20Same%20thing%20on%20this%20end.%20Started%20happening%20around%202-3p%20EST%20on%20Friday%2006%2F28.%20This%20host%20pool%20was%20perfectly%20fine%20prior%20to%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-731351%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-731351%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20having%20this%20issue%20as%20well.%20I%20can%20RDP%20into%20my%20WDV%20VMs%2C%20but%20trying%20to%20run%20published%20apps%20(browser%20or%20RDP%20shortcut)%20fail%20with%20a%20connection%20error.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-732754%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-732754%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here.%20This%20seems%20to%20be%20a%20widespread%20problem.%20For%20us%20started%20last%20week%20on%20Thursday.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-733454%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-733454%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368211%22%20target%3D%22_blank%22%3E%40gdglee%3C%2FA%3E%3A%20thank%20you%20for%20reporting%20this.%26nbsp%3B%20We%20have%20introduced%20additional%20security%20checks%20when%20resolving%20user%20identities.%20In%20some%20environments%20this%20leads%20to%20restricted%20connectivity%20due%20to%20legacy%20set-ups.%20We%20are%20reviewing%20the%20issue%20and%20will%20update%20once%20a%20solution%20is%20available.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20ensure%20that%20you%20follow%20as%20well%20the%20following%20best%20practice%3A%3C%2FP%3E%0A%3CP%3E-%20Have%20a%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fcreate-validation-host-pool%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Evalidation%20host%20pool%20set-up%3C%2FA%3E%20to%20escalate%20issues%20before%20they%20hit%20the%20majority%20of%20your%20users.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fset-up-service-alerts%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESet-up%20service%20alerts%3C%2FA%3E%20to%20receive%20health%20advisories%20and%20notification%20for%20your%20subscription.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-733574%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-733574%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368211%22%20target%3D%22_blank%22%3E%40gdglee%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20here.%3C%2FP%3E%3CP%3EFor%20us%20started%20last%20week%20on%20Friday.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-733632%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-733632%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BThank%20you%20for%20your%20answer!%20Do%20you%20have%20any%20resolution%20date%20%3F%20And%20is%20there%20any%20way%20to%20to%20go%20back%20to%20the%20previous%20version%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734345%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734345%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20also%20having%20the%20same%20issue%2C%20Raised%20ticket%20to%20MS%20Support%20team%2C%20they%20said%20%22%3CSTRONG%3EWe%20cannot%20not%20provide%20support%20for%20Windows%20Virtual%20Desktop%20because%20it%E2%80%99s%20in%20preview%20so%20unfortunately%20we%20cannot%20answer%20your%20questions%2C%20or%20assist%20with%20issues%20you%20are%20experiencing.%3C%2FSTRONG%3E%22%3C%2FP%3E%3CP%3EAlso%2C%20i%20have%20received%20Service%20alert%20from%20Microsoft%20%22%3CSTRONG%3EWindows%20Virtual%20Desktop%20-%20East%20US%202%20-%20Exploring%20Mitigation%3C%2FSTRONG%3E%22%20But%20there%20is%20no%20ETA%20As%20of%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734449%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734449%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3B-%20so%20what%20do%20you%20suggest%20we%20do%20with%20host%20pools%20that%20are%20experiencing%20this%20issue%20in%20the%20meantime%3F%20We%20have%20a%20high%20visibility%20POC%20at%20a%20very%20large%20client%20that%20this%20is%20interrupting.%20Telling%20them%20their%20host%20pool%20is%20ruined%26nbsp%3B%20and%20needs%20to%20be%20redployed%20won't%20go%20over%20so%20well.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWill%20redeploying%20even%20fix%20this%2C%20without%20intervention%20on%20your%20side%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAdditionally%2C%20can%20you%20provide%20some%20more%20detail%20on%20what%20these%20security%20checks%20are%3F%20Any%20details%20on%20what%20leads%20to%20this%20condition%20from%20a%20%22legacy%20setup%22%20perspective%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734674%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734674%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3Bwe're%20having%20the%20same%20issue%20as%20well%20on%20both%20existing%20host%20pools%20that%20were%20working%20properly%20and%20on%20a%20newly%20deployed%20host%20pool.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-735712%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-735712%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E-%26nbsp%3B%20Would%20you%20do%20me%20a%20favor%3F%20We%20have%20redeployed%203%20times%20to%20fix%20this%2C%20but%20didn't%20fix.....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-736954%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-736954%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F227095%22%20target%3D%22_blank%22%3E%40Raja%20R%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3EPlease%20set-up%20a%20validation%20pool%20as%20we%20have%20a%20fix%20deployed%20to%20the%20validation%20pools.%20Learn%20here%20how%20to%20set%20those%20up%3A%20%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%20box-sizing%3A%20border-box%3B%22%3E%3CA%20style%3D%22background-color%3A%20transparent%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%230077d4%3B%20text-decoration%3A%20underline%3B%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fcreate-validation-host-pool%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fcreate-validation-host-pool%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%20box-sizing%3A%20border-box%3B%22%3EWe%20recommend%20to%20make%20use%20of%20Azure%20Service%20Health%20Alerts%20where%20you%20will%20be%20notified%20when%20the%20fix%20is%20available%20for%20production%3A%20%3CA%20style%3D%22background-color%3A%20transparent%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%230077d4%3B%20text-decoration%3A%20underline%3B%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fset-up-service-alerts%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fset-up-service-alerts%3C%2FA%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-736955%22%20slang%3D%22en-US%22%3ERE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-736955%22%20slang%3D%22en-US%22%3EPlease%20set-up%20a%20validation%20pool%20as%20we%20have%20a%20fix%20deployed%20to%20the%20validation%20pools.%20Learn%20here%20how%20to%20set%20those%20up%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fcreate-validation-host-pool%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fcreate-validation-host-pool%3C%2FA%3E%20We%20recommend%20to%20make%20use%20of%20Azure%20Service%20Health%20Alerts%20where%20you%20will%20be%20notified%20when%20the%20fix%20is%20available%20for%20production%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fset-up-service-alerts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fset-up-service-alerts%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737041%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737041%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3Bthat%20is%20good%20to%20know.%20I%20changed%20my%20hostpool%20to%20a%20validationenvironment.%20The%20agent%20is%20upgraded%3A%20AgentVersion%20%3A%201.0.833.5%3C%2FP%3E%3CP%3EUnfortunately%20I%20see%20the%20same%20behaviour%20still.%20Not%20able%20to%20connect%2C%20same%20error.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737059%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737059%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BUnfortunately%20we%20cannot%20deploy%20to%20Validation%20ring%20because%20the%20machine%20fails%20to%20join%20the%20domain.%20We%20are%20using%20the%20same%20script%20as%20to%20deploy%20to%20prod%20ring%20(which%20has%20no%20issues%20to%20join%20the%20domain)%20with%20the%20only%20difference%20being%20the%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EValidationEnv%20%3C%2FSPAN%3E%3CSPAN%3E%24True%20flag%20on%20the%20new-rdshostpool%20command.%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E15%3A10%3A25%20-%20Resource%20Microsoft.Compute%2FvirtualMachines%2Fextensions%20'rmrvwval4-0%2Fjoindomain'%20failed%20with%20message%20'%7B%3CBR%20%2F%3E%22status%22%3A%20%22Failed%22%2C%3CBR%20%2F%3E%22error%22%3A%20%7B%3CBR%20%2F%3E%22code%22%3A%20%22ResourceDeploymentFailure%22%2C%3CBR%20%2F%3E%22message%22%3A%20%22The%20resource%20operation%20completed%20with%20terminal%20provisioning%20state%20'Failed'.%22%2C%3CBR%20%2F%3E%22details%22%3A%20%5B%3CBR%20%2F%3E%7B%3CBR%20%2F%3E%22code%22%3A%20%22VMExtensionProvisioningError%22%2C%3CBR%20%2F%3E%22message%22%3A%20%22VM%20has%20reported%20a%20failure%20when%20processing%20extension%20'joindomain'.%20Error%20message%3A%20%5C%22Exception(s)%20occured%20while%20joining%20Domain%20'%7Bsanitized%7D.com'%5C%22.%22%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%5D%3CBR%20%2F%3E%7D%3CBR%20%2F%3E%7D'%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737085%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737085%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F883%22%20target%3D%22_blank%22%3E%40Dmitri%20Mezhevich%3C%2FA%3E%20Please%20review%20our%20troubleshooting%20section%20under%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fwvdpreview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fwvdpreview%3C%2FA%3E.%20We%20have%20articles%20on%20that%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737143%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737143%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BI%20looked%20over%20the%20troubleshooting%20steps%20but%20none%20of%20it%20applies%2C%20we%20deploy%20to%20a%20new%20resource%20group%20in%20the%20same%20vnet%2C%20same%20region%2C%20same%20source%20image%20as%20our%20production%20ring.%20If%20I%20create%20the%20new%20host%20pool%20with%26nbsp%3B%3CSPAN%3E-%3C%2FSPAN%3E%3CSPAN%3EValidationEnv%20%3C%2FSPAN%3E%3CSPAN%3E%24False%20flag%20then%20there%20is%20no%20problem%20with%20domain%20join%2C%20and%20the%20only%20issue%20is%20the%20SID%20error%20on%20connection.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-737573%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737573%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3EAwesome%2C%20it%20worked%20perfectly.%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20quick%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-738042%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-738042%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BI%20created%20a%20new%20hostpool%20as%20validationenvironment%2C%20to%20see%20if%20that%20would%20make%20difference.%20The%20agent%20is%201.0.833.5%20but%20the%20error%20remains%20the%20same.%20In%20an%20earlier%20reply%20you%20mentioned%20a%20legacy%20setup.%20Could%20you%20elaborate%20on%20that%3F%20What%20could%20we%20setup%20differently%20to%20make%20this%20work%20again%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%20Gerrit%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-741246%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-741246%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20were%20able%20to%20set%20up%20the%20validation%20hostpool%2C%20but%20the%20internal%20error%20occurred%20message%20still%20pops%20up.%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-741896%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-741896%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMaybe%20relevant%20to%20know%20from%20our%20setup.%20Users%20created%20in%20the%20Azure%20AD%20as%20cloud%20only%20are%20able%20to%20connect%2C%20users%20synchronized%20from%20our%20on-premise%20AD%20are%20not.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-743208%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-743208%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F371933%22%20target%3D%22_blank%22%3E%40JanPijnacker%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3B%20This%20is%20true%20for%20us%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-745194%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-745194%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3B-%20anything%20new%20on%20this%3F%20All%20of%20my%20client's%20IDs%20are%20sourced%20from%20on-prem%20AD%20%26gt%3B%20AADC%20%26gt%3B%20AAD.%20The%20error%20remains%20on%20my%20existing%20pools%2C%20and%20based%20on%20the%20feedback%20here%20-%20suspect%20it%20will%20with%20a%20validation%20pool%20deployment.%20Moving%20to%20cloud%20only%20IDs%20isn't%20really%20an%20option%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20provide%20any%20more%20detail%20on%20what%20leads%20to%20this%20condition%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-745201%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-745201%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20started%20working%20for%20me%20yesterday%20without%20any%20intervention%20on%20our%20part.%20I%20did%20notice%20that%20the%20RDS%20Infrastructure%20Agent%20updated%20on%207%2F3%2F19%20to%201.0.833.5%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-745379%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-745379%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BThis%20is%20still%20not%20working%20for%20us%20in%20either%20validation%20pool%20or%20production%20pool.%20These%20are%20the%20agent%20versions%20installed%20on%20my%20VM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERemote%20Desktop%20Services%20Infrastructure%20Agent%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Microsoft%20Corporation%26nbsp%3B%201.0.833.5%3CBR%20%2F%3ERemote%20Desktop%20Services%20SxS%20Network%20Stack%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Microsoft%20Corporation%26nbsp%3B%201.0.1904.29002%3CBR%20%2F%3ERemote%20Desktop%20Agent%20Boot%20Loader%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Microsoft%20Corporation%26nbsp%3B%201.0.0.0%3CBR%20%2F%3ERemote%20Desktop%20Services%20Infrastructure%20Geneva%20Agent%26nbsp%3B%20Microsoft%20Corporation%26nbsp%3B%2042.3.9%3CBR%20%2F%3ERemote%20Desktop%20Services%20Infrastructure%20Agent%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Microsoft%20Corporation%26nbsp%3B%201.0.0.1462%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-746582%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-746582%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F368241%22%20target%3D%22_blank%22%3E%40richiewrt%3C%2FA%3E%26nbsp%3BI%20just%20had%20the%20same%20thing%20happen%20on%20this%20end.%20I'm%20super%20interested%20to%20see%20the%20RCA%20for%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-748687%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-748687%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BAny%20update%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-749792%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-749792%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EFor%20us%20its%20the%20same%20as%20for%20the%20others.%20Only%20some%20InCloud%20accounts%20are%20able%20to%20access%20Virtual%20Desktop.%20The%20validation%20pool%20is%20setup.%20InCloud%20as%20well%20as%20AAD%20synced%20Accounts%20get%20the%20following%20error%3A%3CBR%20%2F%3E%3CBR%20%2F%3EErrorSource%20%3A%20RDBroker%3CBR%20%2F%3EErrorOperation%20%3A%20OrchestrateSessionHost%3CBR%20%2F%3EErrorCode%20%3A%20-2146233088%3CBR%20%2F%3EErrorCodeSymbolic%20%3A%20ConnectionFailedUserSIDInformationMismatch%3CBR%20%2F%3EErrorMessage%20%3A%20OrchestrateAsync%3A%20SID%20value%20in%20the%20database%20is%20different%20than%20the%20value%20returned%20in%20the%20orchestration%20reply%20from%20the%20agent%20for%20user%3CBR%20%2F%3E%E2%89%A4Firstname.Surname%40domain.com%E2%89%A5%20with%20Id%20xxxxxxxx-yyyy-zzzz-xxxx-xxxxyyyyzzzz.%20This%20scenario%20is%20not%20supported%20-%20we%20will%20not%20be%20able%20to%20redirect%20the%20user%20session.%3CBR%20%2F%3EErrorInternal%20%3A%20False%3CBR%20%2F%3EReportedBy%20%3A%20RDGateway%3CBR%20%2F%3ETime%20%3A%2011.07.2019%2010%3A42%3A56%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-753448%22%20slang%3D%22en-US%22%3ERe%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-753448%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BIs%20there%20any%20news%20on%20the%20fix%3F%20We're%20unfortunately%20dead%20in%20the%20water%20here%20with%20synced%20accounts.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754119%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754119%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20review%20our%20troubleshooting%20guide%20for%20domain%20join%20issues%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Ftroubleshoot-set-up-issues%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Ftroubleshoot-set-up-issues%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754826%22%20slang%3D%22en-US%22%3ERE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754826%22%20slang%3D%22en-US%22%3ECan%20I%20just%20move%20my%20pool%20to%20validation%20pool%20instead%20or%20cretaing%20new%20POOL%20%2C%20i%20found%20that%20I%20can%20switch%20the%20POOL%20to%20validation%20pool%20using%20command%20below%20Set-RdsHostPool%20-TenantName%20MVPPOC%20-Name%20POCHOST1%20-ValidationEnv%20%24true%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-756071%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-756071%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20we%20know%20if%20there%20is%20a%20fix%20for%20this%20yet.%26nbsp%3B%20I%20have%20installed%20a%20new%20Validation%20Pool%20and%20still%20the%20same%20error.%26nbsp%3B%20My%20agent%20is%201.0.833.5%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-757702%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-757702%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F139744%22%20target%3D%22_blank%22%3E%40Eva%20Seydl%3C%2FA%3E%26nbsp%3BIt's%20been%202.5%20weeks%20now.%20Can%20you%20get%20some%20ETA%20on%20the%20fix%20for%20this%20problem%3F%20Neither%20validation%20or%20production%20environment%20works!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETenantGroupName%20%3A%20Default%20Tenant%20Group%3CBR%20%2F%3EHostPoolName%20%3A%20MyTest_HostPool%3CBR%20%2F%3EFriendlyName%20%3A%20My%20Test%20Host%20Pool%3CBR%20%2F%3EDescription%20%3A%3CBR%20%2F%3EPersistent%20%3A%20False%3CBR%20%2F%3ECustomRdpProperty%20%3A%3CBR%20%2F%3EMaxSessionLimit%20%3A%20999999%3CBR%20%2F%3ELoadBalancerType%20%3A%20BreadthFirst%3CBR%20%2F%3E%3CSTRONG%3EValidationEnv%20%3A%20True%3C%2FSTRONG%3E%3CBR%20%2F%3ERing%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%20getting%20the%20same%20SID%20error%3A%3C%2FP%3E%3CP%3EErrorSource%20%3A%20RDBroker%3CBR%20%2F%3EErrorOperation%20%3A%20OrchestrateSessionHost%3CBR%20%2F%3EErrorCode%20%3A%20-2146233088%3CBR%20%2F%3EErrorCodeSymbolic%20%3A%20ConnectionFailedUserSIDInformationMismatch%3CBR%20%2F%3E%3CSTRONG%3EErrorMessage%20%3A%20OrchestrateAsync%3A%20SID%20value%20in%20the%20database%20is%20different%20than%20the%20value%20returned%20in%20the%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Eorchestration%20reply%20from%20the%20agent%20for%20user%20%E2%89%A4rhythmnewt%40rhythmnewt.com%E2%89%A5%20with%20Id%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E85a45a4c-413d-4074-2e41-08d6e4d9abe8.%20This%20scenario%20is%20not%20supported%20-%20we%20will%20not%20be%20able%20to%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3Eredirect%20the%20user%20session.%3C%2FSTRONG%3E%3CBR%20%2F%3EErrorInternal%20%3A%20False%3CBR%20%2F%3EReportedBy%20%3A%20RDGateway%3CBR%20%2F%3ETime%20%3A%207%2F16%2F2019%203%3A08%3A54%20PM%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUser%20activity%20log%3C%2FP%3E%3CP%3EActivityId%20%3A%2010dd46a2-4836-49f1-8f89-face053b0000%3CBR%20%2F%3EActivityType%20%3A%20Connection%3CBR%20%2F%3EStartTime%20%3A%207%2F16%2F2019%203%3A08%3A54%20PM%3CBR%20%2F%3EEndTime%20%3A%207%2F16%2F2019%203%3A08%3A54%20PM%3CBR%20%2F%3EUserName%20%3A%20rhythmnewt%40rhythmnewt.com%3CBR%20%2F%3ERoleInstances%20%3A%20%3CSTRONG%3Emrs-eus2r0c001-rdgateway-prod%3A%3ARD2818785C114D%3Bmrs-eus2r0c002-rdbroker-prod%3A%3ARD2818788A0588%3B%3C%2FSTRONG%3E%E2%89%A4rmrvw-0%3CBR%20%2F%3E.rhythmnewt.com%E2%89%A5%3CBR%20%2F%3EOutcome%20%3A%20Failure%3CBR%20%2F%3EStatus%20%3A%20Completed%3CBR%20%2F%3EDetails%20%3A%20%7B%5BClientOS%2C%20%5D%2C%20%5BClientVersion%2C%20%5D%2C%20%5BClientType%2C%20%5D%2C%20%5BPredecessorConnectionId%2C%20%5D...%7D%3CBR%20%2F%3ELastHeartbeatTime%20%3A%207%2F16%2F2019%203%3A10%3A26%20PM%3CBR%20%2F%3ECheckpoints%20%3A%20%7BLoadBalancedNewConnection%2C%20TransportConnecting%2C%20TransportConnected%2C%20RdpStackDisconnect...%7D%3CBR%20%2F%3EErrors%20%3A%20%7BMicrosoft.RDInfra.Diagnostics.Common.DiagnosticsErrorInfo%7D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758092%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758092%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F374394%22%20target%3D%22_blank%22%3E%40rhythmnewt%3C%2FA%3EWe%20would%20like%20to%20understand%20more%20about%20your%20domain%20setup.%20We%20observe%20that%20SID%20which%20VM%20resolves%20the%20user%20to%20doesn't%20match%20the%20SID%20we%20are%20getting%20from%20his%20AAD%20token.%20Can%20you%20please%20give%20brief%20overview%20of%20your%20domain%20setup%20and%20how%20it%20is%20connected%20to%20AAD%3F%20Do%20you%20have%20multiple%20domains%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758093%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758093%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F42810%22%20target%3D%22_blank%22%3E%40Joe%20Flynn%3C%2FA%3E%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F42810%22%20target%3D%22_blank%22%3E%40Joe%20Flynn%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EDo%20we%20know%20if%20there%20is%20a%20fix%20for%20this%20yet.%26nbsp%3B%20I%20have%20installed%20a%20new%20Validation%20Pool%20and%20still%20the%20same%20error.%26nbsp%3B%20My%20agent%20is%201.0.833.5%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758094%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758094%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F42810%22%20target%3D%22_blank%22%3E%40Joe%20Flynn%3C%2FA%3E%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CBR%20%2F%3E%3CP%3EDo%20we%20know%20if%20there%20is%20a%20fix%20for%20this%20yet.%26nbsp%3B%20I%20have%20installed%20a%20new%20Validation%20Pool%20and%20still%20the%20same%20error.%26nbsp%3B%20My%20agent%20is%201.0.833.5%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758128%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758128%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305420%22%20target%3D%22_blank%22%3E%40Roop_WVD%3C%2FA%3E%26nbsp%3BI%20sent%20you%20identifiable%20details%20about%20my%20user%20account%20and%20domain%20in%20a%20PM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20setup%20is%20as%20follows%20On-Prem%20AD%20-%26gt%3B%20Ad%20Sync%20-%26gt%3B%20AAD%20-%26gt%3B%20Azure%20ADDS%3C%2FP%3E%3CP%3EI%20do%20have%20password%20write-back%20enabled.%3C%2FP%3E%3CP%3EI%20do%20NOT%20have%20multiple%20On-Prem%20AD%20instances.%3C%2FP%3E%3CP%3EI%20do%20have%20multiple%20stand-alone%20AAD%20(cloud-only)%20instances.%3C%2FP%3E%3CP%3EVM%20in%20question%20is%20domain-joined%20to%20my%20Azure%20ADDS%20instance%20and%20I%20have%20no%20problem%20authenticating%20into%20it%20with%20my%20domain%20credentials.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20looking%20into%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-758732%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-758732%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305420%22%20target%3D%22_blank%22%3E%40Roop_WVD%3C%2FA%3E%26nbsp%3B%20I%20hope%20you%20look%20into%20this%20in%20a%20more%20general%20way%2C%20as%20we%20are%20many%20with%20the%20same%20problem...%20Our%20setup%20is%20exactly%20the%20same%20as%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F374394%22%20target%3D%22_blank%22%3E%40rhythmnewt%3C%2FA%3E%26nbsp%3B%2C%20so%20please%20express%20your%20findings%20here%20for%20us%20all%20to%20see..%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759477%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759477%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F377587%22%20target%3D%22_blank%22%3E%40Mtollex70%3C%2FA%3E%3A%20Thanks%20for%20letting%20us%20know%20that%20you%20have%20similar%20setup%20and%20yes%20we%20will%20look%20into%20it%20in%20a%20general%20way.%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F377587%22%20target%3D%22_blank%22%3E%40Mtollex70%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305420%22%20target%3D%22_blank%22%3E%40Roop_WVD%3C%2FA%3E%26nbsp%3B%20I%20hope%20you%20look%20into%20this%20in%20a%20more%20general%20way%2C%20as%20we%20are%20many%20with%20the%20same%20problem...%20Our%20setup%20is%20exactly%20the%20same%20as%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F374394%22%20target%3D%22_blank%22%3E%40rhythmnewt%3C%2FA%3E%26nbsp%3B%2C%20so%20please%20express%20your%20findings%20here%20for%20us%20all%20to%20see..%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759731%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759731%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20identified%20a%20bug%20when%20are%20in%20this%20setup.%20This%20is%20now%20documented%20here%20%3A%20%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Virtual-Desktop%2FAnnouncement-Connectivity-issues-from-synchronized-users-to-VMs%2Fm-p%2F759642%23M1036%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-Virtual-Desktop%2FAnnouncement-Connectivity-issues-from-synchronized-users-to-VMs%2Fm-p%2F759642%23M1036%3C%2FA%3E%3C%2FFONT%3E%26nbsp%3B%20.%20We%20are%20actively%20working%20to%20fix%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759785%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759785%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20update%2C%20I%20hope%20the%20fix%20comes%20soon!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-762113%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-762113%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305420%22%20target%3D%22_blank%22%3E%40Roop_WVD%3C%2FA%3EGlad%20to%20hear%20there%20is%20a%20fix%20underway.%20Can%20you%20provide%20us%20at%20least%20a%20rough%20ETA%20please.%20We%20are%20currently%20investigating%20moving%20some%20of%20our%20systems%20to%20WVD%20but%20right%20now%20our%20investigations%20and%20POCs%20have%20had%20to%20go%20on%20hold%20because%20of%20the%20broken%20resource%20templates%20and%20now%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20also%20please%20comment%20as%20to%20when%20this%20service%20will%20be%20covered%20under%20full%20support%20and%20SLA%20if%20clients%20such%20as%20ourselves%20are%20looking%20to%20go%20to%20market%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMark%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759473%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20An%20internal%20error%20occurred%20%2F%20can't%20connect%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759473%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F374394%22%20target%3D%22_blank%22%3E%40rhythmnewt%3C%2FA%3EThanks%20for%20sharing%20this%20detail.%20Its%20very%20helpful%20to%20understand%20the%20setup.%20We%20have%20recently%20introduced%20a%20change%20where%20we%20need%20User%20SID's%20from%20VM%20and%20token%20to%20match%20before%20we%20allocate%20a%20session.%20There%20seems%20to%20be%20a%20case%20with%20AADDS%20where%20they%20may%20not%20always%20match.%20We%20are%20currently%20investigating%20how%20do%20we%20handle%20these%20scenarios.%20I%20will%20keep%20you%20posted%20on%20progress.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

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.

 

46 Replies
Highlighted

@gdglee We've exactly this same issue, we tried to open a case, but it's not supported for preview services :(

Highlighted

@P_haem good to know we're not the only ones.

Highlighted
It's seem's to be cause by the agent upgrade (yesterday around 10PM for us) : New agent version : 1.0.833.4
Highlighted

@P_haem So were you able to resolve?

Highlighted

We are also experiencing this issue.@gdglee 

Highlighted

@gdglee - Same thing on this end. Started happening around 2-3p EST on Friday 06/28. This host pool was perfectly fine prior to this. 

Highlighted

We're having this issue as well. I can RDP into my WDV VMs, but trying to run published apps (browser or RDP shortcut) fail with a connection error.

Highlighted

Same here. This seems to be a widespread problem. For us started last week on Thursday.

Highlighted

@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.

Highlighted

@gdglee 

Same here.

For us started last week on Friday.

Highlighted

@Eva Seydl Thank you for your answer! Do you have any resolution date ? And is there any way to to go back to the previous version ?

Highlighted

@Eva Seydl 

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.

Highlighted

@Eva Seydl - 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? 

Highlighted

@Eva Seydl we're having the same issue as well on both existing host pools that were working properly and on a newly deployed host pool. 

Highlighted

@Eva Seydl-  Would you do me a favor? We have redeployed 3 times to fix this, but didn't fix.....

Highlighted

@Raja R 

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 

Highlighted
Best Response confirmed by Eva Seydl (Microsoft)
Solution
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
Highlighted

Hi @Eva Seydl 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.

Highlighted

@Eva Seydl 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'\"."
}
]
}
}'