errorcode -17501

[Roger_C]

Hi,

When I stop the exection of my Operator Interface (based on the Simple OI) by clicking on the exit button following by a restart (run) of the code and than a "start execution"  of a sequencefile I get an " Unexpected Operating System Error" [Error Code: -17501] . When I close the main Operator Interface vi and reopen it I can run the sequence again without a problem ... Stopping the application, run the application again, start a sequence ... error -17501 again. The "exit callback - LabVIEW event structure" construction (For exiting the application, as purposed in the Simple OI) seems to work correctly ... 

I'm using LabVIEW 2010 for the operator Interface and TestStand 2010 on a Windows XP operating system.

I haven't found any information about this error ... perhaps someone can point me in the right direction?

Thanks,

Roger

[Captain_Jack]

Hi Roger,

In my experience, this error tends to occur when a memory buffer gets overrun. We've seen this when exceeding string buffers, or exceeding the bounds of other memory constructs. I'm not well versed in LabVIEW, so I'll let someone else handle the exit callback structure. It almost sound's like there's something running in the background that isn't getting shut down between launches of the Simple OI.

-Jack

[RayFarmer]

Have you tried the default OI and do you still get the same problem?

[Roger_C]

Hi Jack and Ray,

Both thanks for your reactions. 

Before I post this question I already looked in the code if I didn't mis any close/destroy of any reference/object. I than couldn't find anything but I have to look closer again because (Good suggestion Ray 😉 the original simple OI doesn't show this problem on my system. It does when I first run my operator interface, press the stop button on the frontpanel  (which uses the exit callback mechanisme) and than run the Simple OI ... so it looks like an object which isn't destroyed on exit ... I'm going to investigate this further.

Thanks,

Roger

[Captain_Jack]

Hi Roger,

One other thing that I should have mentioned - the root cause of the -17501 error might be somewhere other than the exit callback; The pernicious thing about -17501 errors is that they can be intermittent, and you only find them when you try to use something that was resident in the memory location that got overwritten.

Good luck finding the problem!

-Jack