LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview 2013 executable works only on develoment machine?

Solved!
Go to solution

Yes, I included VISA drivers

0 Kudos
Message 11 of 17
(1,303 Views)

I ran my executable on the target machine remotely in Debug mode and saw that I had an NI-XNET driver error -1074384895 occurring in the NI-XNET create session VI.  I don't get this driver error when I run the exe or original code on the development machine. Does anyone have any suggestions or inputs?

 

Thanks

0 Kudos
Message 12 of 17
(1,278 Views)

Hi SoIPS,

 

What does the error number mean?

 

- missing hardware?

- missing XNet driver?

- missing CAN database?

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 13 of 17
(1,276 Views)

The error means this:

 

NI-XNET:  (Hex 0xBFF63001) An internal error occurred in the NI-XNET driver. Please contact National Instruments and provide the information from the file %ALLUSERSPROFILE%\Application Data\National Instruments\NI-XNET\niXntErr.log’ (Windows XP file location). On Windows Vista or Windows 7, the file can be found at %ProgramData%\National Instruments\NI-XNET\niXntErr.log. Please note that this location may be hidden on your computer.

0 Kudos
Message 14 of 17
(1,264 Views)

Hi all,

 

I'm currently getting error -1073807343 while running my executable remotely in debug mode. I made sure I created a VISA resource for my device on the target machine and downloaded the latest NI VISA driver and I'm still getting that same error. This seems to be what is preventing my .exe application from running. Any suggestions on how to fix this?

 

Thanks

0 Kudos
Message 15 of 17
(1,240 Views)

@SolPS wrote:

Hi all,

 

I'm currently getting error -1073807343 while running my executable remotely in debug mode. I made sure I created a VISA resource for my device on the target machine and downloaded the latest NI VISA driver and I'm still getting that same error. This seems to be what is preventing my .exe application from running. Any suggestions on how to fix this?

 

Thanks


At his point, I think you are going to have to share some code.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 16 of 17
(1,234 Views)
Solution
Accepted by SolPS

Hi all,

 

Just to provide an update. I was able to finally build a working executable only by building an installer. I had to insert my LabVIEW Device driver cd in my computer and allowing automatc install under additional installer section.

 

Thanks

0 Kudos
Message 17 of 17
(1,205 Views)