RDM 13.5.3.0 Crashing

avatar

RDM has been crashing with SSH sessions that use alternative ports. If I click the X on the tab it is fine, but exit/shutdown/reboot will cause it to crash. A timed out active connection will also cause it to crash. I have tried with other protocols and thus far have been unable to produce the same results.

Event Viewer entries are all the same


Faulting application name: RemoteDesktopManager64.exe, version: 13.5.3.0, time stamp: 0x5ac246ec
Faulting module name: DevolutionsTerminalNative.dll, version: 0.0.0.0, time stamp: 0x5abcdc93
Exception code: 0xc000041d or Exception code: 0xc0000005





David

All Comments (15)

avatar

I will ask our team to investigate.

Regards

David Hervieux

avatar

Hello,

Our office is closed today because of the Easter holiday, but we will have a look at this tomorrow.

I have already opened a ticket to our QA department regarding this because you are not the only one with this issue. I hope that it would be possible for them to reproduce this behavior internally.

Best regards,

Jeff Dagenais

avatar

Hello,

Quick question; do you have a proxy configured in your SSH session?

Best regards,

Jeff Dagenais

avatar

Jeff,

No proxy is configured.


David

avatar

I am experiencing crashing of SSH Shell sessions on 13.5.4.0. Same situation as described by OP, but not limited to alternative ports. Very easily reproduced.

avatar

@David Small and @Brad Richardson,

Are you opening a VPN prior to establish the SSH connection?

Could you export us your SSH Shell session (without the credentials) so that our QA department could analyze them.

Best regards,

Jeff Dagenais

avatar















No VPN. It is using an inherited 'private vault search', for a private key.

Here is the export:

<?xml version="1.0"?>
<ArrayOfConnection>
<Connection>
<Terminal>
<Host>psiweb</Host>
</Terminal>
<TerminalMac />
<ConnectionType>SSHShell</ConnectionType>
<Group>!PSI\Servers\Linux</Group>
<ID>e4a7ccaa-b953-4b6f-b994-68372ea3290f</ID>
<Name>psiweb</Name>
<OpenEmbedded>true</OpenEmbedded>
<Stamp>17664449-9130-40ba-8011-c6e71c312d7a</Stamp>
</Connection>
</ArrayOfConnection>

avatar

Hello,

I will take it from there.

Do you have an ssh entry that do not require a private key that you could try ?


Best regards,

Zacharia Ellaham

avatar

I changed it to a password logon and was unable to get it to crash RDM.

avatar

I take that back. If I don't enter a password in the prompt and click cancel, it will crash RDM every time.

avatar
















No VPN.


<Connection>
<Security>
<AllowOffline>True</AllowOffline>
</Security>
<Terminal>
<Host>172.x.x.x</Host>
<HostPort>9654</HostPort>
<PrivateKeyPromptForPassPhrase>false</PrivateKeyPromptForPassPhrase>
</Terminal>
<TerminalMac />
<ConnectionType>SSHShell</ConnectionType>
<ID>cfd227ad-695d-4f50-a03d-c3e0a4890e94</ID>
<Name>172.x.x.x:9654</Name>
<OpenEmbedded>true</OpenEmbedded>
<Stamp>226d6e2c-fc7d-4b27-9c8b-2c0170f3d142</Stamp>
</Connection>

avatar

RDM is crashing on both connection to SSH - port was not open. And on exit from the session - typing exit.

Crash on exit

Log Name: Application
Source: .NET Runtime
Date: 4/5/2018 13:22:02
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SV-LT-1024.illumio.com
Description:
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 00007FFC69E12FC6
Stack:

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-04-05T20:22:02.744708000Z" />
<EventRecordID>71168</EventRecordID>
<Channel>Application</Channel>
<Computer>SV-LT-1024.illumio.com</Computer>
<Security />
</System>
<EventData>
<Data>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 00007FFC69E12FC6
Stack:
</Data>
</EventData>
</Event>



Log Name: Application
Source: Application Error
Date: 4/5/2018 13:22:04
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: SV-LT-1024.illumio.com
Description:
Faulting application name: RemoteDesktopManager64.exe, version: 13.5.4.0, time stamp: 0x5ac379c2
Faulting module name: DevolutionsTerminalNative.dll, version: 0.0.0.0, time stamp: 0x5abcdc93
Exception code: 0xc0000005
Fault offset: 0x0000000000002fc6
Faulting process id: 0x1544
Faulting application start time: 0x01d3cd19d58bf979
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\DevolutionsTerminalNative.dll
Report Id: c3fca4a0-454e-4dea-a8b2-0080e47ad0f8
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-04-05T20:22:04.941428600Z" />
<EventRecordID>71169</EventRecordID>
<Channel>Application</Channel>
<Computer>SV-LT-1024.illumio.com</Computer>
<Security />
</System>
<EventData>
<Data>RemoteDesktopManager64.exe</Data>
<Data>13.5.4.0</Data>
<Data>5ac379c2</Data>
<Data>DevolutionsTerminalNative.dll</Data>
<Data>0.0.0.0</Data>
<Data>5abcdc93</Data>
<Data>c0000005</Data>
<Data>0000000000002fc6</Data>
<Data>1544</Data>
<Data>01d3cd19d58bf979</Data>
<Data>C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe</Data>
<Data>C:\Program Files (x86)\Devolutions\Remote Desktop Manager\x64\DevolutionsTerminalNative.dll</Data>
<Data>c3fca4a0-454e-4dea-a8b2-0080e47ad0f8</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>




Log Name: Application
Source: Application Error
Date: 4/5/2018 13:22:18
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: SV-LT-1024.illumio.com
Description:
Faulting application name: RemoteDesktopManager64.exe, version: 13.5.4.0, time stamp: 0x5ac379c2
Faulting module name: DevolutionsTerminalNative.dll, version: 0.0.0.0, time stamp: 0x5abcdc93
Exception code: 0xc000041d
Fault offset: 0x0000000000002fc6
Faulting process id: 0x1544
Faulting application start time: 0x01d3cd19d58bf979
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\DevolutionsTerminalNative.dll
Report Id: 84122470-7369-46e3-b085-bfc439701646
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-04-05T20:22:18.969486100Z" />
<EventRecordID>71171</EventRecordID>
<Channel>Application</Channel>
<Computer>SV-LT-1024.illumio.com</Computer>
<Security />
</System>
<EventData>
<Data>RemoteDesktopManager64.exe</Data>
<Data>13.5.4.0</Data>
<Data>5ac379c2</Data>
<Data>DevolutionsTerminalNative.dll</Data>
<Data>0.0.0.0</Data>
<Data>5abcdc93</Data>
<Data>c000041d</Data>
<Data>0000000000002fc6</Data>
<Data>1544</Data>
<Data>01d3cd19d58bf979</Data>
<Data>C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe</Data>
<Data>C:\Program Files (x86)\Devolutions\Remote Desktop Manager\x64\DevolutionsTerminalNative.dll</Data>
<Data>84122470-7369-46e3-b085-bfc439701646</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

avatar

Hello,
We have been able to reproduce the issue, and our engineer are working on a fix.

Regards,

Alex Belisle

avatar










Thanks for the update. I hope it is an easy/quick fix.


David

avatar

I didn't notice a fix in the change log, but it appears the issue is gone in 13.5.6.0.

Thanks.

David