Systemlink Services Not Starting With Failed Requests on Port 12100

Issue Details

• The SystemLink Security, Message and ServiceRegistry services will not start. When I look in the SystemLink error logs, I see exceptions with requests sent on http://127.0.0.1:12100/niauth/v1/auth
• My SystemLink Server doesn't start properly. The Skyline log shows services exiting with exit code 255, and many failed communication requests on port 12100.
• My SystemLink installation was working previously, but due to some unknown reason, the Security service refuses to start. The troubleshooting logs contain entries similar to below.

Configuration | Request attempt 7 of 12 for Security and Uri http://127.0.0.1:12100/niauth/v1/auth. Exception: An error occurred while sending the request.
Security | ERROR - Process exited with exit code 255.
Message | ERROR - Process exited with exit code 255.
ServiceRegistry | Warning: No configuration section found for service. Skipping setting environment variables for service name: ServiceRegistry

Solution

This problem can occur if there are issues with the PATH Environment Variable, or the server communication on port 12100.

Review the steps below to resolve this issue:

• Ensure that the PATH Environment Variable exists on the SystemLink Server. It should exist as a User and System variable.
  
  • If it does not exist, restore it.
  • The exact paths required vary depending on your Windows version and currently installed software. However, [External] Windows Environment Variables List: Complete List on Windows 10 / 11 provides a list of the most basic paths that should come with all Windows 10 and 11 operating systems.
• Verify that there are no additional processes reserving port 12100. This can be done by running netstat -aof | findstr :12100 in Command Prompt.
  • Once this command executes, the last column in the output is the PID (unique identification number for the process). The PID can be cross-referenced with processes in Task Manager to identify the process name.
  • It is expected that the Erlang process is listening on port 12100. No other processes should be present.

• If using any anti-virus or security software, ensure that it is not blocking SystemLink from port forwarding on port 12100.

If the problem persists after following these steps, generate a SystemLink Technical Support Report and share it with NI Support.

Additional Information

To better understand the use case of port 12100 within SystemLink, refer to What Does SystemLink Use Port 12100 For?