Cannot find LabVIEW: (Hex 0x7) File in computer, how to solve?

[RavensFan]

---

@crossrulz wrote:

---

---

Except the error happened at a File Open function.  So it is something related to File IO.

---

Dohh! Of course!

I was ready to respond to that particular message about how the GPIB error is a red herring (how often do we see people say they have an error message like that but don't know what is meant by GPIB).  Then I realized, we really don't know what this user is trying to do.  Maybe it is the situation that they are doing GPIB completely forgetting the part about the File Open+.

So the solution is really in messages 6, 7, and the first sentence of 8.

[NirutG]

The machine have 2 DI/DO Advancetech 64 channels.

---

@RavensFan wrote:

Hmmm.

Good point.  We really don't know what this application is supposed to do.  Maybe it does use GPIB and that secondary possible error message is true.

I find that GPIB is so rarely used, that the error message mentioning that is usually just noise.  I don't even bother reading down that far because it never applies to me.

NirutG, does your program use any GPIB devices?

---

•  

[RavensFan]

You still haven't shown us any VI's so we can see what this program does.

Did you install any drives that may have come with this Advantech device?

[rolfk]

No need to speculate here about anything. This is the File Open vi being called with a path that does not exist. Nothing about non-existing VIs and certainly nothing about GPIB. There are three lines about a bad file or file path and one offering the possibility for a GPIB problem since the old GPIB functions predate LabVIEW and happen to use the same error code range. And people keep jumping on that as a first means to try to fix an app.

There is somewhere in the program simply a File Open vi with an invalid path as input. This is probably even a fixed path constant somewhere that simply doesn’t exist on a new computer (like C:\datalog) or is different on modern Windows systems. It’s caused by the program as written by the original programmer and not by some obscure bug in LabVIEW. As such the only way to fix this is to debug this program with single stepping, wire probes etc at runtime and fix the problem in the source code of the program. There is no magic ‘install this patch’ recipe which could help.

If the OP had attached a zipped up version of the project this could have been pointed out in the second post already, but debugging it himself would have been just as simple.