LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView executable error

Hello,

 

I made some changes on the LabView program, and rebuild the exe.  However, when I deployed it on another machine, I get this error.  

 

How do I fix it?

alibaibai_0-1662767810014.png

 

When I try to run it from the editor, I get this error.  But, all the libraries and dependencies are the same as the old executable file.

alibaibai_0-1662768043109.png

alibaibai_1-1662768088186.png

 

Any suggestions?

 

Thanks,

 

0 Kudos
Message 1 of 13
(1,906 Views)

You should undo your changes.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 13
(1,881 Views)

Hi Bill,

 

Thanks for your input.  I don’t think it is the change in the program that caused it.  The only change in the code is saving the data to another directory.  We even build the original program with this development machine and deployed it in the same workstation that runs fine with the old executable, and it still has the same error. 

0 Kudos
Message 3 of 13
(1,857 Views)

Something changed because now you have an invalid handle.  We can tell you more if you upload the VI.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 4 of 13
(1,851 Views)

Well an Invalid Handle generally means you are not initializing your instrument (opening a new handle) before trying to access it or you are closing the instrument handle and then attempting to access the instrument using the old (invalid) handle.

 

But we need to see your code to know for sure...

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 5 of 13
(1,804 Views)

I'll take a swing at an educated guess.

 

Your original build spec marked the default "remove unused polymorphic instances" then you did not rebuild all and tried to deploy exe changes by just replacing the exe rather than using the new installer.

 

My magic 8-Ball is fairly good.


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 13
(1,786 Views)

I'm ignoring the error you get while running, because that's a runtime error and I'm assuming it's actually correct and you really didn't initialize the hardware correctly, as the others suggested.

 

 

For the EXE error, it helps to search for the error text (here's one example. I assume there are other pages too).

 

I don't see this often, but from what I can remember, it's usually one of two things:

 

  1. You really are missing some dependency which is not installed (If the EXE can run on the computer which has LV this seems likely).
  2. There really was a problem when building the EXE. This happens sometimes and might require clearing the application builder compiled objects cache (Tools>>Advanced), force compiling all the VIs (Ctrl+Shift+Run button on the top level VI) and/or restarting LV.

 

 


___________________
Try to take over the world!
0 Kudos
Message 7 of 13
(1,752 Views)

@tst wrote:

 

I don't see this often, but from what I can remember,.....

  1. ...
  2. There really was a problem when building the EXE. This happens sometimes and might require clearing the application builder compiled objects cache (Tools>>Advanced), force compiling all the VIs (Ctrl+Shift+Run button on the top level VI) and/or restarting LV.

Cleaning the build usually works when that happens ( it was more common in earlier versions but I still habitually always clean my builds before rebuilding).  Just right-click the build spec and select clean build.  This forces the app builder to recreate the temporary source distribution and forgives many sins in the linker.

 

Of course, the better option is to write code without bugs the first time.


"Should be" isn't "Is" -Jay
Message 8 of 13
(1,741 Views)

Hi,

 

Thank you for your advices.  I have tried all the options in this thread and still not able to get this.  I even disable the part that is giving me the Handler error code, and still not able to run the executible.

alibaibai_1-1663007284631.png

 

0 Kudos
Message 9 of 13
(1,720 Views)

It could be a race condition and you were just lucky that it used to work.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 10 of 13
(1,708 Views)