Studio:Why don't Perl scripts run even when Script Engine shows Perl?
Jump to navigation
Jump to search
Even when ActiveState Perl is installed and STRIDE Studio's Script Engine (Tools->Options->Script Engines) shows Perl file types (PL, PLS, PM, etc), you may not be able to run Perl scripts or not see the "Run" button on opened Perl scripts within STRIDE Studio or get a pop up box with error message "Could not identify a script engine for this file type. Please reinitialize your script engine list." One reason could be that ActiveState Perl registration is modified by another program. It is known that iTunes and Real Player take over the ownership of .pls extension used by ActiveState Perl, on which STRIDE Script Engine relies.
To verify the problem:
- Check the value for .pls extension in the registry: HKEY_CLASSES_ROOT\.pls. If the associated value is not “PerlScriptFile”, there is a registration problem.
To fix the problem:
- Run the following on command prompt:
CMD> regsvr32 c:\perl\bin\perlSE.dll
- Remove all Perl file types (PL, PLS, PM, etc) from STRIDE Studio's Script Engine (Tools->Options->Script Engines) and do a "Scan" again.
To verify the solution:
- Select each Perl files type and look for the text under the buttons that says “ActiveScript compliant”.