08-06-2025 02:59 PM
I posted this a couple of hours ago, and it doesn't show up, so I'm trying again...
XNET Create Session (Generic) returns error -1074384895. "Explain Error" gives the following:
NI-XNET: (Hex 0xBFF63001) An internal error occurred in the NI-XNET driver. Please contact National Instruments and provide the information from the file %LOCALAPPDATA%\National Instruments\NI-XNET\log\niXntErr.log. On Windows XP, the file can be found at %USERPROFILE%\Local Settings\Application Data\National Instruments\NI-XNET\log\niXntErr.log. Please note that this location may be hidden on your computer.
The contents of the log file in question is:
Current Row: 0006 Max Num Rows: 001000
(1000) - Log Options: (Internal Errors, User Errors, Internal Warnings, User Warnings)
Date and Time Format YYYY-MM-DD HH:MM:SS (24-hour time)
NI-XNET 25.3.0f234
Row Date and Time Severity Type Component File Line Code (hex) Info (hex)
------------------------------------------------------------------------------------------------------------------------------
0001 2025-08-06 12:31:42 Error Internal 9 37 115 0x00000001 0xa4258073
0002 2025-08-06 12:33:15 Error Internal 1 40 2690 0x00000001 0x84288a82
0003 2025-08-06 12:33:17 Error Internal 1 40 2690 0x00000001 0x84288a82
0004 2025-08-06 12:33:18 Error Internal 1 40 2690 0x00000001 0x84288a82
0005 2025-08-06 12:34:02 Error Internal 9 37 115 0x00000001 0xa4258073
0006 2025-08-06 12:34:08 Error Internal 9 37 115 0x00000001 0xa4258073
The details:
08-06-2025 12:21 PM
XNET Create Session (Generic).vi is giving me error -1074384895.
"Explain error" gives the following text:
NI-XNET: (Hex 0xBFF63001) An internal error occurred in the NI-XNET driver. Please contact National Instruments and provide the information from the file %LOCALAPPDATA%\National Instruments\NI-XNET\log\niXntErr.log. On Windows XP, the file can be found at %USERPROFILE%\Local Settings\Application Data\National Instruments\NI-XNET\log\niXntErr.log. Please note that this location may be hidden on your computer.
The details:
Current Row: 0006 Max Num Rows: 001000
(1000) - Log Options: (Internal Errors, User Errors, Internal Warnings, User Warnings)
Date and Time Format YYYY-MM-DD HH:MM:SS (24-hour time)
NI-XNET 25.3.0f234
Row Date and Time Severity Type Component File Line Code (hex) Info (hex)
------------------------------------------------------------------------------------------------------------------------------
0001 2025-08-06 12:31:42 Error Internal 9 37 115 0x00000001 0xa4258073
0002 2025-08-06 12:33:15 Error Internal 1 40 2690 0x00000001 0x84288a82
0003 2025-08-06 12:33:17 Error Internal 1 40 2690 0x00000001 0x84288a82
0004 2025-08-06 12:33:18 Error Internal 1 40 2690 0x00000001 0x84288a82
0005 2025-08-06 12:34:02 Error Internal 9 37 115 0x00000001 0xa4258073
0006 2025-08-06 12:34:08 Error Internal 9 37 115 0x00000001 0xa4258073
08-06-2025 08:07 PM
Duplicated with XNET Create Session (Generic) returns error -1074384895
08-06-2025 08:11 PM
The test application was compiled using LabVIEW 2014 SP2, version 14.0.1f11 (32-bit)
NI does not test and validate unsupported software version and cannot guarantee that it will work correctly. What you are encountering is most likely a compatibility issue.
08-12-2025 07:08 AM
I just tried it again after building it with LabVIEW 2025Q3 (32-bit) 25.3.2f2. The behavior is identical to the LabVIEW 2014 build.
The first time I run it after powerup, I get error -1074384895.
If I run it again it works fine.
08-12-2025 07:46 PM
In that case, see Error -1074384758 or -1074384895 using NI-XNET Create Session
You might need to add a delay between multiple sessions creation.
08-13-2025 01:27 AM
>The error only occurs the first time the application is run after the computer is powered up, and then only about half the time.
So, after, it's running?
I do not use PXI, but cDAQ crates. If a connection to a cDAQ crate is lost (network, power), I get such errors as well, and forever. When I look into MAX, I can see the error as red dot at my interface as well, the quick fix there is to either run a self-test on the crate, or release the reservation and re-gain it. The red dot varnishes, and after that, I can start a session.
I don't know if this applies to PXI as well, and it's kind of different, since your problem self-heals by restarting your application, if I understand correctly. Nevertheless, maybe you can find out something with MAX.