old application reports "The VI is not executable. The full development version of LabVIEW is required to fix the errors"

[KaareBach]

Hi

I have developed a small, simple aplication. This is build with application builder and installed on several PC's.

This has been running with no problems for years.

One user is now getting this error: "The VI is not executable. The full development version og LabVIEW is required to fix the errors."

The application has not been changed for 6 months, and is build with LabVIEW 2017.

I have searched for possible reasons, but no one of them is usable in my situation.

The application is used every day.

The problem started just after he installed Microsoft Visio.

The user PC has the exact same .NET versions installed as on my development PC.

He has tried to uninstall the application and the LV runtime engine, but nothing helps.

Thanks in advance!

Kaare

[PalanivelThiruvenkadam]

Is there any addon Toolkits used in the application development?

What kind of application is that basically (What it does)?

[wiebe@CARYA]

---

@KaareBach wrote:

This has been running with no problems for years.

One user is now getting this error: "The VI is not executable. The full development version og LabVIEW is required to fix the errors."

The application has not been changed for 6 months, and is build with LabVIEW 2017.

I have searched for possible reasons, but no one of them is usable in my situation. 

---

How has it been running for years while it's developed in LV17? If it changed 6 month ago, I'd say the application is 6 months old. Not that it matters, really. But facts can be critical.

Do you get any reference to the VI that is broken? The name of the VI would be good to know. usually you get a more specific error.

Do you use .net in the application? That would be suspicious, and a likely cause of the problem. Or  ActiveX, including the report generation toolkit? That would be a known issue.

When you say it has the exact same .net versions installed, does that include all the assembly versions? Or just the .net runtime version?

Any dynamically loaded VI's, PLL's, external VI's, etc.?

[KaareBach]

---

wiebe@CARYA wrote:

---

@KaareBach wrote:

This has been running with no problems for years.

One user is now getting this error: "The VI is not executable. The full development version og LabVIEW is required to fix the errors."

The application has not been changed for 6 months, and is build with LabVIEW 2017.

I have searched for possible reasons, but no one of them is usable in my situation. 

---

How has it been running for years while it's developed in LV17? If it changed 6 month ago, I'd say the application is 6 months old. Not that it matters, really. But facts can be critical.

Do you get any reference to the VI that is broken? The name of the VI would be good to know. usually you get a more specific error.

Do you use .net in the application? That would be suspicious, and a likely cause of the problem. Or  ActiveX, including the report generation toolkit? That would be a known issue.

When you say it has the exact same .net versions installed, does that include all the assembly versions? Or just the .net runtime version?

Any dynamically loaded VI's, PLL's, external VI's, etc.?

---

The application did not change for years, but due to another issue, I converted to LV 2017, and made the new installer from here.

No broken VI's.

I don't use .NET, but when googling the problem, it seems to be a common problem.

I guess it is just the runtime versions. Not sure how to check assembly versions.

No dynamically loaded VI's.

Thanks

Kaare

[KaareBach]

---

@PalanivelThiruvenkadam wrote:

Is there any addon Toolkits used in the application development?

What kind of application is that basically (What it does)?

---

No Toolkits used.

And no additional installers.

The application is a simple tool used to keep track on how we use hour time on different development projects.

So it is not a "normal" LabVIEW program: No external I/O boards etc. is used. It is only a user interface.

br

Kaare

[James_W]

on the subject of .NET, unless things have changed recently. LabVIEW in 2015 did not fully support .NET 4.0 (and I don't think it does in 2017 either but I am happy to be corrected.) - You might need to ensure .NET 3.5 is fully installed.

The other possibility that you haven't covered yet is that it is possible to compile an installer "require the development system". Is it possible that you have done this and the license has lapsed on that machine?

James

[KaareBach]

---

@James_W wrote:

on the subject of .NET, unless things have changed recently. LabVIEW in 2015 did not fully support .NET 4.0 (and I don't think it does in 2017 either but I am happy to be corrected.) - You might need to ensure .NET 3.5 is fully installed.

The other possibility that you haven't covered yet is that it is possible to compile an installer "require the development system". Is it possible that you have done this and the license has lapsed on that machine?

James

---

Hi James

No, the user never had the LabVIEW development system installed on his PC.

br

Kaare

[wiebe@CARYA]

So..

+ The user had this application up and running.

+ Then installed Visio.

+ And it stopped running?

+ No ActiveX or .NET in the code (also no report generation)?

+ The error does not mention a specific VI?

Running out of options\ideas...

[KaareBach]

---

wiebe@CARYA wrote:

So..

+ The user had this application up and running.

+ Then installed Visio.

+ And it stopped running?

+ No ActiveX or .NET in the code (also no report generation)?

+ The error does not mention a specific VI?

Running out of options\ideas...

---

Yes, your summary is very precise 🙂

And I am also stuck...

[dkfire]

---

@KaareBach wrote:

---

@PalanivelThiruvenkadam wrote:

Is there any addon Toolkits used in the application development?

What kind of application is that basically (What it does)?

---

No Toolkits used.

And no additional installers.

The application is a simple tool used to keep track on how we use hour time on different development projects.

So it is not a "normal" LabVIEW program: No external I/O boards etc. is used. It is only a user interface.

---

So how do you save the time? 

Database ? Excel ? File ?