LabVIEW 2023 Errors after .EXE build

[JanisLabGuy]

Hello,

if face a strange issue:

The build of the vi is working fine without errors, but when I try to start the .exe the note tells it cannot be accessed. 

The point is that is not true. 

I've clarified with the local IT that we have the access and also tested that in local C:/ where every user has access. Also the IT with all rights has this issue when opening the file.

If I hold down the Enter button for a few seconds to open the file i get the error message a foew times but also some instances of the exe open and work completely fine. So the issue is not really access related - either you have acces or not, that does not change by holding enter for a long time 🙂

I for myself do not have admin rights, but as said before the IT sees the same issue.

I would therefore assume its an issue with the vi.

Ive run the VI Analyzer and see no red errors, some blue, but to my understanding they are more hints what can be optimized.

I have to add, this is version 1.3 of my program that i continue to optimize and version 1.0 to 1.2 work completely fine.

If tried several build options to solve the problem but that did not help either.

I also tried to build the old version 1.0 again but also that does not work anymore.

I copied the block diagram into a new vi - same issue.

Im using the LabJack Module as a add-on for separate functions for the DAQ System: LJM Software Installer Downloads - T4, T7, T8, Digit

The main VI is the LabGas VI.

Id appreciate your support!!

[GerdW]

Hi Janis,

---

@JanisLabGuy wrote:

I have to add, this is version 1.3 of my program that i continue to optimize and version 1.0 to 1.2 work completely fine.

If tried several build options to solve the problem but that did not help either.

I also tried to build the old version 1.0 again but also that does not work anymore.

---

So the conclusion is: something in the system changed, but not the LabVIEW code!

Any new virus scan/protection tool?

Any (silent) updates in the meantime?

Does LabJack need any DotNet environments? (Maybe they changed?)

[dkfire]

What bit version have you installed? 

Is LabVIEW 32 or 64 bit ? 

Is the LabJack driver installed as 32 or 64 bit ?

Is the driver installed on the PC that you run the exe? 

Have you tried running the vi from the LabVIEW IDE ?

[JanisLabGuy]

Thanks for the fast responses:

Regarding your questions:

Any new virus scan/protection tool?

As im a client I can more or less only forward the questions as i myself cannot deactivate anti virus softwares - no admin. But it might be, ill check if the IT can log in and deactivate temporary to check.

Any (silent) updates in the meantime?

Laptops are updated automatically.. those are the latest ones

No Labview update so far

Does LabJack need any DotNet environments? (Maybe they changed?)

Labjack has a calibration software to set up your measurement card, that was a one time installation 2 years ago, same for the Labjack Modules LJM the adon for Labview.

[JanisLabGuy]

Any new virus scan/protection tool?

Addition:

Actually this cannot be the case: When i select the build .exe and hold the enter key it tries to open the exe several times, therefore i get the error multiple times, but also a few instances of the exe open and work fine.

[JanisLabGuy]

Is LabVIEW 32 or 64 bit ? 

Installed is LabVIEW Version 2023 Q3 (64-bit) 23.3.2f2

Is the LabJack driver installed as 32 or 64 bit ?

On the manufacturers side it says it supports both. I cannot remember that there was a choise. but as Labjack did not change, no update or so and it worked before the bit version should be fine.

Is the driver installed on the PC that you run the exe?

I run the exe on the same laptop as the developer leptop with the full labview version including runtime where a ran the previous versions of the software 1.0 - 1.2. The old exe of 1.0 is still working on the developer laptop - my laptop :).

Have you tried running the vi from the LabVIEW IDE ?

I don't know what that is, actually.... so the VI were is see the block diagram and the frontpanel, so not build runs fine in labview. Only the build version shows the error.

[GerdW]

Hi Janis,

---

@JanisLabGuy wrote:

When i select the build .exe and hold the enter key it tries to open the exe several times, therefore i get the error multiple times, but also a few instances of the exe open and work fine.

---

• Do you know which device or file cannot be accessed?
• What is giving you the "access rights missing" error?
• What have you tried to debug your exe?
• Is the exe prepared to execute "several times" in parallel (?)?
• What is the difference between the "several" runs when some instances can execute correctly?
• Are there any files in sync'ed folders (OneDrive, Dropbox or similar)?

[JanisLabGuy]

Addition:

I just had the idea to post the .exe here, but i can only post .zip. So i tried to pack it and then i also get errors...

"Due to an unexpected error you could not copy the data..."

The file is obviously corrupt somehow, but why?

[GerdW]

Hi Janis,

when you can't copy the file then usually two things might happen:

1. Some other process is currently accessing the file and so blocks from access. (I don't think this is the case here.)
2. Some antivirus is blocking you from accessing the file. (This is my favorite guess.)

Btw. I will not run an arbitrary executable from a public forum, so no need to post it. I will open LabVIEW VIs…

Vielleicht hilft dir dieser Artikel bei Heise.de weiter. Ansonsten einfach mal selbst googeln!

[JanisLabGuy]

• Do you know which device or file cannot be accessed?

It says device, path or file cannot be accessed, so a very general message. In the subject it just shows the exe files path.

• What is giving you the "access rights missing" error?

I think its a Windows message,not from Labview or Labview Runtime or anything else.

• What have you tried to debug your exe?

1. Copied it somewhere else (Desktop; c:/ temp; documents) and executed it there

2. Asked the IT with Admin rights to executed - same error

3. used another laptop with LabVIEW RTE - same error

4. tried nearly all build settings in labview with the same results

• Is the exe prepared to execute "several times" in parallel (?)?

Its a stand alone application. Ive not made anything on purpose that it can or cannot execute in parallel. The previous version could run open in parallel whereas it would lead to issues as if the DAQ system is connected to one app it cannot connect to another.

• What is the difference between the "several" runs when some instances can execute correctly?

As i tried different build settings I try different versions to see if there are any differences in behaviour. When holding enter to open several instances, it actually opens one instance that works, but it is not the first one. I think it depends on the rapid fire produced by holding the enter key as the message of no access comes first 2 or three times then the app opens and then 10 or more access message occur, but no further instance of the app opens.

• Are there any files in sync'ed folders (OneDrive, Dropbox or similar)?

It thought about issues with OneDrive as we are used to work with that instead of the local documents folders. So i Changed the build path to the local c:/ users... Documents with the same results.