TestStand 2019 Test Monitor connect to server error -2146233088

[JLohse]

Hi,

I am trying to integrate the test monitor with TestStand 2019 on a SystemLink 2020 R3 Client.

I have followed the SystemLink Documentation and installed the SystemLink Client and TestStand on my windows 10 target.

The client has been connected to the server and the server has approved the client.

I have added the 'SystemLink Test Monitor Client' in the Result Processing in TestStand.

When I try to run a sequence I get the runtime error shown in the image.

It looks like the client cannot connect to the server, but the IP shown in the error description is not for the server but for the client. 

To me it looks like Test Monitor thinks it's on a server and not a client. 

I have used the LabVIEW SystemLink Toolkit to create a result in the Test Monitor and this was successful. The client can therefor send Test Monitor data to the server if the connection data is correct.

How can I change the connection data for the Test Monitor so it correctly connects to the server?

Regards

Jeppe

[alex_weaver · Accepted solution]

Hello Jeppe,

The TestStand plugin, along with other client applications on the target, uses the preferred hostname configured by the NI Web Server, serverside. This setting can be viewed/changed by opening the "NI Web Server Configuration" desktop utility on the server, under the "Remote" tab. What value is your server configured to use for "Preferred host name for generated URLs and certificates?" This setting should usually match the hostname that you typically use to connect to the server from a browser.

In addition to checking this value, have you tried restarting TestStand after the server has approved the target? The client usually reacquires connection information between executions, but a restart of TestStand will allow us to make sure that an old configuration was not cached somewhere.

Thanks,

Alex

[JLohse]

Hi Alex

I was using the default name as the "Preferred host name for generated URLs and certificates". Changing this to the IP of the server seems to have done the trick.

I realized that, since I am using virtual machines, the server and the client had the same name and that might be why Test Monitor was not able to connect correctly.

This solved the issue, thanks a lot.

Regards 

Jeppe