03-14-2012 04:15 AM
Hello, I know there is a thread about this issue, but it did not help me, so I start a new thread.
Here my problem:
The message of the MessageBox is:
in german: "Das VI ist nicht ausführbar. Zur Behebung der Fehler ist das LabView Full Development System erforderlich."
in english: "This VI is not executable. The full development version of Labview is required to fix the errors"
Under LabView development environment (LV2011 SP1), it works, under RunTime Environment (on same PC ! ) it does not.
I use this options:
for all dependencies:
I use these settings:
And this are the removements:
For logs while loading EXE, see attached file.
Any Idea why it does not work?
Thans in advance
Solved! Go to Solution.
03-14-2012 04:57 AM
You have not attached your sources.
Is that issue connected to your previous post?
Do you use dynamic VI calls where you possibly miss VIs of that hierarchy (issue: source distribution)?
Have you tested if "Use LabVIEW 8.x file layout" does have any effect (advanced options tab)?
The debug log (origin?) states something of "target not found" and "target has no VI.LIB. I would focus my search in this direction....
hope this helps,
Norbert
03-14-2012 05:45 AM
Hello Norbert, thank you very much for your help.
This helped for me:
uncheck "SSE2 optimization"
When SSE2 option was unchecked, it worked.
You also asked:
>You have not attached your sources.
No, the project is too big
>Is that issue connected to your previous post?
No, its another project
>Do you use dynamic VI calls where you possibly miss VIs of that hierarchy (issue: source distribution)?
no, currently not
>Have you tested if "Use LabVIEW 8.x file layout" does have any effect (advanced options tab)?
yes, this works also, when SSE2 is disabled
>The debug log (origin?) states something of "target not found" and "target has no VI.LIB. I would focus my search in this direction....
Thanks
03-14-2012 07:03 AM
Hmmm,, SSE2 optimization as reason seems rather odd. SSE2 is a common feature for CPUs now, with quite some successors up till now. So this optimization by itself should not create such issues.
I am wondering if your code includes DLL-calls which might be unable to be optimized for SSE2. This *could* explain the issues you are seeing.
Nevertheless, SSE2 only gives advantage for esp. excessive floating point operations, so if you are not going to do so, and not looking for "top edge performance", deactivating SSE2 for the build is definetly a suitable workaround.
Norbert