RDM can't start RDP session from shortcut

RDM can't start RDP session from shortcut

avatar

Hi,


When I'm trying to start RDP session from the shortcut (something like this "C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager64.exe" /DataSource:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /Session:yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy) I'm getting a error. I've checked x86 and x64 binaries and both don't work. RDP sessions starts without any problems form main application UI.


There is the message box with error and the error message from the RDM log file (RemoteDesktopManager.log):





[10/9/2015 10:09:39 PM]INFO System.NullReferenceException: Object reference not set to an instance of an object.
at Devolutions.RemoteDesktopManager.Business.ScreenHelper.GetDestinationScreen(DisplayMonitor displayMonitor)
at Devolutions.RemoteDesktopManager.Managers.ImportExportManager.WriteToRDP(Connection connection, OpenConnectionMode openConnectionMode)
at Devolutions.RemoteDesktopManager.Business.Connectors.RemoteDesktopConnector.c9a834003f7a84c0603e685c7af8007af(Connection c6aea3d31dfb3fea36c5f53f7fe93584c, String c9890c1f0f290f694272fffe60620576f, OpenConnectionMode c602973c05c2f5870e41c508b048b13c5)
at Devolutions.RemoteDesktopManager.Business.Connectors.RemoteDesktopConnector.c99f8b6a30c4753720e3800500eac2816(Connection c6aea3d31dfb3fea36c5f53f7fe93584c, String& cfa64b658f4d2813cc9a1449b28fac837, OpenConnectionMode c602973c05c2f5870e41c508b048b13c5)
at Devolutions.RemoteDesktopManager.Business.Connectors.RemoteDesktopConnector.Connect(Connection connection, OpenConnectionMode openConnectionMode)

All Comments (5)

avatar

Hi,
I will report this. This should be fixed soon.

David Hervieux

avatar

Still isn't fixed in 11.0.2.0.

avatar

It assigned but not fixed indeed.

David Hervieux

avatar

Hello,

This should be fixed in the next version, could you try it out and give us some feedback when it's available for download? Thank you.

Regards,

Hubert Mireault

avatar

Hubert,

Thank you for the quick response! It's fixed in 11.0.3.0.