Open VI Reference Function and a RUN VI RUN VI Method Causes Error 1000 with version 2014

[robojeff]

I inherited an application that was originally created with LabVIEW version 8.6 for a Windows XP system but I am updating it with LabVIEW 2014 for a Windows 10 system.

It all works except for one section where an Open VI Reference Function is used and later
a RUN VI RUN VI Method is used.

This works fine with the version 8.6 application but with the 2014 version, I am getting an Error 1000.

Is this caused by a bug with version 2014?

Any ideas on how to fix this problem?

Thnaks

Here is what the this part of the application looks like:

[Norbert_B]

Have you compiled that "plugin" VI with LV 2014?

[robojeff]

Thanks for the quick reply...

Which  "plugin" VI?

[robojeff]

Not quite which plugin Vi to compile or how to do that...

Is this done by itself and before the project build?

thanks

[Norbert_B]

The VI you load with Open VI Reference is the one i am referring to. This has to be compiled in LV 2014 as well in order to work correctly.

However, thinking about the error message, it should be a different one if it's in a wrong version.

Are you running the stuff in the LV Development Environment?

What happens if you manually load the VI?

[JÞB]

I would also check Windows file permissions.  XP was a lot more forgiving about files on root.  Win 10 really will not make it so simple to use protected areas.

[jwscs]

can it be that your called vi is broken?

or like this doc suggest a reference is still open and not closed

http://digital.ni.com/public.nsf/allkb/DE45BD35AFE818E2862565FB00592B31

[robojeff]

Thanks Norbert

I am now running this in the 2014 LabView Development Environment  (LDE) but it was failing

in the version 2014 built executable which is why I am now looking at it with the LDE...

The VI will load and run without problems by itself and also when built with LabVIEW v 8.6 and called 

from that built executable.

I did some reading up on Error 1000, and read that this error usually indicates that the VI is already

running when called but this is does not appear to be the case with my application.

The same error will occur if the targeted VI is not running, but is reserved for running when a reference to it is

opened using the Open VI Reference function with a strictly typed VI Refnum wired to the type specifier

VI Refnum input.

I am not using the type specifier to call the VI while using a Call By Reference Node, and as I understand it, the

VI is not reserved for running.

and that is as far as I got with it...

[robojeff]

Thanks Jeff-

I checked the file permissions by removing read only settings for all files in the folder but this didn't help.

Is that what you meant?

[Norbert_B]

---

@robojeff wrote:

Thanks Norbert

I am now running this in the 2014 LabView Development Environment  (LDE) but it was failing

in the version 2014 built executable which is why I am now looking at it with the LDE...[...]

---

So in the DevEnv everything works as expected?

If so: What is inside that VI(s) you call here?

I can imagine that you have a licensing issue when using packages which require an activation of a license....