Error launching the 'LabVIEW.Application [Error Code: -18001]

[OnlyOne]

Hello,
i have a TS 3.4 Sequence wit LabView 8.21-Teststeps.
The Sequence is called from an Labview-OperatorInterface.
In a step which run before 100 times without problems i suddenly get the error-message:

ErrorMessage: Error executing substep 'Run'.Unable to launch the 'LabVIEW.Application' ActiveX automation server [Error Code: -18001]

After a restart of al NI-Software everything is working normal again.
What does this error mean and what should i do with it?
Should i ignore the error and try to execute the step again or does this mean tht the ActiveX-Server was lost forever?
How can this problem happen?

Thanks for your help

[RayFarmer]

Hi,

Its difficult to know what the problems is that causes this. I am guessing you are using either the RTE or Runtime Server rather than LabVIEW Developement system.

Once you get this error you can't ignore it and hope that repeating the step will regain the link to the server. (well that's what I've noticed).

There is a patch for labview 8.2.1 http://joule.ni.com/nidu/cds/view/p/id/906/lang/en that you might what to try.

And there is TS version 4.0.

Regards

Ray Farmer

[OnlyOne]

The OperatorInterface is a compiled EXE-file. The OperatorInterface then opens TestStand which runs a sequence with the Labview-Steps.
The Steps are normal Vis. But they all have an ActiveX-part where they get variables from the TestStand-Step into Labview for the input-Parameters. Parameters are passed withe the TestStand "SquenceContext".

Labview-Version is 8.2.1
I can´t uprade to 4.0 cause its a customer-computer.

But i try to repeat the activeX-thing inside Labview once there is an error. Lets see what happens.

(Problem is only that i cant force the problem to happen.)

[RayFarmer]

Does the error happen in the same place or at any step?

One thing you did mention was whether your labVIEW adapter is configured to use the LabVIEW developement system, the RTE or Runtime Server ( either the Operator Interface ActiveX server or the standalone Runtime Server)

(Even if you are using the Operator Interface, the labVIEW adaptor will still use LabVIEW developement system as the activeX server if set to the default setting.)

Regards

Ray

[OnlyOne]

>Does the error happen in the same place or at any step?

The error did only occur one time up to now.

>One thing you did mention was whether your labVIEW adapter is configured to use the LabVIEW developement system, the RTE or Runtime Server ( either the Operator Interface >ActiveX server or the standalone Runtime Server)
>(Even if you are using the Operator Interface, the labVIEW adaptor will still use LabVIEW developement system as the activeX server if set to the default setting.)

Hmm, i did not change anything in the adapter-settings for labview.
What is the better configuration?

[RayFarmer]

During your development then you would want to beable to debug you labVIEW VI's therefore you would use the LabVIEW Development setting.

When you deploy to your target system and release it to the custom, usually you dont have any developement systems (TestStand, LabVIEW) to stop people changing the code. Therefore you would have the adaptor set to use either the RTE or Runtime Server. Probably the Operator Interface as the ActiveX Server.

Regards

Ray

[RobBoyer]

For what it's worth, I've had similar intermittent problems with the LabVIEW runtime crashing and receiving the -18001 error code.  (In fairness, the version of LabVIEW I was running was 7.0, so this may not have anything to do with it.)

In any case, the problem ultimately turned out to be an intermittent problem with the LabVIEW runtime engine - it didn't work correctly on dual-core machines under certain circumstances.  (I guess there must of been some kind of re-entrancy issue that only surfaced when the added parallelism of multiple CPUs was introduced.)  In any case, setting the affinity of the LabVIEW process to run only on one CPU has fixed the problem for me.  It may be worth a try if NI ultimately leaves you high and dry on this.

Good luck.

[JettR]

Hey OnlyOne,

Have you seen the -18001 error again?  If so, I would be curious to see which adapter type you are using as well.  I look forward to hearing from you!

[RobBoyer]

Hey OnlyOne,

Out of curiousity, did you ever resolve this?  I'm curious because my team may eventually need to upgrade our version of LabVIEW. 

Take care, -Rob

[OnlyOne]

The error did not occur again and nothing is changed yet.
STill on LV 8.2.1 and TS 3.5 without the patch and the same adapter.