LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

executable won't run on target PC

Hi

 

I have written an application to control a 'Data Translation' PCI data acquisition card (DT302) using LabVIEW (8.6.1). I have used Data Translations 'LVLink' VIs in the application. It works perfectly on the development PC as a VI and as an executable.

The problem arises when I try to run the executable on a target PC. The program fails to recognize the DT302 card. I believe I have the necessary extra files/software installed:

 

  • LabVIEW RTE (8.6.1)
  • DT Open Layers for .NET Class Library
  • LVLink2.dll
  • Driver for DT302 card

 

I know the card is installed correctly as it can be recognized by other (non Labview) programs. I think I may require an additional file or .dll but I'm not sure.

 

Any help would be greatly appreciated

 

Thanks

Stuart

0 Kudos
Message 1 of 9
(3,042 Views)

Hi Stuart, 

 

If you can tell us which dlls are dependencies of the project, we can probably tell you what you need to include in your installer. You may be missing something like VISA runtime if the VISA protocol is being used.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 2 of 9
(3,025 Views)

Thanks for your help.

 

The dlls shown as dependencies are:

 

  • advapi32.dll
  • Kernel32.dll
0 Kudos
Message 3 of 9
(3,022 Views)

Stu-Qub wrote:

Thanks for your help.

 

The dlls shown as dependencies are:

 

  • advapi32.dll
  • Kernel32.dll

 

A quick search on the forum came up with advapi32.dll as a windows dll, and I know Kernel32.dll is a windows dll.

 

Unless advapi32.dll is not on the destination PC, I have no suggestions, this isn't as simple as it might have been.

You could try including advapi32.dll in the installer and see if that fixes the problem, if you are not installing to a windows machine of the same OS, that may be your problem.

 

Now I really am out of ideas for now. - this looks like a job for Rolf K or one of the other gurus.

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 4 of 9
(2,994 Views)
Both dlls are on the target PC (both computers running XP). I really am stumped.
0 Kudos
Message 5 of 9
(2,985 Views)

you haven't done something silly in the exe - like tick the box that requires the development environment on the PC when the exe is deployed have you?

 

James

CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 6 of 9
(2,979 Views)
I think that is only an option if you're building an installer - I have only created an application (.exe)
0 Kudos
Message 7 of 9
(2,975 Views)
Ok - an update. I had a spare PC with LabVIEW 8.6.1 installed. I uninstalled LabVIEW, installed the files mentioned above, tried my application and it works. However, it still doesn't work on a 'blank' computer. Anybody have any idea why this is??
0 Kudos
Message 8 of 9
(2,940 Views)

Suspect this is due to a relative path call to the dlls being created by the calling VIs when you compile.

It may be due to a version difference in the files mentioned on your PC and the ones used on the "blank PC".

 

Recommend you make an installer which includes the dlls and re-installs them to the PC - it is possible that the NI calls to the dlls are modifying them or the registry.

 

James

 

Edit:

Compare the Path between your LabVIEW PC and your blank one

 

Also check the correct params are inserted in the path for any calls to functions external to LabVIEW, this could be causing breaks if %PATH% has not got the required files in it.

Message Edited by James W on 05-18-2010 04:31 PM
CLD; LabVIEW since 8.0, Currently have LabVIEW 2015 SP1, 2018SP1 & 2020 installed
0 Kudos
Message 9 of 9
(2,928 Views)