LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

-18001: An error occured accessing the LabVIEW ActiveX automation server

Hi,

I'm currently investigating a problem with a Teststand 2.0 sequence. The
sequence makes use of VI's that call methods of an ActiveX. After a few
successful loops through the test sequence the error "-18001: An error
occured accessing the LabVIEW (6.1) ActiveX automation server" is brought up
in Teststand. I think that somehow the ActiveX automation server is dying
during the execution of the sequence but I don't know where to start
searching...The problem does not seem to lie within the ActiveX istself, but
I'm not sure. Using the same ActiveX within a Visual Basic Application and
performing the same commands several times does not produce a failure. Has
anybody an idea what could be the problem
?

Thanks, Sven.
0 Kudos
Message 1 of 5
(4,542 Views)
There is actually a few Knowledge Bases on NI's website which deals with this exact issue. You will probably want to start there.
1. -18001 Errors When Using TestStand and LabVIEW
2. Why do I Get Error -18001 or -18002 When I Run the Assemble Test VIs for Run-Time Distribution Tool?
J.R. Allen
Message 2 of 5
(4,542 Views)
Thanks, but I already know these entries from the Knowledge Base. I found no
help in there and my error text is also not mentioned there.


JRA schrieb in im Newsbeitrag:
506500000005000000E9D70000-1042324653000@exchange.ni.com...
> There is actually a few Knowledge Bases on NI's website which deals
> with this exact issue. You will probably want to start there.
> 1. >
"http://digital.ni.com/public.nsf/websearch/55574CB4E0F326DF862567FD0077E303
?OpenDocument">-18001
> ...

> 2. >
"http://digital.ni.com/public.nsf/websearch/D8690EC8044C7B3586256C63005D4D84
?OpenDocument">Why
> do ...

0 Kudos
Message 3 of 5
(4,542 Views)
Sven,

just recovered from a problem that resulted in the very same error msg in TS3. Problem was caused by LV7 dying when returning rather complex TypeDef'd data to TS. Solution was to disconnect LV's typedefs. Weird! See http://exchange.ni.com/servlet/Redirect?id=10048096 !
Maybe in your case this is caused by some accumulation of ressources consumption (memory leak?) or delays?
Message 4 of 5
(4,542 Views)

Hi,   I use the Labview 8.2.1 and Teststand 4.0 for my testing. I run the same sub sequence for the 4 different forcing conditions. what i could find is first two or three iterations work fine and later we get the above mentioned error. Do anyone have a solution for it.

0 Kudos
Message 5 of 5
(3,861 Views)