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

VI Server or Code Generation Errors after Installing Desktop Execution Trace Toolkit 1.0

Primary Software: LabVIEW Toolkits>>Desktop Execution Trace Toolkit
Primary Software Version: 1.0
Primary Software Fixed Version: N/A
Secondary Software: TestStand, NI Requirements Gateway, Motion Assistant, Vision Assistant

Problem:
I installed LabVIEW Desktop Execution Trace Toolkit (DETT) 1.0 and noticed I was getting VI Server and Code Generation errors (details given below) in other non-LabVIEW NI Products

NI TestStand
Trying to load LabVIEW VIs in TestStand results in error -18002: VI Server Access Denied.




NI Requirements Gateway
Requirements Gateway analysis of LabVIEW files fail. When the document is selected, an error "LabVIEW: VI Server access denied." is shown.
 


NI Vision Assistant
LabVIEW code generation fails. Going to Tools»Create LabVIEW VI»specifying the target VI path»Finish results in an Incorrect VI Server Settings error



NI Motion Assistant

LabVIEW code generation fails. Going to Tools»Generate Code»LabVIEW Diagram results in the following Error



LabVIEW SignalExpress (includes LabVIEW code generation for other Assistants from within SignalExpress: Control Design Assistant, DAQ Assistant, Sound & Vibration Assistant, etc.)**
LabVIEW code generation fails without any warnings or errors. Going to Tools » Generate Code » LabVIEW Diagram results in a "Generating LabVIEW Diagram" progress bar, which closes after sometime without generating any code or an error.

**Exception: When an Assistant is used in LabVIEW, you will not be affected by this bug; hence code generation in LabVIEW will occur as expected.

Solution:
When the LabVIEW VI Server:Exported VIs list is the default of * (all VIs), the LabVIEW Desktop Execution Trace Toolkit (DETT) 1.0 installer creates an entry in the LabVIEW.ini file for the LabVIEW VI Server:Exported VIs list with only HighlightObject By Context-VI-UID.vi exported. This affects other programs such as TestStand, SignalExpress, Requirements Gateway, etc., which require certain VIs to be exported to work correctly with LabVIEW. The bug exists if you've installed DETT 1.0 through any one of the following distributions
  • LabVIEW 8.6.1 Platform DVD
  • NI Developer Suite Q1 2009 DVD
  • LabVIEW Desktop Execution Trace Toolkit 1.0 CD

To Fix The Problem:
  • Open LabVIEW
  • Go to Tools » Options
  • Select the VI Server: Exported VIs Category
  • Replace HighlightObject By Context-VI-UID.vi with * in the Allow Access List
  • Select OK to save and exit the Options Dialog Box

NOTE:
You will not run into any of the above mentioned VI Server or Code Generation issues in the following cases; 

 

  1. If you were using LabVIEW 8.6 (or 8.6.1) with a custom set of Exported VIs (not *), before installing DETT 1.0; then the installer will not replace any of the existing VIs in the list and it will append HighlightObject by Context-VI-UID.vi to the custom list.
    OR
  2. If you installed the updated DETT 1.0 installer available through ni.com.


Related Links:
LabVIEW 8.6 Help: VI Server: Exported VIs Page (Options Dialog Box)
KnowledgeBase 4V58878Z: -18002 Errors in TestStand
KnowledgeBase 490IRR9S: LabVIEW SignalExpress Code Generation Fails When Multiple Versions of LabVIEW Are Installed
Evaluation Software

Attachments:
Motion_Assistant_Error.jpgRequirements_Gateway_Error.png TestStand_Error.png
Vision_Assistant_Error.png




Report Date: 02/05/2009
Last Updated: 04/13/2009
Document ID: 4U49Q33Y

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