03-17-2022 10:30 AM
On my test sequence, when I click on any LabVIEW step it will freeze for at least 3 minutes and then I'll get this message:
Instead, if I open LabVIEW first (LabVIEW runs fine) and then the TestStand sequence, I'll be able to see the steps with all the info (inputs, outputs, VI icon).
I already tried to switch the LabVIEW adapter from the development system to the run time engine and back to the dev system without success.
If you've ever encountered this before, please share some advice on how to fix it.
Thanks in advance ✌
03-17-2022 11:51 AM
Hi,
Strange behaviour.
Have you tried to repair or reinstall the software ( after un install).
Install LabVIEW first then TestStand.
What is the error that you are getting when you select runtime LV adapter.
Ravi
03-17-2022 11:55 AM
I already uninstalled LabVIEW and installed it again (uninstalled 2019, installed 2019 SP1, but I don't think that matters, same error keeps appearing).
I haven't uninstalled TestStand yet
I'd need to check again with the RTE because I don't remember the error I was getting.
03-18-2022 12:30 AM
Hi,
Please also try running the version selector and click on make active button.
Ravi
03-21-2022 12:51 PM
Hi,
Couple of things to try -
1. Are both TS and LV running with the same user privileges? Is one of them running as administrator and one is not? If so, can you try to execute both of them with the same privilege?
2. Another reason could be that the registration of LV is incorrect on the machine. Try to run LabVIEW.exe with /regserver command line when using an cmd window that has administrator privileges once to try to resolve the issue.
LabVIEW-Defined Command-Line Arguments - LabVIEW 2018 Help - National Instruments (ni.com)
Hope this helps,
Regards,
Anand Jain
NI
08-02-2022 12:12 PM
I had the same issue and the suggestion about user privileges from Anand_Jain Resolved the issue. It turns out that LabVIEW was configured to run as administrator but teststand not.
So I just open the TestStand Version Selector right clicked it>properties>compatibility and check the Run as administrator option.
Thanks!.