Could not start service: Service Dependency Failure about pm2-installer HOT 6 CLOSED

Update:
Workaround: I change manually the user that runs PM2 service, instead of NT AUTORITHY\LOCAL SERVICE I used the Local service user, Idk what is the difference between them but now the service is running

from pm2-installer.

Thank you! This is great. I'd heard of this issue before, but was never able to replicate it.

What version of Node do you have installed? What version of Windows are you running, and what is your system's base language?

There's a small PowerShell script that prints out some information about the service included in the installer. Could you cd into the pm2-installer directory and run PowerShell -NoProfile -ExecutionPolicy Bypass .\src\windows\check-service.ps1? Thanks again.

from pm2-installer.

Hi, @jessety

Node version: v12.17.0
SO version: Windows Server 2016 Standard x64
Base language: Português Brasil

Output from PS:
Confirm-Service -name "pm2.exe"
Found "pm2.exe" service:
State: Running
Status: OK
Started: True
Start Mode: Auto
Service Type: Own Process
Start Name: NT AUTHORITY\LocalService

from pm2-installer.

It seems like this is an issue for all Windows installations where the base language isn't English. Yikes. A fix is now live in the service-dependency-fix branch.

@danilodecanini Try it out! If it works for you I'll merge #6.

Thanks again!

from pm2-installer.

With this fix it works with success!

Thank you so much for this quick fix!

from pm2-installer.

Thanks for reporting it! 🎉👍

from pm2-installer.