Some FTR scripts get gibberish/garbage characters in them and stopped working after FTR 5.5.8 upgrade. We can't even open the script in FTR recorder.
In a Foglight Transaction Recorder (FTR) agent's | Agent properties | 'Script List', has two scripts with the checkbox checked so that they are enabled to be played. However, only one script actually plays.
The log shows the following error
"ERROR [Thread-21] com.quest.ftr.agent.ComMonitorThread - Error checking visibility of script <our_script.ftr> - disabled"
The following was also tried
 The properties were changed to play the single ftr script but the agent still saw it as disabled.
 FTR agent was setup so that none of the scripts that it was playing had their checkbox checked. It played nothing but gave a different sort of message in the log. It said something like "no scripts to play, shutting down".
Software defect EU-520
This occurs with accented characters. It appears these are being translated into characters that are making the script files invalid after being published. The FTR files that have these specific characters in them are not saved out in the agent correctly (they should be saved in UTF8 format). This issue is being tracked as EU-520
There is a patch. Contact Technical Support and ask them about obtaining this patch.
Fixed in FTR version 5.6.2.