Troubleshooting SystemLink Client Connection Issues

The connection process between a SystemLink Server and client can fail due to multiple reasons, including but not limited to a lack of system resources, network connectivity issues, stale cache entries, licensing problems and connection information in a bad state. This guide provides guidance on how to troubleshoot these connections issues.

For information on how an ideal connection process is done and what connection status can be reported, refer to: Inner Workings of the Connection Between a SystemLink Server and Client.

When working with SystemLink connection issues, having knowledge in the following topics can ease the troubleshooting efforts:

• Sizing a SystemLink Server.
• General computer networking (i.e TCP, IP, DNS,...).
• Network security. The SystemLink Operations Handbook provides a summary on best practices.
• Salt Stack.

Troubleshooting Guide

1. Before you do anything else, check the SystemLink component versions in NI Package Manager for both the SystemLink server and any problematic SystemLink client computers.

• You will have to uncheck the Products only checkbox in the Installed tab of NI Package Manager, type “SystemLink” in the search field and hit <Enter>.
• If the server has mixed component versions, then the server installation may be the cause of these symptoms.
• If a client has mixed component versions OR if the client version is newer than the server version, then that could be the cause of these symptoms.

2. For SystemLink Server 2023 Q1 and previous versions, clear out the following folder of all the user_port.txt files except the currently logged in user. Each profile can cause a sequential 2 second delay for any salt job:
 

3. If the above steps do not fix the connection problem, refer to the following options based on the symptoms the connection is having:
 

• If the client can’t contact the server at all, refer to:
  • SystemLink Client Cannot Communicate to the SystemLink Server at All
• If the server has incorrect client information cached and refuses the client request or the client does not appear in the Pending Systems list, refer to:
  • SystemLink Server Refuses Client Connection Request
• If the server and client communicate fine over the network (i.e with a ping command), but the client still fails to connect to SystemLink, refer to:
  • Client Can Reach SystemLink Server but It Fails to Connect
• If the client connects to the server but cannot publish data (tags, files, results) and it has the Partially Connected status, refer to:
  • Client Partially Connected to SystemLink Server Cannot Publish Data