Archived: TestStand 2012 & 2012 SP1 Known Issues By Date

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Panoramica

This document contains the TestStand known issues that were discovered before and since the release of TestStand 2012 & 2012 SP1. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

 

Document Organization:

The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by date.

Known Issues by Category
For those who wish to locate issues by their category, we have also published another version of the known issues table organized by the category of issue, and sorted by the date the issue was added to the document (not necessarily the date the issue was reported to NI). This table is recommended for use in helping determine if an issue has been reported to us, and is also recommended for users wanting to skim the document to learn of potential issues they may face with TestStand 2012 & 2012 SP1 during development. If an issue has multiple categories, it will appear multiple times in this document.

Contacting NI

Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.

If you have feedback on this specific document, please contact NI on this NI Developer Zone post.

Known Issues by Date

The following items are known issues in TestStand 2012 & 2012 SP1 sorted by Date.

.NET Adapter
139737 Cannot create or edit code of a struct using the .NET Adapter
354252 An error can occur when you simultaneously modify the invocations of multiple .NET code modules
356096 An unhandled .NET error can occur when you use the /quit command-line flag to close TestStand
356700 Closing Microsoft Visual Studio after you debug .NET code from TestStand prevents the Visual Studio process from exiting
202206 Error -17500 occurs when you execute .NET code modules that deserialize types
402888 When you access a .NET property in a child class that overrides set or get, only the override is available
406396 Additional Results setting is not respected for elements of arrays within a .NET adapter step
ActiveX/COM Adapter
44060 4GQ7M6JO Cannot specify an underlying data type when passing a variant parameter using the ActiveX/COM Adapter or API in expressions
C/C++ DLL Adapter
157130 Verify Prototype option for the LabWindows/CVI and C/C++ DLL Adapters incorrectly includes the expression value in an array parameter prototype
255602 C/C++ DLL Adapter Create and Edit Code features return errors for functions that specify an array parameter
297248 The Log option in the Parameters Table for complex number parameters in C/C++ DLL steps can behave erratically
Database
359126 Memory usage can increase when you use the SQL Server Stored Proc schema with the Microsoft OLE DB Provider for SQL Server
357315 An error can occur when you log binary data to an Oracle database
375181 TestStand reports multiple differences when validating the default database schemas
390817 Filtering results fails for certain steps when using on-the-fly database logging
File Differ
299368 The TestStand File/Diff Merge application does not support diffing station global variables
IVI
408196 TestStand does not report an error in some cases when importing an unsupported IVI configuration
Installation
164423 Uninstalling TestStand 2.0 from a computer with TestStand 4.x installed removes NI Session Manager files.
164424 Installing IVI components from TestStand 2.0 after installing IVI components from TestStand 4.0 causes errors
172792 Uninstalling a TestStand deployment leaves the TestStand Engine and other additional components on the system
360674 Measurement & Automation Explorer can display incorrect installed versions after uninstalling TestStand 2012
361582 TestStand Version Selector incorrectly displays TestStand 2012 as an available version to activate after you uninstall TestStand 2012
LabVIEW
100053 Enumerations with the same name as a constant show as an error
101510 LabVIEW user interface reports object leaks on shutdown when using ActiveX Variants in ActiveX callbacks
125375 LabVIEW user interface freezes when you move splitter bars
125576 ExpressionEdit controls on LabVIEW front panels do not release keyboard focus
164429 LabVIEW User Interface executables that do not use TestStand UI Controls might hang when launched
164430 Calling a LabVIEW-built DLL from the user interface thread that create the TestStand engine might cause the application to hang
48357 3RFG3UM0 Cannot browse to a VI if the VI filename includes multibyte characters
49481 3Z4EURMF LabVIEW user interface beeps when using menu accelerator keys
49503 3ZCDRG77 Cannot use LabVIEW RTE to load a VI without saving the library
49856 41AHCIMF TestStand UI Controls do not process some key strokes in LabVIEW user interfaces
50897 46PA3DMF Help Topic menu item is disabled
51491 480JGC00 LabVIEW user interface appears hung when Property Leak Report dialog box displays behind application
51752 491GSRM0 VI breakpoint does not bring the VI window to front
158407 LabVIEW VI Server Exported VIs Setting Might Be Modified By Desktop Execution Trace Toolkit (DETT) 1.0
136507 You cannot toggle the Show VI Front Panel When Called option when the Run VI on Remote Computer option is enabled
148697 LabVIEW user interface might hang when using LabVIEW events
153518 Configuring the Formula Express VI in a TestStand step results in error tones
153853 Create VI button on the LabVIEW Module tab or the Edit LabVIEW VI Call dialog box does not create a VI in an LLB
158938 Cannot pass struct containing an array of structs into a DLL built with LabVIEW
160210 TestStand Deployment Utility might appear to hang when building if the LabVIEW Build Specifications dialog box is open
161523 Arrays passed from LabVIEW to TestStand are transposed
179186 Configuring a MessagePopup step as a Modal or Floating popup hangs subsequent LabVIEW steps for which you enabled the Show VI Front Panel When Called option
184366 Clicking the Create Custom Data Type button on the LabVIEW Module tab for a cluster that contains unknown types results in an error
188059 The LabVIEWModule.ExpressVIName property does not update to match the Express VI title when a different configuration changes the title
188119 TestStand is a 32-bit application and has limited support for LabVIEW 64-bit
190260 Calling and unloading an assembly more than once crashes TestStand if the assembly is built with LabVIEW 2009
191741 Clicking a LabVIEW step when TestStand is configured to use the LabVIEW 7.1.1 Run-Time Engine results in a Fatal Error: "LABVIEW.LIB could not locate "FResDir""
203643 Using TestStand to open a VI in a newer version of LabVIEW might leak a handle to the VI and prevent you from saving the VI
250131 LabVIEW code module front panels might update slowly when you use TestStand Start and End Modal Dialog VIs
253952 Passing LabVIEW Class references from step to step can crash LabVIEW
245655 Cannot call VIs from LabVIEW packed project libraries when the full path of the VI is longer than the maximum path length
254553 TestStand might become unresponsive while LabVIEW launches a prompt to save a VI
279822 TestStand appears to hang when LabVIEW search dialog box does not come to front when browsing for a VI that is missing subVIs
217346 Changing the size of a two-dimensional array in a LabVIEW code module can cause TestStand to crash
303452 Logging reference parameters in a LabVIEW step can cause an error
339699 TestStand cannot find VIs in a packed project library that specifies a file path that includes multibyte characters
253149 TestStand does not recognize changes to parameter settings in VI code modules
295614 Using a LabVIEW Project reference parameter in a LabVIEW code module can cause a run-time error
381085 Update VI Calls dialog box does not update code modules a Run VI Asynchronously step calls
390139 VIs in a LabVIEW project saved in the instr.lib directory fail to load when you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine
397556 Keyboard entry is ignored when editing a code module from User Interface built in LabVIEW
397930 Enabling the Logging option for subproperties of a dynamic data type parameter causes a TestStand crash
405883 Configuring a Run VI Asynchronously step in a TestStand User Interface can cause a system-level error
407194 LabVIEW Run-Time Engine number of threads setting is not respected
414363 TestStand User Interfaces Appear to Hang on Shutdown after Executing VI code modules in certain run-time engine versions
LabWindows/CVI
129574 Exiting an external instance of LabWindows/CVI on Windows Vista returns an error
129603 Executing LabWindows/CVI code modules in an external instance can leak memory
129627 Specifying an enumeration in a LabWindows/CVI module displays an incorrect name
36951 49GAQ5G0 Error when loading a TestStand 4.0 or later user interface when TestStand 3.5 is the active version
39257 48IACA9Q Reload Prototype button remains dimmed after building a DLL
171168 Installing LabWindows/CVI 9.0 Run-Time Engine can break TestStand 3.5 deployed components
213984 LabWindows/CVI Adapter does not properly recognize struct parameters when the function name begins with an uppercase letter
218283 Edit Code operation might navigate to the wrong location in a LabWindows/CVI source file
317729 Changes to enumeration values in LabWindows/CVI code modules are not reflected in steps that call the code modules
381096 Additional results logging setting for parameters in LabWindows/CVI or C/C++ DLL steps update incorrectly when you change how the parameter is passed
384718 Out-of-memory error occurs when using LabWindows/CVI-built TestStand User Interfaces on Microsoft Windows 8
Microsoft Visual Studio
109366 Calling a .NET module as an OnNewStep custom substep can error
127991 Receiving UI events in a .NET class that is not created in the UI thread might cause errors
164428 Clicking a TestStand UI Control in a custom .NET user control might cause Microsoft Visual Studio to crash
164431 Microsoft Visual Studio 2005 might crash when viewing a form in Design view after rebuilding a solution that uses TestStand UI controls
41350 4D6GIVRA Cannot edit Visual Basic .NET projects when a function contains an array parameter
48970 3WIAETIF TestStand ActiveX controls can become invisible in the Visual Studio designer
51176 478CHKRA Error when selecting a Button image
51321 47JBHTIA MFC-based TestStand User Interfaces can crash when used with the Microsoft Team Foundation Server SCC provider
52829 4CGDKAB8 .NET user interfaces shut down without prompting to save
98173 Using Step Out within Visual Studio might cause a warning
158302 Microsoft Visual Studio 2005 might hang while debugging a TestStand User Interface when loading symbols for Microsoft Internet Explorer 8
158838 Microsoft Visual Studio always uses the help for the latest version of TestStand if more than one version of TestStand is installed
250286 devenv.exe process continues to run after you close Microsoft Visual Studio 2010 using the close (X) button
287170 You might receive Error 1 "Interop Type Cannot Be Embedded" when you reference the TestStand API in Microsoft Visual Studio 2010
303631 Attempting to build a TestStand User Interface in Microsoft Visual Studio 2010 might result in an error when you target the .NET Framework 2.0–3.5
Miscellaneous
100723 Loading a type with a reference to itself causes a crash
101285 Configure operation for an IVI Dmm step might fail when using the Temperature Measurement extension
102490 Break on First Step incorrectly causes Step Into
124968 Error when running two instances of the Java example step type asynchronously
125444 Saving a sequence file as TestStand 3.0 or earlier might cause type conflicts
128019 Workspace File Documentation tool incorrectly specifies a modification date for VIs in LLBs
164437 Internet Explorer control TestStand uses might leak handles or crash if the control cannot find the XML style sheet
164491 ActiveX EXE servers that launch dialog boxes can cause TestStand to hang if TestStand also launches a dialog box
35247 46REB4YL Error when checking out a project file
41115 4D59O7YL HTML reports do not display correctly in Mozilla Firefox
45334 4I5A0FOS Turning off BSTR cache causes IVI error
48272 3QG976G0 Incorrect suspension location when disabling tracing into callbacks
50593 45KK5S00 File dialog box can leak a USER object
50996 46Q8EUIA IVI Fgen step might not store waveform data
51040 4759DCB8 Incorrect execution arrow position when interactively executing steps
51161 47BK2TUZ SequenceFilePreInteractive and SequenceFilePostInteractive callbacks do not execute when run interactively
51295 47891JJ6 Property Object leak occurs when calling a remote sequence that errors
51427 47TD3KB8 Incorrect suspension point when stepping out of a client sequence file
52274 4AJA99YL Saving a sequence file with Wait steps as TestStand 2.0.1 or earlier might result in an error
96016 Legend in the Sequence Hierarchy window is cut off
132872 Property Loader step does not resize arrays when loading properties
132943 XML Packaging Utility fails on a multibyte operating system with English (US) regional settings
141627 HTML, XML, and ATML reports do not preserve formatting when displaying string values that contain LF('\n'), CRLF('\r\n'), or whitespace characters
143996 Ignoring unique step IDs with the TestStand Differ application does not ignore unique IDs in expressions
149883 Importing a property from a .xls file using a Property Loader step does not import the full property value if the cell contains comma
150427 Switching from a literal path to an expression in the Configure Call Executable dialog box does not refresh the found path display
159453 Loading a TestStand 2.0 sequence file that contains ActiveX Adapter steps results in an error after running a user interface in LabVIEW more than once
159809 Import/Export Properties dialog box does not persist some settings
188160 Setting the HTBasic Working Directory option to "Subroutine file directory" on the HTBasic Module tab or in the HTBasic Adapter Configuration dialog box does not properly set the HTBasic working directory
189528 Perforce 2009.1 and 2009.2 client causes TestStand to crash when closing a workspace file
192247 When you enable On-The-Fly reporting and TestStand records a result after the MainSequence completes, the report shows the UUTStatus as "Running"
198622 TestStand shows the Report Tab after an execution completes for ASCII and HTML report formats even when you disable report generation
205554 Microsoft Windows 7 Most Recently Used (MRU) list for pinned TestStand application includes all files opened with the Open File dialog box
213835 Using foreign characters in XML report style sheets might result in errors during report generation
216539 Using the Property Loader step to import two or more step properties with the same name but different type or representation results in a type mistmatch error
301259 TestStand 2010 SP1 Migration Utility does not support redirecting paths that exist within a string when the string is not a valid path
35026 47LCM4G0 On-the-fly database logging leaks memory when an execution repeatedly creates new threads
360245 The TestStand Sequence Analyzer does not honor code module load and unload settings
363354 The TestStand Sequence Analyzer reports an internal error when analyzing expressions with an incorrectly indexed array
363524 The += operator might not function correctly for appending elements to an array
312695 The Tcl example step might return error -14004 when executed from TestStand
345032 TestStand cannot save a TestStand Sequence Analyzer project file if the file specifies the Hidden attribute in the Windows file system
348612 A warning can appear when you first launch TestStand after you use the TestStand Migration Utility
214265 Launching the Resource Usage Profiler causes TestStand to crash if search directories reference another TestStand version
327928 TestStand does not update to display changes to switch configuration
365348 The UUT Information dialog box for the Parallel process model incorrectly restricts certain users from terminating or aborting test sockets
366317 Property Loader step incorrectly imports strings that contain commas when you use a comma delimiter
366735 Copying and pasting multiple watch expressions can cause the Watch View pane to error in certain cases
397573 The ProcessCleanup callback executes even if the ProcessSetup callback is skipped due to an error
Reports
35106 47FE0BG0 Incorrect indentation might occur when you generate a report on-the-fly
41730 4DQDAQYL Generating reports on-the-fly with asynchronous threads might cause an error
43782 4GGCQA00 Module execution times are not included in an XML report
358354 The offline results processing utility can crash if launched while another instance of the utility is closing
206892 Enabling the Log option in the VI Parameter Table does not function correctly for some LabVIEW data types
357691 ATML reports generated on non-English operating systems contain an improperly formatted start date
358127 An error can occur when generating an On-The-Fly report when a sequence call uses a new thread and executes a post action
224640 Terminated subsequences called in a new execution have a status of Passed
322859 The TS.StartTime property is incorrect when used with remote instances of the TestStand Engine
347289 XML reports might display an incorrect number of results and incorrect failure chain information
347733 The TestStand Offline Results Processing Utility loads slowly when the inbox or outbox contains a large number of files
347941 The offline results processing utility does not reload modified result processing plug-in files
348820 The offline results processing utility can hang when you use a result processing plug-in that causes a run-time error
365232 ATML report hyperlinks do not function for filenames that contain multibyte characters
367731 When you specify a report path by expression, the <Unique> macro does not function if the path does not exist
366100 The Basic Step Time Report example result processing plug-in does not function if Microsoft Visual Basic for Applications is not installed
413424 On-the-fly HTML and ASCII reports generated with a result filtering expression contain unexpected duplicates of certain results
381042 Processing Offline Result files on a separate machine can cause a "Drive Not Ready Error" error when generating reports
390043 ATML reports do not display icons correctly for sequence files that contain Japanese characters
390048 ATML 5 and XML reports do not display in Microsoft Internet Explorer 9 when the style sheet path contains Japanese characters
400978 Errors in a result processing plug-in can cause the TestStand Offline Results Processing Utility to hang
403032 TestStand does not provide a macro for including a part number in a custom report file path
409938 ATML reports do not display icons correctly for sequence files that contain Japanese characters
TestStand Deployment Utility
52184 4ADMCJ77 Building a deployment before LabVIEW completely launches might cause an error
135514 415AQUM0 TestStand Deployment Utility deploys files to an incorrect location if a file path contains multibyte characters and the installation language does not match the target computer language
141991 TestStand Deployment Utility does not adequately document error codes -40 and -30
151624 Deploying VIs in a LabVIEW class might not correctly link dependencies
152924 Deploying files after moving a .tsd file and unchecking files for deployment might change the deployment destination directories or truncate filenames
172759 Including the LabVIEW 8.5.1 _exclsub.llb file in a TestStand workspace along with a sequence file that contains a LabVIEW 8.5.1 code module that calls the Report Generation Express VI results in a TestStand Deployment Utility build error
172793 Leaving the Default Installation Subdirectory field empty in the Installer Options tab of the TestStand Deployment Utility results in a build error
182127 The TestStand Deployment Utility assigns the same default destination directory for two files with the same filename and file hierarchy but located on different drives
191976 TestStand Deployment Utility does not properly update TestStand Deployment (TSD) file paths that contain user names when you move the files and a different user loads the TSD file
192254 Destination directories for files you do not select in the TestStand Deployment Utility appear distorted when you convert TestStand Deployment files from an older version of TestStand to a newer version
219779 TestStand Deployment Utility merges CommonResults type during build without prompts
252650 July 29, 2012TestStand Deployment Utility does not update the workspace path if you save the deployment and workspace files to the desktop then move the files
276342 TestStand Deployment Utility fails when you build a Packed Project Library with source if a project with the same path is already in memory
277891 TestStand Deployment Utility returns an error when building if the TestStand directory and its VIs do not exist in the vi.lib\addons directory
249171 A warning can occur when you build a deployment that includes VIs that contain unsupported Microsoft Windows characters
276637 TestStand Deployment Utility returns a non-descriptive error when the LabVIEW Application Builder in unlicensed
368256 TestStand Deployment Utility does not notify you if certain steps do not have a code module specified
387069 TestStand Deployment Utility can create multiple copies of DLL files that LabVIEW code modules reference
389135 In the TestStand Deployment Utility, changing the installation directory of a LabVIEW packed project library causes settings to change
410806 Deployment does not include unused packed project libraries within a library when you enable the Include All Files in LabVIEW Project option
412636 TestStand Deployment Utility incorrectly deploys LabVIEW projects that contain class member calls to a packed project library
TestStand Engine
131253 You cannot use variables with the same name as an expression constant in an expression
131559 When a run-time error occurs in a step, the module is not unloaded from memory when you select the Unload after step executes option
135202 TestStand returns the error "The TestStand service did not start up promptly" when you launch the sequence editor or a user interface
144062 Calling the Module.CreateCode or Step.CreateCode methods on a .NET step or module returns an error if the methods are called from a non-STA thread
155319 PropertyObject leaks or hangs occur on a TestStand remote sequence execution server if a sequence file has a SequenceFileUnload callback
167667 Clicking Yes in the "Do you want to close all opened document windows?" dialog box after you close a workspace file prevents any open sequence files from reloading when you reopen the workspace
185097 Configuring a SequenceCall step to launch a new execution from within the SequenceFileLoad Engine Callback hangs the SequenceFileLoad execution when you load the sequence file
200279 Using the TestStand Seconds Function or Wait Step might result in incorrect elapsed time
207535 Using the RunEntryPoint command-line argument returns an error when the entry point you specify is defined in the process model associated with the sequence file but not in the station model
222618 Cleanup step post action that jumps to Main step group causes infinite loop when you terminate the sequence
232693 Batch synchronization behaves incorrectly when you set a SequenceCall step and the steps within the subsequence to serial batch synchronization
248782 Custom type container becomes incompatible with its own type when you use a field of the custom type container as the current element of a For Each loop
250674 Making the return value of the PropertyObject.GetValVariant method a 64-bit integer causes an edit-time error
250700 Message Popup step leaks memory when you enable Display Image or Web Page option
254341 Creating an attribute for a parameter of a substep code module results in an error
254771 FTP Files step type does not use the current sequence file directory search path to determine a relative path when browsing for files
298378 TestStand Engine File dialog box does not display correctly and is unusable when you set the font size to 150% DPI on Windows 7
306233 Disabling the Edit Module Prototype option for a step type might not restrict changes to the module of a step instance
359021 The PropertyObject.CreateReportSection method does not function properly with default input values
360098 The Sequence.GetEffectiveType method returns incorrect values when called from a running sequence
360746 A type conflict can occur when you save a sequence file after you change the station model
361039 Terminating a remote Call Executable step might cause a system-level error
322852 Enabling the Log option for parameters of a substep can cause an error
334986 LabVIEW Edit substeps do not support LabVIEW class output parameters
347220 Modifying properties within an ExpressionEdit control on the Module tab of the Step Settings pane for a LabVIEW Edit substep can cause TestStand to hang
51052 473EH1YL You receive an error when you attempt to directly pass TestStand API objects to a sequence you call on a remote computer
334946 TestStand hangs when you use modal dialog boxes in a LabWindows/CVI or LabVIEW code module
339035 Reordering array elements in a large array takes a long time and appears to hang TestStand
358061 Dialog boxes generated in new executions do not display when created within a remote engine
402410 Loading the module of a sequence call step using the API results in an error in certain cases
405812 Type errors might occur when loading a more recent version of a type that is stored only in a sequence file
405858 Using modal dialog box functions to handle the ApplicationMgr.DisplayCustomRunTimeErrorDialog event results in incorrect behavior
TestStand Sequence Editor
104628 Some dynamically defined toolbar items disappear on refresh
164425 Sequence editor caches Execution windows
164426 Selecting the Show Differences option in the Workspace pane context menu can result in a hang if source code control diff or merge utilities are not installed
42416 4ETBRHYL Step Type Menu Editor dialog box displays an error and closes when dragging groups quickly with the mouse
51030 46PDBH77 Selecting different steps is slow when a very large array is expanded on the Variables pane
51062 46QAPEG0 You cannot view the Sequence Properties or Sequence File Properties dialog boxes without unlocking a file first
51293 477DFO9Q Property object leaks reported when closing the TestStand Sequence Editor from the Windows taskbar
51301 47DDCJ77 Variables pane incorrectly highlights an expression property in red
51578 47RDI9YL Create Custom Data Type from Cluster dialog box appears multiple times when multiple steps are selected
137446 Double-clicking a Sequence Call step that calls a sequence in a new file does not scroll the Sequences pane if the new sequence file is not already open
139956 TestStand User Interfaces do not reload a process model if it is modified on disk while loaded into memory
148181 Variables pane can become hidden or partially covered when you auto-hide it and then remove the auto-hide
157583 Undoing changes from the Update Automation Identifiers tool makes all steps in the selected sequence disappear
51939 49O5JI9Q TestStand Sequence Editor seems to hang when launching the Customize Toolbar dialog box after changing the number of monitors in the system
248968 Watch View pane returns an error when you drag an object held by a reference onto the pane
359036 An error can occur when you use the Find/Replace in Files dialog box in sequence files with a SequenceFileLoad Engine callback
354474 Cannot drag and drop array elements when sorting is enabled on any column on the Variables pane
308947 An error occurs when you use the Paste function in an array of object references
314004 You can cannot edit the struct and cluster passing setting after you set the data type as hidden
350367 The Module tab on the Step Settings pane does not display in certain cases after you change the type for a step
TestStand User Interface (UI) Controls
127509 Application Manager control might hang if TestStand is not licensed
50235 43FETR00 Cannot navigate to adapter buttons using the keyboard within the Insertion Palette pane
50418 44CB5HGH SequenceView and ListBar controls can leak memory
50421 44BDJQRA VariablesView control can leak a Windows USER object
51251 476DR6B8 CheckBox control Color properties do not work when used as a button
138406 The /run and /runEntryPoint command-line arguments are ignored when no user is logged in
199119 Clicking a step icon deselects all other selected steps
52249 4ADBS5B8 ActiveX controls located within user controls, such as tabs or panels, on a .NET form might disappear
298496 Expression Browser dialog box elements do not display correctly if the font size is set to 150% DPI
301993 TestStand ActiveX user interface buttons connected to the CommandKind_Edit commands might exhibit unexpected behavior
361491 TestStand User Interface developed with LabVIEW Actor Framework hangs
User Interfaces
164433 TestStand MFC user interface might leak GDI objects when creating and destroying child windows on Windows XP SP2
141889 LabVIEW User Interface in Editor Mode ignores the <Alt+Enter> shortcut to launch Step Properties dialog box
255848 You cannot paste additional results in user interfaces other than the TestStand Sequence Editor
256758 Using the keyboard to select multiple variables in the Variables View control does not work in the MFC, LabWindows/CVI, or LabVIEW UIs

 

Known Issues

ID Known Issue
.NET Adapter
139737

Return
Cannot create or edit code of a struct using the .NET Adapter
You can use the .NET Adapter to call methods and properties of structs and classes. However, although you can use the .NET Adapter to create or edit code for a class, attempting to complete these operations for a struct results in an error.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
354252

Return
An error can occur when you simultaneously modify the invocations of multiple .NET code modules
If you select two or more .NET steps that use the same assembly and class and you then modify the calls within the .NET Invocation control on the .NET Module tab, an error similar to the following error can occur: Array offset 2 is out of range; range is 0..1
Error Code: -17324, Array index out of bounds This error is more likely to occur if the invocations of the two selected steps specify a different number of calls.

Workaround: Modify the invocations of .NET steps individually.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/26/2012
356096

Return
An unhandled .NET error can occur when you use the /quit command-line flag to close TestStand
An unhandled .NET error can occur when TestStand exits and the following conditions are true:
  • You launch TestStand from the command line with an argument that contains the /quit flag
  • You have Visual Studio installed and you enable just-in-time debugging
If you attempt to debug the process from the error dialog box, Visual Studio launches a dialog box that explains that Visual Studio cannot attach to the crashing process and that the process has been terminated.

Workaround: You can safely ignore this error. To prevent the error from displaying, disable just-in-time debugging in Visual Studio.

Reported Version: 2012    Resolved Version: 2013    Added: 07/26/2012
356700

Return
Closing Microsoft Visual Studio after you debug .NET code from TestStand prevents the Visual Studio process from exiting
After you use Visual Studio to debug .NET code modules in TestStand, closing Visual Studio ends the TestStand process but does not end the VSdebugController process used to debug .NET code. If you launch TestStand again and attempt to debug .NET steps, you might receive the Error Code: -17502; System Level Exception error. This issue no longer occurs with Microsoft Visual Studio 2012.

Workaround: If you encounter this error, use the Windows Task Manager facility to terminate the VSdebugController process before you run the sequence. To prevent the error, ensure that you close TestStand instead of Visual Studio to correctly end the Visual Studio and the VSdebugController processes.

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 07/26/2012
202206

Return
Error -17500 occurs when you execute .NET code modules that deserialize types
Refer to the National Instruments KnowledgeBase article, knowledgeBase 65UDANUB: Why Do I Receive Error -17500 When Executing TestStand .NET Code Modules Which Deserialize Types?, for more information about this issue and available solutions.

Workaround: N/A

Reported Version: 3.0    Resolved Version: N/A    Added: 02/05/2013
402888

Return
When you access a .NET property in a child class that overrides set or get, only the override is available
If you use a .NET Adapter step to access a property that overrides the set or get definition of the property in a base class, only the overridden method is available. For example, if you are overriding the set method of a virtual int defined in a parent class, the get method will not be available in TestStand if the child class is specified.

Workaround: Specify the parent class instead of the child class in the Root Class control on the .NET Module tab to access the object. The .NET Adapter still uses the override in this case.

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
406396

Return
Additional Results setting is not respected for elements of arrays within a .NET adapter step
If you enable the option in the Log column of the Parameters Table for one or more individual elements of an array, the Log option for the array itself does not update accordingly. As a result, the array elements do not appear in the Additional Results panel and TestStand does not log them.

Workaround: Enable the option in the Log column for the array itself instead of the individual elements.

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
ActiveX/COM Adapter
44060
4GQ7M6JO

Return
Cannot specify an underlying data type when passing a variant parameter using the ActiveX/COM Adapter or API in expressions
TestStand can call methods of an ActiveX Automation server with variant input parameters. However, some methods can fail if the underlying data type is not correct. The ActiveX/COM Adapter and API in expressions do not support specifying the underlying data type of variant parameters. When you use the ActiveX/COM Adapter to call a COM server method and pass a TestStand numeric value to an optional variant parameter, TestStand passes a variant of the VT_R8 data type to the COM server method. If the method expects a VT_I4 data type and the COM server does not handle the case of a different variant data type being passed in, you receive an error.

Workaround: Create a wrapper VI or DLL that converts the variant data type appropriately and call the COM server method directly.

Reported Version: 4.0.1    Resolved Version: N/A    Added: 05/18/2009
C/C++ DLL Adapter
157130

Return
Verify Prototype option for the LabWindows/CVI and C/C++ DLL Adapters incorrectly includes the expression value in an array parameter prototype
You can use the Verify Prototype option on the LabWindows/CVI and C/C++ DLL Module tabs to modify the prototype of a LabWindows/CVI or C/C++ function to match the parameter list you have specified. However, when creating an array parameter, the Verify Prototype option includes the size of the array, which is not necessary for a C/C++ parameter definition. This can lead to compile errors if you specify a non-constant array parameter size, such as using the GetNumElements() function.

Workaround: Delete the incorrectly added text in the generated prototype.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
255602

Return
C/C++ DLL Adapter Create and Edit Code features return errors for functions that specify an array parameter
The C/C++ DLL Adapter Create and Edit Code features return errors for functions that specify an array parameter. In the Create Code case, Visual Studio correctly launches and creates the new function, but TestStand is unable to find the function and returns an error. In the Edit Code case, TestStand returns an error.

Workaround: You can ignore the error. In the Edit Code case, navigate to the function manually.

Reported Version: 4.2.1    Resolved Version: N/A    Added: 08/01/2011
297248

Return
The Log option in the Parameters Table for complex number parameters in C/C++ DLL steps can behave erratically
If you configure a C/C++ DLL step and you add a CNiComplex or CNiComplexVector parameter, configuring the Log option in the Parameters Table for the real and imaginary components causes the logging behavior for the container or the components to change in an unexpected way. TestStand does not support logging only the real or imaginary portion of a complex number, and logging should be non-editable for the components.

Workaround: Only enable the Log option for the complex number container and not the real or imaginary components.

Reported Version: 2010    Resolved Version: N/A    Added: 07/29/2012
Database
359126

Return
Memory usage can increase when you use the SQL Server Stored Proc schema with the Microsoft OLE DB Provider for SQL Server
Memory usage can increase when using the SQL Server Stored Proc schema and the database connection string uses the Microsoft OLE DB Provider for SQL Server. The memory usage appears to oscillate but shows growth over time.

Workaround: Use the Microsoft SQL Native Client database provider to avoid this issue.

Reported Version: 2010    Resolved Version: 2013    Added: 07/25/2012
357315

Return
An error can occur when you log binary data to an Oracle database
You might encounter the following error when you log binary data to an Oracle database: An error occurred calling 'LogResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'
An error occurred while setting a column value.

Description: ORA-22990: LOB locators cannot span transactions
Number: -2147467259
NativeError: 22990
The error appears when all of the following conditions are true:
  • You are logging data to an Oracle database.
  • You enable the Share Data Link Between Executions option on the Data Link tab of the Database Options dialog box.
  • You are logging binary data to the database.
  • TestStand 2013 and later now warn you when you configure a database logging schema with these settings.

    Workaround: Disable the Share Data Link Between Executions option. If you are not using on-the-fly database logging, you can also prevent this issue by enabling the Use Transaction Processing option on the Data Link tab of the Database Options dialog box.

    Reported Version: 4.1    Resolved Version: 2013    Added: 07/26/2012
375181

Return
TestStand reports multiple differences when validating the default database schemas
If you select one of the default schemas on the Schemas tab of the Database Options dialog box and click the Validate button, TestStand reports multiple differences. These differences are incorrect and you can safely ignore them.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
390817

Return
Filtering results fails for certain steps when using on-the-fly database logging
If you specify a result filtering expression that includes only Passed and Done results, Wait and Sequence Call steps with a Failed result are not filtered. This behavior occurs only when using on-the-fly database logging.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
File Differ
299368

Return
The TestStand File/Diff Merge application does not support diffing station global variables
The TestStand File/Diff Merge application does not support diffing station global variables and instead returns a Value invalid or out of range error.

Workaround: Save the station global variables file in XML or INI format and use a text-based tool to diff the files.

Reported Version: 2010    Resolved Version: N/A    Added: 08/01/2011
IVI
408196

Return
TestStand does not report an error in some cases when importing an unsupported IVI configuration
If you attempt to import an IVI configuration that requires the NI-DAQmx or NI Switch Executive drivers, TestStand does not return an error even though the import will not succeed. TestStand does return an error when other required drivers are missing.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 06/28/2013
Installation
164423

Return
Uninstalling TestStand 2.0 from a computer with TestStand 4.x installed removes NI Session Manager files.
When you uninstall TestStand 2.0 from a computer on which you also installed TestStand 4.x, the TestStand 2.0 uninstaller might incorrectly remove the NI Session Manager 4.x files.

Workaround: Navigate to Add/Remove Programs on the Windows Control Panel and use the National Instruments Software maintenance utility to repair the NI Session Manager and restore the files.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
164424

Return
Installing IVI components from TestStand 2.0 after installing IVI components from TestStand 4.0 causes errors
Do not install the Interchangeable Virtual Instrument (IVI) components from the TestStand 2.0 CD after you install the IVI Compliance Package (ICP) from the NI Device Driver CD or DVD included with TestStand 4.x. If you installed ICP 2.2 or later from the NI Device Driver CD or DVD before you installed TestStand 2.0, do not install the IVI components from the TestStand 2.0 CD. Disable the Basic IVI Class Drivers feature within the IVI Engine and Drivers feature when you install TestStand 2.0.

Workaround: If you installed the TestStand 2.0 IVI components after you installed ICP 2.2 or later from the NI Device Driver CD or DVD, navigate to Add/Remove Programs on the Windows Control Panel and use the National Instruments Software maintenance utility to repair the ICP product and correct this incompatibility.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
172792

Return
Uninstalling a TestStand deployment leaves the TestStand Engine and other additional components on the system
When you run a TestStand Deployment Utility installer that includes the TestStand Engine and other additional components, the installer adds two items to the Add/Remove Programs dialog box. The first item is the name of the TestStand system you defined when you configured the TestStand Deployment Utility. The second item is "National Instruments Software", which provides the functionality to modify, repair, or remove any installed National Instruments software, such as the TestStand Engine or other additional components that the TestStand Deployment Utility installer includes. Uninstalling the first item has no effect on the second item, thus leaving the TestStand Engine and other additional components installed on the computer.

Workaround: After you uninstall the TestStand system using the Add/Remove Programs dialog box, select the "National Instruments Software" item and manually uninstall the TestStand Engine and additional components.

Reported Version: 3.5    Resolved Version: N/A    Added: 12/11/2009
360674

Return
Measurement & Automation Explorer can display incorrect installed versions after uninstalling TestStand 2012
If you have both TestStand 2010 (not TestStand 2010 SP1) or earlier and TestStand 2012 installed, and then you uninstall TestStand 2012, the software section of Measurement & Automation Explorer (MAX) incorrectly indicates that TestStand 2012 is installed and TestStand 2010 or earlier is not installed.

Workaround: You can safely ignore this issue, or you can fix the behavior by running a repair installation of TestStand 2010 or earlier.

Reported Version: 2012    Resolved Version: 2013    Added: 07/25/2012
361582

Return
TestStand Version Selector incorrectly displays TestStand 2012 as an available version to activate after you uninstall TestStand 2012
The TestStand Version Selector incorrectly allows you to select TestStand 2012 in the Installed TestStand Versions combo box after you uninstall TestStand 2012.

Workaround: You can fix this behavior by running a repair installation of an earlier version of TestStand that is also installed.

Reported Version: 2012    Resolved Version: 2013    Added: 07/25/2012
LabVIEW
100053

Return
Enumerations with the same name as a constant show as an error
The Edit VI Call dialog box highlights expressions as an error for variables that have the same name as an enumeration value.

Workaround: Ignore error.

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
101510

Return
LabVIEW user interface reports object leaks on shutdown when using ActiveX Variants in ActiveX callbacks
A LabVIEW user interface reports object leaks on shutdown when you pass a TestStand object as the ActiveXData parameter of a UIMessage in the UIMessage callback VI. LabVIEW does not release the object reference until you unload the LabVIEW callback VI.

Workaround: Refer to the National Instruments KnowledgeBase article, located at http://www.ni.com/cgi-bin/redirect.cgi?dest=infcoprod&src=help&openagent&code=rdlug3, for more information about using a dynamically called VI to ensure that LabVIEW releases the object.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
125375

Return
LabVIEW user interface freezes when you move splitter bars
A LabVIEW user interface front panel might hang within LabVIEW if you move a splitter bar while an execution is tracing. LabVIEW 2009 fixes this behavior.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
125576

Return
ExpressionEdit controls on LabVIEW front panels do not release keyboard focus
ExpressionEdit controls on LabVIEW front panels do not release keyboard focus when you select another LabVIEW control in the LabVIEW development environment. ExpressionEdit controls behave properly in an application built with LabVIEW. LabVIEW 8.6.1 fixes this issue.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
164429

Return
LabVIEW User Interface executables that do not use TestStand UI Controls might hang when launched
LabVIEW User Interface executables that do not use the TestStand User Interface (UI) Controls might hang when launched. The hang occurs when TestStand loads the LabWindows/CVI Run-Time Engine and both LabVIEW and the run-time engine access computer resources simultaneously.

Workaround: You can prevent the hang by using a Call Library Function VI to invoke a function in the LabWindows/CVI Run-Time Engine to force LabVIEW to synchronously load the run-time engine into memory before creating the TestStand Engine.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
164430

Return
Calling a LabVIEW-built DLL from the user interface thread that create the TestStand engine might cause the application to hang
LabVIEW applications, such as a TestStand LabVIEW User Interface, might hang when you call a function in a LabVIEW-built DLL from the user interface thread. For example, a TestStand LabVIEW User Interface can hang when you create the TestStand Engine and the engine loads a Sequence File Translator DLL built with LabVIEW.

Workaround: Create the TestStand Engine in a non-user interface thread, such as Other 2, to work around this issue.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
48357
3RFG3UM0

Return
Cannot browse to a VI if the VI filename includes multibyte characters
The LabVIEW Adapter cannot browse to a VI in a LabVIEW library if the VI filename includes multibyte characters.

Workaround: N/A

Reported Version: 3.5    Resolved Version: N/A    Added: 05/26/2008
49481
3Z4EURMF

Return
LabVIEW user interface beeps when using menu accelerator keys
A LabVIEW user interface beeps when you press <Alt-F> or other menu accelerator keys.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
49503
3ZCDRG77

Return
Cannot use LabVIEW RTE to load a VI without saving the library
You cannot use the LabVIEW RTE to load a VI when you add the VI to the LabVIEW library without saving the library.

Workaround: You must save the library first.

Reported Version: 3.5    Resolved Version: N/A    Added: 05/26/2008
49856
41AHCIMF

Return
TestStand UI Controls do not process some key strokes in LabVIEW user interfaces
LabVIEW does not call PreTranslateAccelerator for ActiveX controls, which prevents TestStand UI Controls in LabVIEW user interfaces from processing some key strokes, such as pressing <Tab> to autocomplete expressions or navigate within controls, pressing <Ctrl-Shift> to perform an operation, or pressing <Shift-Arrow> to select multiple items.

Workaround: N/A

Reported Version: 4.0    Resolved Version: 2013    Added: 05/26/2008
50897
46PA3DMF

Return
Help Topic menu item is disabled
If a TestStand UI Control loses focus, the Help»Help Topic menu item is disabled in the TestStand LabVIEW User Interface.

Workaround: If the Help»Help Topic menu item is disabled, click a TestStand UI Control to re-enable the menu item.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51491
480JGC00

Return
LabVIEW user interface appears hung when Property Leak Report dialog box displays behind application
The Debug Warnings dialog box is not modal and launches behind the LabVIEW Simple User Interface front panel when you exit the application and the process does not correctly release TestStand objects.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51752
491GSRM0

Return
VI breakpoint does not bring the VI window to front
When you run a VI from TestStand and the VI contains a breakpoint, TestStand does not bring the VI window to the front when the VI reaches the breakpoint.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
158407

Return
LabVIEW VI Server Exported VIs Setting Might Be Modified By Desktop Execution Trace Toolkit (DETT) 1.0
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 NI TestStand, LabVIEW SignalExpress, NI Requirements Gateway (see complete list below) etc., which require certain VIs to be exported to work correctly with LabVIEW. The bug exists if you have installed DETT 1.0 through any one of the following distributions: 1) LabVIEW 8.6.1 Platform DVD 2) NI Developer Suite Q1 2009 DVD 3) LabVIEW Desktop Execution Trace Toolkit 1.0 CD

Workaround: Please see KB 4U49Q33Y at www.ni.com for more information about the issue and for the fix.

Reported Version: 4.2    Resolved Version: N/A    Added: 02/06/2009
136507

Return
You cannot toggle the Show VI Front Panel When Called option when the Run VI on Remote Computer option is enabled
When you enable the Run VI on Remote Computer option in the LabVIEW Advanced Settings window in the sequence editor or in the Advanced Settings dialog box in a user interface for a LabVIEW step, you cannot enable or disable the Show VI Front Panel When Called option on the LabVIEW Module tab in the sequence editor or in the Edit LabVIEW VI Call dialog box in a user interface, even though the Show VI Front Panel When Called option retains the value that was set previously. However, regardless of the display, the front panel of a VI never displays on the remote computer.

Workaround: You can ignore the setting of the Show VI Front Panel When Called option because the front panel never displays on the remote computer.

Reported Version: 4.1    Resolved Version: N/A    Added: 05/18/2009
148697

Return
LabVIEW user interface might hang when using LabVIEW events
A LabVIEW user interface that registers ActiveX callbacks and uses an Event structure might hang when the user interacts with a LabVIEW control or indicator. The hang is rare, but when it occurs, TestStand User Interface Controls remain responsive, but all LabVIEW user interface elements appear frozen. LabVIEW 2009 fixes this behavior.

Workaround: Activate another application and reactive the LabVIEW user interface.

Reported Version: 4.1.1    Resolved Version: N/A    Added: 05/18/2009
153518

Return
Configuring the Formula Express VI in a TestStand step results in error tones
Selecting the Formula Express VI for a step, launching its configuration dialog box, or selecting a step that specifies the Formula Express VI as its code module cause a series of system error tones.

Workaround: The tones are harmless and you can ignore them.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
153853

Return
Create VI button on the LabVIEW Module tab or the Edit LabVIEW VI Call dialog box does not create a VI in an LLB
When specifying a LabVIEW code module, you can create a VI by clicking the Create VI button on the LabVIEW Module tab or the Edit LabVIEW VI Call dialog box. However, you cannot create a VI directly in an LLB, and attempting to do so returns the error '"newfilename" File not found in LLB, Please verify the correct file name was given.'

Workaround: Create the VI outside of the LLB, resave the VI in the LLB using LabVIEW, and update the path to the VI in TestStand.

Reported Version: 3.5    Resolved Version: N/A    Added: 05/18/2009
158938

Return
Cannot pass struct containing an array of structs into a DLL built with LabVIEW
You can call a DLL built with LabVIEW using the C/C++ DLL Adapter in TestStand. However, for parameters that are structs containing an array of structs, TestStand does not allocate the memory properly, resulting in a TestStand Error: -17502 System Level Exception error.

Workaround: You can pass arrays of numbers, arrays of strings, or individual clusters as parameters to a DLL built with LabVIEW.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
160210

Return
TestStand Deployment Utility might appear to hang when building if the LabVIEW Build Specifications dialog box is open
As part of the build process, the TestStand Deployment Utility uses the LabVIEW application builder to create a source distribution of all VIs included in the distribution. If any build specification dialog box is open in the LabVIEW development environment, the Deployment Utility might appear to hang while the Build Status is "Processing VIs..."

Workaround: Close the open build specification dialog box to allow the TestStand Deployment Utility to continue the build process.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
161523

Return
Arrays passed from LabVIEW to TestStand are transposed
When a VI connector pane passes an array from LabVIEW to TestStand, the array is transposed. For example, a 2D array of four columns and five rows from a LabVIEW VI appears as an array of five rows and four columns when stored in a TestStand PropertyObject.

Workaround: Pass the array back to LabVIEW, and the opposite transformation occurs to restore the original position of the elements.

Reported Version: 3.0    Resolved Version: N/A    Added: 05/18/2009
179186

Return
Configuring a MessagePopup step as a Modal or Floating popup hangs subsequent LabVIEW steps for which you enabled the Show VI Front Panel When Called option
If you enable the Make Modal or Make Floating option in the Dialog Options section of the Message Popup Layout edit tab and call LabVIEW code modules after you call the Message Popup step, the LabVIEW code modules hang if you enabled the Show VI Front Panel When Called option on the LabVIEW Module tab in the TestStand Sequence Editor or in the Edit LabVIEW VI Call dialog box in a TestStand User Interface for the LabVIEW steps. LabVIEW 2009 SP1 fixes this issue.

Workaround: Do not enable the Make Modal or Make Floating options of the MessagePopup Layout edit tab or create your own code module in LabVIEW to display the message you want. LabVIEW 2009 SP1 fixes this issue.

Reported Version: 3.5    Resolved Version: N/A    Added: 12/11/2009
184366

Return
Clicking the Create Custom Data Type button on the LabVIEW Module tab for a cluster that contains unknown types results in an error
When you click the Create Custom Data Type button on the LabVIEW Module tab to create a custom data type for a cluster that contains unknown types, such as 64-bit integers, TestStand returns the following error: "Bad object type passed Error Code: -17001, Program Error."

Workaround: N/A

Reported Version: 3.5    Resolved Version: N/A    Added: 12/11/2009
188059

Return
The LabVIEWModule.ExpressVIName property does not update to match the Express VI title when a different configuration changes the title
When you browse to and select an Express VI to load, TestStand launches the Express VI configuration dialog box. Some Express VIs modify the title of the VI based on the current configuration settings. TestStand does not update the LabVIEWModule.ExpressVIName property to match the modified Express VI title once you configure the Express VI.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
188119

Return
TestStand is a 32-bit application and has limited support for LabVIEW 64-bit
Refer to the National Instruments KnowledgeBase article 50O9851O, Does TestStand support calling VIs using LabVIEW 64-Bit? on the National Instruments Web site for information about LabVIEW 64-bit support in TestStand.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
190260

Return
Calling and unloading an assembly more than once crashes TestStand if the assembly is built with LabVIEW 2009
When TestStand calls and unloads an assembly a second time and the assembly is built with LabVIEW 2009, TestStand crashes because the reference count is not properly incremented. LabVIEW 2009 SP1 fixes this issue.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
191741

Return
Clicking a LabVIEW step when TestStand is configured to use the LabVIEW 7.1.1 Run-Time Engine results in a Fatal Error: "LABVIEW.LIB could not locate "FResDir""
This error occurs when the LabVIEW 2009 Run-Time Engine (RTE) is loaded into memory after the LabVIEW 7.1.1 RTE has already been loaded into memory. When you configure the LabVIEW Adapter to use the LabVIEW 7.1.1 RTE, TestStand loads the LabVIEW 7.1.1 RTE into memory. Selecting a LabVIEW step causes TestStand to attempt to load the LabVIEW 2009 RTE into memory to use it to perform a checksum of the VI connector pane, which results in a Fatal Error: "LABVIEW.LIB could not locate "FResDir" ". LabVIEW 2009 SP1 fixes this issue.

Workaround: Configure the LabVIEW Adapter to use the LabVIEW development environment instead of the LabVIEW 7.1.1 RTE. LabVIEW 2009 SP1 fixes this issue.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
203643

Return
Using TestStand to open a VI in a newer version of LabVIEW might leak a handle to the VI and prevent you from saving the VI
If you use the Edit VI feature in TestStand to open a VI and the active LabVIEW version is more recent than the version of the VI, LabVIEW might leak an extra handle to the VI and prevent you from saving the VI. LabVIEW 2010 fixes this issue.

Workaround: If you mass compile the VI to the active LabVIEW version, you can open the VI from TestStand and save it. If you already opened the VI from TestStand and made significant modifications, you can leave the VI open and close TestStand. Once TestStand closes, you can save the VI. LabVIEW 2010 fixes this issue.

Reported Version: 4.0.1f1    Resolved Version: N/A    Added: 08/25/2010
ID Known Issue
250131

Return
LabVIEW code module front panels might update slowly when you use TestStand Start and End Modal Dialog VIs
The TestStand - Start Modal Dialog VI sets the Parent Window for Dialogs LabVIEW application property to True, which might cause front panel controls to update or refresh more slowly than usual. LabVIEW 2011 fixes this issue.

Workaround: If you use the TestStand Start and End Modal Dialog VIs, set the Panel.DeferPanelUpdates property in the VI to True until all controls have been updated, then set the property back to False. LabVIEW 2011 fixes this issue.

Reported Version: 4.0.1f1    Resolved Version: N/A    Added: 04/10/2011
253952

Return
Passing LabVIEW Class references from step to step can crash LabVIEW
If you configure two steps to call VIs from the same LabVIEW project and those VIs pass LabVIEW Class references, LabVIEW crashes when you execute the second step if the Load/Unload Options of both steps are set to Load dynamically and Unload after step executes. LabVIEW 2010 fixes this issue.

Workaround: Do not unload the steps until the execution completes. LabVIEW 2010 fixes this issue.

Reported Version: 2010    Resolved Version: N/A    Added: 04/10/2011
245655

Return
Cannot call VIs from LabVIEW packed project libraries when the full path of the VI is longer than the maximum path length
When you configure TestStand to call a VI from a LabVIEW packed project library and the full path of the VI is longer than the maximum path length, TestStand does not find the file or reports that the VI is an unexpected type.

Workaround: Ensure that the full path of the VI you call is shorter than the maximum path length.

Reported Version: 2010    Resolved Version: N/A    Added: 08/01/2011
254553

Return
TestStand might become unresponsive while LabVIEW launches a prompt to save a VI
If you attempt to create or edit a VI from TestStand while the LabVIEW Development Environment launches a prompt to save a VI, TestStand might become unresponsive.

Workaround: Close the LabVIEW dialog box to make TestStand responsive again.

Reported Version: 4.0    Resolved Version: N/A    Added: 08/01/2011
279822

Return
TestStand appears to hang when LabVIEW search dialog box does not come to front when browsing for a VI that is missing subVIs
The LabVIEW search dialog box is not modal to a TestStand User Interface, so When you browse for a VI that is missing one or more subVIs, a maximized TestStand User Interface hides the LabVIEW search dialog box, and it appears that TestStand has hung and become unresponsive.

Workaround: Minimize the TestStand User Interface window or make LabVIEW active to bring the LabVIEW search dialog box or open file dialog box to the front.

Reported Version: 4.0.1f1    Resolved Version: N/A    Added: 08/01/2011
217346

Return
Changing the size of a two-dimensional array in a LabVIEW code module can cause TestStand to crash
If you resize a two-dimensional array in a LabVIEW code module when all of the following conditions are true, TestStand might behave unexpectedly or crash when you click the Reload Prototype button.
  • You expand the two-dimensional array in the VI Parameter Table in TestStand when you also change the size of the array in LabVIEW.
  • You select Edit»Make Current Value Default in LabVIEW after you resize the array.
  • You enable the Default option in the VI Parameter Table for the array in TestStand.
  • If either dimension of the array is smaller than the original size, TestStand crashes with the An error has occurred. Please save your work and restart the sequence editor. error. If one or both dimensions are larger than the original size, TestStand displays incorrect indexesfor the newly added elements.

    Workaround: After you change the default value and size of an array in a LabVIEW code module, close and reopen the sequence file instead of using the Reload Prototype button.

    Reported Version: 4.1    Resolved Version: N/A    Added: 07/26/2012
303452

Return
Logging reference parameters in a LabVIEW step can cause an error
If you call a LabVIEW code module that meets all of the following conditions, TestStand returns the Type of argument expression is incompatible with parameter. Expected Number, found Object Reference. [Error Code: -17313, Could not accept the parameter passed in.] error when the step executes:
  • The code module contains a reference parameter that is represented as a numeric (such as a VI refnum).
  • You enable the Log option in the Parameters Table for the parameter.
  • You do not specify a value for the parameter.


Workaround: Specify a value or disable logging for the parameters.

Reported Version: 4.2.1    Resolved Version: N/A    Added: 07/29/2012
339699

Return
TestStand cannot find VIs in a packed project library that specifies a file path that includes multibyte characters
On operating systems for languages that require multibyte support, such as Chinese versions of Windows, TestStand cannot find VIs in a packed project library that specifies a file path that includes multibyte characters.

Workaround: Ensure that the path for the packed project library does not contain multibyte characters.

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 07/29/2012
253149

Return
TestStand does not recognize changes to parameter settings in VI code modules
If you change only the parameter settings within a VI code module, such as changing a parameter from recommended to required, steps that call the VI do not update to reflect the change until you reselect the step or reload the code module.

Workaround: N/A

Reported Version: 4.1    Resolved Version: 2013    Added: 06/28/2013
295614

Return
Using a LabVIEW Project reference parameter in a LabVIEW code module can cause a run-time error
If you call a LabVIEW code module that includes a reference to a project as an input or output in the VI connector pane, and you pass this parameter to or from a TestStand property in the VI Parameter Table, the following error occurs: Parameter 'Project Reference': Type of argument expression 'Locals.test' is incompatible with parameter. Specified value does not have the expected type. -17313; Could not accept the parameter passed in. This issue occurs only when you configure the LabVIEW Adapter to use the LabVIEW Development System.

Workaround: Cast the project reference to a number when you pass it to TestStand.

Reported Version: 4.0.1    Resolved Version: 2013    Added: 06/28/2013
381085

Return
Update VI Calls dialog box does not update code modules a Run VI Asynchronously step calls
The Update VI Calls dialog box does not update code modules a Run VI Asynchronously step calls.

Workaround: Manually reload the prototypes for the code modules of Call VI Asynchronously steps.

Reported Version: 4.1    Resolved Version: 2013    Added: 06/28/2013
390139

Return
VIs in a LabVIEW project saved in the instr.lib directory fail to load when you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine
Calling a VI code module returns a File Not Found error when all of the following conditions are true:
  • A LabVIEW project contains the VI and a TestStand step specifies the project
  • The LabVIEW project file is saved in the instr.lib or vi.lib directory
  • You configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine
This error occurs because TestStand incorrectly generates the VI file path by replacing LabVIEW\ with TestStand\bin\. This issue does not occur on a deployment target computer because the TestStand Deployment Utility moves the dependencies to a different location that does not experience this issue.

Workaround: Call the VI directly and do specify a project path.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 06/28/2013
397556

Return
Keyboard entry is ignored when editing a code module from User Interface built in LabVIEW
When you use a TestStand User Interface built in LabVIEW and you click the Edit VI button on the Module tab to edit a VI code module, you cannot use the keyboard when editing the code module.

Workaround: Open and edit the VI directly in LabVIEW. Do not use the Edit VI button to open the VI.

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
397930

Return
Enabling the Logging option for subproperties of a dynamic data type parameter causes a TestStand crash
If you are calling a VI code module that has an input or output parameter that is a dynamic data type, TestStand might crash if you enable the Log option for any subproperties of the parameter.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2013    Added: 06/28/2013
405883

Return
Configuring a Run VI Asynchronously step in a TestStand User Interface can cause a system-level error
When you configure a Run VI Asynchronously step in a TestStand User Interface and you click the Edit LabVIEW Call button to launch the Edit LabVIEW VI Call dialog box, click Cancel, and then click the Edit LabVIEW Call button a second time, TestStand returns an error that indicates that a system-level error has occurred.

Workaround: If you click Cancel in the Edit LabVIEW VI Call dialog box, you must also close the Run VI Asynchronously Step Configuration dialog box before you attempt to edit the LabVIEW call again.

Reported Version: 2012    Resolved Version: 2013    Added: 06/28/2013
407194

Return
LabVIEW Run-Time Engine number of threads setting is not respected
When you configure the Number of Threads option for the LabVIEW Run-Time Engine (RTE) in the LabVIEW Adapter Configuration dialog box to a non-default value, TestStand ignores the value you specify and instead uses the default value. In some cases, this results in a system-level error when you specify a non-default number of threads and you attempt to execute LabVIEW steps in the LabVIEW RTE.

Workaround: If you require a certain number of threads for executing a VI, change the execution system of the VI from same as caller to another option.

Reported Version: 2010    Resolved Version: 2013    Added: 06/28/2013
414363

Return
TestStand User Interfaces Appear to Hang on Shutdown after Executing VI code modules in certain run-time engine versions
For more information on this issue, refer to the following article:

KnowledgeBase 6APAG6UB: My TestStand User Interface Appears to Hang on Shutdown

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 06/28/2013
LabWindows/CVI
129574

Return
Exiting an external instance of LabWindows/CVI on Windows Vista returns an error
On Windows Vista, LabWindows/CVI returns an error when exiting after TestStand uses the external instance of LabWindows/CVI to execute code modules. LabWindows/CVI 9.0.1 fixes this issue.

Workaround: N/A

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
129603

Return
Executing LabWindows/CVI code modules in an external instance can leak memory
In some instances, TestStand leaks memory when executing LabWindows/CVI code modules in an external instance of LabWindows/CVI.

Workaround: Configure the LabWindows/CVI Adapter to execute code modules in-process to prevent this issue.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
129627

Return
Specifying an enumeration in a LabWindows/CVI module displays an incorrect name
The LabWindows/CVI Module tab in the TestStand Sequence Editor and the Edit LabWindows/CVI Module Call dialog box in a TestStand User Interface display a name the Microsoft Interface Definition Language (MIDL) generates instead of the actual enumeration name from the type library when you select a DLL built with LabWindows/CVI 8.5 or later. LabWindows/CVI 9.0.1 fixes this issue.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
36951
49GAQ5G0

Return
Error when loading a TestStand 4.0 or later user interface when TestStand 3.5 is the active version
LabWindows/CVI returns an error when you load a TestStand 4.0 or later user interface and TestStand 3.5 is the registered active version of TestStand.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
39257
48IACA9Q

Return
Reload Prototype button remains dimmed after building a DLL
When you use the LabWindows/CVI Module tab on the Step Settings pane in the TestStand Sequence Editor to create a LabWindows/CVI DLL, the Reload Prototype button on the LabWindows/CVI Module tab remains dimmed after you build the DLL in LabWindows/CVI.

Workaround: On the LabWindows/CVI Module tab, click the File Browse button and select the DLL again.

Reported Version: 4.0    Resolved Version: 2013    Added: 05/26/2008
171168

Return
Installing LabWindows/CVI 9.0 Run-Time Engine can break TestStand 3.5 deployed components
The TestStand Message Popup steps, LabVIEW, and LabWindows/CVI user interfaces use the NI ActiveX Container. The LabWindows/CVI 9.0 and 9.0.1 Run-Time Engines install a version of the NI ActiveX Container without listing its dependencies to the Microsoft 2005 C Run-Time (CRT) DLLs, specifically MSVCP80.DLL and MSVCR80.DLL. Building a deployment in TestStand 3.5 does not include the necessary Microsoft 2005 CRT DLLs, which causes the previously mentioned components to break on the target computer. This problem does not exist in TestStand 4.0 and later. TestStand 4.2.1 includes an updated version of the LabWindows/CVI 9.0.1 Run-Time Engine that fixes the issue.

Workaround: Include a National Instruments component that lists the Microsoft 2005 CRT DLLs as dependencies in the TestStand 3.5 deployment.

Reported Version: 3.5    Resolved Version: N/A    Added: 09/18/2009
213984

Return
LabWindows/CVI Adapter does not properly recognize struct parameters when the function name begins with an uppercase letter
The LabWindows/CVI Adapter interprets struct parameters as a long * when the function name begins with an uppercase letter. The adapter correctly interprets parameters when the function name begins with a lowercase letter.

Workaround: Make the function name begin with a lowercase letter or correctly configure the parameter manually in the parameters table.

Reported Version: 3.5    Resolved Version: N/A    Added: 08/01/2011
218283

Return
Edit Code operation might navigate to the wrong location in a LabWindows/CVI source file
When you use the Edit Code operation for the LabWindows/CVI Adapter, TestStand might navigate to the wrong location in the source file if you made edits to the file that modify line numbers or if you have not rebuilt the project.

Workaround: Rebuild the project.

Reported Version: 4.2.1    Resolved Version: 2013    Added: 08/01/2011
317729

Return
Changes to enumeration values in LabWindows/CVI code modules are not reflected in steps that call the code modules
If you call a LabWindows/CVI code module that has an enumeration as an input parameter, TestStand displays the enumeration constant names in the Parameters Table. The step data stores the value this constant represents. If you make a change to the value associated with an enumeration constant in the code module, steps that use the enumeration do not reflect this change and continue to use the previous value for the enumeration constant.

Workaround: Recreate any steps that use the enumeration after you make any changes to the values of enumeration constants you have already defined.

Reported Version: 4.0    Resolved Version: N/A    Added: 07/29/2012
381096

Return
Additional results logging setting for parameters in LabWindows/CVI or C/C++ DLL steps update incorrectly when you change how the parameter is passed
If you configure a parameter in a LabWindows/CVI or C/C++ DLL step to be passed by reference and then you enable the Log option in the Parameters Table, TestStand logs both the In and Out values of the parameter. You can configure the logging of the In and Out data independently on the Additional Results panel of the Properties tab of the Step Settings pane. If you later change the parameter settings such that it is passed by value, then execute the sequence, you will encounter an error similar to the following: Details: The following error occurred while logging additional result 'x [Out]': Array offset -1 is out of range; range is 0..0.. Error in parameter 1, 'x'. Error Code: -17324; Array index out of bounds. This error occurs because the the log setting for the "Out" value is still enabled, despite the fact that it is no longer a valid option.

Workaround: To disable logging for the Out value and prevent the error, you must configure the parameter so it is passed by reference so that the Out logging option is available. After disabling the option, set the parameter back to being passed by value.

Reported Version: 2010    Resolved Version: N/A    Added: 02/05/2013
384718

Return
Out-of-memory error occurs when using LabWindows/CVI-built TestStand User Interfaces on Microsoft Windows 8
Refer to the following National Instruments support article, KnowledgeBase 64GCHJUB: Out of Memory Exception when Using LabWindows/CVI Built TestStand User Interface On Windows 8, for information about this issue and how to resolve it.

Workaround: N/A

Reported Version: 2012    Resolved Version: 2013    Added: 06/28/2013
Microsoft Visual Studio
109366

Return
Calling a .NET module as an OnNewStep custom substep can error
TestStand returns an error when calling an OnNewStep custom substep that calls a .NET WinForm that requires an STA thread.

Workaround: N/A

Reported Version: 4.0.1f1    Resolved Version: N/A    Added: 05/26/2008
127991

Return
Receiving UI events in a .NET class that is not created in the UI thread might cause errors
Registering a .NET class to receive UI events from a TestStand UI Control, such as the Application Manager control, can cause unexpected re-entrancy issues when the .NET class is not created in the UI thread.

Workaround: N/A

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
164428

Return
Clicking a TestStand UI Control in a custom .NET user control might cause Microsoft Visual Studio to crash
If you click a TestStand User Interface (UI) Control hosted in a .NET user control in the Design view of Microsoft Visual Studio 2005, Visual Studio might crash. Visual Studio 2008 fixes this issue.

Workaround: Refer to the Microsoft Knowledge Base article ID 916495, located at http://support.microsoft.com/?kbid=916495, for more information about the hotfix for this Visual Studio 2005 limitation.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
164431

Return
Microsoft Visual Studio 2005 might crash when viewing a form in Design view after rebuilding a solution that uses TestStand UI controls
Microsoft Visual Studio 2005 might crash when you rebuild a solution that uses the TestStand User Interface (UI) Controls and you try to view a Microsoft Windows Form in Design view. The Design view might not show the Windows Form, and you might receive error messages.

Workaround: Refer to the Microsoft Knowledge Base article 912019, located at http://support.microsoft.com/kb/912019/en-us?spid=3041, for more information about this issue.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
41350
4D6GIVRA

Return
Cannot edit Visual Basic .NET projects when a function contains an array parameter
The .NET Adapter Edit Code option does not work for functions with array parameters in Visual Basic projects.

Workaround: N/A

Reported Version: 4.0.1    Resolved Version: N/A    Added: 05/26/2008
48970
3WIAETIF

Return
TestStand ActiveX controls can become invisible in the Visual Studio designer
TestStand ActiveX controls become invisible in the Visual Studio 2005 or Visual Studio 2008 C# designer when you drag the controls into or out of a panel control. This issue is a known issue with Microsoft Visual Studio and ActiveX controls in general.

Workaround: Close and reopen the designer to make the controls visible again. If you are using ActiveX controls in a user control, you can call the Hide and Show methods on each ActiveX control in the OnCreateControl event.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51176
478CHKRA

Return
Error when selecting a Button image
Visual Studio 2005 generates the error message "Parameter is not valid" when you attempt to select an icon file as the image for a TestStand User Interface Button control and the icon file contains only a 16-bit color image.

Workaround: Set the icon image programmatically at run time or load an icon file that contains a 256-color image.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51321
47JBHTIA

Return
MFC-based TestStand User Interfaces can crash when used with the Microsoft Team Foundation Server SCC provider
TestStand User Interfaces based on the Microsoft Foundation Class (MFC) might crash when you use the Workspace Browser dialog box with the Microsoft Team Foundation Server SCC provider.

Workaround: Programmatically install a different message filter. Contact NI Support for more information.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
52829
4CGDKAB8

Return
.NET user interfaces shut down without prompting to save
The C# and Visual Basic .NET user interfaces shut down without prompting to save when Windows shuts down.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
98173

Return
Using Step Out within Visual Studio might cause a warning
When you perform a step over or step out operation from within Visual Studio for the first execution of a .NET debug session, Visual Studio launches a warning that no source code is available for the current location.

Workaround: Click the Continue button.

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
158302

Return
Microsoft Visual Studio 2005 might hang while debugging a TestStand User Interface when loading symbols for Microsoft Internet Explorer 8
When you debug an application with Microsoft Visual Studio, you can define a symbol server from which Visual Studio can download module symbols. If Microsoft Internet Explorer 8 is installed, Visual Studio might hang when trying to download the debug symbols for rasapi32.dll while launching a TestStand User Interface.

Workaround: Complete the following steps to work around the issue.
  1. In Visual Studio 2005, select Tools»Options to launch the Options dialog box.
  2. Expand the Debugging option and select Symbols to display the Symbols panel, and temporarily disable debug symbols.
  3. Launch the TestStand User Interface.
  4. In Visual Studio, enable debugging symbols when the user interface is running.


Reported Version: 4.2    Resolved Version: N/A    Added: 05/18/2009
158838

Return
Microsoft Visual Studio always uses the help for the latest version of TestStand if more than one version of TestStand is installed
If you install more than one version of TestStand on a computer that also has Microsoft Visual Studio installed, Visual Studio always uses the most recent version of the TestStand help, regardless of which version of TestStand is active.

Workaround: N/A

Reported Version: 4.2    Resolved Version: N/A    Added: 05/18/2009
250286

Return
devenv.exe process continues to run after you close Microsoft Visual Studio 2010 using the close (X) button
Devenv.exe process continues to run after you close Visual Studio 2010 using the close (X) button if TestStand launched the application when you clicked the Step Into button on the Debug toolbar in the sequence editor.

Workaround: Stop debugging before you close Visual Studio, select File>Exit to close Visual Studio, manually attach Visual Studio to TestStand before you perform the Step Into operation, or manually close the devenv.exe process using the Microsoft Windows Task Manager.

Reported Version: 2010    Resolved Version: N/A    Added: 08/01/2011
287170

Return
You might receive Error 1 "Interop Type Cannot Be Embedded" when you reference the TestStand API in Microsoft Visual Studio 2010
Refer to the National Instruments support article, Error 1 "Interop Type Cannot Be Embedded" When Referencing the TestStand API in a New Visual Studio 2010 Project that Targets the .NET 4.0 Framework for more information about this issue.

Workaround: Refer to the National Instruments support article, Error 1 "Interop Type Cannot Be Embedded" When Referencing the TestStand API in a New Visual Studio 2010 Project that Targets the .NET 4.0 Framework for more workarounds for this issue.

Reported Version: Universal    Resolved Version: 2013    Added: 08/01/2011
303631

Return
Attempting to build a TestStand User Interface in Microsoft Visual Studio 2010 might result in an error when you target the .NET Framework 2.0–3.5
Refer to the National Instruments KnowledgeBase article 5NK6NKXU, Why do I Receive an Error when Using Visual Studio 2010 to Build a TestStand User Interface?, located at http://digital.ni.com/public.nsf/allkb/4AED737DA540A036862578D400457F66, for more information about this issue.

Workaround: Refer to the National Instruments KnowledgeBase article 5NK6NKXU, Why do I Receive an Error when Using Visual Studio 2010 to Build a TestStand User Interface?, located at http://digital.ni.com/public.nsf/allkb/4AED737DA540A036862578D400457F66, for information about workarounds for this issue.

Reported Version: 4.0    Resolved Version: N/A    Added: 08/01/2011
Miscellaneous
100723

Return
Loading a type with a reference to itself causes a crash
TestStand crashes when loading a file if TestStand resolves a type conflict in such a way that the type contains an instance of itself.

Workaround: N/A

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
101285

Return
Configure operation for an IVI Dmm step might fail when using the Temperature Measurement extension
The Configure operation for an IVI Dmm step fails if you enable the Temperature Measurement extension on the Extensions tab for the Configure operation of the Edit IVI Dmm Step dialog box and the instrument does not support all three temperature sub-extensions.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
102490

Return
Break on First Step incorrectly causes Step Into
The Break on First Step debugging option in the Execute menu incorrectly performs a Step Into operation on the module that the first step in a hidden execution calls.

Workaround: N/A

Reported Version: 3.5    Resolved Version: N/A    Added: 05/26/2008
124968

Return
Error when running two instances of the Java example step type asynchronously
Running the Java example step type in two executions can generate an error if the first execution that uses the step type completes after the second execution that uses the step type.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
125444

Return
Saving a sequence file as TestStand 3.0 or earlier might cause type conflicts
Type conflicts occur for built-in step types when you load a sequence file saved in TestStand 4.1 or later to be compatible with TestStand 3.0 or earlier and the sequence file contains built-in step types attached to but not used in the sequence file.

Workaround: N/A

Reported Version: 4.2    Resolved Version: N/A    Added: 05/26/2008
128019

Return
Workspace File Documentation tool incorrectly specifies a modification date for VIs in LLBs
The Workspace File Documentation tool incorrectly indicates a modification date of 12/31/1600 6:00:00 PM for VIs that reside in LLBs.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
164437

Return
Internet Explorer control TestStand uses might leak handles or crash if the control cannot find the XML style sheet
The Microsoft Internet Explorer control that TestStand applications use to display XML reports might leak handles or crash when the control cannot find the style sheet you specify in the Report Options dialog box and the control attempts to display XML report files.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
164491

Return
ActiveX EXE servers that launch dialog boxes can cause TestStand to hang if TestStand also launches a dialog box
ActiveX EXE servers that launch a dialog box and call any TestStand API function that launches a second dialog box while the first dialog box is still active must create the first dialog box in a thread initialized as single-threaded apartment for the TestStand dialog box to function correctly and to prevent TestStand from hanging.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
35247
46REB4YL

Return
Error when checking out a project file
When you check out a project file, TestStand incorrectly attempts to check out files under the project file in the workspace that are not under source code control (SCC). TestStand returns an error if you do not exclude these files from the check out operation.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
41115
4D59O7YL

Return
HTML reports do not display correctly in Mozilla Firefox
TestStand HTML reports do not show the correct fonts in Mozilla Firefox.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
45334
4I5A0FOS

Return
Turning off BSTR cache causes IVI error
When you turn off the Windows BSTR cache by setting the system environment variable OANOCACHE to 1, IVI returns errors to TestStand when retrieving the names of IVI components. The IVI Compliance Package 4.0, which is installed with the August 2009 NI Device Drivers, fixes this issue.

Workaround: N/A

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
48272
3QG976G0

Return
Incorrect suspension location when disabling tracing into callbacks
TestStand suspends an execution in a subsequence that the Post-Step callback calls when you disable tracing into callbacks.

Workaround: N/A

Reported Version: 3.1    Resolved Version: N/A    Added: 05/26/2008
50593
45KK5S00

Return
File dialog box can leak a USER object
The TestStand File dialog box can leak a Windows USER object.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
50996
46Q8EUIA

Return
IVI Fgen step might not store waveform data
  1. When you import a waveform while editing a Configure operation of an IVI Fgen step, the Edit IVI Fgen Step dialog box might not store the waveform data with the step.
  2. Executing an IVI Fgen step returns an error if the step configures the instrument to load a waveform using data stored with the step.
  3. If you browse to a file to configure the step to load the waveform from a file, the step might not save the filename setting.


Workaround:
  1. Immediately close the dialog box after you import the data to work around this issue.
  2. Configure the step to load the waveform from a file to work around this issue.
  3. You must edit the filename in the path control to ensure the step saves the changes to the filename setting.


Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
ID Known Issue
51040
4759DCB8

Return
Incorrect execution arrow position when interactively executing steps
The execution arrow can appear in the wrong location after interactively executing steps if you previously suspended an execution on a step because of a watch breakpoint, post action breakpoint, or run-time error breakpoint. In addition, a run-time error can occur if you also set the next step to another step in a different step group and the step index of the step at which you originally suspended exceeds the number of steps in the new step group.

Workaround: When this error occurs, you must restart TestStand.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51161
47BK2TUZ

Return
SequenceFilePreInteractive and SequenceFilePostInteractive callbacks do not execute when run interactively
TestStand does not call the SequenceFilePreInteractive and SequenceFilePostInteractive callbacks when running a step interactively using a process model.

Workaround: N/A

Reported Version: 3.5    Resolved Version: 2013    Added: 05/26/2008
51295
47891JJ6

Return
Property Object leak occurs when calling a remote sequence that errors
When you enable the Report Object Leaks options in the Debug Options dialog box that you access from the Preferences tab of the Station Options dialog box, TestStand property objects leak if you call a remote sequence and a run-time error occurred because you passed extra parameters to the sequence.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51427
47TD3KB8

Return
Incorrect suspension point when stepping out of a client sequence file
TestStand suspends an execution in a process model callback instead of suspending in the model entry point sequence when you step out of a client sequence file.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
52274
4AJA99YL

Return
Saving a sequence file with Wait steps as TestStand 2.0.1 or earlier might result in an error
If you save a sequence file in the TestStand 2.0.1 or earlier format and the file contains Wait steps configured to wait on a thread or execution of a sequence call, when you execute the sequence file in the earlier version of TestStand, TestStand returns a run-time error that indicates the Wait step attempted to wait on a sequence call that has not yet run or that is not a multithreaded sequence call.

Workaround: Manually reconfigure the Wait steps.

Reported Version: 3.0    Resolved Version: N/A    Added: 05/26/2008
96016

Return
Legend in the Sequence Hierarchy window is cut off
TestStand might truncate the legend in the Sequence Hierarchy window when you save the hierarchy to disk.

Workaround: N/A

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
132872

Return
Property Loader step does not resize arrays when loading properties
The Property Loader step can load arrays but does not resize the PropertyObject when doing so. If the array in the file is larger than the TestStand array PropertyObject, an error occurs.

Workaround: Ensure the TestStand PropertyObject into which the array is being loaded is large enough to accept the array in the file. You can resize the array in a pre-expression of the Property Loader step if necessary.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
132943

Return
XML Packaging Utility fails on a multibyte operating system with English (US) regional settings
Using the XML Packaging Utility to package a TestStand XML report and its style sheet returns an error if you are using a multibyte operating system but have the English (US) regional settings selected.

Workaround: Change to the native regional settings to prevent this error.

Reported Version: 4.2    Resolved Version: 2013    Added: 05/18/2009
141627

Return
HTML, XML, and ATML reports do not preserve formatting when displaying string values that contain LF('\n'), CRLF('\r\n'), or whitespace characters
Reports based on the HTML and XML stylesheet are transformed into HTML when displayed in the Report pane or in a browser. Whitespace characters, such as multiple spaces, and line breaks do not display in the report because XML parsers strip them out when displaying them displaying HTML.

Workaround: You can manually convert line break characters to the string <br/> if you intend to generate an HTML report. You can similarly convert multiple whitespace characters into &nbsp; characters.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
143996

Return
Ignoring unique step IDs with the TestStand Differ application does not ignore unique IDs in expressions
The TestStand Differ application flags the differences of unique step IDs in expressions, such as post actions or pre-expressions, even if you enabled the Ignore Unique Step IDs option in the Differ window.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
149883

Return
Importing a property from a .xls file using a Property Loader step does not import the full property value if the cell contains comma
If a text cell in a Microsoft Excel spreadsheet has a value with a comma in it, the Property Loader step imports only the text after the last comma and not the full text of the cell. For example, if a cell contains the value 10,11,12,13 the Property Loader step imports only 13. This behavior occurs because the Property Loader step uses expressions to assign values, such as in Locals.myLocal = (10,11,12,13). However, the TestStand expression language uses commas to separate expressions within an expression, so numbers within the parentheses are considered a set of expressions separated by comma. When a series of expressions separated by commas exist within an expression, the result of evaluating the expression is the result obtained from evaluating the last expression. For example, if the last expression is the number 13, the value assigned to the property is 13.

Workaround: Add quotes around the string to force the Property Loader step to consider the text as a string instead of a series of expressions. When you use the Property Loader step to import text properties, the step imports the text as a string automatically.

Reported Version: 3.0    Resolved Version: N/A    Added: 05/18/2009
150427

Return
Switching from a literal path to an expression in the Configure Call Executable dialog box does not refresh the found path display
If you specify a path literal in any of the path controls in the Configure Call Executable dialog box in a TestStand User Interface, the found path control, located below the File Pathname control, updates to show the full path. If you enable the Specify File Path by Expression option, specify a new expression or modify an existing expression, and then disable the Specify File Path by Expression option, the found path control does not update but continues to show the previous full path. This issue affects all path controls that have a found path control below them in the Configure Call Executable dialog box. This behavior does not occur on the Call Executable edit tabs on the Step Settings pane in the TestStand Sequence Editor.

Workaround: Close and relaunch the Configure Call Executable dialog box to refresh the full path display or edit the path again, and tab off of the control.

Reported Version: 4.2    Resolved Version: 2013    Added: 05/18/2009
159453

Return
Loading a TestStand 2.0 sequence file that contains ActiveX Adapter steps results in an error after running a user interface in LabVIEW more than once
Loading a TestStand 2.0 sequence file that contains steps configured to use the ActiveX Adapter can generate an "Unknown type name 'AutomationStep' " error after running a user interface in the LabVIEW development environment more than once. The error occurs because the TestStand Engine does not properly reregister required types to open the older sequence file.

Workaround: Shut down LabVIEW before running the user interface and opening the older file.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
159809

Return
Import/Export Properties dialog box does not persist some settings
When you close and then relaunch the Import/Export Properties dialog box, most settings are saved so you can easily export a limits file again. However, the Sequence option on the Properties tab does not persist correctly, which might cause an existing limits file to become invalid after exporting again.

Workaround: Verify that the Sequence option on the Properties tab is correct every time you launch the Import/Export Properties dialog box before you exporting the settings.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
188160

Return
Setting the HTBasic Working Directory option to "Subroutine file directory" on the HTBasic Module tab or in the HTBasic Adapter Configuration dialog box does not properly set the HTBasic working directory
Selecting "Subroutine file directory" for the HTBasic Working Directory option on the HTBasic Module tab or in the HTBasic Adapter Configuration dialog box does not properly set the HTBasic working directory to the directory where the subroutine file of the step resides.

Workaround: Select "Use specified directory" for the HTBasic Working Directory option and browse to the directory that contains the subroutine file of the step or use the MSI function in an HTBasic subroutine to change the HTBasic working directory from within the subroutine file.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
189528

Return
Perforce 2009.1 and 2009.2 client causes TestStand to crash when closing a workspace file
If you configure source code control (SCC) to use the Perforce SCM Provider, TestStand loads the Perforce SCC DLL when you open a workspace file and unloads the DLL when you close the workspace file. If you use the Perforce 2009.1 client, TestStand might crash after unloading the Perforce SCC DLL when you close a workspace file. If you use the Perforce 2009.2 client, a delay might exist before a possible TestStand crash after you close the workspace file. Use the new Perforce 2010.1 client or the previous 2008.2 client to fix this issue.

Workaround: Use the new Perforce 2010.1 client or the previous 2008.2 client.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
192247

Return
When you enable On-The-Fly reporting and TestStand records a result after the MainSequence completes, the report shows the UUTStatus as "Running"
When you enable On-The-Fly reporting, if the process model executes steps that are configured to record results, if the sequence calling the steps does not enable the Disable Result Recording for All Steps option, and if the steps execute after MainSequence completes executing, the report shows the final UUT Status as "Running".

Workaround: Enable the Disable Result Recording for All Steps option of the Sequence Properties dialog box for any sequence or subsequence in a client sequence file that MainSequence does not call.

Reported Version: 3.5    Resolved Version: N/A    Added: 12/11/2009
198622

Return
TestStand shows the Report Tab after an execution completes for ASCII and HTML report formats even when you disable report generation
If you select ASCII Text File or HTML Document as the Report Format in the Report Options dialog box and you enable the Disable Report Generation option, when you select Test UUTs or Single Pass from the menu bar, the Report tab becomes active at the end of the execution and includes the text "Report generation is disabled." This behavior does not exist for the XML Document or ATML Report Document report formats.

Workaround: If you do not want to generate a report for an execution and do not want the Report tab to display at the completion of the execution, modify the Report Options dialog box to disable the Disable Report Generation option, change the Report Format to XML Document or ATML Report Document, and then enable the Disable Report Generation option again.

Reported Version: 3.5    Resolved Version: N/A    Added: 12/11/2009
205554

Return
Microsoft Windows 7 Most Recently Used (MRU) list for pinned TestStand application includes all files opened with the Open File dialog box
When you pin a TestStand application, such as the sequence editor or a user interface, to the Taskbar in Windows 7, the MRU list includes any files you opened with the Open File dialog box in the application.

Workaround: N/A

Reported Version: 4.1    Resolved Version: N/A    Added: 08/01/2011
213835

Return
Using foreign characters in XML report style sheets might result in errors during report generation
Using some foreign characters in the XML report style sheets might result in the "An invalid character was found in text content." error.

Workaround: Use the HTML code equivalent for the foreign character or add the appropriate encoding attribute to the <xsl:output> tag of the style sheet.

Reported Version: 4.2.1    Resolved Version: 2013    Added: 08/01/2011
216539

Return
Using the Property Loader step to import two or more step properties with the same name but different type or representation results in a type mistmatch error
If a sequence contains 2 or more steps that contain a property with the same name but different type or representation and you use the Property Loader step to import the property, TestStand returns a type mismatch error because TestStand sets the expected type and representation of the property to the type and representation of the property found in the first step in the sequence.

Workaround: N/A

Reported Version: 3.0    Resolved Version: N/A    Added: 08/01/2011
301259

Return
TestStand 2010 SP1 Migration Utility does not support redirecting paths that exist within a string when the string is not a valid path
The TestStand 2010 SP1 Migration Utility does not support redirecting paths that exist within a string when the string is not a full or valid path. For example, the migration utility does not redirect the path "C:\Program Files\National Instruments\TestStand 2010" in Connection String Expression of the Database Options dialog box.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 08/01/2011
35026
47LCM4G0

Return
On-the-fly database logging leaks memory when an execution repeatedly creates new threads
On-the-fly database logging slowly leaks memory when executions repeatedly use a Sequence Call step to create new threads.

Workaround: N/A

Reported Version: 4.0    Resolved Version: 2013    Added: 06/12/2012
360245

Return
The TestStand Sequence Analyzer does not honor code module load and unload settings
When analyzing a sequence file, the TestStand Sequence Analyzer loads code modules as part of the analysis process. However, the analyzer does not honor any load or unload options for the code modules. Instead, the analyzer preloads all code modules before analysis and does not unload them after analysis completes. This can cause an error in the following scenarios:
  • A sequence can load two different VI code modules with the same name as long as you configure the code modules to be unloaded dynamically. However, the analyzer reports that the second code module could not be loaded because the first code module remains in memory during analysis.
  • If you have configured the analyzer to analyze before executing, VI code modules the analyzer preloads can conflict with dynamically loaded modules in the sequence. In this case, TestStand returns an error similar to the following error:

    Unable to load VI '<VI 1 path>'.
    LabVIEW already has the VI '<VI 2 path>' loaded and cannot load different VIs with the same name.


Workaround: You can avoid the second scenario by disabling the Analyze File Before Executing option in the Sequence Analyzer Options dialog box. If you analyze the sequence manually, be sure to select File»Unload All Modules before executing.

Reported Version: 2010    Resolved Version: 2013    Added: 07/25/2012
363354

Return
The TestStand Sequence Analyzer reports an internal error when analyzing expressions with an incorrectly indexed array
If you analyze a sequence that contains an expression that references an array with the incorrect number of indexes, such as the expression array[0] for a two-dimensional array, the sequence analyzer reports the Internal Error: Fatal error occurred during analysis error.

Workaround: Correct any expressions with incorrectly indexed arrays.

Reported Version: 2010    Resolved Version: N/A    Added: 07/26/2012
363524

Return
The += operator might not function correctly for appending elements to an array
When you use the += operator to append to an array, TestStand might not correctly set the parent of the added elements, which can cause errors when you attempt to access or delete the elements. This behavior occurs when the following conditions are true:
  • You are using an array literal to build the array being concatenated.
  • The array literal contains references to existing properties.
For example, this behavior occurs for the expression Locals.myArray += {Locals.myNumber}.

Workaround: To append an element to an array, use the SetNumElements expression to increase the size, and then set the newly created element to the desired value, as shown in the following example expression: SetNumElements(Locals.myArray, GetNumElements(FileGlobals.DynamicArray) + 1), Locals.myArray[GetNumElements(Locals.myArray) - 1] = Locals.DemoStructure

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 07/26/2012
312695

Return
The Tcl example step might return error -14004 when executed from TestStand
Refer to the National Instruments KnowledgeBase article, http://digital.ni.com/public.nsf/allkb/120923C96FEBBDA6862579910074AB9F?OpenDocument, for more information about this error.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/29/2012
345032

Return
TestStand cannot save a TestStand Sequence Analyzer project file if the file specifies the Hidden attribute in the Windows file system
If you attempt to save an existing sequence analyzer project file, TestStand displays a access denied error if the file specifies the Hidden attribute in the Windows file system.

Workaround: Ensure that the sequence analyzer project file does not specify the Hidden attribute in the Windows file system when you save the project file.

Reported Version: 2010    Resolved Version: N/A    Added: 07/29/2012
348612

Return
A warning can appear when you first launch TestStand after you use the TestStand Migration Utility
After using the migration utility to migrate settings to a newer version of TestStand, TestStand might display the Toolbar data out of date in file: C:\Users\Username\AppData\Local\National Instruments\TestStand 2012\layout_current.bin error when you first launch TestStand. After you dismiss the warning, TestStand launches with the correct imported layout despite the warning.

Workaround: To avoid this warning, deselect layout_current.bin when you use the migration utility. If you do encounter the warning, you can safely ignore it.

Reported Version: 2012    Resolved Version: N/A    Added: 07/29/2012
214265

Return
Launching the Resource Usage Profiler causes TestStand to crash if search directories reference another TestStand version
If you configure the TestStand search directories such that the installation directory for another version of TestStand precedes the installation directory for the current TestStand version, selecting Tools»Profile Resource Usage causes TestStand to crash.

Workaround: Avoid adding paths to other TestStand versions to the search directories.

Reported Version: 4.1    Resolved Version: N/A    Added: 02/05/2013
327928

Return
TestStand does not update to display changes to switch configuration
TestStand does not automatically refresh the switch configuration when it is saved in another process, such as Measurement & Automation Explorer (MAX). The Switch Executive Virtual Device drop-down menu does not update unless you restart TestStand.

Workaround: You can force the step to reload the configuration information by disabling and then re-enabling the Enable Switching option on the Switching panel of the Properties tab of the Step Settings pane.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 02/05/2013
365348

Return
The UUT Information dialog box for the Parallel process model incorrectly restricts certain users from terminating or aborting test sockets
Users with only Terminate and Abort permissions cannot click the Terminate and Abort buttons in the UUT information dialog box for the Parallel process model. The buttons are disabled unless the user has all available permissions through the GrantAll privilege.

Workaround: You can manually fix this issue by replacing all instances of Priv_Abort with Abort and Priv_Terminate with Terminate in the paralleluutdlg.c source file, located in the <TestStand>\Components\Models\TestStandModels directory. After making this change, recompile the modelsupport2.prj file, located in the same directory.

Reported Version: 4.2.1    Resolved Version: 2013    Added: 02/05/2013
366317

Return
Property Loader step incorrectly imports strings that contain commas when you use a comma delimiter
If you attempt to import a string property using a Property Loader step or the Import/Export Properties dialog box and the string contains a comma, the Property Loader step or Import/Export Properties dialog box incorrectly interprets the comma as the end of the string. This behavior occurs despite the comma being enclosed in quotes, and causes an evaluation error similar to the following:

Error evaluating expression:RunState.InitialSelection.SelectedFile.Data.Seq["MainSequence"].Locals.Local = (""test") Unexpected token: test

This error occurs only when you configure the Property Loader step to use a comma delimiter.

Workaround: Use the default tab delimiter.

Reported Version: 4.0    Resolved Version: N/A    Added: 02/05/2013
366735

Return
Copying and pasting multiple watch expressions can cause the Watch View pane to error in certain cases
If you select multiple watch expressions on the Watch View pane and some expressions you select are valid but others are invalid, and you then attempt to copy and paste the expressions, TestStand returns the Object reference not set to an instance of an object error. An invalid watch expression displays an "X" icon to the left of the expression.

Workaround: N/A

Reported Version: 2012 SP1    Resolved Version: 2013    Added: 06/28/2013
397573

Return
The ProcessCleanup callback executes even if the ProcessSetup callback is skipped due to an error
If an error occurs in the Begin entry point in a process model plug-in, the process model does not call the ProcessSetup callback in the client file, but it does call the ProcessCleanup callback. TestStand 2013 fixes this behavior by calling only the ProcessCleanup callback if the ProcessSetup callback executes.

Workaround: N/A

Reported Version: 2012 SP1    Resolved Version: 2013    Added: 06/28/2013
Reports
35106
47FE0BG0

Return
Incorrect indentation might occur when you generate a report on-the-fly
When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box to generate a report on-the-fly, the report incorrectly indents step results that follow a Sequence Call step that creates a new thread.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
41730
4DQDAQYL

Return
Generating reports on-the-fly with asynchronous threads might cause an error
When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box to generate a report on-the-fly, TestStand returns a run-time error when the asynchronous thread continues to execute after the process model entry point completes.

Workaround: N/A

Reported Version: 4.0.1    Resolved Version: N/A    Added: 05/26/2008
43782
4GGCQA00

Return
Module execution times are not included in an XML report
TestStand XML reports that use the horizontal style sheet do not reflect the setting of the Include Execution Times option on the Contents tab of the Report Options dialog box.

Workaround: N/A

Reported Version: 4.0.1    Resolved Version: N/A    Added: 05/26/2008
358354

Return
The offline results processing utility can crash if launched while another instance of the utility is closing
If you launch the offline results processing utility while another instance of the utility is closing, the new instance of the utility might crash.

Workaround: Launch the offline results processing utility again.

Reported Version: 2012    Resolved Version: N/A    Added: 07/25/2012
206892

Return
Enabling the Log option in the VI Parameter Table does not function correctly for some LabVIEW data types
If a LabVIEW code module specifies a parameter of data type digital waveform, digital data, or dynamic data, enabling the Log option in the VI Parameter Table does not log the parameter if you do not provide an argument in the Value column of the VI Parameter Table.

Workaround: Ensure that any parameters for which you enable the Log option also specify an argument in the Value column.

Reported Version: 4.2    Resolved Version: N/A    Added: 07/26/2012
357691

Return
ATML reports generated on non-English operating systems contain an improperly formatted start date
The ATML Test Results and Session Information schema requires that timestamps use the yyyy-mm-ddThh:mm:ss format. On a computer with a non-English operating system, the localized date is not properly converted to the English format the ATML Test Results and Session Information schema requires.

Workaround: Modify the ATML style sheet you are using to correctly display the start date.

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 07/26/2012
358127

Return
An error can occur when generating an On-The-Fly report when a sequence call uses a new thread and executes a post action
The Error -17500: Operation Failed error can occur when you run a sequence in which all of the following conditions are true:
  • You enable report generation and you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box
  • The sequence contains a Sequence Call step configured to use a new thread
  • You configure a post action for the Sequence Call step to call a subsequence
  • If you ignore this error, the report still generates correctly.

    Workaround: To call the subsequence, use a second Sequence Call step that specifies a precondition instead of using a post action.

    Reported Version: 2012    Resolved Version: N/A    Added: 07/26/2012
224640

Return
Terminated subsequences called in a new execution have a status of Passed
If you call a sequence and select the Use New Execution execution option on the Sequence Call Module tab, you can obtain the results of the called sequence by using a Wait step. However, if the called sequence execution is terminated, the Wait step reports the sequence result as Passed instead of Terminated.

Workaround: N/A

Reported Version: Universal    Resolved Version: N/A    Added: 07/29/2012
322859

Return
The TS.StartTime property is incorrect when used with remote instances of the TestStand Engine
The TS.StartTime property in the ResultList array contains the time in seconds since the creation of the TestStand Engine. However, when you execute steps in a remote instance of the TestStand Engine, this property uses the creation time of the remote engine rather than the local engine, which can cause calculations of absolute time to be incorrect if the calculation is based on the engine creation time obtained from the Seconds() function.

Workaround: N/A

Reported Version: Universal    Resolved Version: N/A    Added: 07/29/2012
347289

Return
XML reports might display an incorrect number of results and incorrect failure chain information
When you generate a XML report and do not use on-the-fly report generation, the Number of Results value and the failure chain information can be incorrect if the sequence file uses Engine callbacks. The report includes the steps in these callbacks in the Number of Results value but does not include the results for the steps in the report. In addition, the failure chain in the report might also incorrectly contain references to steps in the Engine callbacks.

Workaround: Enable on-the-fly reporting for the XML report, or use a different report format.

Reported Version: 3.0    Resolved Version: 2013    Added: 07/29/2012
347733

Return
The TestStand Offline Results Processing Utility loads slowly when the inbox or outbox contains a large number of files
If the inbox or outbox of the offline results processing utility contains 50,000 or more files, the utility can appear unresponsive and slow. The severity of the problem increases as the number of files increases.

Workaround: If the inbox contains a large number of files, allow the utility time to process the files or move the files to another location on disk. If the outbox contains a large number of files, move the files to another location on disk.

Reported Version: 2012    Resolved Version: 2013    Added: 07/29/2012
347941

Return
The offline results processing utility does not reload modified result processing plug-in files
If you make changes to a result processing plug-in while the offline results processing utility is open and the utility loaded the plug-in before you made the change, the utility does not reload the new version of the file.

Workaround: Close and reopen the offline results processing utility to load the most recent version of the plug-in.

Reported Version: 2012    Resolved Version: N/A    Added: 07/29/2012
348820

Return
The offline results processing utility can hang when you use a result processing plug-in that causes a run-time error
If you use a result processing plug-in that causes a run-time error in the PreBatch callback with the offline results processing utility, the utility appears to hang with no indication that an error has occurred.

Workaround: Process the TestStand result file (.tsr) directly from the TestStand Sequence Editor. TestStand displays the standard run-time error dialog box to help you debug the plug-in.

Reported Version: 2012    Resolved Version: N/A    Added: 07/29/2012
365232

Return
ATML report hyperlinks do not function for filenames that contain multibyte characters
If an ATML report contains hyperlinks to sequence files, the links do not function if the filenames contain multibyte characters. This issue occurs only when you are using a multibyte operating system.

Workaround: Use only standard characters for sequence file paths that you link from an ATML report.

Reported Version: 2012    Resolved Version: 2013    Added: 02/05/2013
367731

Return
When you specify a report path by expression, the <Unique> macro does not function if the path does not exist
When you specify a report path by expression, the <Unique> macro does not function if the path does not exist. If you are simultaneously generating multiple reports using the same expression, the reports can be overwritten because the report name will not be unique.

Workaround: Ensure that report paths exist before you execute the sequence, or use a different macro, such as <FileTime>, to ensure a unique filename.

Reported Version: 4.2    Resolved Version: 2013    Added: 02/05/2013
366100

Return
The Basic Step Time Report example result processing plug-in does not function if Microsoft Visual Basic for Applications is not installed
Refer to the National Instruments support article, Knowledgebase 65TBQIUB: TestStand Basic Step Time Report Example Result Processing Plug-in Is Not Generating the Excel Report, for more information about this issue.

Workaround: N/A

Reported Version: 2012    Resolved Version: 2013    Added: 03/05/2013
413424

Return
On-the-fly HTML and ASCII reports generated with a result filtering expression contain unexpected duplicates of certain results
Unexpected duplicate results can appear in reports if all the following conditions are true:
  • You are generating reports in HTML or ASCII format
  • You are using on-the-fly reporting
  • You set the Select a Report Generator for Producing the Report Body option on the Contents tab of the Report Options dialog box to Sequence.
In this case, TestStand replaces a result that you expect TestStand to filter with a duplicate entry of the previous unfiltered result.

Workaround: Set the Select a Report Generator for Producing the Report Body option on the Contents tab of the Report Options dialog box to DLL.

Reported Version: 2012    Resolved Version: N/A    Added: 06/25/2013
381042

Return
Processing Offline Result files on a separate machine can cause a "Drive Not Ready Error" error when generating reports
The default results processing configuration the TestStand Offline Results Processing Utility uses specifies the client sequence file location as the report location. If an instance of the offline results processing utility on a different computer uses configuration, the sequence file path is likely no longer valid, and the Drive Not Ready Error error might occur.

Workaround: Change the offline results processing configuration to use a valid directory to store report files.

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
390043

Return
ATML reports do not display icons correctly for sequence files that contain Japanese characters
When you execute a sequence file with Japanese characters in the file path on a Japanese operating system, the ATML report cannot load the images for the expand/collapse button and the error icon.

Workaround: N/A

Reported Version: 2012    Resolved Version: 2013    Added: 06/28/2013
390048

Return
ATML 5 and XML reports do not display in Microsoft Internet Explorer 9 when the style sheet path contains Japanese characters
If you generate ATML 5.0 or XML reports that specify a style sheet path that contains Japanese characters, the report does not display correctly in Microsoft Internet Explorer 9. In this case, the report displays the raw XML text.

Workaround: You can use any of the following workarounds to avoid this issue:
  • Use the compatibility mode feature in Internet Explorer 9.
  • Place the style sheet in a directory that does not contain Japanese characters in the file path.
  • Use the XML Packaging utility to pack the XML report and all dependencies.


Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
400978

Return
Errors in a result processing plug-in can cause the TestStand Offline Results Processing Utility to hang
When the TestStand Offline Results Processing Utility processes files, a hang can occur if a run-time error occurs in a result processing plug-in.

Workaround: Use the TestStand Offline Results Processing Utility results configuration in the TestStand Sequence Editor to troubleshoot and fix the run-time error in the plug-in.

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
403032

Return
TestStand does not provide a macro for including a part number in a custom report file path
When you use the Specify Report File Path by Expression option on the Report File Pathname tab of the Report Options dialog box, TestStand provides several macros so you can include TestStand data in the report file path. TestStand does not provide a macro for including the part number.

Workaround: Use one of the following TestStand expressions to access the PartNumber property:
  • Sequential model—PropertyExists("Parameters.UUT.PartNumber")?Parameters.UUT.PartNumber:"")
  • Batch and Parallel models—PropertyExists("Parameters.TestSocket.UUT.PartNumber")?Parameters.TestSocket.UUT.PartNumber:"")


Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
409938

Return
ATML reports do not display icons correctly for sequence files that contain Japanese characters
When you execute a sequence file with Japanese characters in the file path on a Japanese operating system, the ATML report cannot load the images for the expand/collapse button and the error icon. TestStand 2013 fixes this issue for all stylesheets except for tr5_horizontal.xsl.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 06/28/2013
TestStand Deployment Utility
52184
4ADMCJ77

Return
Building a deployment before LabVIEW completely launches might cause an error
Building a deployment can return an error when the output of the deployment generates LLB files before LabVIEW completely launches. This problem is known to occur in LabVIEW versions 8.5 or later.

Workaround: Launch LabVIEW and wait until LabVIEW has finished initializing before you build a deployment.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
135514
415AQUM0

Return
TestStand Deployment Utility deploys files to an incorrect location if a file path contains multibyte characters and the installation language does not match the target computer language
If you choose to install files in a location that contains multibyte characters or if the filename contains multibyte characters, the files might be installed to an incorrect location under either of the following conditions:
  • If the installer language is set to English.
  • If the installer language setting does not match the language setting of the target computer.
You cannot deploy multibyte file paths using an installer set to English.

Workaround: If you must deploy files with multibyte characters or if the install location contains multibyte characters, you must verify that the installer language matches the language setting of the target computer.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
ID Known Issue
141991

Return
TestStand Deployment Utility does not adequately document error codes -40 and -30
Error codes -40 and -30 can occur in the TestStand Deployment Utility when building additional NI installers into an installer. Refer to the National Instruments Web site at ni.com/ask to contact National Instruments Support for more information after attempting the workarounds documented below.

Workaround: If you receive the error "Error: Internal error. (Error code -40)" try removing or renaming the <National Instruments>\Shared\MDF\Manifests directory and repairing all installed NI software. If you receive the error "Error: Improper function call or command line argument. (Error code -30)" try deleting all cached installers in the <All Users>\Application Data\National Instruments\MDF\ProductCache directory.

Reported Version: 4.1    Resolved Version: N/A    Added: 05/18/2009
151624

Return
Deploying VIs in a LabVIEW class might not correctly link dependencies
If you deploy a LabVIEW 8.6.1 or later VI that is in a LabVIEW class, the TestStand 4.2 Deployment Utility might not correctly link dependencies of the VI. LabVIEW 2009 fixes this behavior. When using earlier versions of LabVIEW, refer to the National Instruments Web site at ni.com/info and enter the info code rdtsdiv to access the National Instruments KnowledgeBase article Building a TestStand Deployment that Includes VIs in a Class may Sometimes Produce a Bad Deployment for more information about deploying a VI in a LabVIEW class.

Workaround: Recompile the VI after you build the deployment.

Reported Version: 4.2    Resolved Version: N/A    Added: 05/18/2009
152924

Return
Deploying files after moving a .tsd file and unchecking files for deployment might change the deployment destination directories or truncate filenames
If you change the directory in which a deployment .tsd file resides and you unchecked files from being deployed after saving the .tsd file, the TestStand Deployment Utility might display truncated filenames after analyzing the files. When building, the TestStand Deployment Utility might also change the structure of the destination files, so that the structure is different compared to the structure that existed before you moved the .tsd file.

Workaround: Keep the .tsd file in the same directory in which it was created or leave at least one file checked in the topmost directory to prevent the algorithm that determines the destination directory structure from returning a different result.

Reported Version: 4.1    Resolved Version: N/A    Added: 05/18/2009
172759

Return
Including the LabVIEW 8.5.1 _exclsub.llb file in a TestStand workspace along with a sequence file that contains a LabVIEW 8.5.1 code module that calls the Report Generation Express VI results in a TestStand Deployment Utility build error
When you include the LabVIEW 8.5.1 _exclsub.llb file in a TestStand workspace and that workspace also includes a sequence file that calls one or more LabVIEW 8.5.1 code modules that use the Report Generation Express VI, the TestStand Deployment Utility returns the following build error: "Error: The following VIs or Project Libraries have duplicate names. You must change the names or add them to project libraries: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\_office\_wordsub.llb\font.ctl while Processing VIs... C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\_office\_exclsub.llb\font.ctl while Processing VIs...". However, you must include _exclsub.llb because the Report Generation Express VI dynamically calls VIs the LLB contains. The Express VI statically links to the font.ctl file, which causes a duplicate copy when you include the _exclsub.llb library in a TestStand workspace. LabVIEW 8.6 and later fix this issue.

Workaround: To build successfully, exclude the font.ctl file from the _exclsub.llb library in the Distributed Files tab of the TestStand Deployment Utility. LabVIEW 8.6 and later fix this issue.

Reported Version: 3.5    Resolved Version: N/A    Added: 12/11/2009
172793

Return
Leaving the Default Installation Subdirectory field empty in the Installer Options tab of the TestStand Deployment Utility results in a build error
If you leave the Default Installation Subdirectory field empty in the Installer Options tab of the TestStand Deployment Utility because you want the files to install in the base directory, the deployment utility returns the following message when you attempt to build: "The build contains one or more invalid paths: Invalid Default Installation Subdirectory: """

Workaround: Place a period in the Default Installation Subdirectory field to install files in the base directory.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
182127

Return
The TestStand Deployment Utility assigns the same default destination directory for two files with the same filename and file hierarchy but located on different drives
If a workspace contains two files with the same filename and file hierarchy on two separate drives (for example, C:\ and D:\), by default the TestStand Deployment Utility assigns the same destination directory for both files, which results in an "Error: The following files have conflicting destinations:" build error.

Workaround: Manually modify the destination directory for one of the files.

Reported Version: 4.2    Resolved Version: N/A    Added: 12/11/2009
191976

Return
TestStand Deployment Utility does not properly update TestStand Deployment (TSD) file paths that contain user names when you move the files and a different user loads the TSD file
If file paths of a TestStand Deployment (TSD) file, such as the Workspace File Path, contain a user name (User A's Desktop) and you move the files to a path that does not contain the user name (C:\), when a different user loads the TSD file, the TestStand Deployment Utility incorrectly updates the file paths to point to the previous path using the new user name (User B's Desktop) instead of pointing to the correct path (C:\).

Workaround: Do not store the files in paths that contain user names, such as Desktop or My Documents. Alternatively, when you move the files from a path that contains user names to a path that does not contain user names, load the TSD file with the same user to correctly update the paths.

Reported Version: 4.1    Resolved Version: N/A    Added: 12/11/2009
192254

Return
Destination directories for files you do not select in the TestStand Deployment Utility appear distorted when you convert TestStand Deployment files from an older version of TestStand to a newer version
When you load a TestStand Deployment file that was saved in a previous version of TestStand into the TestStand Deployment Utility, the destination directories on the Distributed Files tab appear distorted for files that you have not selected.

Workaround: Select and then revert the selection for the file to update the Distributed Files tab with the correct destination directory but leave the file excluded from the deployment.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
219779

Return
TestStand Deployment Utility merges CommonResults type during build without prompts
If a TestStand deployment contains sequence files that include different versions of CommonResults, the TestStand Deployment Utility automatically merges the different versions of CommonResults into one version without prompts or notifications. TestStand 2010 SP1 includes a rule in the TestStand Sequence Analyzer to report different CommonResults versions.

Workaround: Resolve type conflicts for all sequence files before deployment. TestStand 2010 SP1 includes a rule in the TestStand Sequence Analyzer to report different CommonResults versions.

Reported Version: 4.2.1    Resolved Version: N/A    Added: 04/10/2011
252650

Return
July 29, 2012TestStand Deployment Utility does not update the workspace path if you save the deployment and workspace files to the desktop then move the files
When you save workspace and deployment files on the desktop, move the files to a new location, and then load the deployment file in the TestStand Deployment Utility, the Workspace Path control expects the workspace file to be located in the Desktop directory.

Workaround: Browse to the new workspace file location.

Reported Version: 4.0    Resolved Version: N/A    Added: 08/01/2011
276342

Return
TestStand Deployment Utility fails when you build a Packed Project Library with source if a project with the same path is already in memory
The TestStand Deployment Utility incorrectly returns the following error: "Internal error code 1357 Processing VIs... Could not process LabVIEW VIs. Fix any broken VIs before rebuilding." when you build a Packed Project Library and include the source files when a project with the same path is already in memory.

Workaround: Close LabVIEW to remove all projects from memory and build the deployment again.

Reported Version: 2010    Resolved Version: N/A    Added: 08/01/2011
277891

Return
TestStand Deployment Utility returns an error when building if the TestStand directory and its VIs do not exist in the vi.lib\addons directory
If the TestStand directory and its contents does not exist in the vi.lib\addons directory of the current LabVIEW version, the TestStand Deployment Utility returns the following error when building a deployment that includes LabVIEW files: "Error: Unable to find all subVIs from saved VIs. Either a subVI is missing or the VI is not saved in the current LabVIEW version."

Workaround: If the error lists a call chain that includes the "TestStand - Deployment Utility Splash Screen.vi", close TestStand and the deployment utility and use the TestStand Version Selector to make that version of TestStand active again. Check the vi.lib\addons directory of the current version of LabVIEW to ensure that the TestStand directory exists before attempting to build the deployment again.

Reported Version: 2010    Resolved Version: N/A    Added: 08/01/2011
249171

Return
A warning can occur when you build a deployment that includes VIs that contain unsupported Microsoft Windows characters
If a deployment contains VIs that use characters that are not valid for Microsoft Windows files, such as the slash (/) or question mark (?) character, and you enable the Output VIs to Packed Project Library option in the LabVIEW VI Options dialog box, the TestStand Deployment Utility returns a warning similar to the following warning when building the deployment: Warning: Cannot update VI Path: Step '<stepName>', sequence '<sequenceName>', sequence file '<sequenceFilePath>' If you install the deployment on a target computer, the step the warning references does not not execute. This issue occurs because the paths for VIs contained within a packed project library must use only valid Windows filename characters, which is not the case for VIs within LLBs or LabVIEW libraries.

Workaround: Use only valid Windows filename characters when naming VIs and virtual folders.

Reported Version: 2010    Resolved Version: N/A    Added: 07/29/2012
276637

Return
TestStand Deployment Utility returns a non-descriptive error when the LabVIEW Application Builder in unlicensed
If you attempt to build a deployment with the Output VIs to a Packed Project Library option enabled in the LabVIEW Options dialog box, TestStand returns a non-descriptive error similar to the following:

Internal error code 1327 Processing VIs... Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error: mxLvErrorHandler.vi:1

The LabVIEW Application Builder must be licensed to successfully build a deployment.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 02/05/2013
368256

Return
TestStand Deployment Utility does not notify you if certain steps do not have a code module specified
If you attempt to deploy a sequence that contains LabWindows/CVI, C/C++ DLL, or HTBasic steps that do not have a code module specified, the TestStand Deployment Utility does not provide a warning and errors might occur when you run the sequence on the target computer.

Workaround: Before you build a deployment, use the TestStand Sequence Analyzer to verify that these steps specify a code module.

Reported Version: 2012    Resolved Version: 2013    Added: 02/05/2013
387069

Return
TestStand Deployment Utility can create multiple copies of DLL files that LabVIEW code modules reference
If you create a deployment that meets all of the following conditions, the resulting image contains two copies of the referenced DLL:
  • The deployment contains a VI that calls a DLL
  • You include the called DLL in the deployment
One copy of the DLL will exist in the destination you specify for the DLL, and a second copy will exist in the supportvis directory because the DLL is a dependency of a VI in the deployment. Any VIs in the deployment that reference the DLL will use the supportvis directory location. This behavior can cause VIs that call the DLL to break in the case that the duplicate DLL requires other DLL dependencies in a specific location because the dependent DLLs will not be moved to the support VIs directory.

Workaround: Configure the destination of any affected DLLs to be the supportvis directory to ensure that no duplicates are created. If the DLL has dependencies, add them to the deployment, and configure the destination directory to also be the supportvis directory to ensure that the dependencies are located.

Reported Version: 4.0    Resolved Version: 2013    Added: 02/05/2013
389135

Return
In the TestStand Deployment Utility, changing the installation directory of a LabVIEW packed project library causes settings to change
In the TestStand Deployment Utility, if you change the installation directory of a LabVIEW packed project library (.lvlibp), the other settings for the file (Force File to Install and Create Program Item) revert to the disabled state.

Workaround: When configuring settings for a LabVIEW packed project library, ensure that settings are correct after you change the destination directory.

Reported Version: 2010    Resolved Version: N/A    Added: 02/05/2013
410806

Return
Deployment does not include unused packed project libraries within a library when you enable the Include All Files in LabVIEW Project option
If you create a TestStand deployment that includes a LabVIEW library and the library contains a packed project library that is not a dependency of any files included in the deployment, the TestStand Deployment Utility does not include the packed project library even if you enable the Include All Files in LabVIEW Project option on the Distributed Files tab.

Workaround: Add the packed project library to the workspace from which you are deploying.

Reported Version: 2010    Resolved Version: N/A    Added: 06/28/2013
412636

Return
TestStand Deployment Utility incorrectly deploys LabVIEW projects that contain class member calls to a packed project library
When you deploy a sequence that contains a LabVIEW project that contains class member calls to a packed project library and you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine, the TestStand Deployment Utility does not update the sequence properly and some LabVIEW steps return VI Not Loadable errors.

Workaround: N/A

Reported Version: 2012    Resolved Version: 2014    Added: 06/28/2013
TestStand Engine
131253

Return
You cannot use variables with the same name as an expression constant in an expression
If you use a variable with the same name as an expression constant in an expression, TestStand returns a syntax error when evaluating the expression. The following constants are reserved names:
  • True
  • False
  • Nothing
  • PI
  • NAN
  • IND
  • INF
  • Color constants, which follow the form ts<ColorName> and are less susceptible to this issue.


Workaround: Use the GetVal API functions in an expression to interact with objects that have the same name as expression constants, such as in the function Locals.PIValue = ThisContext.AsPropertyObject.GetValNumber("Step.Result.PI",0).

Reported Version: 3.0    Resolved Version: N/A    Added: 05/18/2009
131559

Return
When a run-time error occurs in a step, the module is not unloaded from memory when you select the Unload after step executes option
A run-time error in a step causes TestStand to skip the unloading of a module if you select the Unload after step executes unload option on the Run Options tab of the Step Properties dialog box, Run Options panel of the Properties panel on the Step Settings pane, or the General tab of the Sequence File Properties dialog box.

Workaround: Use another unload option such as Unload after sequence executes if you expect a step to return a run-time error.

Reported Version: 3.5    Resolved Version: N/A    Added: 05/18/2009
135202

Return
TestStand returns the error "The TestStand service did not start up promptly" when you launch the sequence editor or a user interface
When the TestStand Engine is created, the engine checks with the National Instruments TestStand Service to ensure that external environments such as LabVIEW, LabWindows/CVI, and Microsoft Visual Studio are properly updated. If the service is not available, TestStand returns the error "The TestStand service did not start up promptly." The TestStand Service is required for this external environment setup to allow non-administrator users to properly configure these environments. The TestStand Service can sometimes be delayed while launching because a previous service hangs when starting. For example, the Windows Workstation service might hang for a few minutes on startup when trying to reconnect to mapped network drives if the drives are not immediately available. This can cause the TestStand Service to be unable to start, and if a TestStand User Interface is launched before the service starts, TestStand returns this error.

Workaround: Generally, you dismiss the error dialog box and continue to use TestStand normally, as long as you do not require the external environments to be configured. To remove the error, try to determine the offending service that is delaying the TestStand Service from starting, and see if you can correct the source of the slow start. You can also delay the launching of the offending service by marking the service as manual startup, and adding a command to the startup group to start the service after other services have been started.

Reported Version: 4.1    Resolved Version: N/A    Added: 05/18/2009
144062

Return
Calling the Module.CreateCode or Step.CreateCode methods on a .NET step or module returns an error if the methods are called from a non-STA thread
The Module.CreateCode and Step.CreateCode methods must be called from a Single Threaded Apartment (STA) thread if you are trying to create .NET code. If you do not call these methods from an STA thread, TestStand returns the following error: "Error -18500: An error occurred during Visual Studio automation: The message filter indicated that the application is busy."

Workaround: Most development environments initialize a UI thread to be an STA thread, so calling these methods from the UI thread is usually safe. Otherwise, you must manually initialize a thread to be STA, and the procedure differs with each environment.

Reported Version: 4.2    Resolved Version: N/A    Added: 05/18/2009
155319

Return
PropertyObject leaks or hangs occur on a TestStand remote sequence execution server if a sequence file has a SequenceFileUnload callback
Shutting down a TestStand User Interface that called sequences on a remote computer can cause PropertyObject leaks or hangs of the remote engine if a sequence file called remotely contains a SequenceFileUnload callback sequence. If the SequenceFileUnload callback sequence contains a dialog box and you do not dismiss the dialog box, neither the remote engine nor the client user interface exit.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
167667

Return
Clicking Yes in the "Do you want to close all opened document windows?" dialog box after you close a workspace file prevents any open sequence files from reloading when you reopen the workspace
The Reload Documents When Opening Workspace option on the Station Options Preferences tab loads the documents you had open when you last closed the workspace file. When you enable this option and you close the workspace file while sequence files are currently loaded, a dialog box prompts you to close all opened document windows. If you click Yes in this dialog box, all loaded sequence files close along with the workspace file. When you reopen the workspace file, the previously loaded sequence files do not reload. If you click No in the dialog box or if you exit TestStand, the previously loaded sequence files reload when you reopen the workspace file.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
185097

Return
Configuring a SequenceCall step to launch a new execution from within the SequenceFileLoad Engine Callback hangs the SequenceFileLoad execution when you load the sequence file
If the SequenceFileLoad Engine Callback contains a SequenceCall step configured to launch a new execution, when you load the sequence file and the SequenceCall step executes, the SequenceFileLoad execution hangs until you manually terminate it. This behavior exists only when you load the sequence file. Running the SequenceFileLoad sequence manually executes properly.

Workaround: Configure the SequenceCall step to launch a new thread instead of a new execution or use the TestStand API Engine.NewExecution method to programmatically launch a new execution.

Reported Version: 3.5    Resolved Version: N/A    Added: 12/11/2009
200279

Return
Using the TestStand Seconds Function or Wait Step might result in incorrect elapsed time
Refer to the National Instruments KnowledgeBase article 5703Q01O, Using the TestStand Seconds Function or Wait Step Might Result in Incorrect Elapsed Time, located at http://digital.ni.com/public.nsf/allkb/0015849ED3933840862576D9003B693F, for more information about this issue.

Workaround: Refer to the National Instruments KnowledgeBase article 5703Q01O, Using the TestStand Seconds Function or Wait Step Might Result in Incorrect Elapsed Time, located at http://digital.ni.com/public.nsf/allkb/0015849ED3933840862576D9003B693F, for information about workarounds for this issue.

Reported Version: 3.0    Resolved Version: N/A    Added: 08/01/2011
207535

Return
Using the RunEntryPoint command-line argument returns an error when the entry point you specify is defined in the process model associated with the sequence file but not in the station model
Using the RunEntryPoint command-line argument returns an error when the entry point you specify is defined in the process model associated with the sequence file but not in the station model.

Workaround: Change the station model to the process model that defines the entry point you want to use.

Reported Version: 4.0    Resolved Version: N/A    Added: 08/01/2011
222618

Return
Cleanup step post action that jumps to Main step group causes infinite loop when you terminate the sequence
Defining a post action that jumps to the Main step group from a Cleanup step results in an infinite loop when you terminate the sequence before reaching that Cleanup step.

Workaround: Abort the execution.

Reported Version: 4.0    Resolved Version: N/A    Added: 08/01/2011
232693

Return
Batch synchronization behaves incorrectly when you set a SequenceCall step and the steps within the subsequence to serial batch synchronization
When you configure a SequenceCall step for serial batch synchronization and also configure the steps of the subsequence for serial batch synchronization, the execution behaves unexpectedly when the steps the subsequence calls include a For Loop.

Workaround: Configure batch synchronization only for the SequenceCall step or only for the steps the subsequence calls. Do not configure batch synchronization for both.

Reported Version: 4.2.1    Resolved Version: N/A    Added: 08/01/2011
248782

Return
Custom type container becomes incompatible with its own type when you use a field of the custom type container as the current element of a For Each loop
When you use a field of a custom type container as the current element of a For Each loop and then attempt to assign the custom type container to a container of the same type, TestStand returns the following run-time error: "Variable or property types do not match or are not compatible."

Workaround: N/A

Reported Version: 4.0    Resolved Version: 2014    Added: 08/01/2011
250674

Return
Making the return value of the PropertyObject.GetValVariant method a 64-bit integer causes an edit-time error
The TestStand Sequence Analyzer returns an edit-time error when you make the return value of the PropertyObject.GetValVariant method a 64-bit integer. However, the sequence executes successfully.

Workaround: You can ignore this error.

Reported Version: 2010    Resolved Version: N/A    Added: 08/01/2011
250700

Return
Message Popup step leaks memory when you enable Display Image or Web Page option
The Message Popup step leaks memory when you enable the Display Image or Web Page option and the file is not a .ico or .bmp file.

Workaround: N/A

Reported Version: 4.0.1f1    Resolved Version: N/A    Added: 08/01/2011
254341

Return
Creating an attribute for a parameter of a substep code module results in an error
When you specify the code module for a substep and attempt to create an attribute for a parameter of the code module, the Attributes dialog box returns the "One or more errors have occurred. Please save your work and restart the application." error. This behavior does not occur for substeps that use the .NET Adapter.

Workaround: Do not edit or create attributes for parameters of substep modules.

Reported Version: 2010    Resolved Version: 2013    Added: 08/01/2011
254771

Return
FTP Files step type does not use the current sequence file directory search path to determine a relative path when browsing for files
When you use the FTP Files step type and browse for files, TestStand prompts you to add a search directory or use an absolute path even when the file you want to select resides in the current sequence file directory or a subdirectory of the current sequence file directory.

Workaround: Manually provide a correct relative path to ensure the step executes correctly at run time.

Reported Version: 4.0    Resolved Version: 2013    Added: 08/01/2011
298378

Return
TestStand Engine File dialog box does not display correctly and is unusable when you set the font size to 150% DPI on Windows 7
On Windows 7, when you set the font size to 150% DPI, the OK, Cancel, and Help buttons, the File Name field, and the Files of Type filter are not visible in the TestStand Engine File dialog box.

Workaround: Use a font size up to 125% DPI.

Reported Version: 4.0    Resolved Version: 2013    Added: 08/01/2011
306233

Return
Disabling the Edit Module Prototype option for a step type might not restrict changes to the module of a step instance
Disabling the Edit Module Prototype option on the Disable Properties tab of the Type Properties dialog box for a step type does not restrict you from making changes to the module of a step instance if you configured the step to use the LabVIEW, .NET, or ActiveX/COM Adapter.

Workaround: N/A

Reported Version: 3.5    Resolved Version: N/A    Added: 08/01/2011
359021

Return
The PropertyObject.CreateReportSection method does not function properly with default input values
The PropertyObject.CreateReportSection method returns an error if you do not directly specify the Format parameter. This behavior occurs because the default value of this parameter is an empty string, but the only supported value is XML.

Workaround: Ensure that you pass the value XML for the Format parameter. You can pass an empty string for the DefaultName and FormatSting parameters to specify their default values.

Reported Version: 2012    Resolved Version: 2013    Added: 07/25/2012
360098

Return
The Sequence.GetEffectiveType method returns incorrect values when called from a running sequence
The Sequence.GetEffectiveType method always returns the value 0 when called using a reference to a running copy of a sequence, such as the RunState.Sequence.GetEffectiveType() call.

Workaround: Call the method on the edit copy of the sequence to obtain the correct value, such as RunState.SequenceFile.Data.Seq["MainSequence"].GetEffectiveType().

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 07/25/2012
360746

Return
A type conflict can occur when you save a sequence file after you change the station model
A type conflict can occur when you save a sequence file after you complete the following steps.
  1. Create a new sequence file, and override the PreUUT or PostUUT callback in the sequence file.
  2. Change the station model.
In this case, TestStand returns an error similar to the following error: Failed to save sequence file '<sequenceFilePath>'. Type '<typeName>' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the files with conflicting types in the Sequence Editor, resolve the conflicts and resave the updated files.

Workaround: To prevent this behavior, save any new sequence files before changing the station model.

Reported Version: 2010    Resolved Version: N/A    Added: 07/25/2012
361039

Return
Terminating a remote Call Executable step might cause a system-level error
When you configure a Call Executable step to run the executable on a remote computer, terminating the step might cause the -17502; System Level Exception error. TestStand reports this error only when you configure the standard input, standard output, or standard error to non-default settings.

Workaround: You can safely ignore this error, or you can prevent the error from displaying by configuring the Call Executable step to ignore run-time errors. To handle other errors encountered in the Call Executable step, add a step after the call to handle the error information if the execution is not terminating.

Reported Version: 2010    Resolved Version: N/A    Added: 07/25/2012
ID Known Issue
322852

Return
Enabling the Log option for parameters of a substep can cause an error
When you configure the code module for a substep of a custom step type, enabling the Log option for any parameter on the Module tab of the Step Settings pane can result in a run-time error similar to the following error: Error executing substep '<substepName>'. Parameter <parameterName>': The following error occurred while logging additional result '<parameterName>': Array offset -1 is out of range; range is 0..1. This error occurs because substeps do not support logging additional results. TestStand 2013 and later no longer allows you to configure additional results for substeps.

Workaround: To log substep parameter data, store the data in a custom step property within the Result container of the step, and enable the IncludeInReport flag for the property.

Reported Version: 2012    Resolved Version: 2013    Added: 07/29/2012
334986

Return
LabVIEW Edit substeps do not support LabVIEW class output parameters
If you select a code module for an Edit substep you define for a custom step type and the code module specifies a LabVIEW class reference as an output parameter, TestStand returns the following error when calling the code module: Error Executing substep 'Edit'
Parameter 'class out':
System Level Exception.
Error Code: -17502


Workaround: Refer to the TestStand 4.2.1 section of the National Instruments KnowledgeBase article, Using LabVIEW class References with TestStand National Instruments KnowledgeBase article, located at http://digital.ni.com/public.nsf/allkb/EE3EA0A08FBB6E4A862573A9004C5A07?OpenDocument, for information about how you can pass a LabVIEW class reference as an output parameter for the code module of an Edit substep

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/29/2012
347220

Return
Modifying properties within an ExpressionEdit control on the Module tab of the Step Settings pane for a LabVIEW Edit substep can cause TestStand to hang
TestStand and LabVIEW hang when all of the following conditions are true:
  • You configure the LabVIEW Adapter to use the LabVIEW Development Environment
  • The selected step is an instance of a step type that specifies a LabVIEW Edit substep, and the substep code module contains an ExpressionEdit control
  • You launch the Edit substep for the selected step using the context menu while the Module tab is active on the Step Settings pane
  • You attempt to modify, add, or remove a property through the VariablesView window of the ExpressionEdit control in the Edit substep code module.
Changing the value or creating a property by right-clicking the expression do not cause the hang.

Workaround: If you encounter this hang, you must end the TestStand process and restart it to recover. To prevent the hang from occurring, ensure that the Module tab is not active on the Step Settings pane when you launch the Edit substep code module that contains an ExpressionEdit control by using the Substeps tab of the Step Type Properties dialog box to launch the substep.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/29/2012
51052
473EH1YL

Return
You receive an error when you attempt to directly pass TestStand API objects to a sequence you call on a remote computer
When you use a Sequence Call step to call a sequence on a remote computer and you specify an expression that contains TestStand API calls for the value of an object reference parameter, TestStand might display the -17308: Specified value does not have the expected type. error.

Workaround: Create a local variable or other property to assign the TestStand API property you want to pass to the remote sequence and use this property in the Parameter Table of the remote Sequence Call step.

Reported Version: 4.0    Resolved Version: N/A    Added: 07/29/2012
334946

Return
TestStand hangs when you use modal dialog boxes in a LabWindows/CVI or LabVIEW code module
Refer to the National Instruments KnowledgeBase article, KnowledgeBase 5UEEN300: TestStand Hangs When Using Modal Dialogs in a LabWindows™/CVI™ or LabVIEW Code Module, for more information about this issue and available solutions.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 02/05/2013
339035

Return
Reordering array elements in a large array takes a long time and appears to hang TestStand
If you attempt to reorder the elements in an array property using drag and drop, the operation can take a long time to complete for large arrays. During this time, you cannot interact with the TestStand environment and it appears to be hanging.

Workaround: N/A

Reported Version: 2012    Resolved Version: 2013    Added: 06/28/2013
358061

Return
Dialog boxes generated in new executions do not display when created within a remote engine
If you call a sequence on a remote target and the sequence creates a new execution, any dialog boxes the execution generates—such as a message box or a run-time error dialog box—do not display, making it appear that the execution is hanging.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2013    Added: 06/28/2013
402410

Return
Loading the module of a sequence call step using the API results in an error in certain cases
If you configure a Sequence Call step to create a new execution and specify a model file, and you try to load the code module for the step using the Step.LoadModule, Sequence.LoadModules, or SequenceFile.LoadModules method with the LoadModule_LoadModulesInSubsequences option, TestStand attempts to load the specified entry point from the client sequence file instead of the process model, which results in an error.

Workaround: You can prevent the error by creating a sequence in the client sequence file with the name of the entry point you want to call. You can obtain the correct sequence to load by giving this sequence a Sequence Call step that calls into the correct entry point.

Reported Version: 4.1.1    Resolved Version: N/A    Added: 06/28/2013
405812

Return
Type errors might occur when loading a more recent version of a type that is stored only in a sequence file
If a step or data type is stored only in a sequence file, you might encounter errors in some cases when opening another sequence file that contains a newer version of the type. This behavior occurs only when the sequence file that contains the type is executed before you open the file that contains the more recent type version.

Workaround: If this behavior occurs, close and reopen the file that contains the older version of the type.

Reported Version: 4.1.1    Resolved Version: N/A    Added: 06/28/2013
405858

Return
Using modal dialog box functions to handle the ApplicationMgr.DisplayCustomRunTimeErrorDialog event results in incorrect behavior
The ApplicationMgr.DisplayCustomRunTimeErrorDialog event allows you to launch a custom dialog box when a run-time error occurs. However, using modal dialog box functions to handle this event results in incorrect behavior because the event handler is always executed in the UI thread.

Workaround: N/A

Reported Version: 2013    Resolved Version: 2014    Added: 06/28/2013
TestStand Sequence Editor
104628

Return
Some dynamically defined toolbar items disappear on refresh
If you drag a dynamically created submenu item to the TestStand toolbar, the item you added might disappear from the toolbar when you refresh the menu by pressing the <Ctrl> key.

Workaround: N/A

Reported Version: 4.1    Resolved Version: N/A    Added: 05/26/2008
164425

Return
Sequence editor caches Execution windows
By default, the sequence editor caches Execution windows to work around an issue where the operating system occasionally leaks objects when you close windows. As a result of caching, the sequence editor process holds on to Windows USER and GDI objects. Windows Task Manager reports that the sequence editor does not release USER and GDI objects when you close Execution windows, which is expected behavior because the sequence editor reuses the USER and GDI objects in subsequent executions. By default, TestStand caches all Execution windows until the number of available USER objects or GDI objects in the TestStand process is less than 1000. Typically, you do not need to change this limit, but you can specify the maximum number of windows in the cache by creating a DWORD registry value named SeqeditExeDocCacheSize under the HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\TestStand\4.x key. The recommended value is the number of execution windows you typically have open concurrently when running executions in the sequence editor. For example, if you typically run a batch process with eight test sockets, specify a value of 9, which includes eight executions that correspond to the test sockets and one controlling execution. You might leak USER objects and GDI objects when the number of concurrent execution windows you create is greater than the number you specify in the registry. The registry entry is an unsigned integer. A value of 0 disables the cache. When the sequence editor attempts to open a new document and finds that there are fewer than 500 USER objects or GDI objects available, the sequence editor clears the cache and returns a warning message.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
164426

Return
Selecting the Show Differences option in the Workspace pane context menu can result in a hang if source code control diff or merge utilities are not installed
If you right-click a file on the Workspace pane and select Show Differences from the context menu, the TestStand Sequence Editor might hang if the difference and merge utilities the source control provider specifies are not installed.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
42416
4ETBRHYL

Return
Step Type Menu Editor dialog box displays an error and closes when dragging groups quickly with the mouse
The Step Type Menu Editor dialog box returns an error and closes when you drag groups quickly with the mouse. The dialog box works correctly when you open it again.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51030
46PDBH77

Return
Selecting different steps is slow when a very large array is expanded on the Variables pane
Selecting different steps on the Steps pane of the TestStand Sequence Editor is slow when you select an element of a large array on the Variables pane.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51062
46QAPEG0

Return
You cannot view the Sequence Properties or Sequence File Properties dialog boxes without unlocking a file first
The TestStand Sequence Editor incorrectly prompts you to unlock a file before launching the Sequence Properties or Sequence File Properties dialog boxes.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51293
477DFO9Q

Return
Property object leaks reported when closing the TestStand Sequence Editor from the Windows taskbar
The TestStand Sequence Editor occasionally reports property object leaks when you select Close from the Windows taskbar context menu to close the application and you enabled the Report Object Leaks option in the Debug Options dialog box you access from the Preferences tab of the Station Options dialog box.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51301
47DDCJ77

Return
Variables pane incorrectly highlights an expression property in red
The Variables pane incorrectly highlights an expression property in red when you select multiple steps and the expression contains references to variables in locals, parameters, or file globals.

Workaround: Select each step individually.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51578
47RDI9YL

Return
Create Custom Data Type from Cluster dialog box appears multiple times when multiple steps are selected
The LabVIEW Module tab incorrectly launches the Create Custom Data Type from Cluster dialog box multiple times when you select multiple steps and you click the Create Custom Data Type button.

Workaround: Select only one step before you click the Create Custom Data Type button.

Reported Version: 4.0    Resolved Version: 2013    Added: 05/26/2008
137446

Return
Double-clicking a Sequence Call step that calls a sequence in a new file does not scroll the Sequences pane if the new sequence file is not already open
Double-clicking a correctly specified Sequence Call step opens the sequence being called and highlights the sequence on the Sequences pane. However, if the sequence file being called is not already open, the sequence is highlighted on the Sequences pane, but the Sequences pane does not scroll so that the selected sequence is visible.

Workaround: Scroll the Sequences pane to view the selected sequence.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
139956

Return
TestStand User Interfaces do not reload a process model if it is modified on disk while loaded into memory
If the sequence editor or a user interface loads a process model into memory and the process model then changes on disk, the sequence editor or user interface does not automatically reload the process model. This issue occurs because loading a sequence file automatically loads the associated process model, and the process model can be modified on disk by a Source Code Control (SCC) system or by another TestStand process.

Workaround: Select File»Unload All Modules or manually open the process model file from disk to force a reload of the process model.

Reported Version: 3.5    Resolved Version: N/A    Added: 05/18/2009
148181

Return
Variables pane can become hidden or partially covered when you auto-hide it and then remove the auto-hide
When you use the Large Screen Example sequence editor configuration and you have two Sequence File window tabs tiled and you auto-hide the Variables pane in one Sequence File window and then remove the auto-hide, the second Sequence File window cuts off part of the Variables pane.

Workaround: Close the Sequence File window and reopen it to fix the display of the Variables pane. You can also reset the layout using Sequence Editor Options dialog box.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
157583

Return
Undoing changes from the Update Automation Identifiers tool makes all steps in the selected sequence disappear
If you undo changes from the Update Automation Identifiers tool, all steps in the selected sequence disappear from the Sequences pane.

Workaround: Click on a different sequence and then return to the original sequence to make the steps reappear. You can also close and reload the file to workaround this issue.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
51939
49O5JI9Q

Return
TestStand Sequence Editor seems to hang when launching the Customize Toolbar dialog box after changing the number of monitors in the system
The Customize Toolbar dialog box is a modal dialog box. If you configured a system to use multiple monitors, opened the Customize Toolbar dialog box, then moved the dialog box to a secondary monitor screen before closing the dialog box, when you remove the additional monitor(s) from the system, the TestStand Sequence Editor appears to hang the next time the Customize Toolbar dialog box launches. This occurs because the Customize Toolbar dialog box tries to display on a monitor that no longer exists in the system.

Workaround: If you experience this apparent hang, press the <Enter> key to close the modal Customize Toolbar dialog box. Configure the system to use multiple monitors, launch the Customize Toolbar dialog box, move the dialog box to the primary monitor, and then close the dialog box. If you remove the additional monitor(s) from the system, subsequent launches of the Customize Toolbar dialog box display the dialog box on the primary monitor.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
248968

Return
Watch View pane returns an error when you drag an object held by a reference onto the pane
For an Object Reference called Ref that references a TestStand property called Foo, when you drag Foo to the Watch View pane, TestStand populates the watch expression with Ref.Foo and returns an error.

Workaround: Drag the Object Reference into the Watch View pane and expand it to get to the property you want.

Reported Version: 4.0    Resolved Version: N/A    Added: 08/01/2011
359036

Return
An error can occur when you use the Find/Replace in Files dialog box in sequence files with a SequenceFileLoad Engine callback
When you use the Find/Replace in Files dialog box to replace text in an unopened sequence file, the following error can occur if the sequence file contains a SequenceFileLoad Engine callback: Replacing the matched text in the value of object <object> with <string> failed.
Cannot edit <sequence file name>. The file is either in use by an execution, marked as read-only, or you do not have the necessary user privileges. This error occurs because the callback executes when the Find/Replace in Files dialog box opens the sequence file, which blocks the Find/Replace in Files dialog box from editing the sequence file.

Workaround: Open in the sequence editor any sequence files that use the SequenceFileLoad callback before you use the Find/Replace in Files dialog box to modify them.

Reported Version: 2010 SP1    Resolved Version: 2013    Added: 07/25/2012
354474

Return
Cannot drag and drop array elements when sorting is enabled on any column on the Variables pane
Refer to the National Instruments KnowledgeBase article, http://digital.ni.com/public.nsf/allkb/5F08134811CB6B0A86257A2300574A03?OpenDocument, for more information about this issue.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 07/26/2012
308947

Return
An error occurs when you use the Paste function in an array of object references
If you copy an object reference property to the clipboard and then attempt to paste the object reference into an array of object reference properties, TestStand returns the Expected Container found Object Reference. Error Code: -17308, Specified value does not have the expected type error.

Workaround: Use the Insert Element or Resize Array functions to add elements to an array of object references instead of using the Copy and Paste functions

Reported Version: 2.0    Resolved Version: 2013    Added: 07/29/2012
314004

Return
You can cannot edit the struct and cluster passing setting after you set the data type as hidden
If you set a container data type to be hidden using the PropFlags_Hidden or PropFlags_HiddenInTypes flags, you cannot edit the struct and cluster passing setting. This behavior only occurs if the struct and cluster passing setting is disabled before you set the data type as hidden. If the struct and cluster passing setting is enabled, you can continue to edit the setting even after you set the data type as hidden.

Workaround: To change the struct and cluster passing setting of a hidden data type, unhide the data type, change the struct and cluster passing setting, and then rehide the data type.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/29/2012
350367

Return
The Module tab on the Step Settings pane does not display in certain cases after you change the type for a step
The Module tab on the Step Settings pane does not display when you complete the following steps, and you cannot configure the code module and its parameters for the step.
  1. Create a step type, and disable the Specify Module option on the Disable Properties tab of the Step Type Properties dialog box.
  2. Create an instance of the step type.
  3. Change the type of the new step to a different step type that does support a Module tab on the Step Settings pane, such as an Action step.


Workaround: To recover from this issue, save the sequence file and restart TestStand. You can avoid the issue by creating a new step instead changing the type of an existing step.

Reported Version: 4.0    Resolved Version: 2013    Added: 07/29/2012
TestStand User Interface (UI) Controls
127509

Return
Application Manager control might hang if TestStand is not licensed
If you do not activate TestStand properly, the Application Manager control can hang after you call the Start method.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
50235
43FETR00

Return
Cannot navigate to adapter buttons using the keyboard within the Insertion Palette pane
You cannot use the keyboard to navigate to the adapter buttons within the Insertion Palette pane for non-.NET applications.

Workaround: N/A

Reported Version: 4.0    Resolved Version: 2013    Added: 05/26/2008
50418
44CB5HGH

Return
SequenceView and ListBar controls can leak memory
The SequenceView and ListBar controls can leak memory when you quickly launch and dismiss the context menu multiple times.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
50421
44BDJQRA

Return
VariablesView control can leak a Windows USER object
The VariablesView control can leak a Windows USER object when you use the keyboard to change a Boolean value.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
51251
476DR6B8

Return
CheckBox control Color properties do not work when used as a button
The CheckBox.ForeColor and CheckBox.BackColor properties do not change the appearance of a control when you set the CheckBox.Style property to CheckBoxStyle_Button.

Workaround: N/A

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
138406

Return
The /run and /runEntryPoint command-line arguments are ignored when no user is logged in
The Application Manager control automatically handles the /run and /runEntryPoint command-line arguments to run a sequence when a user interface is started. However, if you set the ApplicationMgr.LoginOnStart property to False, the command-line arguments are ignored, even if you also set the StationOption.RequireUserLogin and StationOption.EnableUserPrivilegeChecking properties to False.

Workaround: Modify the user interface to automatically log in a user.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
199119

Return
Clicking a step icon deselects all other selected steps
If you select multiple steps to move within a sequence or to move from one sequence to another sequence, clicking a step icon deselects all the other selected steps. This behavior does not occur if you click anywhere else in the highlighted region.

Workaround: Hold or key when clicking, or click any part of the highlighted region other than a step icon to drag and drop a collection of steps.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
52249
4ADBS5B8

Return
ActiveX controls located within user controls, such as tabs or panels, on a .NET form might disappear
A known issue with ActiveX controls in the .NET Designer results in the disappearance of ActiveX controls. This behavior might occur at edit time when you move ActiveX controls into or out of the user control, or it might occur at run time when you programmatically create or move ActiveX controls within the user control.

Workaround: If the ActiveX controls disappear in the .NET Designer at edit time, close and reopen the form. If the ActiveX controls disappear at run time, override the OnCreateControl event to call the Hide and Show methods on each ActiveX control.

Reported Version: 4.0    Resolved Version: N/A    Added: 12/11/2009
298496

Return
Expression Browser dialog box elements do not display correctly if the font size is set to 150% DPI
If the font size of Windows 7 is set to 150% DPI, the Replace and Insert buttons, descriptions, and variable names on all tabs of the Expression Browser dialog box do not display correctly or at all.

Workaround: You can still use the Expression Browser dialog box by double-clicking on an element. If you do not select any text, double-clicking an element inserts the element in the expression control at the bottom of the current cursor position. If you do select text, double-clicking an element replace the existing text with the element. Hovering over an element launches the context help, which contains almost all the information that is this display issue hides.

Reported Version: 4.0    Resolved Version: N/A    Added: 08/01/2011
301993

Return
TestStand ActiveX user interface buttons connected to the CommandKind_Edit commands might exhibit unexpected behavior
If you use a button to trigger a CommandKind_Edit command, such as CommandKind_Edit_Delete, clicking the button does not result in a delete operation. This unexpected behavior occurs because clicking the button moves the focus from the TestStand User Interface control that you want to delete to the button, and TestStand cannot determine which control to delete.

Workaround: Use shortcut keys or other events that do not remove focus from the TestStand User Interface control to trigger CommandKind_Edit commands.

Reported Version: 4.0    Resolved Version: 2013    Added: 08/01/2011
361491

Return
TestStand User Interface developed with LabVIEW Actor Framework hangs
When creating a TestStand User Interface using the LabVIEW Actor Framework, LabVIEW might hang if actors that contain TestStand UI Control references are initialized while other actors are initializing.

Workaround: Use synchronization to ensure that actors that contain TestStand UI Controls are not initialized while other actors are initializing.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 06/28/2013
User Interfaces
164433

Return
TestStand MFC user interface might leak GDI objects when creating and destroying child windows on Windows XP SP2
MFC-based applications, such as TestStand User Interfaces, might leak GDI objects on computers that run Windows XP SP2 when the applications create and destroy child windows. Windows XP SP3 fixes this issue.

Workaround: Refer to the Microsoft Knowledge Base article 319740, located at http://support.microsoft.com/kb/319740, for information about how to resolve this known Microsoft issue.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/26/2008
141889

Return
LabVIEW User Interface in Editor Mode ignores the <Alt+Enter> shortcut to launch Step Properties dialog box
The LabVIEW User Interface in Editor Mode lists the shortcut to launch the Step Properties dialog box as <Alt+Enter>. However, pressing this key combination does not launch the dialog box.

Workaround: Use the <Ctrl+Shift+P> is the correct shortcut for launching the Step Properties dialog box in the LabVIEW User Interface in Editor Mode. Alternatively, you can double-click the step or right-click the step and select Step Properties from the context menu.

Reported Version: 4.0    Resolved Version: N/A    Added: 05/18/2009
255848

Return
You cannot paste additional results in user interfaces other than the TestStand Sequence Editor
In the sequence editor, you can cut or copy an additional result and paste the result in the same step or in a different step. In a user interface, the AdditionalResults cut, copy, and delete context menu options work, but the paste option does not.

Workaround: Manually create the additional result you were trying to paste.

Reported Version: 2010    Resolved Version: N/A    Added: 08/01/2011
256758

Return
Using the keyboard to select multiple variables in the Variables View control does not work in the MFC, LabWindows/CVI, or LabVIEW UIs
In the Microsoft Foundation Classes (MFC), LabWindows/CVI, or LabVIEW Editor UIs, you cannot select multiple variables by holding down the <Shift> key and using the up or down arrow keys on the keyboard. This issue does not exist in the .NET Editor UIs.

Workaround: Use the mouse along with the <Shift> key to select multiple variables in the Variables View of the MFC, LabWindows/CVI, or LabVIEW Editor UIs.

Reported Version: 4.2.1    Resolved Version: N/A    Added: 08/01/2011

Document last updated on 6/28/2013

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).