Closed dsbert closed 4 years ago
Is your app configured to do something on the file system, like reading/writing a file? error: The operation attempted is not supported.
suggests there is an issue interacting with the file system... which is often permissions related.
Yes it does handle files. However, I do not understand how an IO exception thrown in node could manifest as an unhandled System.IO.IOException
in the shim.
Closing due to age, and apologies to @dsbert for being no help whatsoever. If anyone else runs into issues where there are port conflicts, use porthog to identify the service and confirm whether it is an orphan process or node-windows just trying to restart the process.
I have a server running two different applications with node-windows. One of these is a web server and one is a file monitor. At right about the same time, both of these seem to have lost track of the running instance and I ended up with multiple instances of each application running. I had to manually stop the services and kill all remaining instances through task manager. I'm having trouble finding a root cause.
I do see the following error in the event logs at about that time (app.exe is one of the shims located in the daemon folder). I did not see this for the other application, but right after this is when I begin seeing errors indicating another instance already had the application port open.