Perl command line interpreter has stopped working v 5.24.1 Problem Event BEX64

Posted by ppeel@sambaplans.com on 2017-06-26 06:50

We recently installed perl 5.24.1 on our new windows server 2012. The very first perl script I ran I got a windows pop up that said 'Perl Command Line Interpreter has stopped working.'
The details were:
Problem Event Name: BEX64
Application Name: perl.exe
Application Version: 5.24.1.2402
Application Timestamp: 586df0fc
Fault Module Name: StackHash_c6d7
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: PCH_5D_FROM_ntdll+0x0000000000090C6A
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: c6d7
Additional Information 2: c6d7177f18e00ff82ab902718d1239fd
Additional Information 3: d987
Additional Information 4: d987967ef47cf7b2214177908b8fe4a4

grahams
ActiveState Staff
Mon, 2017-06-26 15:54

That message means Perl was forced to terminate by Windows.

BEX64 errors are usually from a DEP intervention, so it might be productive to look at how the new server is set up vs where Perl is installed.

Also, if you transferred any of the old Perl 5.16 binaries in addition to your scripts, that would be a problem.

ppeel@sambaplans.com | Tue, 2017-06-27 09:15

I'm not sure what to look for as to how the new server is set up. What should I be looking for?

I installed perl in a directory on the C: Drive. C:\ActivePerl. We run our scripts from the D: Drive.

I did not copy any binaries from the old server. All modules were installed fresh.

I can tell you that when we do run a perl script and we are writing output files, the files are created during the open, however nothing ever gets written to them.

I 'print' the output to a file and to STDOUT. I can see the STDOUT, but the data never gets written to the output file.
We've check permissions and they seem to be okay.

Do I need to uninstall perl from the C drive and reinstall perl on the D drive?

grahams
ActiveState Staff
Thu, 2017-06-29 08:08

I don't see anything obvious from what you've posted. You should open a ticket by mailing a short summary (please include some hardware details, just in case) and a (small) testcase that shows the issue to support@activestate.com

I don't think that installing to D: would help. The odds are it should make things somewhat worse.

ppeel@sambaplans.com | Thu, 2017-06-29 08:40

Actually, we uninstalled perl 5.24 and installed v 5.16 on the new server because we knew it was working for us on the old server. Now it seems to be working okay. So we can continue on with our conversion. Once we get everything working on the new server we will attempt to upgrade perl and have more time to debug.