We are running an automation tool to sync RDM parameters from our database. The tool uses Powershell script with a dedicated Powershell host (via C# and Windows Service). I see after it successfully working for a few days, it stops communicating with server. Then on, for a command say, get-rdmuser, it simply returns nothing. If I restart my service everything starts to work as it should be for some random time until it fails. It seems like the powershell host looses connection to the RDM server and never trying to re-establish one. Is there any way to fix this behavior?
Hello,
What RDM version are you using?
You mention that it stop communicating with the server, is it Devolutions Password Server? If so, what version are you using?
And which is the service you are restarting?
Best regards
Érica Poirier
RDM version is 'Enterprise Edition 2020.1.10.0'.
'It stops communicating...' where it means the powershell host, and the destination is Devolutions Password Server and the DPS version is 2019.2.12.0
The service I am restarting is a Windows service that hosts a powershell instance.
Hello,
Thank you for the information.
It is possibly the token that is expired as in DPS, the maximum value of Token Valid Time parameter is 24 hours.
https://helpserver.devolutions.net/webinterface_advanced.html
Could you please try to add the Update-RDMUI cmdlet at the beginning of your PowerShell script to refresh the connection to DPS and getting a new token to see if this will help?
Best regards,
Érica Poirier
Hello, I have tried your suggestion and it has no impact. The commands will not work after some time.