in reply to Re^5: Perl Command Line is not working
in thread Perl Command Line is not working

i am not sure what is otrs user. i think it is not relaTED to OTRS Daemon because this serivce should not running in the beginning as in OTRS Installation Doc so i am not sure if i should look in this part. regarding to the system i created user called otrs then i created also one group called otrs user but still the same error so i i think it is not under system . On windows server 2012 R2 i did not find WSL. I installed Active v 5.16 without PerlEx. it is one feature make otrs very quick more than perl.exe. i am using now perl.exe to run otrs. OTRS said you should use PerlEx to make otrs faster. PerlEx is expensive 999 $ pro year.

Replies are listed 'Best First'.
Re^7: Perl Command Line is not working
by soonix (Chancellor) on May 11, 2018 at 14:44 UTC

    The OTRS website disadvises installing OTRS on Windows. However, since WSL is essentially Linux running in Windows (and I misread the 2012 as 2016), I thought you might have succeeded installing it this way.

    The script uses fork and kill, which behave differently on Windows. fcntl isn't implemented. It would probably be easier setting up Linux in a VM and run it there (if 2016* is "fresh" enough for you, there's even a (third party) premade VM).

    * - production year, not Windows version

[reply]
Re^7: Perl Command Line is not working
by marto (Cardinal) on May 11, 2018 at 08:24 UTC

    PerlEx seems ancient:

    "New product improves performance of Perl scripts running on NT Web servers by up to 30 times."

[reply]
      which product?could you tell me please?is it free on windows server 2012 r2? Thanks in advance
[reply]

        I don't think you read my reply. The post I responded to talked about PerlEx. I linked to the search results from for this product and a quote from the first hit. What are you actually looking for?

[reply]

In Section Seekers of Perl Wisdom