-18000 Errors

[WayneR1]

I am using TestStand 2014 and Labview 2015 both 64bit, I am running TestStand in batch mode with 8 sockets. I am randomly getting -18000 errors, it could happen after 10minutes or 2 - 3hours and i can not see if a specific vi is the problem.

Are there any settings in either Labview or TestStand that can help track down this problem.

[Norbert_B]

Can you attach a screenshot of the error message popup?

Error -18000 is a user defined error so it is important to know what the error description states.

Norbert

[WayneR1]

Further to my -18001 error i thought i would try and get my project running using the Labview Runtime Engine. The first run is OK but as soon as i try a capture on the PicoScope i get the following error.

If i run using the Development Environment 99% of the time i get no problems then occasionally the -18001 error.

####
#Date: 11 Nov 2016 12:04:32
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: SeqEdit
#Version: 15.0.1f2 64-bit
#AppKind: AppLib
#AppModDate:
#LabVIEW Base Address: 0x0000000030000000

InitExecSystem() call to GetCurrProcessNumProcessors() reports: 4 processors
InitExecSystem() call to GetNumProcessors()            reports: 4 processors
InitExecSystem()                                      will use: 4 processors
starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3561710676.24485830, (12:04:36.244858265 2016:11:11)]
starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3561710676.24485830, (12:04:36.244858265 2016:11:11)]
starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3561710676.24485830, (12:04:36.244858265 2016:11:11)]
starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3561710676.24485830, (12:04:36.244858265 2016:11:11)]
starting LabVIEW Execution System 306708506 Thread 1 , capacity: 4 at [3561710679.01513530, (12:04:39.015135289 2016:11:11)]
starting LabVIEW Execution System 306708506 Thread 2 , capacity: 4 at [3561710679.01513530, (12:04:39.015135289 2016:11:11)]
starting LabVIEW Execution System 306708506 Thread 3 , capacity: 4 at [3561710679.01513530, (12:04:39.015135289 2016:11:11)]
starting LabVIEW Execution System 306708507 Thread 1 , capacity: 4 at [3561710682.02443600, (12:04:42.024435997 2016:11:11)]
starting LabVIEW Execution System 306708507 Thread 2 , capacity: 4 at [3561710682.02443600, (12:04:42.024435997 2016:11:11)]
starting LabVIEW Execution System 306708507 Thread 3 , capacity: 4 at [3561710682.02443600, (12:04:42.024435997 2016:11:11)]

<DEBUG_OUTPUT>
11/11/2016 12:04:45.468
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 58ebb209-2d15-4604-9811-26a17643b3aa
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x000000000427120E - nierInterface <unknown> + 0
0x0000000004276422 - nierInterface <unknown> + 0
0x000000000427681F - nierInterface <unknown> + 0
0x00000000779EBC10 - KERNEL32 <unknown> + 0
0x0000000077AF0108 - ntdll <unknown> + 0
0x0000000077A87958 - ntdll <unknown> + 0
0x0000000077A9812D - ntdll <unknown> + 0
0x0000000077A8855F - ntdll <unknown> + 0
0x0000000077ABBCB8 - ntdll <unknown> + 0
0x000007FE00000000 - <unknown> <unknown> + 0
0x000007FEDB38A94F - <unknown> <unknown> + 0
0x000000000FF6A940 - <unknown> <unknown> + 0

[WireWeaver]

If LabVIEW crashes while using the development adapter, TestStand loses the connection to the LV ActiveX server and throws -18001. In your last post it looks like LabVIEW is crashing due to an access violation. I'd recommend:

1. Narrow down what step LV is crashing on - it's probably either the step that throws Error 18001, or the last LV code module before that.
2. Take a look into that VI and try to find the cause
   1. Are you using any drivers or DLL calls in that VI?

It looks like that log generated a crash dump "minidump id: 58ebb209-2d15-4604-9811-26a17643b3aa". Can you attach that?

-Trent

[WireWeaver]

Just realized I should probably point out where LabVIEW stores crash dumps.

-Trent