ASG-RemoteDesktop 2019 Generating RDP Error 4360

[3xchaos]

Having an issue with version 12.0.6261.1 of RemoteDesktop 2019 where on some servers when trying to RDP getting an error when trying to connect. "The remote computer returned an RDP protocol error (Return code: 4360). 

When using native RDP (MSTSC) I am able to successfully connect to the server.

Currently running on Windows 10 build 10.0.15063

Again, this is sporadic and started a few weeks ago

[DevOma]

Are you using ASGRD in 32bit or 64bit mode?

[3xchaos]

64 bit version is installed

[DevOma]

Ok - the error message says "Failed to reconnect" - so when does this error occur - when you lost your connection and a automatic reconnect fails? Or when you initially connect to a server?

[3xchaos]

Initial connection

If using VisionApp I get this error on a few connections, if using native windows RDP (MSTSC) the issue does not happen

[3xchaos]

Appears to be an issue with the 2019 version of the App , rolled back to my 2018 version and can make connections to the one that have been giving me issues

[DevOma]

To what version (Patch level) did you roll back?

[support@heens-it.be]

To what version (Patch level) did you roll back?

Hi Olivier,
I just had the same issue and after going back from patch to patch 2, my issue was solved (for now at least ;-))

[jnarayer]

To what version (Patch level) did you roll back?

Hi Olivier,
I just had the same issue and after going back from patch to patch 2, my issue was solved (for now at least ;-))

I did exactly the same roll back to Patch Level 2. (Tried 32Bit version same error and below)
Also the problem is when creating a portable version and running this.
There you also get other errors:
- Return Code 3336: Your computer does not have enough virtual memory available.
- Return Code 3334: Because of a protocol error, this session will be disconnected

These problem do not occur with Patch Level 2

We did a maintenance weekend, and my way of working is not changed, I only updated ASG to Patch Level 3

[pvasirani]

To what version (Patch level) did you roll back?

Hi Olivier,
I just had the same issue and after going back from patch to patch 2, my issue was solved (for now at least ;-))

HI,

Also for us (10 installations) after going back to patch 2 (from patch 3) the issue disappears

[DevOma]

We didn't change anything regarding RDP implementation - currently we have no idea why it is working with Patch2 but not with Patch3

[ClintonJones]

We ran into the same issue, I could connect to a few desktops but anything more than a few (3-5) at once and I would have to disconnect from one to connect to another. I rolled back to Patch 2 and the issue went away.

[Oliver.Matic]

Hello DevOma,

Same Issue here, I am getting the return code: 4360 

ASG-RemoteDesktop 2019
Version: 12.0.6342.1
Windows 10 Enterprise 
Version: 1709 (OS Build 16299.1087)

We own a 5 Admins Licence and the issue started with Patch 3.
How can I uninstall the Patch 3 and use the Patch 2 again? Just start the older Version?

Thanks!

Best Regards,
Oma

[DevOma]

You can reinstall Patch2 (override Patch3)

[Oliver.Matic]

You can reinstall Patch2 (override Patch3)

Thanks, working like expected.
Best Regards,
Oma

[MarkusKn]

We have the same problem with patch 3 (ASG-RD 12.0.6342.1) after installing the following updates on our Windows Server 2016. RDP is built by a Windows 10 v1809.

- 2019-06 Servicing Stack Update for Windows Server 2016 for x64-based Systems (KB4503537)"
- "2019-06 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4503267)"

Installing patch 2 (ASG-RD 12.0.6279.1) helps as workaround.

[dan.lebaron]

Same issue here, we are unable to open more than 9 RDP sessions with Hotfix 3.  If we roll back to hotfix 2 that issue goes away, though other connection issues present.

[JuergenB]

Same issue here, i am unable to open some RDP sessions with Hotfix 3.

Und ich hab die Lizenz noch verlängert um Patch 3 zu erhalten.

[Michael Scholz]

Hi Jürgen,

I'm sorry to hear that. Right now it's not clear what could cause those issues only on some installations. As my colleague stated we didn't change anything related to RDP in patch3. So first we need time to be able to reproduce the problem on our side and also this month is affected by vacation so things generally need a bit more time. If you extended your license then you will be able use the next patches as well.
Can you see similarities between those RDP sessions that won't work ? ( target system / patches ?)

Best regards,
Michael

[Oke87]

Same issue with Patch 3 here.
Rolling back to Patch 2 resolved the problem.