Odd state-exec error when executing perl script

Perl
,
1

Env: Win 10 x64 Enterprise, ActiveState Perl-5.38.2-Windows

I am building a (legacy) Windows codebase using Visual Studio 2008 (I know, I know… :grinning:) aka vc9. I am in a VS 2008 x64 Win64 Command Prompt, running the command

nmake /f msdev.mak

There are several perl -n -e <simple print cmd> commands which succeed without error. Then a perl script is run, and I get the following errors:

state-exec: run failed: cannot create new executor meta: cannot get matching bin by path: no matching binary by path "C:\\Users\\brie22\\AppData\\Local\\activestate\\cache\\bin\\perl.EXE"
state-exec: Not user serviceable; Please contact support for assistance.
NMAKE : fatal error U1077: 'C:\Users\brie22\AppData\Local\activestate\cache\bin\perl.EXE' : return code '0x1'
Stop.

state-exec is not being called directly anywhere in the script. And this worked ~1 year ago under a different Windows account! Suggestions as to next step troubleshooting?

2

That is not the typical path to anything for Perl, and that is almost certainly why the command is failing. Your commands that work are either pointing at a correct fully qualified file path to Perl, or are using a shortcut that finds a default which works.

Local\activestate\cache is the correct folder but there should be at least one folder with an eight character hash value which stores the runtime for Perl. If there isn’t, you don’t have a Perl runtime available on your user ID. You can’t run a Perl runtime that is installed for someone else’s user ID.

1 Like
3

That was it! Thanks very much. I saw the nicer 'cache\bin' path and thought that was the correct one. Onward and upward…