Object reference not set to an instance of an object.
When upgrading to a newer version of RDM, in this case from multiple older versions, (2020.3.27 / 2021.1.20) to 2021.1.27 , the first startup of the application gives us the error: Object reference not set to an instance of an object. upon 1st launch.
Stacktrace:
NullReferenceException - Object reference not set to an instance of an object.
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.get_DataSourceSettings()
at Devolutions.RemoteDesktopManager.Managers.PasswordTemplateManager.get_CanEditShared()
at Devolutions.RemoteDesktopManager.Managers.PasswordTemplateManager.get_CanEdit()
at Devolutions.RemoteDesktopManager.Managers.MainMenuManager.SetControlStates(ConnectionControlStates states)
at Devolutions.RemoteDesktopManager.Forms.FrmMainRibbonBase.SetControlStates(ConnectionControlStates states)
at Devolutions.RemoteDesktopManager.Forms.FrmMainDocumentManager.c2629e5386ca79647ba654083fc6ae347(Object c19f185fd70cefc696ba148af1c4faf54, EventArgs cf1018bb83ec7debd818319fd3cb4844e)
at System.Windows.Forms.Form.OnShown(EventArgs e)
at DevExpress.XtraEditors.XtraForm.OnShown(EventArgs e)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
I have the impression is has to do with configured but removed features, since cleaning the localappdata folder often solves the problem, but all local settings are reset to default.
Sometimes we can close the application and restart, then it is solved, but now it isn't. also cleared my local user profile using:
Remove-Item $env:Appdata\Devolutions\RemoteDesktopManager -Recurse -Force
NOTE! above screenprint is with my existing RemoteDesktopManager.cfg file, where theme is set: <Theme>Office2016Dark</Theme>
After only renaming that file: ren RemoteDesktopManager.cfg RemoteDesktopManager.1.cfg, the RDM started up without any error, but in the default blue color.
So it IS some (now legacy) setting in the config file. I've attached my old copy with some information obscured with SOMEINFOREPLACED
Regards, Ben van Zanten
RemoteDesktopManager.cfg
All Comments (10)
Hello Ben,
Thank you for contacting us on that matter!
Instead of deleting your local files, you can instead go under the "Window" tab in RDM's ribbon and use the "Reset Layout" feature.
This option should also fix this issue.
Let me know if that helps!
Best regards,
James Lafleur
Hi James
I'm sorry that doesn't work. if we dismiss the error, we get an empty RDM screen without any menu items so there is no Reset Layout to be clicked..
Regards, Ben van Zanten
I've protected the code that crashes, it's a start. We will take a look at your configuration to see what the underlying issue might be.
The crash fix will be available in the next release.
Best regards,
Stéfane Lavergne
This has been happening to me dozens of times a day since upgrading to Remote Desktop Manager 2022.3.10.0 64-bit (Beta). It happens almost every time I click on a new object or session within RDM.
Can someone please help me with this?
Thank you,
Richard Mulrain
Hi Richard,
First of all, thank you for testing with the Beta. I would suspect that the exception you are seeing isn't the exact same call stack as above. To help us diagnose the issue we would need the details of your error(s).
You can post them here, open a support ticket with support or send us the error report using the "Send Error Report" button and we will investigate and get back to you.
Best regards,
Stéfane Lavergne
Stéfane,
Sure, no problem. But I have been sending Devolutions reports from within RDM using the "Send Error Report" button since the issue first appeared for me, but no one has gotten back to me nor acknowledged my reports at all.
Thank you,
Richard Mulrain
Richard,
Thank you for the heads-up, I will investigate as this is not normal.
Best regards,
Stéfane Lavergne
Hi Richard,
After investigation it was confirmed to me that the issue has been resolved internally with build v2022.3.11. From what I understand it has to do with a bug in the Macro/Script/Tools.
Unfortunately this version (.11) also has a few high-DPI bugs, so we are not expecting to release it (publicly). We expect to have the v2022.3.12 ready in the next few days. In order to get you unblocked, we could send you a download link of .11 if you like.
Best regards,
Stéfane Lavergne
Yes, since I would like to keep testing the RDM Beta version, please send me the download link of .11
Thank you,
Richard Mulrain
Hello Richard,
I just sent you a private message with a link to the 2022.3.12 beta version of RDM. Let us know if it helps with your issue!
Best regards,
Richard Boisvert