-
the "OTRS user" would be the userid, under which the OTRS daemon (linux terminology) or service (windows terminology) is running. You have to find out which one that is. Might be the "local system", or a special user.
The script wants to run under that same user. If it's "system", it might be easier to have the daemon changed to a special user instead (e.g. the otrs user you created)
-
There probably is a difference between things running from cmd.exe versus running from the linux subsystem. If the OTRS daemon is started from the WSL (Windows Subsystem for Linux), then you should do the same with the script.
-
Did the perl.exe come with OTRS, or did you install it yourself? Which flavour (Active, Strawberry, Cygwin, ...) and version is it? And most importantly: is it the same perl(.exe) that OTRS uses itself?
| [reply]
[d/l] |
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.
| [reply] |
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] |
| [reply] |