Unable to run vi with labview run time engine

[CobhamDC Blackburn]

Hi All,

I have a VI that controls and reads from an NI PXI Spectrum Analyser (5600). The VI works perfectly as expected, I can make a project of it and create a runtime application and installation with no problems, using Labview 8.6.

When I make a call to it from Test Stand 4.1 it works lovely.

When I change the VI adaptor in Test Stand 4.1 from development to use the LV Run Time engine 8.6 it fails to work, Test Stand gives the following dialogue (see attached).

I have uninstalled all older versions of Labview as I've had similair issues before, I've mass compiled everything I think is associated with this VI.

I don't really understand! And am tearing my hair out.

The only idea I have is that perhaps there is something in one of the 5 DLLs that is causing a problem or the NI_AALBase.lvlib, NIAALPro.lvlib or NI_PtbyPt.lvlib librarys that are password locked and I presume don't get mass compiled.

I have attached the problemVI.lvproj.

Thanks for any advice or help.

Matt

[Norbert_B]

Matt,

please check if you selected the correct version of the LV RTE for your TS adapter. Additionally, make sure that all VIs are compiled in this very LV version using the mass compile tool in LV.

hope this helps,

Norbert 

[CobhamDC Blackburn]

Hi,

Sadly I've mass compiled and checked that I am using the correct run time adaptor - but to no avail.

I've even tried opening and running each Sub Vi.

Not a sausage.

Cheers

Matt 

[Norbert_B]

Matt,

is the application imported from an older version of LV? Does a new VI containing VIs from the RFSA create the same issue?

Is this error ocurring on the PC with the developement system or only on the one where it is deployed?

hope this helps,

Norbert 

[CobhamDC Blackburn]

Hi NorbertB,

Thanks for your interest.

This problem both occurs on my development PC and another PC that the sequence was deployed to but this also has a development environment, I haven't tried on a PC with only Testand Runtime, I'll try it and see. I've tried "Save for previous version" which threw up the fact that the Toolkit version NI_AALBase is at 8.2 and AALPro lvlib is at 8.5 but these are pass word protected and I don't think they mass compile.

I've tried "Saving As" and duplicating the VIs hierachy to a new location and mas compiling that and then copying them back with no luck - but it doesn't copy library files when it duplicates the hierachy.

I'm not really getting anywhere.

Cheers

Matt

[Norbert_B]

Matt,

it sounds like you are having older versions of toolkit/driver VIs in your application. In developement environment, this works since the dev-system is capable to recompile older VIs just during loading and therefor not having issues with older versions.

Running the VIs using the Runtime Engine, recompilation is not possible. Because every VI knows "its version", the VI will not be executable unless the RTE version matches the VI's. If the VI is older (or newer, doesn't matter), the observed error occurs.

Please make sure that you have current versions of drivers and toolkits installed in your LV environment instead of simply copy them from older versions of LV (this would be the common source for such issues).

hope this helps,

Norbert