RDM also not responding

We are aware that the 64 bit version is slower and unfortunately there is not much we can do:

http://blog.devolutions.net/2014/02/32-bit-vs-64-bit-versions-of-remote.html

Could you try the ngen script here:

http://forum.devolutions.net/topic11780-bit-and--bit-rdm-launches-horribly-slowly.aspx

Sorry, I haven't tried the script yet (because the issue didn't occur again) - until today. Then when I launched RDM after it had crashed, I received a popup that a new version was available. Then I realized that this may be the reason that RDM stops responding because it is trying to perform a new version check.

Previously, one of my posts (a Feature Request) was to have RDM periodically check for new versions not only at startup but on a schedule (i.e., daily, etc.) for those of us that leave RDM running for days without closing it. Was this request ever implemented? When I checked this morning (manually), RDM didn't report any new release available. Now it reports that there is a new version available. I have to wonder if RDM is trying to check for a new version (on a "scheduled" check) and because a new release is available, this is causing RDM to lock up. RDM hasn't locked up in a week or two and there hasn't been a new release in a week or two.

When did the new release become available today? About 30 minutes ago is when RDM stopped responding.


Thanks

I have created a new release this morning at this time. I'm not aware that RDM check except at startup. This is really strange.

Yeah, definitely strange.

Another thing that is strange. On my home PC I have RDM 9.2.4 installed. This morning when I did an update check (Help - Check Version), RDM reported that it is up to date. I restarted RDM and my home PC, got the same result. I checked About and RDM reports 9.2.4 as the installed version. I checked the website and it shows 9.2.6 as the current version.

I have not copied any of the configuration from my work PC to my home PC since 9.2.4.

Hi,
We only have activated the auto update for those who have the beta auto update flag. I always wait few days before activating the global auto update.

Sorry, I should have mentioned that this is a manual update check. I do have the BETA update check box selected, and the auto-update doesn't report the new version when I launch RDM either. The client doesn't recognize the new version whether it is the automatic update check or a manual check.

Could you retry?

Before the check, I verified that both boxes are checked (check for updates and include BETA versions in update check).

I retried on my home PC and now RDM recognizes that there is an update available (so I downloaded and installed it).

I'm not sure if it matters but I noticed in the update popup that there was a v9.2.5 released. Neither of my RDM installs (work or home) reported that v9.2.5 was available as an update.

Thanks for your help

Just a follow up...

The RDM client locking up is not related to the RDM updates. The update today didn't cause any problems with my RDP sessions. RDM did lock up one time on Monday (2 days ago) but has behaved since then.

Is there a debug mode for RDM? Having done some programming, I know that sometimes I put code into my apps to enable debugging and make troubleshooting with users easier. Does RDM have that feature?


Thanks

We have a debug level in File->Options->Advanced but this could slow down you apps if you put a number too high

OK - my issue has nothing to do with new RDM releases, I was wrong. There has been a new release out and it didn't cause RDM to lock up plus RDM has locked up on me a number of times recently when there wasn't an update to RDM available. I wasn't sure that the RDM update check was the problem but it was the only thing that I could find at that moment that might be causing the issue. So if that wasn't the problem, I am hoping to figure out what is causing the problem. Are there specific flags that you would recommend for setting with the debug level? In summary - my problem is that occasionally RDM stops responding when I close RDP sessions. I usually have to kill the RDM process to recover. Even though I have logged off of the embedded RDP session, the RDM client still has the tab displayed in the top navigation area (RDM looks like I selected an embedded RDP session and clicked "Undock" on the tab - but I actually logged off from the client side). When it locks up, RDM has the tab in the navigation area and crashes. It only happens occasionally (maybe once a day if even that much).

Is there a recommended debug level (or flags) that I should start out with?


Thank you

Could you try clear your application log and set the basic debug level to 1.

I'm curious about this issue as well.


Closing down tabbed RDP sessions (within RDM) is sporadically causing RDM to stop responding, then ultimately, I need to terminate the RDM application and relaunch.

Again, it isn't consistent. Running version 9.2.8 Enterprise. I've flushed my application log and bumped the debug to 1. I will report back with log entries when it occurs.

My RDM crashed but didn't write much to the application log:

The program RemoteDesktopManager.exe version 9.2.8.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1048
Start Time: 01cf6aae373d4d31
Termination Time: 44
Application Path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe
Report Id: f08ffdbc-d6c0-11e3-a9b6-005056c00008

I'm thinking that I should increase the debug logging (currently set to 1)?

This will not help. This is a native error and RDM can't catch it. It must come from the Microsoft ActiveX directly.

It did it again. Ran fine the past day or so, and I "started" it three times this morning (I had to reboot a couple of times) - patch Tuesday updates and all. But it was running, I tried to close RDM and it hung again. I forced the process closed, restarted RDM and there was an update available (an update that wasn't there this morning). Strange that it (seems to have) noticeably hung twice when an update becomes available.

Hi,
It's really seems related to the auto update detection. This morning it was a beta notification but the file transfer failed. This is now available. Could you try to disable the auto update notification?

I disabled the auto-update notification and haven't had an issue with it. I've done a manual check and know that 9.4.3.0 is out, but RDM hasn't locked up yet (while auto update check is disabled).

This is interesting. I don't know what it is exactly but perhaps a dialog appear in another thread causing a lock. I will investigate that.

I thought about that but when the lockups occur, I haven't been able to find any additional dialog that is open or RDM process that is running. Maybe just a fresh install will do the trick...

This RDP/RDM lockup has been killing me. I've been pouring through Google searches and, finally, I might have a workaround.

I applied this registry change two weeks ago, and have NOT had a single instance of RDP/RDM locking up since. Maybe coincidence.

Technically, it applies to Windows 2008/2008 R2, but decided to try it with Windows 7 SP1 64-bit.

Your mileage may vary. Attempt at your own risk. Just sharing my efforts.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Sysprocs]

Value name: splwow64.exe
Data type: REG_DWORD
Base: Hex
Value data: 0

References:
http://support.microsoft.com/kb/2513330
http://community.spiceworks.com/how_to/show/2907-remote-desktop-will-hang-when-logging-off-of-win2008

Good find - thanks.

RDM hasn't locked up in a week or so. Ironic though, I made the change today on my Win7 x64 client (while RDM 9.4.7 BETA was running) and once I closed my final 2008 R2 session, RDM locked up. Maybe it required a restart of RDM?

Hopefully this will resolve the issue.
edited by STGdb on 6/16/2014

Well...the fix was short-lived. Having lockups on RDM again.
edited by AuxMax001 on 7/24/2014