Posted  by  admin

How To Install Perl On Windows Server 2008

How To Install Perl On Windows Server 2008 Rating: 10,0/10 8876 reviews
Server

I've got an old website that I need to keep running on a new server - Windows Server 2008 R2 with IIS 7.5. The website uses Perlfect search , which requires both Perl and the DBFile Perl module. The latest versions of ActiveState Perl (5.10 and above) come with a script to correctly work with IIS 7.5, but for some reason are unable to run DBFile (details are available on the ActiveState site). The latest version of ActiveState Perl that will run DBFile on windows is 5.8, but that version does NOT come with the script that configures IIS 7.5. I couldn't make any headway on the 'No DBFile for Perl 5.10 + on windows', so I decided to tackle integrating Perl 5.8 with IIS 7.5. I installed ActiveState Perl 5.8.7 (32 Bit). I installed DBFile using ppm (install DBFile).

Copying the Perl Binaries. Before any IIS setup can be done, the Perl binary files must be extracted to your system. Download the ActiveState Perl distribution package (get the AS zip file and not the installer) and extract them to a folder on your server (i.e. We will map IIS to use the files located in this directory.

I verified that Perlfect worked at the command line by running the indexer.pl script first, then running searches using the search.pl script. To get Perl scripts working in IIS I adapted the instructions for PHP in IIS 7.5 at. Open IIS.

Click on the webserver name in the left hand panel. Double click on the Handler Mapping icon in the IIS section of the middle pane. Click on 'Add Script Map' located at the right hand side under Actions. In the pop up window set 'Request path:' to '.pl', 'Executable:' to 'c: perl bin perlis.dll' and the 'Name' to 'Perl' and click OK. Say 'yes' to the dialog box that asks if you want to enable this ISAPI script. Click on 'Application Pools' on the left hand pane in IIS.

In the middle pane, right click on the application pool you are using (in my case 'DefaultAppPool'). Choose Advanced Settings.

Set 'Enable 32 Bit Applications' to True (I did not test the 64 bit version of Perl). Click on the webserver in the left hand pane, then click on the 'Restart' link that appears in the right hand pane. That worked for me. I should be able to limp along until we upgrade the search function to the 21st century.

Hi, it's the first time I post it and the first time I can't install active perl on a server. Sorry first for my english style. I want to install activePerl on a Windows 2008 R2 SP1, we could do it on Prod environment but doesn't work on staging. I just launch the msi file and just after making the choices, it just end abruptly. I did already see some forums, telling we had to be on c: locally on server, but still the same issue. You surely already answered this question, but didn't find it already.

I could install with a log. Here is the part where I get an FatalError Dlg: = 0, shutdown will be denied. Counter after decrement: -1 MSI (s) (B0:08) 18:10:32:729: Restoring environment variables MSI (c) (E4:48) 18:10:32:729: Back from server. Return value: 1603 MSI (c) (E4:48) 18:10:32:729: Decrementing counter to disable shutdown.

Installing Perl On Windows 10

If counter = 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (E4:48) 18:10:32:729: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is '1'. Action ended 18:10:32: ExecuteAction. Return value 3.

MSI (c) (E4:48) 18:10:32:729: Doing action: FatalErrorDlg Action 18:10:32: FatalErrorDlg. Action start 18:10:32: FatalErrorDlg. MSI (c) (E4:48) 18:10:32:729: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'FatalErrorDlg' Action 18:10:32: FatalErrorDlg. Dialog created Action ended 18:10:34: FatalErrorDlg.

Return value 2. Action ended 18:10:34: INSTALL. Return value 3. I should normally be admin on my server It seems there are no other logs. Can send the whole one if needed.

Can anyone help? Thanks in advance. Update- Some old ActivePerl installers are known to throw this error if a newer Perl (also possibly a non-ActiveState Perl) is already installed on the system. Check for Perls included as part of another software product, such as Oracle. 1603 is a very generic error, and there are a number of causes, so it can be tricky to correct. The issue may be a problem with your Windows configuration.

2016

Install Perl On Windows Server 2012

Windows support forums often contain posts like: Since your error happens during an attempt to change registry settings, it could be from a virus scanner or local policy setting which prevents registry changes.