07-14-2020 02:31 PM
I have LabVIEW 2017 SP1 and Veristand 2013 SP1 set up in a virtual machine.
I want to take a look at some of the project properties, but the function to open them always fails.
Specifically NI Veristand - Open Project Reference.vi. (I would attach code, but the VI fails by itself, never mind in my code.)
I have tried with localhost, 127.0.0.1, and the IP address of the VM as reported inside the VM and with the setting in the project (Veristand Gateway IP Address) set to the same thing.
I have tried turning off the windows firewall.
I get an error 1172 with the following text:
Invoke Node System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
Inner Exception: NationalInstruments.VeriStand.VeriStandException: Could not connect to the VeriStand server. Make sure you have the correct address to the gateway, the gateway is running, and any firewalls are configured correctly before attempting to connect.
Inner Exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://127.0.0.1:2041/NI/VeriStand_Project/2017/ProjectServer that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. <append><b>System.ServiceModel.EndpointNotFoundException</b> in NI_VS Project ExecutionAPI.lvlib:NI VeriStand - Open Project Reference.vi
Solved! Go to Solution.
07-14-2020 05:04 PM
I am assuming you are using the Labview API for VeriStand and getting errors. You must always use the same version of Labview and Veristand. If you have VS 2013, you must use Labview 2013 API to communicate with it.
07-15-2020 07:32 AM
What a ludicrous requirement.
I will try this. Thank you.
07-15-2020 10:35 AM
I installed a matching pair of LabVIEW and Veristand and was able to connect from LabVIEW to Veristand without error.