TestStand 2016 Bug Fixes

Visión General

This document contains the TestStand Bug Fixes that were discovered before and since the release of TestStand 2016. Not every bug fix known to NI will appear on this list; it is intended to only show the severe and more common issues that have been addressed.

Each Issue appears as a row in the table and includes these fields:

  • Issue ID - the number at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
  • Legacy ID (optional) -  If an issue has a legacy ID from NI's legacy/deprecated bug reporting database, you will see it appear on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
  • Issue Title: in italics - it describes the issue in one sentence or less
  • Problem Description - a few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
  • Workaround - possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
  • Reported Version - the earliest version of TestStand the issue was reported in. If you discover the issue appears in an earlier version of TestStand than is reported in this field, you can report that to NI (contact information below) to have the field updated.
  • Resolved Version - version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
  • Date Added - the date the issue was added to the document (not necessarily the reported date)

JavaScript is disabled. Details


Bug Fixes

The following items are Bug Fixes in TestStand 2016.

ID Legacy ID Fixed Issue Issue Details
131253
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.
131559
When a runtime error occurs in a step, the module is not unloaded from memory when you select the "Unload after step executes" option A runtime 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.
132872
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.

This issue affects the legacy Property Loader step type included in TestStand 2014 SP1 and earlier. It has been resolved in the redesigned Property Loader included with TestStand 2016.
149883
Importing a property from a .xls file using a Property Loader step does not import the full property value if the cell contains a 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 commas. When a series of expressions separated by commas exists 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.

This issue affects the legacy Property Loader step type included in TestStand 2014 SP1 and earlier. It has been resolved in the redesigned Property Loader included with TestStand 2016.
159809
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.

This issue affects the legacy Property Loader step type included in TestStand 2014 SP1 and earlier. It has been resolved in the redesigned Property Loader included with TestStand 2016.
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 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.
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 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.

Note: This issue affects the legacy Property Loader step type included in TestStand 2014 SP1 and earlier. It has been resolved in the redesigned Property Loader included with TestStand 2016.
298496
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.
317729
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.
348612
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.
361491
TestStand User Interface developed with LabVIEW Actor Framework hangs When creating a TestStand User Interface using the LabVIEW Actor Framework, LabVIEW 2012 and earlier might hang if actors that contain TestStand UI Control references are initialized while other actors are initializing. This issue does not occur with LabVIEW 2013 and later.
366317
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 in TestStand 2014 SP1 and earlier 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.


This issue affects the legacy Property Loader step type included in TestStand 2014 SP1 and previous. It has been resolved in the redesigned Property Loader included with TestStand 2016.
389275
C/C++ DLL and CVI Adapters report an error if a parameter in a struct has a name other than the name provided in the function prototype N/A
468389
TestStand Deployment Utility may generate incorrect relative paths when code module files are set to install to a separate base directory from the calling sequence file When you configure a code module to install to a separate base directory from its calling sequence file, the TestStand Deployment Utility may create a path relative to the base directory, even if that path is not included in the TestStand search directories. This action will lead to an error in the deployed system since TestStand is unable to find the code module file.
469726
Database Viewer user interface elements may not display properly when font size is set to greater than 100% When font size is set to greater than 100%, user interface items in the Database Viewer may appear to be truncated or otherwise not display properly.
474540
TestStand Deployment Utility does not correctly deploy shortcuts (.lnk files) If you include a file-shortcut (.lnk) file in a deployment, the TestStand Deployment Utility copies the file that the shortcut references rather than the shortcut itself.
477923
Building the MFC user interface from source code in Microsoft Visual Studio 2013 may generate error MSB8031 stating that the project cannot be built for a non-Unicode character set Since the MFC user interfaces do not have the project multibyte character encoding setting set as "Unicode", they will not build properly in MIcrosoft Visual Studio 2013.
489283
TestStand fails to retain Auto Hide settings between executions.  
490195
Error -17313 occurs when attempting to assign a LabVIEW Variant parameter to an array element When a LabVIEW code module passes a value back to TestStand as a Variant data type, Error -17313 will occur if this value is assigned to a specific index of an array variable.
519397
Process model plugins and addons do not work if the Password Protection setting in the plugin or addon sequence file is set to Not Viewable. No errors are generated as a result of this setting, but when the sequence file is configured in this way the plugin or addon callbacks will not be executed.
530980
When creating a patch deployment, the Shortcuts button on the Distributed Files tab of the TestStand Deployment Utility is not disabled if the file selected is not included in the patch. N/A
532671
The LabVIEW module pane incorrectly generates a Prototype Invalid error message instead of a Broken VI error message when the step's LabVIEW VI is broken N/A
533354
Error occurs when using the Start Modal Dialog and Stop Modal Dialog VIs multiple times within a single LabVIEW VI An Input Parameter is Invalid error will occur if you pass a TestStand Engine reference into a LabVIEW VI and use the Start Modal Dialog and Stop Modal Dialog VIs multiple times within the VI.
533930
If a LabVIEW Packed Project Library (PPL) used in a test sequence is not included for deployment, TestStand incorrectly modifies the VI Path to include the VI name twice. An example of this is, "path\Library.lvlibp\Code.vi\Code.vi".
534263
The LongFile.WriteAllText() function in the NationalInstruments.TestStand.Utility .NET assembly does not truncate previous data when writing to an existing file. When writing to an existing file on disk, the LongFile.WriteAllText() function should erase any existing data in the file before writing new data; however, the function instead opens the file and overwrites all existing data with new data. This could result in unexpected data in the file if the new set of data is shorter than the previous set of data in the file.
535370
The background color of Message Popup buttons cannot be changed. Although the button background color can be configured in the Step Settings pane for the Message Popup step, buttons will always appear with the default background color at runtime.
535475
ATML reports will log only one entry from the UUT.Documentation container When the UUT.Documentation container is used to store documentation information for inclusion in an ATML report, the ATML report will contain only the last element in the Documentation container.
536114
TestStand Deployment Utility will not correctly build a packed project library when code module VIs contain dependencies between vi.lib, user.lib, and/or instr.lib. In cases where the TestStand Deployment Utility is configured to build VIs into a packed project library (PPL) and the deployed VIs contain dependencies between two or more of vi.lib, user.lib, and instr.lib, the PPL will fail to build with no generated error. This scenario is likely to occur when using NI-RFmx, as the NI-RFmx VIs contain dependencies between vi.lib and instr.lib, but can occur with any set of VIs with dependencies between the library directories.
537554
Object not set to instance of an object error may occur after canceling shutdown of the TestStand Sequence Editor. This error most commonly occurs when the selecting a step which uses the LabVIEW adapter.
541373
File Differ may crash when deleting a property from one of the files being compared The File Differ application may crash if you delete a property in a file using the Editing Option»Delete This Property In This File function.
543915
TestStand Synchronication API that uses cross-process objects may cause a hang if the SequenceContext parameter is not provided from a running execution When you use a synchronization object with the * character prefix to make the object cross-process, a hang may occur if you do not specify the SequenceContext parameter in the call to the synchronization object.
549120
Sequences may appear multiple times in Sequence File Hierarchy Viewer when called by multiple Sequence Call steps N/A
549391
Enum values do not appear properly in LabVIEW module parameters when a typedef LabVIEW Tab Control is used When you use a LabVIEW Tab Control that is a typedef, the Tab Control input parameter will be displayed as a Number type rather than an Enumeration type. This issue occurs only if the Tab Control has been turned into a typedef in LabVIEW.
551771
Error -19001 will occur when attempting to build a deployment with the "Remove Block Diagrams" option enabled if a LabVIEW VI included in the deployment does not have either a front panel or block diagram When you deploy a test sequence with a LabVIEW VI call that contains a subVI that has had its front panel and block diagram removed, if the "Remove Block Diagrams" option on the LabVIEW Options dialog is enabled the deployment build will fail with Error -19001.
553104
Process model runtime components are not included by default when the "Install TestStand Runtime" option is enabled for a TestStand deployment If the process model runtime is not included in the deployment, the TestStand process models may not execute properly on the deployed system.
556654
Stepping into Visual Studio 2015 C# and C++ DLLs from TestStand 2014 SP1 64-bit does not work properly When attempting to step into a DLL from TestStand 2014 SP1 64-bit with Visual Studio 2015, the error Failed to step into '<function>'. Could not find DIA CLSID for this version of Visual Studio. will occur. After the error is displayed, the execution will continue as if the Step Out operation was performed.
557562
Large sequence files can be retained in memory longer than required when using 32-bit TestStand on a 64-bit Windows operating system, causing unexpected memory usage in systems that load multiple large sequence files The TestStand Engine caches sequence files when they are accessed, and unloads files from memory under certain conditions, such as when memory usage reaches a high threshold. Under certain conditions, especially when using 32-bit TestStand with 64-bit Windows and loading very large sequence files into memory, the sequence files may not be unloaded from memory even when the process is using a large percentage of its available memory space. This can cause out-of-memory errors during execution.
558463
Step icons are not displayed in the Steps Pane when using a Windows 10 system configured to use the English (Europe) region When you are using Windows 10 with the Region settings configured to English (Europe), step icons will not appear in the Steps Pane of the TestStand Sequence Editor.
560022
Select Source dialog in the TestStand Deployment Utility is not modal and can be hidden by other windows, preventing the dialog from being closed In some cases, such as after using the Drivers and Components dialog to include a driver in the deployment, a dialog may appear asking you to specify the location of the installation media for the driver. If you click outside of this dialog, the dialog will be hidden behind the TestStand Deployment Utility window, which puts the application into a state where it must be closed using the Task Manager.
560492
Error -19056 occurs in the TestStand Deployment Utility when you attempt to deploy a test sequence with a Call Executable step that does not call a file with the .exe extension This error will occur when the deployment source files are analyzed, and will cause the deployment build to fail. This error is most likely to occur when you use the Call Executable step type to execute a Windows command, such as net or xcopy, since these commands do not require the .exe extension when executed from the command line.
562958
TestStand Deployment Utility launches on second screen when no second screen is connected If you have multiple monitors connected and close the TestStand Deployment Utility while it's on another screen, it's next launch will also be on that screen. This is still the case even if that other monitor is no longer connected.
563024
TestStand 2014 SP1 TestStand Deployment Utility does not fail the build when the log contains error -19060 When you deploy a TSD that contains an XNode and another file not included in the build, 2014 SP1 TestStand Deployment Utility shows the overall status of the build as "Pass", but the log contains error -19060 (The deployment utility was unable to find the code module for the specified step within the Packed Project Library created in the deployment).
564632
TestStand Offline Results Processing Utility unecessarily modifies testexec.ini The TestStand Offline Results Processing Utility modifies testexec.ini by removing specific lines and overrides the settings previously established in Station Options.
566260
Reference memory leaks can occur when 'Same as caller' VI code module uses LabVIEW runtime and is called from a TestStand STA execution thread When the TestStand LabVIEW Adapter executes steps using the LabVIEW Runtime, the adapter executes 'Same as caller' VIs using multiple threads, instead of using the TestStand STA execution thread, which can result in reference memory leaks.
571785
Import/Export Properties dialog generates a null pointer exception if PLPropertyLoader.ini file is corrupted or from an old version of TestStand The PLPropertyLoader.ini file (<Cfg> directory, default settings for Import/Export Properties dialog) was modified in TestStand 2014 to use the tag PROPERTIES_SQL_STATEMENT instead of STATEMENT_SQL_STATEMENT. As a result of this change, if the <Cfg> directory contains an old version of this INI file, possibly as a result of migrating settings from another machine, a null pointer exception will be generated if you attempt to launch the Import/Export Properties dialog.
575312
TestStand Deployment Utility fails to build and returns no error The TestStand Deployment Utility fails to build without reporting an error if a VI has a dependency on a library that is missing a VI.
575563
Custom data type will not be created if the custom data type is an empty array When you create a custom data type, if you enable the "Empty Array" option on the Array Dimensions dialog, the custom data type will not be created.
579926
Windows cannot find TestStandElevatedCommand.exe when you attempt to change the default source code control provider for the system When you try to change the default source code control provider for the system, you get the error "Windows cannot find 'C:\Program Files (x86)\National Instruments\TestStand 2014\Bin\TestStandElevatedCommand.exe'".
590688
"This property is not supported in LabVIEW" error when using TestStand LabVIEW runtime server When you use the out-of-process TestStand LabVIEW runtime server (TestStandLVRTS shipped with TestStand) to execute VIs, if you do not enable the "Reserve VIs for Execution" option, the error "This property or method is not supported in LabVIEW" will appear when you execute the sequence.
592773
File Diff/Merge Utility may crash when viewing differences in an array property N/A

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).