Because of a protocol error...

Hi cptsparrow,

Please have a look at the following topic
http://help.remotedesktopmanager.com/troubleshooting_protocolerror.htm

Best regards,

Closing RDM works all the time. But how much longer will this go until its resolved? Never had this issue in RDM Standard. Only once everything was moved to free. There are times I do have 20-30 tabs open. Closing RDM and reopening everything can be a real pain.

Solution 1 didnt work. I will resort to Solution 2 but having an idea when this bug will be fixed would be nice.

Hi,
This is not a bug. It's a limitation in the 32 bit version (Windows limitation). This was also happening with the Standard edition as well and it depends of which RDP host you use. RDP 8.0 use a lot more of memory. By the way RDM Free is just a rename of the Standard and it's build exactly the same way.

RDM 64 bit does not have this limitation since it's possible to use much more memory in the same process.

Sorry I forgot the link:

http://help.remotedesktopmanager.com/troubleshooting_largememoryawa.htm

This could also help if you enable the Large Memory Space

Thank you for your reply. I understand the 32 bit version is limited by windows. But currently the 2GB limit isnt a windows limitation, its a software limitation. RDM should be able to utilize up to 2GB, 3GB(x86) or 4GB(x64), if large address aware is used. However, the memory footprint on RDM was lower than 400MB. I rarely see RDM go above about 800MB. Most Ive ever seen it use is ~ 1GB. In my case, when I ran into this issue, I had 3 external SecureCRT sessions open, after that I could not open any other RDP session. (I had no other RDP sessions open on the server). So it just seemed a bit strange to me that I was not able to open even one remote session. Perhaps I am seeing this issue more frequently in RDM of late (and just assumed it was a change in Standard to Free) because I have since moved nearly all of my servers to 2012.

Generally a limitation in software,as in the current version of RDM, is considered a bug. I see you have provided a work around to allow a change in the boot config data. That will hopefully prevent this issue from re-occuring. My main concern was not that there is a limitation to 2GB on RDM 32bit. My concern was that I am seeing this issue with only 3 securecrt tabs open and only 1 RDP tab open, with RDM using less than 400MB, much lower than its 2GB of max addressable.

Either way, thanks for your quick replies. I will continue to watch the memory footprint and if I see issues where RDM can not open RDP's with less than ~ 1GB, I will open another thread. This is by far the best remote protocol program on the market. Enough so you have convinced many of us to go with the Pro version. Just so happened on this current server the free version was running when I ran into this oddity.

Keep up the amazing work, seriously this product is second to none. Nothing else even comes close to what you can do with it.
edited by cptsparrow on 1/29/2015
edited by cptsparrow on 1/29/2015

Hi,
This could be related to another setting if you see it with just one opened tab. Could you verify the auto resize and perhaps turn it off:

http://blog.devolutions.net/2014/10/embedded-sessions-reconnecting-its-a-new-feature-of-the-rdp-activex.html

Its set to default, but I have seen the linked issue as well. Mainly when I try to right click on the tab and select smart-resizing, before I am fully logged in.

Anyhow, Ill keep an eye out for the protocol error. I have RDP dumping memory events to Event Viewer. Maybe if it happens with such little memory use again, we can find out way.

Thanks!

How do you get the x64 version of RDM? I download the MSI and it appears to be for x86.

Hi toddca,

From the installation folder of RDM, just launch RemoteDesktopManager64.exe instead of RemoteDesktopManager.exe.

Best regards,

Perfect! Thanks Jean-Francios -- maybe this should be an installation option...