Running into a new issue. We're replacing our older machines
with some new ones running Windows Server 2016 -- I've also
replaced our use of ActivePerl with Strawberry as I finally saw
that ActiveState had changed their license.
Everything seems to behave normally, except when I install
the services via the Win32::Daemon -service -installservice,
the services it creates will start with the NOT_STOPPABLE,
NOT_PAUSABLE, and IGNORES_SHUTDOWN states.
Of course I can still kill the individual perl processes with
taskkill, but I would prefer to be able to stop and start
the processes via the services tools (net start|stop,
sc start|stop, and services.msc).
The only other differences I've noted is that with the
Strawberry instance, I'm actually running 64 bit perl
application so i had to shift my DSNs from 32 to 64 bit,
and that on my older Win2008 R2 box, the reg keys
have two subkeys, Enum and Security, which do not
exist with the install on Win2016; however, I do not
remember if these were created by the install or if
I had simply copied what I used in earlier win32
service installations utilizing instsrv.exe and srvany.exe.
So far, I've not found what triggers this state. Has anyone
else ran into this or have suggestions?
Sitestar Internet Services
radiator mailing list