No Connection to NI Server, Using Tags. Error Msg: LabVIEWHTTPClient.lvlib:GET.vi:390002<APPEND>

[AussieEric]

I have been trying to setup a connection between a cRIO 9030 real time target and the NI Web Server on my laptop so I'll be able to read Tags from the cRIO.

At the moment I'm just trying to send a single Tag so I can confirm the connection works.

When I run the VI locally on my laptop with the server name it connects properly.

When I deploy the same VI, but with the networked server address I'm not getting a connection. The error message LabVIEWHTTPClient.lvlib:GET.vi:390002<APPEND> is appearing and I'm not quite sure what that means.

Does anyone know what this error message means?

I've attached the VI code I'm using (with the username/password removed).

Thank you for any help you can provide.

[JoshuaP]

Try changing your server url from http://192.168.1.5:80/c002107326/ to http://192.168.1.5:80

[AussieEric]

I tried changing the server url to http://192.168.1.5:80, but it still showed the same error.

[cordm]

What is the error code and complete error message?

The part you posted only somewhat shows where the error appeared. Is it Open Tag or Write Tag?

[AussieEric]

The error appears after Open Tag. The error after Open Configuration is clear, no error.

Code: 56

Complete Call Chain

LabVIEWHTTPClient.lvlib:GET.vi:390002

NISkyline Utilities.lvlib:Execute HTTP Verb.vi:7500001

NI Skyline Tag HTTP Library.lvlib:Open Existing Tag.vi:1500001

NI Skyline Tag HTTP Library.lvlib:Open Tag.vi:1540001

Ni Skyline Tag HTTP Library.lvclass:Open tag.vi:3570001

Main Remote.vi

[cordm]

That means the server is not reachable or does not answer.

The web server must allow remote connections, see here how to enable them: 

https://www.ni.com/docs/en-US/bundle/ni-web-server-feature/page/choosing-a-remote-setting.html

If it still does not work, check if the cRIO can reach your laptop at that IP. How are they connected?

[AussieEric]

I have setup the Web Server to use HTTP only, on Port 80.

It will allow all remote connections, even from public networks.

CORS is setup to be enabled for all origins.

My laptop and the cRIO are connected directly with an ethernet cable. The cRIO is 192.168.1.2 and the laptop is 192.168.1.5.

I'm able to deploy new software and connect with NI Max over this connection. When I login to the cRIO with Putty I'm able to ping 192.168.1.5 successfully.

I'm wondering if its a firewall issue? I'm going to try setting up a second laptop that I have better control over firewall setup.