ActivePerl 5.20.2 -- issues with Perl Package Manager

Hey Guys,

So I have a new windows server 2019 with ActivePerl 5.20.2 installed. When I open perl package manager (GUI) it launches tries to connect and download the package lists but before it can it disappears with no direct errors.

Using the command line you see the following:

ppm> repo sync
Downloading ActiveState Package Repository dbimage...redirect
Downloading ActiveState Package Repository dbimage...                                                                   ppm>

In event viewer I do see an issue:

Fault bucket 1872577010239762322, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: perl.exe
P3: 55ad5c5f
P4: SSLeay.dll
P6: 55ad6213
P7: c0000005
P8: 00000000001410e3
Faulting application name: perl.exe, version:, time stamp: 0x55ad5c5f
Faulting module name: SSLeay.dll, version:, time stamp: 0x55ad6213
Exception code: 0xc0000005
Fault offset: 0x00000000001410e3
Faulting process id: 0xc2c
Faulting application start time: 0x01d885957e3c7981
Faulting application path: C:\Perl64\bin\perl.exe
Faulting module path: C:\Perl64\lib\auto\Net\SSLeay\SSLeay.dll
Report Id: 0ca28afa-afee-4f0d-b799-a04d10fbba72
Faulting package full name: 
Faulting package-relative application ID: 

Thought it might be an SSL error so enabled all the old security protocols but that has not fixed the issue. There is no web filtering or AV currently on the box.

Any ideas, cant find any more verbose logs.

The repository is the default installed:

ppm> repo describe 1
Id: 1
Name: ActiveState Package Repository
Enabled: yes
Last-Status: - (never accessed)

thanks in advance

PPM is not longer supported, and hasn’t been maintained since 2018. We strongly recommend that you update to a version of Perl that no longer needs PPM.

Some time ago our servers on the cloud had to have TLS 1.2 switched on as the mandatory minimum level of security. Many of the old PPM clients can’t support TLS 1.2, so at that point, those older versions were unable to use the GUI.

The only workaround is to download the package manually, and then install that package from the command line with PPM. That process allows the TLS connection to be managed by an internet browser, which will have far more modern SSL tooling available. The downside to manual mode is that PPM dependency checking cannot be used. You will probably have to make multiple attempts, with a trail and error approach, until you find the correct order which any dependencies need to be downloaded and installed.