coreybutler / coreybutler/node-windows
The very first time node-windows is used to install a service, it won't start.
- Dominant language
- JavaScript
- Stars
- 2.9k
- Forks
- 368
- PR merge metrics
- No merged PRs in 30d
Description
I am using `node-windows` to run a basic script to install and run a service. The very first time this script is executed, the service appears in the Windows services manager, but does not start, even though my on-start listener was triggered.
Every subsequent time I invoke this script on this device, the service starts normally. Strangely enough, I can remove all files, uninstall the service using `node-windows`, even `sc delete` the service, and after invoking the script, the service starts normally as well. I can even give the service a different name and description, and that service now starts normally too.
When I examine the `daemon` folder, there are none of the log files I expect to see either until I invoke the `start` operation again.
I am using the latest version of `node` and `node-windows`. I have seen this issue both on Windows 7 and Windows Server 2008.
Contributor guide
Assessment
This issue has not been assessed yet.