Customer has a Transaction Script that is password protected. However they either forgot the password or it was not documented.
Functioning as designed. Transaction has a feature where you can "lock" the script with a password or the developers choosing.
Unfortunately we do not have a way of "breaking" this lock as that is it's design. The customer would need to locate the script developer to find out the password.
-It may be possible to find a .bak file which would have been created at the same time as the original script was recorded. This would be a backup file which would not have any mapping associated with it. The .bak file could then be re-named so that the extension is changed to .txr and then mapped to match the previous script.
-There is a Metadata data button in the upper right corner from the Run screen where you can remove the lock however it would require you to know the current password. In a couple of scenarios the script was not actually locked and you can select "OK" without entering a password and proceed.
-The script would need to be re-recorded.