Error Message: The VI is not executable. The full development version of LabVIEW is required to fix the errors.

[Viper]

I have an exe that has been working but my latest builds open an error window on launch. When you click OK the front panel show a broken arrow. My environment is a Widows 10 PC developing with LV2013SP1-32. The error window is shown below with the message repeating almost 250 times. It fills my 1920x1200 monitor almost completely.

 There are some very old threads on this topic but they have not helped me solve this. My main.vi runs fine in LabView with no problems. I just can't get a exe build to run.

This is a fairly large app with over 1200 VIs. and an event case with 25-30 events

Things I have tried.

1. Roll back source to an older version from TFS and build. No Joy
2. Change PCs. Install LV2013 ful dev on another PC download my source from TFS and build. No Joy
3. Try a new project from main and build. No Joy
4. Port to LV2020. I am short toolkits that work in 2020. (G Toolkit, SSH Toolkit from LabWerx) working on getting them. Will try later.
5. Remove sub vis from my main to try to identify the offending sub vi. (Finally ran when 90% of my code was removed)
   1. My main has many event cases that are control by button down events
   2. Data to the subvis in the event case are handled by several shift registers in the while enclosing the event structure.
   3. I removed event cases until the shift registers were no longer required. Then the exe would run. Yippee.
   4. Since the shift registers were un initiated I initiated them with all event cases and rebult. No Joy.
   5. I made sure all the output tunnels on the event cases were wired and turned off "used default if unwired" 
6. I am wondering if I should learn how to use the debugger and see if this yields any usefully information.

Any pointers will be greatly appreciated.

I've been beating on this for a week and I'm out of ideas.

Norm

[FireFist-Redhawk]

---

@Viper wrote:

I have an exe that has been working but my latest builds open an error window on launch.

---

The first question here is, what has changed since the working state?

[Viper]

---

@FireFist-Redhawk wrote:

---

@Viper wrote:

I have an exe that has been working but my latest builds open an error window on launch.

---

The first question here is, what has changed since the working state?

---

That is an excellent question. My prior backup was just as the Covid-19 lock down in California. So there are several months of development before my last commit. My bad i'm feelin' da pain. I backed out the two event cases that were added since that last commit but that didn't fix the issue.

Norm

[FireFist-Redhawk]

Yeahhh bad move there 😅 also your master branch should only contain working code and if you're developing, you should be on some development branch and merge back in to master once you're sure everything is working.

The one time this happened to me was when my team tried (unsuccessfully) to migrate to 2019 from 2017. We rebuilt a couple apps in 2019 then tried to run them and got that. We've backed up to '17 again for the moment. No changes in the version of LabVIEW or any packages/toolkits/dependencies?

[Viper]

I use totally different branches for LV13 and LV19 I'm afraid I'll step in it real bad if you know what I mean.

[paul_cardinale]

---

@Viper wrote:

---

@FireFist-Redhawk wrote:

---

@Viper wrote:

I have an exe that has been working but my latest builds open an error window on launch.

---

The first question here is, what has changed since the working state?

---

That is an excellent question. My prior backup was just as the Covid-19 lock down in California. So there are several months of development before my last commit. My bad i'm feelin' da pain. I backed out the two event cases that were added since that last commit but that didn't fix the issue.

Norm

---

Yikes  "several months"!  I get worried if I go more than a day without a backup.  And I keep all the old versions because sometimes I find out about a mess-up weeks after the fact.

[thols]

If you build and include a startup VI with a standard menu, you can open VI's from it and see if they are broken. That can help you narrow it down.

throwing out some thoughts without thinking them through:

- mass compile?

- forced recompile? (CTRL+SHIFT+RUN on top level VIs)

- try creating new project and new build spec. The project/build-spec maybe got corrupted.

And please please start using SCC and have a backup script or something too.

[Yamaeda]

Are you using some DLL?

I've had a similar thing happen where the .exe suddenly didn't find the DLL and kind of only found it if it was in the same folder as the .exe (instead of the normal Data-folder), and ended up having to move it in my Project so it was the same structure. I have no idea why and can only guess that it has something to do with a windows update (as LV doesn't update as often).

[thols]

Yes, that's what happened to me once too. A dll that was not found. I don't think it was the same reason though for me.

[Viper]

OP here

I am guessing that this problem is caused by my installing LV2020 on my system. I have NI-845x and LV2020 removed the driver for LV2013. I hand copied the driver back into LV2013. I think I need to scrub my laptop and reinstall LV2013.

Norm