Key Agent Manager crashing
Trying to start the Key Agent Manager (or start a session for entry using it) crashes the application. This issue only appeared since the new update 4 days ago at just after 12 noon on 11/4/2020.
The error is:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Reproduction 1:
- Tools > Key Agent Manager
- Click "Start Agent"
- It then says Agent is Running, but "Start Agent" button is still available and "Stop Agent" and "Add Key" buttons are not.
- Clicking "Start Agent" produces the crash.
Reproduction 2:
- Start Session for any entry that has "Use SSH authentication agent" enabled will produce a crash.
Corrections tried:
- Re-installed the app.
- Delete \AppData\Local\Devolutions\RemoteDesktopManager and start with fresh settings.
Versions:
- Enterprise RDM 2020.3.14.0 64-bit No Add-Ons
- .NET Runtime v4.0.30319
- .NET Version: Version 4.7.2 or better
- Windows 10 build 19041.610
Notes:
- Key Agent Manager is not set for startup.
- If I do not start the Key Agent Manually, then starting any SSH session that uses Key Agent Manager simply crashes the application.
- SSH for an entry will connect if I disable "Use SSH authentication agent" and use a standalone private key
- I cannot run Performance Profiling since the application crashes
Windows Event Viewer Entry 1
Event Manager > Application
Error
Event 1026 .NET Runtime
Application: RemoteDesktopManager64.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FF9AF35FFA8 Stack:
Windows Event Viewer Entry 2
Event Manager > Application
Error
Event 1000 Application Error
Faulting application name: RemoteDesktopManager64.exe, version: 2020.3.14.0, time stamp: 0x5fa03495 Faulting module name: DevolutionsProtocols.dll, version: 2020.10.30.1, time stamp: 0x5f9c594f Exception code: 0xc0000005 Fault offset: 0x000000000009ffa8 Faulting process id: 0x22b8 Faulting application start time: 0x01d6b305896e7552 Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe Faulting module path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\x64\DevolutionsProtocols.dll Report Id: 0497d769-3b78-49ec-aa59-84652066e956 Faulting package full name: Faulting package-relative application ID:
Application Log attached.
2020-11-06-RemoteDesktopManagerApplicationLogs-DavidSchargel.log
All Comments (11)
Hello,
Thank you for contacting us on that matter!
Even though performing a clean installation did not work, would it be possible for you to create a portable version of RDM on your Desktop and see if this issue still occurs?
To do so, you will need to do the following:
1- Download the .zip file below:
https://remotedesktopmanager.com/home/thankyou/rdmbin
2- Create a new folder on your Desktop
3- Extract the content of the .zip file into the folder created at #2
4- Go in this folder once the .zip file has been extracted and run remotedesktopmanager64.exe
5- Enter your current serial
According to my tests, once the Key Agent Manager is started using the "Start Agent" button, it is no longer possible to press on this button again until you have used the "Stop Agent" button.
Best regards,
James Lafleur
Ugh.
With the portable version, I was able to Start/Stop Agent at first. I am then able to Add a Key (plus password). Then things crashed repeatedly once tried to Stop Agent.
After that first crash anytime I re-launched the portable version and clicked Start Agent, I can enter the password, close the dialog, and connect. As soon as I click Stop Agent, the application crashes again. I also get a crash when I "Remove Key."
When no keys are added, the application does not crash and I can open/close app and click the Stop Agent or Close buttons with no issues.
As I mentioned for #3 above...yes, normally once the Key Agent Manager is started, the "Start Agent" button is not available and the "Stop Agent" button is the only option (besides add/remove keys). In the submitted issue this AM, I did not have a "Stop Agent" button available.
James,
I tried again with trashing the settings files in the Portable directory and am still not successful.
I don't know if it is related but 2 days before the update to Enterprise RDM 2020.3.14.0 64-bit, I installed KB4580419 and KB4580364.
David
Hi,
i have also Problems with RDM Enterprise 2020.3.14.0 64-bit. Every SSH Sessions with enabled Agent are crashing on connect.
If i disable this Option, SSH Session is working
If the Key Manager stopped, on SSH Connect with enabled Option, i got the following Error Message:
I dont have any Problems with 3.13.
Regards
Sebastian
Hello,
Not quite sure why you get the error when the KeyAgent is activated, but you can refer to this help topic for the solution :https://kb.devolutions.net/rdm_error_code_fail_1_non_speciffic_error.html
Best Regards,
Etienne Lord
Etienne,
This did not solve my issue. I enabled every single Custom Algorithm to Cipher, Host Key, Kex, MAC and nothing changed. I am still crashing as indicated in the original and updated forum submissions.
David
Sebastian & Etienne,
For what it's worth..if the Key Agent Manager is NOT running and I try to open a Session with an Entry that still has the "Use SSH authentication agent" enabled, I AM able to get that "Error code FAIL (-1) non specific error". This does not fix any issues though.
David
I am seeing the exact same behavior since 2020.3.14.0. I use the key manager to connect to most of my servers but since the last update RDM crashes every time I try to connect to one using an ssh key. When using a password I can connect successfully.
I also tried to open the "Key Agent Manager" but nothing happen when I click on it.
Mathieu
Hello Everyone,
Our Engineering Department just informed me that RDM 2020.3.16.0 will contain a fix for the Key Agent Manager.
Once this version is released, these crashes should no longer occur.
Best regards,
James Lafleur
I just got the 2020.3.16 update and I can confirm this fixed the issue for me.
Thanks,
Mathieu
Tested and working with 2020.3.16 update. Thanks!