We have automated reports that connect to a third party resource for source files. That password needs to be updated every two months. We reset the password last Friday and updated TOAD with the right password, successful test, saved, and closed TOAD.
Scheduled reports ran Sunday unsuccessfully, and I found the account locked out Monday.
We reset the password Monday, updated TOAD with the right password, successful test, saved, and closed TOAD. Kicked off the reports that didn’t run Sunday and they completed with no issues. Scheduled reports ran unsuccessfully this morning (Thursday) and the account is again locked out.
After some investigation, I have found password references in the TAS files that are static, and password references in the ftpconnections.xml file that update as we change password in TOAD.
Two things come to mind... either TOAD is using a cached password that I don't know about, or it is relying on a password stored in each TAS (this approach would be ridiculous). So the password reference in each TAS must refer to a connection in the ftpconnections.xml file. Since that must be the case, each TAS would have the new password on hand at any given run time (unless it is cached somehow). I can't find any settings in TOAD Data Point options.
Why would this suddenly start happening after we updated password when previous to last Friday these were running flawlessly? I might think it is new settings at the remote system but that would be quite coincidental.
These surround compliance reporting so we cannot miss a step, and this issue makes automating the process moot.
Win 10 Ent 1909