Deployment utility error "VI not executable"

[PatSpring]

I do not understand the error below. I am using GET.VI in the HTTP Client library of LabVIEW 12. My sequence works and the VI also works when opened in LabVIEW. Can someone explain what is happening? Thanks!   Note that if I check the "Include item without processing item or dependencies" (on the Distributed files tab) then it will build without errors.

TestStand13 Deploy Util Output:

LabVIEW Version: 12.0f3 (2012) (32-bit) English
Internal Error Code 6503 Processing VIs...
Could not process LabVIEW VIs. Fix any broken VIs before you rebuild. LabVIEW error:
Exception occured in LabVIEW: LabVIEW:  The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select <b>File>>Open</b> to open the VI and then verify that you are able to run it. in Dynamically Call Method in LLB - TestStand.vi:5->Dynamically Call Build VI Distribution LV 2010 or Above - TestStand.vi->Dynamically Call Build VI Distribution - TestStand.vi->Call Build VI Distribution for Unique VI Hierarchies LV 8.6 or Above - TestStand.vi->Deploy without LabVIEW Projects - TestStand.vi->Package VIs - TestStand.vi->Build Create Image - TestStand.vi->Build - TestStand.vi->Distribution Wizard GUI - TestStand.vi->Deployment Utility Splash Screen  - TestStand.vi
An error prevented the creation of an installer.

Regards,

Pat

[Daniel-E]

Hey Pat,

Actually, it looks like this error might be occurring if one of the VIs we use in the deployment process is broken. To diagnose the error, please complete the following steps:

1. Open <TestStand>\Components\Tools\Deployment Utility\TestStand - Build VI Distribution\12.0\ and back up the whole directory (copy it to a different location on your machine)
2. Open <TestStand>\Components\Tools\Deployment Utility\TestStand - Build VI Distribution\12.0\Distribution VIs.llb and in there open the VI "Build VI Distribution 2010 - TestStand.vi" and verify that it is broken
3. If it was broken, reinstalling TestStand should fix the problem.

4. If it was not broken, our VI is being relinked with some of the other VIs in your deployment, which means the error is being caused by something in this specific use case. The first thing I would try is to close LabVIEW before deploying, to ensure none of your VIs are still in memory.

If you do discover that the Deployment Utility VIs are broken, please send me the folder of VIs so we can examine them to figure out what happened. We can communicate by private message and figure out a way to get the files over to us if that was the case.

If these steps do not resolve the issue, please let me know and we can figure out some additional troubleshooting steps. I'll look forward to hearing back from you about it!

[PatSpring]

Thank you for the help. I followed your steps and found it was not executable.  VI's "TestStand API Numeric Constants.vi" and "TestStand API Numeric Constants.ctl" and "TestStand - Get Resource String.vi" not found. I reinstalled TS but the problem was not fixed. Maybe I didn't select the correct options for TS install?   FYI I did the Setup.exe -reinstall command else nothing would install.

Thanks!

[Daniel-E]

Pat,

Those two items are actually part of the TestStand API in the <TestStand>\API\LabVIEW folder, so it's strange that they still aren't being found. Could you close LabVIEW and TestStand, and then try running the TestStand Version Selector and re-select your version as active? This will re-register the API VIs. If the error persists, it might be wise to try uninstalling and reinstalling TestStand to ensure that all files are replaced. Of course, be sure to back up your own test sequences as well as the Cfg directory and any custom process models you have created, to be sure that these items are not overwritten.

[PatSpring]

Daniel, I found the cause of the VI not being able to execute. During installation I selected the default setup options which does not include "API". I selected the API option and after it installed the build process completed! Thanks! Without your help I was at a loss.

Best regards!

Pat

[Daniel-E]

Great to hear, Pat. I'm glad it's working properly now!

[Joe_Gerhardstein]

I had similar problem with TS 2013, LV 2013.  In my case, the addons directory was completely empty, even though we had installed the TS Deployment Utility.

Reinstalling TestStand solved the problem!

[JimmyB23]

Hi Guys, 

This question is meant mainly to Joe, Did you have to re-install TestStand completely or just certain components?

I tried to just uninstall and re-install the "Tools" piece since it contains all of the deployment vi's but that was not successful.