Mir geht es genau so, "The remote computer returned an RDP protocol error (Return code: 4360).
Teilweise lassen sich nur 5 gleichzeitge RDP verbiundungen öffnen,manchmal 15 und mehr oder auch nur 3.
Schließe ich eine Verbindung, kann eine neue geöffnet werden.
Scheinbar frisst da irgendwas Speicher / gibt diesen nicht wieder vernünftig frei / benötigt zusammenhängende Speicherbereiche Bereiche?!
Der Fehler lässt sich (re) provozieren.
Hatte auch schon öfters die FM aus der Anlage - da hat sich das komplette ASG verabschiedet.
W10 18.03
ASG2019 12.0.63.42.1 32 bit
Weiter konnte ich beobachten, dass mit 5-10 Session ca. 1,3 GB auf dem Client benötigt werden.
Patch2 ist mit 500 MB zufrieden, bei 10 Sessions.
Die Grenze (Return code: 4360) liegt da bei mir bei 30 Sessions / 1,6 Gb Speicher - der Client hat aber noch 5 GB frei.......
Nachdem alle 30 Sessions geschlossen sind, wird der RAM nicht freigegeben - ASG belegt weiter 1,4 GB, ohne eine geöffnete Session.
Hoffe dies hilft etwas beim Eingrenzen der Ursache.
We have replaced the mstsc-Interop-Assemblies for the next patch - hope that this helps - currently we can't reproduce the error in our test environments
DevOma Wrote:We have replaced the mstsc-Interop-Assemblies for the next patch - hope that this helps - currently we can't reproduce the error in our test environments
Fine. When will the fix be available or could you provide any files to test?
We are using Windows 10 1809 OS build 17763.720.
ASGRD consumes a lot of memory. If I open approx.. 7 or sessions, I get a RDP protocol Error (Return Code: 3336)
ASGRD Error log shows: Out of memory.
It appears to occur if 1 GB of memory is reached.
Memory usage is 80% of 8 GB with ASGRD.exe 1.042.920 K allocated.
After closing and reopening ASGRD all is fine.
The same sessions are reconnected with ASGRD.exe 618,3 MB allocated.
Do you use 32bit version? It should work with 2GB mem - I will check if this is still working - but if it is possible you should use 64bit version - there should be no memory limitation (only your installed memory :-)
We try to have a stable version by end of next week
DevOma Wrote:Do you use 32bit version? It should work with 2GB mem - I will check if this is still working - but if it is possible you should use 64bit version - there should be no memory limitation (only your installed memory :-)
We try to have a stable version by end of next week
Yes, 32bit Version.
Currently ASGRD2018 (11.0.6169.1) 32bit Version is used by our admins.
We plan to upgrade.
Do we risk any problems switching to 64bit Version of ASGRD 2019 Patch4?
Thank you.
Same issue here, once i get over 6 RDP connections. I get the following:
The remote computer NAME returned an RDP protocol error (Return CodeL 3334)
Because of a protocol error, this session will be disconnected. Pleae try conncting to the remote computer again.
If i close some of the connections or close and re-open ASG-RD it works again for a period of time and can open more than 6 connections, but then over time that day the error comes back.
What do you need to find a fix for this, its been an ongoing issue since post HF2? Its annoying\frustrating.
(09-09-2019, 10:19 AM)DevOma Wrote: We plan to publish a new patch in the next days...
How exactly did you manage to solve this problem?
I'm asking because I'm developing a RDP management software myself and I also get the 4360 error from time to time.
The strange thing about the error is that sometimes it already occurs on the second or third connection, and sometimes I can rapidly open over 10 connections without any problems. Also when the error occured once I cannot open anymore connections until I restart my application completeley.
My best guess at the moment would be that it has something to do with our ActiveDirectory because I get the most 4360 errors when a lot of users are working in our domain. Maybe the Active Directory server is dropping some of the login requests if a lot of users are working and this causes the 4360 error.
HI,
I am new here but we have the same problems some servers can be reached with ASG and some not its frustrating. Is there a solution we have version 12.0.6279.1 version and windows 10 build 1903
05-02-2020, 11:48 AM (This post was last modified: 05-02-2020, 11:49 AM by TheNetStriker.)
I found a solution for my problem in my own application in the meantime. The problem only seems to occur on some computers for unknown reasons, but I found a setting in the rdp advanced settings that solves the problem on those computers:
rdp.AdvancedSettings8.BitmapPersistence = 0;
This slows down the rdp connection a bit, but with this I never got the error again. I've added a workarround setting that can be enabled on computers that have this problem. It already helped on multiple computers that had the same problem.
