TestStand 3.0 Program Error# -17001: "Illegal attempt to add multiple releasable references to the same object"

[LuI]

Hi,

I keep getting this error message (attached) and it seems to increase its frequency.
Over all I get the impression that TS gets instable:
* this error
* Sometimes some values passed to a called step via reference do change their value (from, say, 0 or 1 to -1).
This may or may not have to do with calling a LabVIEW VI that itself calls a (wrapper-)DLL that in turn calls other DLLs. (Used to keep 'dangerous' functions out of reach for customers, but provide them the necessary (basic) DLLs.)
A test VI playing with this construction does operate flawlessly.
My system: PC PII/450 Mhz, 384 MB RAM, W2k German SP2, LabVIEW 7.1 English, TestStand 3.0
English (with newer ß installed, but not used in this project), lots of HW, IVI, VISA etc.

So here are my Qs:
1. Anyone having a clue as to what causes this error message?
2. Is there any advantage in passing scalars to called steps by reference? Or may I also use 'PassByValue'?
3. Can a construction like this TS>LV>WrapperDLL>DLL cause such problems 'just for fun'? I do not get any access violations or exceptions or so. Just sometimes with interrupted tests I might leave some handles open.

TIA and Greetings from Germany!
--
Uwe Frenz

[Scott_Richardson]

Uwe -
The error that you are seeing is an internal warning that something is odd about the references to the model file in our sequence file cache. We are trying to update the menus for model entry points. I have never seen a customer raise this error before.

Questions:
1) What do you do right before the error occurs? Do you bring to front a client sequence file? Was the model file recently opened?
2) Does the problem occur if the model file is not open in the sequence editor?
3) Do any of the client sequence files have sequence call steps that call back into the model? If yes, which model sequences?
4) Do you have any code that calls LoadModule using the API?
5) Are you using more than one model when this happens?
6) Do you have any odd exc
eptions or errors that the sequence editor displays before this occurs?
Scott Richardson (NI)

[abachler]

I have had this issue several times.  It appears that LabView does not properly load DLL's that then load other DLL's.  My suggestion is to either wrap all the functionality within one DLL and hide the 'dangerous' functions by not exporting them, or alias the dangerous functions.  my favorite aliasing method is -

#define MyFunc DO_NOT_USE_aaaaaaa

#define MyFunc2 DO_NOT_USE_aaaaaab

etc.

Message Edited by abachler on 12-26-2007 02:10 PM