The RD Connection Broker server is not available or the relevant services are not running

%3CLINGO-SUB%20id%3D%22lingo-sub-1033387%22%20slang%3D%22en-US%22%3EThe%20RD%20Connection%20Broker%20server%20is%20not%20available%20or%20the%20relevant%20services%20are%20not%20running%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1033387%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20have%20installed%20Windows%20Server%202016%20STD%20with%20Session%20Host%2C%20Connection%20Broker%20on%20one%20server%20(AD%20domian%20joined).%3C%2FP%3E%3CP%3EThere%20is%20no%20problem%20when%20i%20have%20connected%20less%20than%20~200%20user.%20When%20i%20have%20more%20than%20~200%20users%20when%20i%20try%20to%20check%20%22shadow%20session%22%20i%20have%20error%20%22The%20RD%20Connection%20Broker%20server%20is%20not%20available%20or%20the%20relevant%20services%20are%20not%20running%22.%3C%2FP%3E%3CP%3EWhen%20i%20try%20to%20open%20services.msc%20i%20have%20error%3A%20%22The%20system%20encountered%20the%20following%20error%20while%20reading%20the%20list%20of%20services%20on%3A%20Error%201783%3A%20The%20stub%20received%20bad%20data%22%3C%2FP%3E%3CP%3EWhen%20i%20try%20to%20open%20event%20viewer%20i%20have%20error%3A%26nbsp%3B%20%22Event%20Viewer%20cannot%20open%20the%20event%20log%20or%20custom%20view.%20Verify%20that%20Event%20Log%20service%20is%20running%20or%20query%20is%20too%20long.%20The%20RPC%20server%20is%20too%20busy%20to%20complete%20this%20opertion%20(1723)%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1033387%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ERemote%20Desktop%20Services%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETerminal%20services%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1426170%22%20slang%3D%22en-US%22%3ERe%3A%20The%20RD%20Connection%20Broker%20server%20is%20not%20available%20or%20the%20relevant%20services%20are%20not%20running%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1426170%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F469295%22%20target%3D%22_blank%22%3E%40mmarc120%3C%2FA%3E%26nbsp%3Bi%20have%20the%20same%20problem%20on%20WS%202019.%20Do%20you%20find%20the%20solution%3F%20I%20figure%20out%20error%201783%20happens%26nbsp%3Bwhen%20in%20services%20are%20too%20many%20%22services%20per%20user%22.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fapplication-management%2Fper-user-services-in-windows%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fapplication-management%2Fper-user-services-in-windows%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20what%20do%20with%20that%20i%20dont%20know.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Visitor

Hello,

I have installed Windows Server 2016 STD with Session Host, Connection Broker on one server (AD domian joined).

There is no problem when i have connected less than ~200 user. When i have more than ~200 users when i try to check "shadow session" i have error "The RD Connection Broker server is not available or the relevant services are not running".

When i try to open services.msc i have error: "The system encountered the following error while reading the list of services on: Error 1783: The stub received bad data"

When i try to open event viewer i have error:  "Event Viewer cannot open the event log or custom view. Verify that Event Log service is running or query is too long. The RPC server is too busy to complete this opertion (1723)"

1 Reply
Highlighted

@mmarc120 i have the same problem on WS 2019. Do you find the solution? I figure out error 1783 happens when in services are too many "services per user". https://docs.microsoft.com/en-us/windows/application-management/per-user-services-in-windows

 

But what do with that i dont know.