![]() ![]() The user never gets a session established. All that is seen is Event 40: "Session nnn has been disconnected, reason code 12" which I believe is a User Logoff, though as described, If they try again later in the dayīroker shows users connected, arbitration beginning, but no successful arbitration message is logged. No particular group of users is affected, seems to be randomly distributed, might have none today, and several affected tomorrow. Sessions, as well as those reconnecting to existing sessions - does not seem to be a pattern. Repeated attempts by that user over an extended period (hours) gives same error, in the meantime everyone else is logging in happily. ![]() ![]() However, if a particular user gets the error it will persist for them for quite some time. Network utilization is minimal) and are quite happily serving connections to multiple users before and after the error happens. When this occurs, the Brokers show no sign of stress (cpu, memory and We are getting an intermittent error telling the user that "The task you are trying to do can't be completed because Remote Desktop Services is currently busy". The Gateway is lightly utilised (bypassed for local connections), maybe half a dozen users Have in excess of 200 staff connected spread across various sites/collections, most is about 100 at our largest site spread across 3 x RDSH (each 16 core, 32GB RAM). Deployment: Server 2016 RDS deployment with Hyper-V virtuals, 1xGateway, 2xBrokers (HA), 10 x collections (site specific).
0 Comments
Leave a Reply. |