Number of RDP sessions causing RDM to crash
I am using RDM Enterprise 10.0.19.0 and I am running into a problem with RDM crashing whenever I try to open more than 27 RDP sessions (different servers, one session to each server, mix of 2003, 2008, R2, 2012, XP, etc.). It seems that when I have around 28 sessions open, RDM crashes on me (I am using a single line on my RDM tab bar). I say around 28 because I can’t think that I have seen more than 27 listed on the dropdown Window List menu when I have tested this. I’ve tried opening the connections (different combinations of systems) using both PlayLists and manually through the DashBoard. I get the following error from RDM:
Problem signature:
Problem Event Name: APPCRASH
Application Name: RemoteDesktopManager.exe
Application Version: 10.0.19.0
Application Timestamp: 5481b7f1
Fault Module Name: clr.dll
Fault Module Version: 4.0.30319.18444
Fault Module Timestamp: 52717e84
Exception Code: c0000005
Exception Offset: 003793f2
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: a5ec
Additional Information 2: a5ec0690d321031f7b5b739bed09f4c3
Additional Information 3: b430
Additional Information 4: b4307064d54d1a3db8d65b4a6333af1f
What I have done to work around this is to configure 26 servers per playlist (and just have multiple playlists). When I complete work on servers from playlist one, I move on to playlist two, etc. This issue has been occurring for a while (it isn’t new to this version of RDM), just I haven’t looked into it with much detail until now.
I have also notice that RDP sessions updating slowly the more sessions that I have open in RDM. When I start out manually opening sessions one by one, the RDM Dashboard updates the open sessions as I open them quickly. After maybe a dozen or so, it starts to take some time before the RDM Dashboard updates itself (i.e., making the session name darker to indicate that it has an existing open session with it).
I’ve also noticed that after RDM crashes now (when you start RDM back up), RDM no longer indicates that there were any open sessions prior to the crash. Previously, if RDM crashed, it would report that there were open sessions when it crashed (I assume that RDM kept track of opened sessions when they are not closed properly – maybe via a file or something). Anyway, it doesn’t report that information when it crashes like it used to. Has this capability been removed (or is 28 sessions too many for this feature to work)?
Thanks
All Comments (3)
Do you use RDM 64 bit?
David Hervieux
Good call, I missed that one. I should have provided that info in my original post. It’s Monday (slow brain day).
No, I am using the 32-bit flavor. I was using x64 when you first released it (back before the shortcut was even created for it) and back then, the 64-bit had other issues, and so I’ve been using the 32-bit version since with much success. I just tried a test using the 64-bit and it works opening up to 40 servers (so the limit appears to be an issue with the 32-bit version of RDM) – I can try more servers if you like me to test. Also, having just tried the 64-bit version again, the things that were broken previously seem to be working now. I will admit that the 64-bit version even loads quickly now (it was horribly slow originally). Good work – I think that I may start using 64-bit again, and can create a single playlist for all the servers.
Do you want me to try anything for testing using the 32-bit version (to see if it can be resolved using the 32-bit version)? Do you know if the 64-bit has a limit?
Thanks
The only thing you can try with the 32 bit version is the Large Memory Aware setting:
http://help.remotedesktopmanager.com/troubleshooting_largememoryawa.htm
David Hervieux
