RemoteDesktopManager crashes on new connection

RemoteDesktopManager crashes on new connection

avatar

Most of the time I try to open a second remote desktop connection on RDM (unfortunately not all the time), I get the following exception:

Unhandled exception at 0x617cf63d in RemoteDesktopManager.exe: 0xC0000005: Access violation reading location 0x00000240.

This only happens at home, where I have a single monitor (as opposed to dual monitors at work) and an NVIDIA GPU (as opposed to an embedded ATI at work)

I'm guessing that this is probably some graphics card related problem, even though I can't understand why.

I'm also pasting here the call stack, as found out by Visual Studio 2010 (hoping it helps):



















































All Comments (11)

avatar

Hi,
Do you open the remote connection in embedded mode? Do you have that if you open it in external mode?

David Hervieux

avatar







No, it happens only in embedded mode (as far I can see)

avatar

Have you installed the latest Remote Desktop Client?

http://support.microsoft.com/kb/969084

David Hervieux

avatar








I'm on 64-bit Windows 7 SP1 on both PCs (home and work), so it doesn't seem I need this update. I'm fully updated as well, if that's any help.
edited by GSchizas on 4/22/2011

avatar

Hi,
You right, it's weird, the ActiveX is crashing. Do you have the latest video dirver installed? Also, can you try to disable the theme or change the screen color depth just for a test.

David Hervieux

avatar







I have the very latest NVidia driver (270.61) on my PC, yes (I wouldn't be surprised if it introduced some bug - but I only get it with RDM)

Ok, I've stopped the "Desktop Window Manager Session Manager service" (uxsms) and it crashed like this:









































































I've started the dwm and just changed the theme (disabled transparency) and got this:












































































(sorry for missing that earlier, apparently I pressed add message before pasting the stacktrace)
edited by GSchizas on 4/26/2011
edited by GSchizas on 4/26/2011

avatar

Hi,
What I mean, is in the RDP session properties, in the experience tab, try to disable most of the properties for a test. You can also try the Microsoft Remote Destkop Connection Manager tool, we share the same activex.
edited by dhervieux on 4/26/2011

David Hervieux

avatar

Ok, it seems it *is* working when I just disable Desktop Composition (I also disabled desktop background, but I do that anyhow).

MS Remote Desktop Connection Manager is working with no problems at all, even when I enable Desktop Composition there (it was not where I expected it to be).


So, the problem seems to be that, when you enable Desktop Composition, you can't have more than one RDP connection.
edited by GSchizas on 4/27/2011

avatar

Addendum: Sometimes MS RDCM does seem to have some glitches (probably GPU related), but there isn't any crash (well, not yet at least :))

avatar

Ok, now it (RDCMan) really crashed, and with a stacktrace very similar to the previous ones, so this is probably a graphics drivers problem...

Oh well, I guess I'll have to live with no desktop composition for a while...
edited by GSchizas on 4/27/2011

avatar

Thank you for the information, may I suggest you to report that to Microsoft. They have more resources to investigate the ActiveX problem and they might also have contact with Nvidia. We do our best to make the best software, but we still are a very small company in the RDP world.

Thank you again.

David Hervieux