Executable error in LabVIEW 0x00

[Fredo123Danzel]

When I run the project, I don't get any errors. However, when I create a new .ex file and execute it, an error message appears (see below).

//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

LabVIEW: (Hex 0x0) Error connecting to GPIB driver or device. The NI-488.2 driver may not be installed.
=========================
Error connecting to driver or device. The NI-488.2 driver may not be installed.
=========================
VISA: (Hex 0x0) Operation completed successfully.

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

Would you happen to have any idea what might be causing this, please?
The hardware is functioning correctly, especially since my previous .ex file runs without any issues

[GerdW]

Hi Fredo,

---

@Fredo123Danzel wrote:

Would you happen to have any idea what might be causing this, please?

---

Something in your "Fichier…" VI…

(You should debug that VI. Does it generate an error cluster with status=TRUE and code=0?)

[Fredo123Danzel]

Hi, 

Error 0 is not generated anywhere in my VI. In development mode, the VI runs correctly.

I also have an older executable that works without any issues. This problem only occurs with my new executable.

[GerdW]

Hi Fredo,

---

@Fredo123Danzel wrote:

This problem only occurs with my new executable.

---

So what did you change?

---

@Fredo123Danzel wrote:

Error 0 is not generated anywhere in my VI. In development mode, the VI runs correctly.

---

Do you know the exact place where that error does occur?

[cordm · Accepted solution]

"Fichier de configuration introuvable", apparently a configuration file cannot be found. 

Working in development vs not working in executable could mean

- configuration file was not copied to the PC where the executable is running 

- configuration file path is defined relative to a VI path, which will be different in the executable

Check the recommendations from this page: Error 7 in Executable When Using the Current VI's Path Constant

(It is not your error code, but that could have been overwritten by your error handling)

You should also check in your source control what changed between the last working version and the current one.