NI2022 teststand cannot run vi's written with NI2013 from TestStand 2022 (ignore this thread)

[DLMC]

Sorry, this topic was started in another thread.  I can't delete this, but will copy what was here to that other thread.

DLC

The specifics:

Old NI2013 running on Windows 7 pro

New NI2022 running on Windows 10 Enterprise

I want to migrate the test written years ago with NI2013 to our NI2022 version of Labview/Teststand.

When I try to run a sequence from the NI2013 on my NI2022 I get an error that says the vi must run the LV 2013 version. 

Where in TestStand would such a setting be?  Do I need to build the project from NI2013 without that restriction so I can see where other problems with the migration will be? 

The system this TestStand OI was built in has several NI versions on it, is there a way to build a project on a system with several NI version without mandating a particular NI release to run it?

Lots of questions and I fear I may not be stating the issue very clearly.

Notably, I have migrated LV2010/TS 4.2 stuff to my NI2022 environment will little difficulty.  I had to make some TestStand Model changes, but otherwise the migration was pretty straightforward.  This NI2013 build is different in some way.

Here is the error that I get when running the teststand sequences:

TestStand cannot locate a LabVIEW Run-Time Engine of version '10.0' and bitness '32-bit'.

ERROR CODE -17338

-17338: The LabVIEW runtime DLL (lvt.dll) is not loaded.

be well,

DLC

be well,

[Anand_Jain · Accepted solution]

Hi, 

It is likely, that the error is being reported because your VIs are still saved in LV 2013. 

If you want to migrate to TS 2022, you will have to mass compile your VIs to a newer version of LabVIEW (I think LV 2019 or later) before you can execute them from TS 2022. 

Hope this helps. 

Regards, 

Anand Jain

NI

[DLMC]

"

If you want to migrate to TS 2022, you will have to mass compile your VIs to a newer version of LabVIEW (I think LV 2019 or later) before you can execute them from TS 2022.

"

I didn't think of that.  So obvious.  Thanks for the comment.  I will do that and report how it went.

That was it.  Thanks for helping a confused developer.

be well,

DLC