search

coreybutler / node-windows

Windows support for Node.JS scripts (daemons, eventlog, UAC, etc).
Other
2.83k stars 356 forks source link

Service created BUT NOT RUNNING #339

Open imyoga opened 1 year ago

imyoga commented 1 year ago

Issue: Used exact same code provided.

When I run the file, it does create the service but the service is not running. I can not manually even turn it on from GUI. See the error below. image

coreybutler commented 1 year ago

Do you have another web server running on the same port when you try to start this? That would cause this.

imyoga commented 1 year ago

Nope, I killed the process running before creating the service. Tried again. Same error.

imyoga commented 1 year ago

When I uninstall the service, Console says: Uninstall complete. The service exists: false.

coreybutler commented 1 year ago

Sorry for trailing off. I get hundreds of messages a day and this just fell off my radar.

As previously stated, if there is another web server running on the same port (doesn't have to be node... could be anything), it could cause the script to crash. If there is a firewall preventing the hello world script from launching the web server on the specified port, the script will crash.

See https://github.com/coreybutler/node-windows/wiki

If the uninstall doesn't actually remove the service, then I suspect the user account used to do the uninstall doesn't have permissions to remove the service.

ShadowXTS commented 11 months ago

I have been trouble shooting the same error codes on my system. It turned out to be some missing modules in the package-lock.json or package.json file. When I checked the error logs under the daemon folder, it showed a "MODULE_NOT_FOUND" error. I ended up deleting those two json files and recreating it and the 1067 error went away. I was migrating from a Linux WSL virtual machine to deploy on a windows server, so some of the missing packages may have been during development.

Maybe that would help someone else if its the same cause.