When running the Set-RDMCurrentDatasource I get the message "WARNING: Data source not found".
I'm able to run the CmdLet from another system without a problem so this isn't a show stopper. Unfortunately, I have all of my development tools installed on this box and would rather not re-image it.
Hello,
The data sources exist only in the current logged user profile. Are you connect with the same user on this machine when using PowerShell?
What data source type are you trying to connect to?
Could you please try to disable the Caching mode to see if this could help?
Best regards,
Érica Poirier
Thanks Erica, I disabled the cache but the error persists.
It does not matter what type of data source I try to connect to as I've tried creating new datasources with Devolutions Server, SQL, SQLite, and Access. None of the datasources are returned when running Get-RDMDatasource (except default SQLite Local Data Source - which is recreated and not shown in the navigation pane)
Hello,
What version of PowerShell is installed on this computer?
Could you please post a print screen of the data source list on this machine when connected with the same user you use with PowerShell?
Best regards,
Érica Poirier
Version 5.1 - Attached is a screenshot of the issue
RDM_error.jpg
Hello,
Could you please go in File - Data Sources and check what is the setting for the On start up option? Is it possible that this option is set to Use default data source and the default data source it should connect to doesn't exist anymore?
Best regards,
Érica Poirier
This was set to 'Last used data source'
Hello,
Are you available for a remote session?
Please send us an email at support@devolutions.net and we will send you our online calendar to schedule an appointment.
Best regards,
Érica Poirier
I was able to identify that the issue was caused by the enablement of FIPS compliance. Once I had the server removed from that OU, the powershell CmdLets are functional again. This will likely be an issue at some point as the terminal servers will be classified as PCI1B and will require FIPS.
Hello,
I'm glad that removing the server from this OU has fixed the issue.
Thank you for your feedback.
Best regards,
Érica Poirier