I have a Tidal job that executes a PowerShell script. The encrypted password is stored in a password file on the application server. In the PowerShell script, there is the line below that gets the contents of the password file. $encryptPW = Get-Content "C:\Program Files\MyCompany\MyApp\encryptPW.txt" | ConvertTo-SecureString On my development enviroment, Tidal was referencing the Agent/Adapter (app server name) and the Runtime User (domain\userID) fine. The script was executing well until recently when the Tidal server was rebooted. After the reboot, the PowerShell script execution is erroring out with the message "ConvertTo-SecureString : The system cannot find the file specified." It appears that when the PowerShell script is executed from Tidal, it is unable to find the password file using the Runtime User specified in the Tidal job. The Runtime User has the proper access on the application server because we must sign-on as that user in order to generate the password file to hold the encrypted password for the Runtime User. It is as if Tidal is not passing the right credentials when it is executing the PowerShell script. Has anyone come across this issue?
... View more