Error -17600 [LV2010 & TS2010]

[swalkin]

Hi,

I have a working code in LV2009 and TS4.2 and I am upgrading to LV2010 and TS2010 and I am having some deployment issue.

I am calling a set of steps to initialise a piece of equipment, Litepoint IQnav GPS Simulator.

- When I run it on the source PC everything runs fine.

- When I build the deployment, everything builds without any issues

- I then install on my target machine and when I try to run the code, I get -17600 error saying that the steps can't be loaded due to something been missing or VI is not executable.

I have taken the deployment structure back to my development PC and ran it and it is fine.

I have ran the development PC in RunTime adapter mode and it runs fine.

The error on the target machine is saying that it can't run the step through LV Runtime 10.0.1 for due to broken VI or missing subVIs.

Has anyone seen this before. I think I have exhausted all checks but any feedback would be appreciated.

The steps are calling a dll and the functions in that. I have re-build the dll import project through LV2010 and this didn't help either.

All help appreciated....thanks.

[RayFarmer]

do you need to install a driver for the Litepoint IQnav GPS Simulator on the deployment system?

[swalkin]

Hi Ray,

Yes in the previously working setup under older version of TS & LV I did and I have it installed on the target machine at the moment.

Simon

[Norbert_B]

Simon,

it is possible, that the installer provides LV VIs which are "old", so not the correct version of LV. So if you have just installed the driver's installer and not any updated api (VIs), then i would expect some errors like this....

Please make sure that all LV components required for the test application are installed by an installation package from the developement system.

Norbert

[swalkin]

Hi Norbert,

The installer from Litepoint doesn't provide VI's, it is only DLL's.

I have built VI's through the Import tool in Labview and I have updated this setup with LV2010 but I am still seeing the issue.

Simon

[Norbert_B]

Simon,

do you use VI Server to load and execute VIs dynamically?

Norbert

[swalkin]

Hi Norbert,

No I have TestStand call a LV VI that has a Call Library Function Node in it.

I have generated these subVIs for all functions using the Tools-->Import-->Shared Library and it generated a LV Project with a VI for each function. Then I call these through TS.

All relevant DLL's are included in the deployment and as I mentioned before, this setup as worked previously with the following combinations:

TS4.1 & LV8.5

TS4.2 &  LV2009

[Norbert_B]

Simon,

is it possible, that the deployment system is running a different OS (XP vs. 7 for instance)?

It is possible, that this is simply a path problem in the CLFN's. Since those store the path info and expect the DLL to be available there, this could be easily an issue if the DLL is located somewhere else....

hope this helps,

Norbert

[swalkin]

Hi Norbert,

The OS issues "shouldn't" be a problem unless it has been introduced in TS2010 as I have done Win7 to XP development to Target deployments without issues.

I have checked the paths to the DLL's and all seem to be fine.

Simon

[Norbert_B]

Simon,

the OS could be an issue because of different security settings and path-layouts (user folders!). So this is nothing in the  responsability of TS.

One thing which has changed from TS 4.2 and 2010:

You can now include the LV project to your steps if necessary. There are certain cases where you have to configure this and maybe your application is running into that.

I could explain the behavior behind this, but this is a lengthy explanation and if does not change anything, the explanation is simply "FYI".... so i will postpone that.

One question:

Can you pindown the issue to a certain step/module?

thanks,

Norbert