Installation Support for ActivePerl

Installation Problems, Installer content, and FAQs for ActivePerl

Upgrading while keeping all your settings/modules intact

I discovered that my current AS perl, 5.12, is no longer ppm'able [without a business license] so I'm upgrading to 5.16. I'm worried about how that 'upgrade' should/will go. right now perl is installed in c:\perl64. Can I just install the new 5.16 in the same directory and will it basically leave my installed modules and other such along [perhaps needing a big update via ppm, but still there]? Or will I run into problems?

"Perl Command Line Interpreter has stopped working" when running PPM.

Can't get the PPM GUI to run. This is on Win 7 64-bit. Tried reinstalling 5.16.2 64-bit, with the same result. PPM command line seems to work. Just the GUI won't run. Tried 5.16.2 x86 and this launches the GUI fine.

The following is in the event log:
Faulting application name: perl.exe, version: 5.16.2.1602, time stamp: 0x50d17d90
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c
Exception code: 0xc0000005
Fault offset: 0x0000000000036b3b
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11

Having a problem? Check here first:

Frequently encountered problems may have an FAQ available.

http://community.activestate.com/faq-list?tid=50

perlis.ddl missing?

I just upgraded to Perl 5.16.3 (on Win 2003) due to an "ActivePerl Heartbleed Security Update" email from activestate. After the upgrade my plx scripts stopped working on my web site. I checked IIS and it was set correctly to map plx to c:\perl\bin\perlis.dll.
I checked and perlis.dll did not exist! I ran the installer again and checked PERL ISAPI and I got: "Use of this feature requires a Business Edition license". WTF!? When did this start? Can anyone help me with this?

Unattended installation to custom directory

I'm trying to automate ActivePerl installations on Windows, referencing the following document:

http://docs.activestate.com/activeperl/5.16/install.html#windows installers

What I've noticed is that the TARGETDIR is actually a base directory. If I want to install the win32-x64 ActivePerl to c:\perl, I can't do that. Specifying a TARGETDIR of c:\perl ends up creating c:\perl\perl64.

Installing ActivePerl on Windows Server 2008 and Windows Server 2012

I am working on migration of a legacy application that uses ActivePerl on Windows 2000 server.
Can ActivePerl run on 32-bit or 64 bit Windows Server 2008 and Windows Server 2012?

Thanks,
Sant T

ActivePerl for Windows 8.1 that uses MSVCR110

Hi,

I would like to develop a desktop app for windows 8.1 using ActivePerl. The most recent version of ActivePerl 5.18.2 depends on MSVCRT.DLL - as far as I understand MSVCRT.DLL cannot be used in a Windows 8.1 store app, MSVCR110.DLL and related DLLs should be used instead. Since Microsoft is forcing the move to Window 8.1 will ActivePerl for Windows 8.1 be compiled against MSVCR110.DLL and related runtime libraries?

Tomek Wardega

how do uninstall a ActivePerl license from the wrong machine?

this question has been resolved via a support ticket.

ActivePerl 5.18.x persisting bug + packages upgrade script request

Hello,
I tried yesterday update to newest AP 5.18.2.1801 and have not succeed to get it working.
Firstly uninstalled completely previous perl. Then new install to the same directory, and perl is crashing on most of my existing scripts that were working with perl 5.16. I think the bug which was already present in AP 5.18.1 is still present (wrong linkage to perl516.dll). Anyway I didnot manage any of 5.18 perls fully functional and I did update this software many times. So I assume there's something wrong with all 5.18 builds.

Upgrading from 5.8.822 to 5.16.x

Hello all,

I work for a company which is currently using AP 5.8.822 on their 2003 box and have quite a few Perl scripts. I see in the AS 5.16 documentation, it says build 16xx is incompatible with previous version's binaries, though I'm not sure what that entails.

If we were to upgrade to 5.16.x as I have on my PC, would it break all of the existing Perl scripts written and used in the 5.8.822 environment? I would like to upgrade so I can use the remove_tree function and output to a scalar variable for logging purposes, as opposed to just the spray and pray of rmtree.