Error -18001 or -18002 in TestStand

Updated Oct 31, 2018

Reported In

Software

  • TestStand 2016
  • LabVIEW Full
  • TestStand 2014 SP1
  • LabVIEW Professional
  • LabVIEW Base

Issue Details

I am getting a -18001 or -18002 error in TestStand. What can I do to resolve this? 

Solution

There are several sources for this error code as explained below: 

Error occurred accessing LV ActiveX Automation Server

The LabVIEW process is closed after TestStand has started an execution
 LabVIEW can be closed manually by the user, programmatically with the Quit LabVIEW VI, or automatically by the Operating System in the event of a LabVIEW crash. To avoid this, make sure that LabVIEW is running and not stopped in the background of your test program. If LabVIEW is crashing, try to replicate the crash outside of the TestStand environment.

TestStand attempts to connect to a running instance of LabVIEW launched with different user permissions TestStand
In this case, close the existing instance of LabVIEW and allow TestStand to launch a new instance.

TestStand is attempting to access a version of LabVIEW that is not present on your machine
This requires Changing the Active Version in the TestStand LabVIEW Adapter, or using the LabVIEW Run-Time Engine.

The ActiveX Automation Server is not correctly registered
Run the TestStand Version Selector and select the make active button.

Server Access Denied

Error: LabVIEW VI Server Access Denied when opening LabVIEW VI 

This problem may be due to the VIs exported by LabVIEW. To change this option: 
  1. Open either a new or existing VI in LabVIEW.
  2. Select Tools>>Options from the LabVIEW menu bar. 
  3. Select VI Server: Exported VIs from the list box at the top of the dialog. This displays a list of VIs that are exported by LabVIEW.
  4. Enter a * in the exported VIs field so that you expose all VIs. Then select VI Server: Browser Access (VI Server: User Access if using LabVIEW 8.x or later) from the list box and make sure that you have given permission to * (everyone), specific domains or IP addresses.

Unable to Launch the 'LabVIEW.Application (or other name of LabVIEW Server)' ActiveX Automation Server First Cause: 

TestStand is trying to access a version of LabVIEW that is not present on your machine
This requires Changing the Active Version in the TestStand LabVIEW Adapter, or using the LabVIEW Run-Time Engine.

TestStand is trying to access a version of LabVIEW that is not activated
Open NI License Manager and make sure that LabVIEW is activated. If not, launch LabVIEW and activate it according to the help.
 
Settings are not configured to allow the server to be launched and accessed through ActiveX automation
If you have selected 'Other Executable' in the LabVIEW Adapter Configuration, you must make sure the server is registered and your Distributed COM (DCOM) settings are configured to allow the server to be launched and accessed through ActiveX automation. If you have questions about this, please contact NI Support.

WAS THIS ARTICLE HELPFUL?

Not Helpful