Skyline API AQMP failing to connect to socket

[rdecarre11]

I restarted the server and that file was generated. That is a step in the right direction.

I tried the examples again and still get the same issue.

[JoshuaP]

After rebooting the server and seeing that the file was generated did you close and reopen LV?  It should detect when this file changes, but just in case it is best to restart the application to ensure the client library gets reloaded.

[rdecarre11]

Okay after some changes:

I created a new Windows 10 VM, installed LV2017, installed systemlink, connected to the server, opened the example and tried to run it. 

Same issue about not finding a port. The salt service is running, is there something else I can try?

Is it possible that this example never actually worked?

[GreyGrey]

I am able to run the examples and get the expected behavior. How is the server's (which is running on the VM) network configuration set up? Is it configured to have its own IP address? Is it on a private network with the host machine? Does it have a link local IP address or address on your network?

[rdecarre11]

The VM is on our corporate network, I connect the Systemlink Client using the hostname.

I tried changing the local firewall settings to allow communication for the LabVIEW and Python processes, but still says Unable to Connect.

What would need to be allowed in order for this to work?

[GreyGrey]

Have we gone through and made sure that we opened the ports used by SystemLink and its services? The ports we use are below:

• Web Application: port 80 (insecure) or 443 (secure TLS/SSL)
• Salt: Default ports are 4505 and 4506.
• RabbitMQ: Default port is 5672.

[JoshuaP]

Since we use TLS with RabbitMQ it runs on port 5673, but the others are accurate.

[rdecarre11]

Is rabbitmq supposed to be installed on the client too? I don't have that.

I have configured my local firewall to allow communication for 4505/6 and the labview application, still the same issue.

I have not configured that on the server, that involves IT here. I can connect to the port manually using labview or otherwise.

[JoshuaP]

All of the ports listed above need to be open on the server, not the client.  And no, you don't need to install the RabbitMQ broker on the client. 

The clients connect to the broker on the server on port 5673, but rely on the other ports to get the configuration and credentials for connecting to it.

[simenfu]

Hey,

I'm also struggling with this issue and was wondering if a solution was found. I'm running the server on a Win7 VM (firewalls disabled). The two clients are running on a Win7 VM (not same as server) and a cRIO. Both clients are connected to the server and publish the Health-data without any trouble. Further, when I set up the API to use HTTP I'm able to write to the tag and see it updating on the server. However, when I attempt to use AMQP (to open a tag), it immediately gives an error code -251022 and says AMQP error: Failed to open socket. 

Obviously there is communication between the clients and the server, but somehow this communication fails. Any ideas?