Trouble switching adapter from LabVIEW development to runtime engine

[RoxtheFox]

What version of TestStand are you using? TestStand 2017 SP1 has improved error handling for loading VIs in the runtime engine that make finding the solution to your problem much simpler. 

[Bill_Lewis]

TS2016 SP1

[RoxtheFox]

Can you try 2017 SP1 or share the smallest set of code that exhibits this behavior?

[Bill_Lewis]

I don't have a license for 2017. I'm afraid that if I go to 2017 I will not be able to revert back. I would be happy to email you my LV project since it seems to be a issue with it. I can load a different project and just add a LV action and it will run in RT mode fine. Something in the LV project is creating the issue

[Bill_Lewis]

I have not heard back but I think I have found the issue. Both of the vi’s that have an issue of changing from development to runtime use database subvi’s from the C:\Program Files (x86)\National Instruments\LabVIEW 2018\vi.lib\addons\database\ library. If I press control and the run arrow they recompile and then I save. I can do the same again immediately and they will recompile again and I will have to save.

It seems that these files in the .llb will not update to the current version after the recompile. In the VI properties is shows version 18 but this is not true because the VI want to recompile each time and will not save in the current version. These llb files are password protected by NI and all of the files within the database toolkit have the same behavior.

Is it a permissions issue LLB with NI? I have mass compiled the database directory with no errors and this still does not solve the issue.

[svacek]

Hi Bill,

Were you ever able to solve your issue?  I'm having the exact same problem and have yet to come up with a working solution.  My issues seem to be caused by subvi's being called from the C:\Program Files\National Instruments\LabVIEW 2017\vi.lib\Utility\error.llb.  Cant seem to get them to recomplile.  I've tried moving this llb to a different working directory, but LabView doesn't like that.

Thanks in advance for your time.

Kind Regards,

Steve Vacek

[Bill_Lewis]

Yes, remove any unused dependancy vi's out of the project or any vi that is in the project that has a broken arrow. Mass compile the project directory and try again with the deployment. Make sure that any llb that your using was not copied from a older version of LV but was installed via the proper installer. My case was that the report generation tool was copied over from a older LV version and it would not run in runtime mode but would in development mode

[svacek]

Thanks for the suggestions Bill. Much appreciated

Steve Vacek