LV 2010 SP1 installed, The VI is not executable message, NI bug workaround not working either.

[sfleming]

Vi worked perfect until installing SP1 for LV 2010.  Known bug and workaround DID NOT WORK. Frustrated!!!!!  Finalizing LV project and wanted to use latest LV version/SP.  Regret it now!  Please help if you have found a solution.

The VI is not executable. The full development version of LabVIEW is required to fix the errors" popup on a built app
If you have a built application that contains a polymorphic VI in a LabVIEW library which has an instance VI that is private, and a VI outside the LabVIEW library calls the polymorphic VI, this error might occur in the built application.

Workaround: In App Builder, under "Additional Exclusions", uncheck the "Remove unused polymorphic VI instances" option.

Reported Version: 2010 32-bit

Resolved Version: N/A

Added: 03/08/2010

[sfleming]

Additional info - my app was developed in LV 10.0 and exe worked perfect on 2010 SP1 desktop development system.

ALSO using Simplicity PDF toolkit developed in LV 8.6 (polymorphic VI in a LabVIEW library which has an instance VI that is private, and a VI outside the LabVIEW library calls the polymorphic VI).  Did mass compile as suggested, but I may have done it prior to upgrading to 2010 SP1.  Will try mass compile again using 2010 SP1 on Monday 6-6-11 to see if it helps, doubtful though as it should not matter???? Never had to do this with other libraries.  Last straw, desparate as jeopardizing my deadline.  

NI WORKAROUND DID NOT WORK: In App Builder, under "Additional Exclusions", uncheck the "Remove unused polymorphic VI instances" option.

Standalone app (.exe) must work on system in cleanroom; ugh too much gowning up (may have to install 2010 SP1 on laptop for development and convienience, prefer not to though). 

Did full install of SP1 RTE on deployment system to no avail.

FRUSTRATED - please help!

Why are what should be the simpliest of things, the most difficult?

[Thør]

I see you're using Simplicity ai's PDF Toolkit in your code. Did you include those functions into the EXE or installer, so the target machine would also have those functions? If you've done that and it's still not working, then it might be worth doing a mass-compile on both your VIs as well as the VIs in the PDF Toolkit. While upgrading your version from LabVIEW 2010 to 2010sp1 recompiling those VIs before putting them into an executable would make sure they're up-to-date with the most recent data. Additionally, make sure you have the 2010 SP1 runtime engine on your target machine. If you've upgraded your development machine without updating your target's runtime engine then that may also cause a problem. Thanks for the question! 

[sfleming · Accepted solution]

Kyle,

All excellent suggestions and probably required; did all to be sure.  However, problem turned out to be .net Framework 1.1 did not work, CONFIRMED 2.0 (maybe later versions too; didn't test) needed to be installed on the target machine.

From what I saw/tested my application built with VIs from SAI_PDF_Toolkit_1.0.2.zip http://www.simplicityai.co.uk/products_services/products/pdftoolkit/ did not
work as stated in SAI "readme.txt" http://www.simplicityai.co.uk/products_services/products/pdftoolkit/readme.txt
with .net framework 1.1 and produced  "This VI is Not
Executable Error When Running Executable".  My application (.exe) DOES WORK on
target PC now that .net framework 2.0 is installed too.

THANKS!

PS It had been a while since I worked on the application and the one thing I added, but did not test without SP1 was using the PDF toolkit VIs.  The problem obviously has nothing to do with the SP1.  Ooops...SORRY...pretty important detail....but now we know...

Regards, 

[Thør]

Awesome!  I'm glad you were able to get to the bottom of this.