Set-RDMCurrentDataSource : Object reference error when starting PowerShell (RDM CmdLet)
Using:
Remote Desktop Manager Enterprise
13.5.6.0 64-bit
If I run RDM from one machine the PowerShell (RDM CmdLet) opens fine.
On a second machine the PowerShell (RDM CmdLet) opens but then displays the following error message:
Set-RDMCurrentDataSource : Object reference not set to an instance of an object.
At line:6 char:1
+ Set-RDMCurrentDataSource -ID "91c7xxxx-xxxx-xxxx-xxxx-xxxx3e30b83e"
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Set-RDMCurrentDataSource], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,RemoteDesktopManager.PowerShellModule.SetRDMCurrentDatasourceCommand
Both installations are connected to the same shared cloud database with the same user and account.
Both machines running Windows 10 Pro 64-bit.
That ID doesn't match the Data Source ID found under File > My Data Source Information.
Running
Update-RDMUI
produces the following error message:
Update-RDMUI : Object reference not set to an instance of an object.
At line:1 char:1
+ Update-RDMUI
+ ~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Update-RDMUI], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,RemoteDesktopManager.PowerShellModule.UpdateRDMUICommand
Am I missing something?
Jamie
Hello,
If you try to do a full refresh with CTRL+F5, then are you able to open the PowerShell (RDM Cmdlet)?
If not, could you please try to go in File - Data Sources and create a new cloud data source with the same credentials to see if you will be able to open it from this new data source?
Best regards,
Érica Poirier
Hi Érica,
Full refresh CTRL+F5 didn't do the trick but re-creating the Data Source seems to have taken care of the issue!
Thank you.
Jamie
Hello,
Thank you for your feedback! Glad that re-creating the data source resolves the issue.
Best regards,
Érica Poirier