I'm not sure what is going on, but the `Set-RDMSession` cmdlet no longer works.
```
IsConnected : True
IsOffline : False
Name : Customers
Type : SQLServer
VERBOSE: [Set-RDMSession] Start
Set-RDMSession: Z:\SCRIPTS\powershell\Create-RDMCredential.ps1:77
Line |
77 | Set-RDMSession $cr -Refresh -Verbose
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Your connection is not ready
VERBOSE: [Set-RDMSession] Finish
```
I've rebooted the server multiple times, updated RDM, and updated the powershell module with the same result. It's not a permission problem as every other command works and I can do everything manually in RDM itself.
Is there any way to figure out why this isn't working? Everything looks like it should work.
Thanks,
Chris
Hello VirTechSystems,
Thank you for reaching out to the Devolutions support team.
It looks like this cmdlet has something special, even the get-help returns a get-command.
I will open an investigation ticket for this issue.
I suggest using Set-RDMEntry instead of Set-RDMSession.
Best regards,
Patrick Ouimet
I went back to try that command and I started getting db out of date warnings, so I rolled the module back to be more in line with the RDM version we're at. Everything worked afterwards.
I then changed Set-RDMSession with Set-RDMEntry and it's all still working.
Thanks for the help,
Chris