Launcher unable to bind on Windows
If you are using an Agilicus Launcher with Rockwell Studio rslinx to reach one or more PLCs, you may see an error “listen tcp 127.74.52.3:44818: bind: An attempt was made to access a socket in a way forbidden by its access permissions.”
This indicates you have another process running which has globally opened this port. You may find this process via:
netstat -an |findstr 44818
If you see a result like:
TCP 0.0.0.0:44818 0.0.0.0:0 LISTENING
This means that there is a process running with this port globally, exclusively, open. You can find the process:
netstat -anb
and you will see the named process. Stop this process which has the port open exclusively, and, the Agilicus Launcher should now work.
To avoid this, you can either use a different port, reconfigure the exclusive process to use a specific IP (instead of 0.0.0.0), or, run the Agilicus Launcher first.