Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
1 rating:
 1 out of 5     Rate this Document

Cannot Launch LabVIEW 8.2.1 Via ActiveX After Installing LabVIEW 8.5 or Later on Windows Vista.

Primary Software: LabVIEW Development Systems>>LabVIEW Professional Development System
Primary Software Version: 8.5
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Signal Express, TestStand

Problem:
Previously, using ActiveX to launch LabVIEW would open the version of LabVIEW that was last used. Certain NI products, like LabVIEW SignalExpress, Sound and Vibration Assistant, and TestStand, use this feature for things like code generation and VI automation. When LabVIEW 8.5 is installed on Windows Vista, using ActiveX to launch LabVIEW always launches LabVIEW 8.5. This causes errors in my program, code generation and/or VI automation.  What are my options for working around this behavior?

Solution:
LabVIEW SignalExpress and Sound and Vibration Assistant Code Generation Specific Workaround:

If you have previously installed LabVIEW 8.2.1 on Windows Vista along with LabVIEW SignalExpress and/or the Sound and Vibration Assistant and then installed LabVIEW 8.5, this behavior will affect you when you try to do code generation.  This is because the code generation needs to launch LabVIEW 8.2.1, where the code generation VIs were originally installed. However, due to the above described behavior, LabVIEW 8.5 will be launched instead. If you want to work in LabVIEW 8.2.1, use the general workaround listed below.  If you want to work in LabVIEW 8.5, do the following.

  1. Uninstall LabVIEW SignalExpress (if applicable).
  2. Uninstall Sound and Vibration Toolkit or Measurement Suite (if applicable). 
  3. Reinstall LabVIEW SignalExpress and/or Sound and Vibration Toolkit or Measurement Suite to the LabVIEW 8.5 directory.
This specific workaround will fix the code generation issue as the needed VIs will now exist for LabVIEW 8.5. The general workaround can also be implemented.

TestStand Specific Workaround:

If LabVIEW is already open when the TestStand Engine is launched, calling the LabVIEW ActiveX server will use the opened instance of LabVIEW.
  1. While TestStand is closed, launch the desired version of LabVIEW.
  2. Launch TestStand.
The general workaround can also be implemented for a more permanent solution.

General Workaround:

If you know what version of LabVIEW you want to control, you can do the following.

  1. Login as an administrator.
  2. Select Start and type Cmd into the search field.
  3. Run the desired version of LabVIEW from the command line with /RegServer as the parameter.  For example, if you want to use LabVIEW 8.2.1, you would enter the full path to the correct LabVIEW.exe surrounded by quotes and followed by /RegServer. LabVIEW will not launch visibly, but it will register itself.

This general workaround will make the specified version of LabVIEW launch when called through ActiveX.



Related Links:

Attachments:





Report Date: 07/18/2007
Last Updated: 03/12/2008
Document ID: 4BAC1SUK

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit