"The VI is not executable."

[altenbach]

What kind of processor does this computer have? (I am not quite sure what you mean by "similar type")

Remember that for targets with relatively old CPUs (e.g. Athlon XP or pre-Pentium 4 intel), you need to disable SSE2 in the build specifications. By default, SSE2 is enabled, so the code will not run on these old processors. (See also).

(Just another idea. I am actually not sure how the error would look like in such a case...)

[hartzde]

All 32-bit

Development system is Win7

Targets are all XP Sp3

[altenbach]

---

@hartzde wrote:

All 32-bit

Development system is Win7

Targets are all XP Sp3

---

You still did not mention the exact processor model.

[altenbach]

Duplicate

[hartzde]

Development is a Core i7.

The Program runs on an "x86 Family 6 Model 15 Stepping 11"

The Target is an "x86 Family 15 Model 4 Stepping 10"

Per System information.

[altenbach]

Thanks, I think this is a P4, so it should be OK.

[hartzde]

I unchecked the SSE optimization and rebuilt the program and installer.

This did not change anything.

[cirrusio]

Did you ever fix this problem, hartzde?  I am having/have had this same problem and I can't seem to remember how I fixed it before.

Matt

[Whit-E_Wall-E]

Hello Matt,

It may be better to start a new discussion forum regarding the error and explain the steps that you have tried in order to get more feedback.

I would see if you are able to run the executable on any other machines?  Verify the correct Run Time Engine is installed.

Also check out this article: http://digital.ni.com/public.nsf/allkb/F715F1ED66878F8E862574F8006AD6A1?OpenDocument

[cirrusio]

Thanks, Whit-E_Wall-E.

I realized that I had already posted in another message with the same title.  I won't rehash my own issue and the solution here (you can go to the link above to read more about it - I was able to resolve my problem in a similar fashion), but it would still be nice to hear from the original poster whether they were able to resolve this.  It would provide further insight into what might cause this issue as it seems the article you referenced did not provide a solution for his problem or mine and this is the only article that actually references the error.

Cheers, Matt