LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

executable

Hello,

I was wondering if you could give me some insight to a problem that I am having. I have an executable that runs fine on one machine but produces errors on a different machine. The errors that I receive are in the
attachments. It is looking for some external sub-routines but this is strange since an executable should not need this. Any thoughts would be appreciated.

Thanks
Kyle
Download All
0 Kudos
Message 1 of 13
(4,657 Views)
An executable doesn't necessarily contain all files necessary to run. It might require drivers for DAQ or GPIB hardware or in your case, the lvanlys.dll. When you created your exe, a data folder was created that had the DLL in it. Copy the data folder or create an installer. The installer will automatically include the Data folder and the LabVIEW run-time engine.
0 Kudos
Message 2 of 13
(4,656 Views)
Doesn't that dll come with NI-MAX?

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 3 of 13
(4,656 Views)
I think it comes with the LV Analysis package.
0 Kudos
Message 4 of 13
(4,656 Views)
Yes that is probably correct.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 5 of 13
(4,656 Views)
I'm 90% sure you missed some vi while you're building your exe. I met the same problem previously, and solved it by checking missed vis. What I suggest is that you re-check the building process, make sure all the vis are in correct position, and don't add them into resource file if a vi is dynamic.

Hope this will help some.
Inhaler
0 Kudos
Message 6 of 13
(4,656 Views)
I have an executable (builded with LabVIEW 7.1) that runs fine on the machine where it has been builded, but produces errors on a different machine with same environment. The errors those I receive are given in the below:

"An error occured loading VI
'imgCopyAreaWithOccur.vi'
LabVIEW load error Code 21: An
external subroutine required for
execution could not found."

and then while clicking "OK"

"Missing SubVI
imgCopyWithOccur.vi in VI
IMAG Copy Acuired Buffer.vi"

Anybody please let me know, if possible, what is wrong.
0 Kudos
Message 7 of 13
(4,489 Views)

Hi Basanta,

As Dennis mentioned above, the executable you build does not always include all the files you need to run the application.  It appears from the error, you are using some image acquisition functions.  Make sure you have the IMAQ driver and any other appropriate driver installed on the destination system.


Have a great day,


Ecleamus Ricks, Jr.
National Instruments
Applications Engineer

0 Kudos
Message 8 of 13
(4,462 Views)


@Ecleamus R wrote:

Hi Basanta,







As Dennis mentioned above, the executable you build does not
always include all the files you need to run the application.  It appears from the error, you are using some
image acquisition functions.  Make sure
you have the IMAQ driver and any other appropriate driver installed on the
destination system.












Have a great day,


Ecleamus Ricks, Jr.
National Instruments
Applications Engineer






Dear Ecleamus
Thanks for your reply.
I am trying to run the executable in another system where also I have installed all the necessary NI hardwares and softwares and the main LabVIEW program (from where I have builded the executable) is running in both the computers. But unfortunately, the executable is not working in the other system.
Another thing I also want to know: while building the Application, all the VIs supposed to be closed. But it is asking for IMAQ COPY.VI to save the Sufis, though I have not even opened it. Please let me know what to do.
Regards,
Basanta
0 Kudos
Message 9 of 13
(4,455 Views)
Hi Basanta,

Refer to this knowledgebase and let me know if it helps.

Ecleamus Ricks, Jr.
National Instruments
Applications Engineer
0 Kudos
Message 10 of 13
(4,430 Views)