RDS 2019 issues related with to much services

Question

Hello All,

I have installed new RDS server on latest 2019 standard server. This is standalone RDS server. Server is used by more than 100 people and has enough resources and licenses etc... Users can connect to one RDS web app published on the server without any problems. Everything looks fine till time when i want to check few things on the server.

I can't open services mmc, because i'm receiving error message: "Error 1783: The stub received bad data":

Same from powershell. Result of Get-Service is empty.

Solution is here:

https://learn.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/error-1783...

Completely not acceptable for me, but i think above issue is correlated with: "Per-user services in Windows 10 and Windows Server":

https://learn.microsoft.com/en-us/windows/application-management/per-user-services-in-windows

So if one user can create few services, how much services will be if on server will be more than 100.

I can't open also Remote Desktop Services Overview from server manager:

Next issue is related with monitoring system which can't get some data from this server.

Everything is coming back to normal if server is by fewer people, because when RDS session is disconnected then per user services also are removed. Then everything described above is working correctly.

So my question is what is the solution for this case, because i as administrator can't provide good quality of the RDS service, because i don't see many things described above. Probably is much more.

Answer 1

Hi,

Sorry but your solution can't be accepted. Please fully read my previous post. The problem is related with:
https://learn.microsoft.com/en-us/windows/application-management/per-user-services-in-windows
So please give me a solution for windows server 2019 where more services are generated by users which are connected there. This is not a problem with third party apps, but with some limitation on your system. Everything was fine on server 2016 or 2012 where some per user services were not created.

I'm awaiting for solution for you. Till today in my opinion windows server 2019 is not ready to apply RDS on this system. There are another issues related with splash screen which is described i another post etc...

So please wake up and give us correct update. As i see you didn't get feedback from me about it. Please believe me I'm working with your systems from many years and before i published this issue i checked everything which can be related with this issue.

Answer 2

Hi,

It may also related to third party applications installed on the RDS servers.

To figure out that, we suggest that you could do a clean boot on your RDS server and then let more than 100 users to connect it to see if the issue persists.

Please refer to below link for clean boot.
https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows.

Thanks,

Eleven

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 3

I'd suggest starting a case here with product support on this one.
https://support.serviceshub.microsoft.com/supportforbusiness

Note: a card is required to secure the support contract but support is also free for confirmed bugs.

If you didn't want to go that route you can report this as feedback here on uservoice.
https://windowsserver.uservoice.com/forums/301872-remote-desktop-services

--please don't forget to Accept as answer if the reply is helpful--

Answer 4

Please also look here:
https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/rds-2019-issues-related-with-to-much-services/m-p/1761435

If you want connect to my system just please contact with me directly. I can show you during live remote session where is the problem.

Answer 5

I'd suggest starting a case here with product support on this one. They're the ones that need to see it.
https://support.serviceshub.microsoft.com/supportforbusiness

Also this is not a fix but it is likely the reason you cannot open services.msc. Because of the 256 kb buffer limit. I'd guess the Server Manager issue is related to this buffer limit,
https://learn.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/error-1783-services-msc

--please don't forget to Accept as answer if the reply is helpful--