Parameter 'error out':LabVIEW version '14.0' is not installed:

[rsmrostov]

I am very new to TestStand.  I am doing some tutorials and all the lv files were in LV 10, I have LV14 Development.  I have changed the adapter settings to "use active Labview Version 2014 SP1", I have made all the vi's in the tutorial folder writeable (they were read-only) and recompiled them all in LV 2014.

The vi Icon is showing up under the module I am trying to run, all the parameters show up and the Value expressions pass the "Check Expression for errrors'

However when I run this simple tutorial which just has a Message Popup and the String Value test modules it errors out on the LV module saying that LV is not installed...

[~jiggawax~]

Were the VIs recompiled on the same machine?

What about calling a brand new VI that wasn't in LV10?

64 or 32 bit?

Is LV development open on that machine (it shouldn't need to be but just for sanity sake ensure that it is already open)?

Hope this helps,

[rsmrostov]

Recompiled on the same machine

Lv 10 vis return the same error

Tried with lv open and closed

Created a brand new vi and calling it causes the same issue

The only thing: lv 2014 is 32 bit and testtand is 64 bit, I though that could be a problem?  Adapter settings do pick up lv 2014 sp1 just fine though.  I am able to open the vi from test stand just fine as well.

Testsand is running in legacy mode

P.S.  should I be running test stand 32 bit is 64 bit problematic?

[~jiggawax~]

http://digital.ni.com/public.nsf/allkb/D0D5704B3F5696FC86257D24004C92D1

[rsmrostov]

Thanks a lot!

However, I have tried this intuitively, before I even read this article...this still returns the same error.

1. Navigate to Configure»Adapters...
2. Select the LabVIEW adapter and click the Configure button.
3. Click the LabVIEW Development System radio button and click the Use Active 32-bit Version radio button.

[rsmrostov]

I have figured this out, the problem was - each vi in the sequence had the path input and the syntax was wrong.  Seems like that error code is the generic code for TestSTand

[~jiggawax~]

you would think that it wouldn't even run if this were the case.  Did you analyze the sequence before running it?  Just curious if it reported something suspicious.

Glad you figured it out.

Regards,

[rsmrostov]

Yes, I have analyzed.

Let me correct myself - the syntax of the path was right, the path itself was not pointing to the right location.