From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
This document contains the TestStand Bug Fixes
that were discovered before and since the release of
TestStand 2012 & 2012 SP1. 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:
The Bug Fixes Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.
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.
The following sections list the bugs that existed in TestStand 2010 SP1 or earlier and have been fixed in TestStand 2012 or 2012 SP1. This is not an exhaustive list of issues fixed in TestStand 2012 or 2012 SP1. If you reported an issue to National Instruments and were given a CAR ID to track the issue, you can search for the CAR ID in the ID or Legacy ID column to determine whether the issue has been fixed.
| ID | Legacy ID | Fixed Issue | Issue Details |
|---|---|---|---|
| .NET Adapter | |||
| 298630 | The .NET Adapter does not display static methods an inherited class defines | When you define a derived class in a .NET assembly that inherits from a base class, the base class contains a static function, and you use the .NET Adapter to select the derived class, the .NET Adapter does not show the inherited static method. | |
| 322670 | .NET steps might encounter a deadlock when the constructor uses the TestStand API in a parameter expression | Executing a .NET step might cause a deadlock under the following conditions:
| |
| 334136 | TestStand does not release .NET object references you pass as parameters to new executions until the execution is destroyed | TestStand does not release .NET object references you pass as parameters to new executions until the execution completes. This behavior causes the .NET assembly to remain loaded if any such executions remain open, even if you select File»Unload All Modules to unload all modules. | |
| .NET Adapter; LabVIEW | |||
| 290991 | When you use LabVIEW or .NET code modules, the additional results feature does not log all elements | When you select to include an array output parameter of a code module as an additional result, TestStand might not log some elements of the array under the following conditions:
| |
| 359373 | You cannot close the Type Properties dialog box after you rapidly click the Specify Module button on the Substeps tab | When you use the Substeps tab of the Type Properties dialog box to configure the substeps for a custom step type, clicking the Specify Module button multiple times before the Specify Module dialog box appears prevents you from closing the Type Properties dialog box. This issue occurs with .NET substeps in TestStand 2010 SP1 and with .NET and LabVIEW substeps in TestStand 2012. | |
| Database | |||
| 341273 | On-the-fly database logging might return an error when you execute a sequence that uses a Sequence Call step to create a new thread that collects results | An error can occur when you use on-the-fly database logging and TestStand attempts to log the first result from a new thread that a Sequence Call step created. | |
| Documentation | |||
| 365966 | Help file index and search results do not display TSFundamentals.chm topics | Using the index or search functionality in the TestStand 2012 version of the NI TestStand Help to find topics contained in the NI TestStand Fundamentals Help (located at <TestStand>\Doc\Help\ TSFundamentals.chm) does not yield any results. | |
| File Differ | |||
| 253897 | Closing multiple TestStand File Diff/Merge application instances on Windows 7 with the Close All Windows taskbar option sometimes results in an error | Closing multiple TestStand File Diff/Merge application instances on Windows 7 with the Close All Windows taskbar option might cause the following error: Error writing to file '<TestStand Application Directory>\Cfg\ FileDiffer.ini'. | |
| Installation | |||
| 374240 | TestStand 2012 installation prompts you to install the Microsoft .NET Framework 3.5 on Windows 8 computers | When you install TestStand 2012 on a Windows 8 computer, you are prompted to install the .NET Framework 3.5, even though TestStand 2012 does not require it. | |
| LabVIEW | |||
| 191678 | When you use LabVIEW 2009 to build the LabVIEW Simple User Interface, the user interface remains open if you do not move the mouse after closing the user interface | If you rebuild the LabVIEW Simple User Interface with LabVIEW 2009 and then run the executable, failing to move the mouse after clicking the close button on the titlebar or clicking the Exit button causes the user interface to remain open. When you move the mouse, the user interface closes successfully. This behavior does not exist with the LabVIEW Full-Featured User Interface. LabVIEW 2012 fixed this behavior. | |
| 366452 | Expanding an array parameter or deselecting the default setting for a LabVIEW code module can cause an error | If a LabVIEW code module contains an array parameter with default values, and you have the Default and Log options selected in the parameters table, expanding the array or deselecting the default option shows an error dialog with the message "Unknown variable or property name 'AdditionalResult'". After you close the error dialog, the parameters control can no longer be used until TestStand is restarted. The error only happens when using LabVIEW 2012 and later. | |
| 206259 | The LabVIEW Adapter does not coerce out-of-range values you pass to an enumeration parameter in a LabVIEW code module | When you pass a value to an enumeration parameter in a LabVIEW code module, the LabVIEW Adapter does not modify values that are out of range to a valid item index. | |
| 233755 | Loading a VI that calls a .NET assembly fails when using Turkish regional settings | Loading a VI that calls a .NET assembly fails in TestStand on a computer configured to use Turkish regional settings. If you configure the LabVIEW Adapter to use the LabVIEW Development System, TestStand returns the error An error occurred accessing the LabVIEW ActiveX automation server. If you use the LabVIEW Run-Time Engine for the LabVIEW Adapter, TestStand hangs. LabVIEW 2011 fixed this behavior. | |
| 284675 | The LabVIEW Adapter ignores the code and message fields of an error out parameter of a substep when the occurred field is set to False | If a substep module modifies the code and message fields within the Step.Result.Error error container for a step but the occurred field is set to False, the changes do not persist. This behavior does not occur when you make a similar change for the code module of the step. | |
| 290616 | The LabVIEW Adapter might exhibit unexpected edit-time issues if the most recent installation of LabVIEW is a version TestStand no longer supports | If the most recent version of LabVIEW you install is a version that TestStand does not support, such as installing LabVIEW 7.1.1 and using TestStand 2010, you might encounter unexpected edit-time issues when you create or modify LabVIEW steps in TestStand. | |
| 290994 | TestStand does not include LabVIEW code module parameters with the Default option enabled in additional results | When you call a LabVIEW code module, TestStand does not log any top-level input parameter you select to include as an additional result when you also enable the Default option in the Parameters Table. | |
| 306422 | Manually exiting LabVIEW after executing a VI from TestStand might result in LabVIEW load error code 23 | If you configure a LabVIEW step to display the front panel of a VI that you mass compiled in the active version of LabVIEW, manually exiting LabVIEW after executing the VI from TestStand might result in LabVIEW load error code 23. Close TestStand, which also closes LabVIEW, to avoid this error. | |
| 307558 | Timestamps returned from a LabVIEW code module might specify incorrect values | If a timestamp returned from a LabVIEW code module is noon (12:00:00 PM) or midnight (12:00:00 AM), TestStand stores the values as 00:00:00 PM and 00:00:00 AM, respectively. | |
| 310030 | Passing a binary string to TestStand from a LabVIEW code module results in different behavior based on the configuration of the LabVIEW Adapter | When you pass a binary string to TestStand from a LabVIEW code module, TestStand stores the string differently depending on whether you execute the code module in the LabVIEW Development Environment or in the LabVIEW Run-Time Engine (RTE). TestStand uses the correct binary representation for the string when you execute the code module with the LabVIEW RTE but uses the incorrect ASCII representation for the string when you execute the code module with the LabVIEW Development Environment. | |
| 310671 | Unable to load a LabVIEW .NET interop assembly when TestStand loads the .NET CLR 4.0 | When you call a LabVIEW-built assembly from an application targeted to the .NET Common Language Runtime (CLR) 4.0, the assembly fails to load and returns the Failed to call init lv client function error. This error occurs because of a change in the .NET CLR 4.0 in which the LoadLibrary function, defined in kernel32.dll, is not called when loading an assembly. LabVIEW 2012 fixed this behavior. | |
| 316995 | TestStand hangs when executing a VI that uses shared variables and when you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine | TestStand hangs when executing a VI that uses shared variables and when you configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine (RTE). This issue occurs only under the following conditions:
| |
| 317305 | LabVIEW code modules with an input parameter with a default value of INF or NaN can cause a module load error | LabVIEW code modules with an input parameter with a default value of INF or NaN can cause a module load error. This behavior only occurs with TestStand 2010 SP1 and LabVIEW 2011 or later. This issue has been fixed in the TestStand 2010 SP1 f1 patch. Refer to the following KnowledgeBase article for more information: KnowledgeBase 60RBK8UB: TestStand 2010 SP1 f1 Patch Details | |
| 360969 | An Index was out of range error occurs after you select certain parameters and then select another step | Selecting certain parameters in the VI Parameter Table and then selecting another step can put TestStand in a bad state. This issue can occur if you complete the following steps at edit time.
Error occurred while trying to refresh edit panel "SeqEdit.ba": Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index After you dismiss the error, the error continues to occur for any LabVIEW step you select until you restart TestStand. | |
| 361649 | LabVIEW code modules with a TDMS file reference in the connector pane can cause a generic error | If you use a LabVIEW code module in a sequence that passes TDMS file references in or out of the VI, TestStand might return the following error: Error loading step '<name of step>' of sequence '<name of sequence>' in file '<name of sequence file>'. Failed to load VI <path of VI> in the 'LabVIEW Development System' version '11.0'. LabVIEW: Generic error. Error Code: -18002, LabVIEW reported an error. See 'LabVIEW: ' message for more details. Source: 'TSAPI' | |
| 363405 | TestStand incorrectly assigns timestamp data passed from and to a LabVIEW code module | If a LabVIEW code module passes a timestamp as an output parameter to a string property, TestStand removes leading zeroes in the fractional seconds field. For example, the timestamp 01:35:45.005 is assigned to a string property as 01:35:45.5 in TestStand. However, if TestStand receives a timestamp value as an output parameter and passes the value back to LabVIEW as an input parameter, the correct value is maintained.NOTE: Even with the below patches installed, if you pass a string timestamp value from TestStand to a timestamp in LabVIEW, TestStand adds leading zeroes to create the fractional field. For example, the string 01:35:45.5 is assigned as 01:35:45.005 in LabVIEW. TestStand 2012 SP1 fixes this secondary issue. | |
| 364787 | 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. | |
| 368275 | TestStand can crash if you configure the LabVIEW Adapter to use the LabVIEW Run-time Engine while a LabVIEW project is loaded in memory | TestStand 2012 f1 patch fixes this issue. Refer to the National Instruments KnowledgeBase article, KnowledgeBase 60RBLMUB: TestStand 2012 f1 Patch Details, for more information. | |
| 381698 | Using the Update VI Calls tool on an unsaved sequence file that calls an express VI can cause LabVIEW to crash | If you use the Update VI Calls tool on an unsaved sequence file that contains a call to a LabVIEW express VI, the tool reports that updating the steps failed, and LabVIEW crashes. | |
| 382692 | TestStand does not log parameters of LabVIEW code modules with the Default option and Log option selected | When you use the VI Parameter Table to configure a parameter to use the default value and to be logged in the report, and TestStand executes the code module using the LabVIEW Run-time Engine, TestStand does not add the parameter result to the other test results. | |
| 384407 | Selecting the Default option for an array of waveforms parameter causes TestStand to hang | If you call a LabVIEW code module that contains a parameter with a data type that is an array of waveforms, selecting the Default option for this parameter in the VI Parameter Table can cause TestStand to hang or might result in other unexpected behavior. | |
| 385360 | The Number of Threads option in the LabVIEW Adapter Configuration dialog box can change each time you relaunch the dialog box | In the LabVIEW Adapter Configuration dialog box, if you specify a non-default value in the Number of Threads option for the LabVIEW Run-time Engine, TestStand increments the value each time you relaunch the LabVIEW Adapter Configuration dialog box. | |
| 41665 | 4DQCFCB8 | LabVIEW 8.5 or later returns a warning when you load the LabVIEW Simple User Interface example | When you load the LabVIEW Simple User Interface example using LabVIEW 8.5 or later, LabVIEW returns a warning that indicates that LabVIEW changed a constant wired to a Case structure to maintain compatibility with LabVIEW 7.1 or earlier. |
| LabWindows/CVI | |||
| 373331 | Using the TestStand 2012 Adapter API in LabWindows/CVI Causes "Multiple Definitions for Symbol" Error | ||
| 376277 | An out-of-memory error occurs when using LabWindows/CVI-built TestStand User Interfaces on Windows 8 | ||
| Miscellaneous | |||
| 302929 | The Update VI Calls tool fails when you update the Report Express VI | When you use the Update VI Calls tool to update the Report Express VI, TestStand launches a dialog box that indicates that the VI path is invalid. When you close the dialog box, the Update VI Calls tool times out. | |
| 373104 | Issues exist when using Microsoft Internet Explorer 10 and TestStand | Multiple minor issues exist when using Internet Explorer 10 to view TestStand Analyzer, TestStand Differ, and TestStand ATML Reports. These issue has been addressed in TestStand 2012 SP1. | |
| 35081 | 47DD4PIA | An incorrect prompt to reload files might appear when you use source code control | TestStand prompts you to reload files when source code control (SCC) providers, such as MKS Source Integrity, Serena PVCS, and IBM Rational ClearCase, change the timestamp of files when you add the files to source control or check the files in or out of source control. TestStand might return errors for some operations when you reload the files. |
| 35172 | 482KEHIA | Selecting the Undo Check Out option from the Workspace pane context menu to revert a workspace does not prompt you to reload modified projects | If you make changes to a TestStand project in a workspace and then select Undo Check Out from the Workspace pane context menu, TestStand does not prompt you to reload modified projects within the workspace. This modified project remains in memory does not match the project on disk. |
| 360808 | Errors exist in the Parallel Execution, Property Loader, and Dynamic Client Sequence File example programs that ship with TestStand | The TestStand 2012 f1 patch fixes these issues. Refer to the National Instruments KnowledgeBase article, KnowledgeBase 60RBLMUB: TestStand 2012 f1 Patch Details, for more information. Refer to the following National Instruments support documents for more information about the errors in the Parallel Execution, Property Loader, and Dynamic Client Sequence File example programs that ship with TestStand. | |
| 367308 | Copying arrays of object references can result in invalid references | If you create an array of object references, and copy the object references to a second array using the = operator, the references in the second array are not valid if the first array is deleted. This behavior occurs because the references in the second array are not fully copied and depend on the original references. | |
| 37637 | 3T9BCN6I | When you select Save All after you add a file to a TestStand project, the project does not save | Adding a file to a TestStand project changes the project, and you must save the project to preserve the changes. However, when you select Save All after you add a file to a project, the project does not appear in the Save All file list. Additionally, TestStand marks the workspace as modified, even if you did not modify the workspace file. This issue can cause problems with source-code-controlled project files. TestStand requests that you check out the project file when you add a file but indicates that no changes were made to the project when checking in the changes. |
| 48066 | 3PIA7EYL | Automatically setting up a remote execution does not work for non-English Windows XP SP2 operating systems | Enabling the Allow All Users Access from Remote Machines option on the Remote Execution tab of the Station Options dialog box does not work on some non-English Windows XP SP2 operating systems, such as German Windows XP. The option adds the built-in account name ANONYMOUS LOGON to the DCOM access permissions, but the account name ANONYMOUS LOGON is incorrect for some non-English operating systems. |
| Reports | |||
| 242364 | TestStand incorrectly formats the report for a post action of a step that calls a sequence | When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box and an execution calls a sequence as a post action for a step, TestStand incorrectly formats the report. | |
| 244953 | TestStand incorrectly formats reports when Sequence Call steps loop and you enable the On-The-Fly Reporting option | When you configure multiple Sequence Call steps to loop, disable the Record Result of Each Iteration option on the Looping panel of the Step Settings pane, and enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box, the report displays the first Sequence Call step with a status of Running and displays all the steps the sequence executes under the first sequence. | |
| 250975 | The XML report header incorrectly displays Test Socket Index for sequential execution when you set the Numeric Format report option to Hexadecimal, Octal, or Binary | The XML report header incorrectly displays Test Socket Index for sequential execution when you set the Numeric Format report option to Hexadecimal, Octal, or Binary. | |
| 301515 | On-the-fly reports do not contain a failure chain section | Reports that you generate on-the-fly do not contain details about the steps in the failure chain. | |
| 305551 | Question mark characters appear in ATML reports instead of indentation spaces when you use the TR_horizontal.xsl style sheet | Question mark characters appear in ATML reports instead of indentation spaces when you use the TR_horizontal.xsl style sheet. This issue occurs only under the following conditions:
| |
| 316633 | The Expand/Collapse All Loop Indices button does not function for XML reports that use the report.xsl style sheet | The Expand/Collapse All Loop Indices button does not function for XML reports that use the report.xsl style sheet. This button exists only when you configure a step in the sequence to loop. In this case, you might also encounter an Object expected error when clicking the button in Microsoft Internet Explorer. | |
| 35009 | 47FEKD00 | On-the-fly reporting leaks memory when an execution repeatedly creates new threads | Generating a report on-the-fly slowly leaks memory when executions repeatedly use a Sequence Call step to create new threads. |
| 357253 | Results do not display in an ATML report for a post action of a step that calls a sequence | When all of the following conditions are true, a report does not display results:
| |
| 360856 | Result processing plug-in examples do not recognize TestStand user permissions | The result processing plug-in examples included with TestStand (the Simple Text report and Basic Step Time Report plug-ins) do not recognize TestStand user privileges. Users without the ConfigReport privilege can modify the Enabledand Display settings for instances of these plug-ins. | |
| 373096 | Graphs in ATML 5.0 and XML reports do not display in Microsoft Internet Explorer 10 on Windows 8 | If you use Internet Explorer 10 on a Windows 8 computer to view an ATML 5.0 or XML report that contains one or more graphs, the graphs do not display. Instead, the report displays the graph data in a table. | |
| 377624 | ATML 5.0 report displays incorrect code module times for steps | When you select the TR5_Expand.xsl or TR5_report.xsl style sheets with the ATML 5.0 report format, the report incorrectly displays the total step time value and not the code module time for a step. | |
| 384211 | TestStand cannot display an ATML report if any logged limits contain the value INF | If you generate an ATML report for a sequence that contains any Numeric Limit Test steps with the INF constant defined as a limit, the report does not display, and instead TestStand returns the following error:Unable to load the XML Report. Required white space was missing. | |
| 46782 | 314DQ9MT | TestStand does not call the ModifyReportHeader and ModifyReportFooter callbacks when you generate reports 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, TestStand does not call the ModifyReportHeader and ModifyReportFooter callbacks because the ProcessOTFStepResult sequence in the report generation sequences does not call these callbacks. Note: This issue has been fixed only in the TestStand 2012 process models. |
| TestStand Deployment Utility | |||
| 207845 | Using the horizontal scrollbar in the deployment utility prevents you from selecting files | You cannot select or deselect files on the Distributed Files tab of the deployment utility when you use the horizontal scrollbar. | |
| 277685 | The deployment utility returns an incorrect error when the path to a LabVIEW packed project library source file is too long | If the path for a LabVIEW packed project library source file is too long, the deployment utility returns the following error: The build was aborted because LabVIEW is missing one or more files. The Deployment Utility is now determining which VIs reference the missing file(s). Internal error code 7 Processing VIs.... | |
| 301234 | The deployment utility might encounter errors when deploying locked VIs when you enable the Apply New Password option | When you enable the Apply New Password option in the LabVIEW VI Options dialog box of the deployment utility and any VIs you include in the deployment call a subVI with the Locked (No Password) setting enabled, the deployment fails. | |
| 312382 | Errors can occur when you set VI destinations to LLBs and you enable the Output VIs to a Packed Project Library option | When you create a deployment that includes VIs, an error occurs in the build process under the following conditions:
| |
| 317336 | The Specify Configuration Directory option does not function in the TestStand 2010 SP1 Deployment Utility | The Specify Configuration Directory option in the Advanced Installer Options dialog box does not function in the TestStand 2010 SP1 Deployment Utility. The deployment utility uses the default configuration directory on the deployment target computer even when you enable this option. | |
| 333714 | TestStand User Interfaces might contain blank VariablesView controls or return an unhandled error on the computer to which you deployed the test system | If you create a TestStand deployment with the following conditions, TestStand might return an error when you attempt to edit sequences on the computer to which you deployed the test system:
TSDotNetSupport.dll failed to register. error. | |
| 357522 | LabVIEW can crash when building a deployment with destination VI paths exceeding 255 characters | When using the Output VIs to a packed project library option, the TestStand Deployment Utility can encounter a crash if the destination VI paths exceeds 255 characters | |
| TestStand Engine | |||
| 235098 | Performing a Step Into operation on a step might step into subsequences that pre-step or post-step Engine callbacks call | If a pre-step or post-step Engine callback, such as SequenceFilePostStep, calls a subsequence, performing a Step Into operation on a step steps into the subsequence the callback calls. If the callback does not call a subsequence, performing a Step Into operation on a step executes the step and moves on to the next step. | |
| 251806 | TestStand attempts to step into the Determine Report File Path C/C++ DLL step after stepping out of a PreUUT callback | If you are debugging a PreUUT callback sequence and you try to step out of the sequence, TestStand attempts to step into the Determine Report File Path C/C++ DLL step in the Test UUTs Execution entry point. If you had originally traced into the Test UUTs sequence, this behavior would not occur. | |
| 283247 | Viewing expression steps with a large number of comma-separated statements can cause TestStand to stop responding | Viewing expression steps with a large number of comma-separated statements can cause TestStand to crash or stop responding. | |
| 305733 | Performing a Flush or GetStatus operation on a global TestStand queue might return error -17500 | Performing a Flush or GetStatus operation on a global TestStand queue might return error -17500 if you configure the operation to store the queue elements in an array, such as by specifying the Location to Store Array of Queue Elements option. This issue exists for global TestStand queues, which are queues with names that start with an asterisk (*), but not for local TestStand queues. | |
| 311855 | The default UUT data type does not provide a Part Number field | For many applications, UUTs specify both a serial number and a part number, but the default UUT data type in TestStand does not provide a specific field to store a part number. | |
| 316288 | Using the <Esc> key or closing the Run-Time Error dialog box causes the execution to pause | Closing the Run-Time Error dialog box using the <Esc> key or by closing the window causes the execution to pause. This behavior might be a problem for users with operator privileges because these users do not have sufficient privileges to resume the execution. | |
| 335596 | Passing a value of 0 for the subProperty parameter of the PropertyObject.InsertSubProperty method causes TestStand to stop responding | After you execute a sequence that calls the PropertyObject.InsertSubProperty method from an ActiveX/COM step and you pass a value of 0 or nothing for the subProperty parameter, TestStand stops responding when you use autocomplete while editing an expression. You must restart TestStand to recover from this state. | |
| 346934 | The comparison function can yield different results when operands are swapped if one operand is zero | When using the comparison operator in TestStand to compare a value of magnitude 1e-14 or smaller to exactly zero, swapping the operands can yield different result. For example, the comparison 0 == 1e-14 returns True but the comparison 1e-14 == 0 returns False. The same difference in behavior occurs with the not equal (!=) and greater and less than (< and >) operators. This issue will be fixed in a future version of TestStand. | |
| 349971 | Boolean logic might return an incorrect result when you use constant values for both operands | The Boolean logic operators && and || might return an incorrect result when you use constants for both operands, such as, 'False && True'. This issue does not occur if either operand contains a variable value. | |
| 360941 | Using the Find/Replace dialog box can modify locked types | If you use the Replace operation in the Find/Replace dialog box to change the value of a property within a locked type, TestStand makes the change without prompting for the password for the locked type. | |
| 370893 | Min() or Max() expression function can return an error when evaluating an array stored in a parameter | If you pass an array parameter to the Min() or Max() expression function, the expression function returns an error under one of the following conditions:
-17308; Specified value does not have the expected type. | |
| 371724 | TestStand crashes upon launch on Windows 8 if installed before the .NET 3.5 Framework | ||
| TestStand Sequence Editor | |||
| 153495 | Syncing files with a source code control system from the TestStand File/Diff Merge application in the sequence editor returns an error | If you try to diff files in the sequence editor with a workspace file open, TestStand prompts you to edit the current files, sync the files with a source code control (SCC) system first, or cancel the operation. If you choose to sync the files first, TestStand returns the One or more errors have occurred. Please save your work and restart the application. | |
| 193751 | Using a LabVIEW Edit substep to remove an element from a TestStand array while elements of that array are visible on the Variables pane causes an error on the Variables pane | When you enable the Show VI Front Panel When Called option for a LabVIEW Edit substep and use that substep to remove an element from a TestStand array while elements of that array are visible on the Variables pane, the Variables pane returns an error under certain screen resolution or color quality settings. You must restart TestStand in this situation. | |
| 253099 | The Watch View pane might not refresh all watch expressions | In some cases, the Watch View pane might not refresh all current watch expressions after you make an edit to an expression. | |
| 313685 | The RunState.IsEditor property evaluates to False in the SequenceFileLoad callback of a process model when launching the sequence editor | When you launch the sequence editor, the RunState.IsEditor property evaluates to False in the SequenceFileLoad callback of a process model. | |
| 314101 | An error can occur when you change the run mode for multiple selected Sequence Call steps | When you select multiple Sequence Call steps and you change the run mode step setting, you might encounter error -17325 if any of the Sequence Call steps contain one or more multi-dimensional array parameters. | |
| 315092 | The Parameters Table for a Sequence Call step might crash when you use the navigation buttons while a parameter is selected | If you click the Back or Forward navigation buttons while you have a parameter selected in the Parameters Table on the Sequence Call Module tab, the Parameters Table might crash and require a restart of the sequence editor. This error occurs only if you modified the selected parameter before clicking the navigation button. | |
| 316107 | Errors occur when you save or modify a TestStand Sequence Analyzer project while a TestStand workspace is open | If you modify or save a TestStand Sequence Analyzer project while a TestStand workspace file is open, TestStand returns the Object reference is not set to an instance of an object error. This error can also occur when you shut down the sequence editor while a TestStand workspace and sequence analyzer project are open because shutting down TestStand saves the sequence analyzer project. | |
| 337449 | Sequence Hierarchy window cannot open with certain security policy settings | If the System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing policy setting is enabled in the Microsoft Windows security policy settings, the Sequence Hierarchy window fails to launch and returns an error that indicates that the GoView license is invalid or expired. | |
| 344948 | Deleting rows or columns of a multi-dimensional array terminal of a LabVIEW front panel can cause the VI Parameter Table to stop functioning | When you configure the parameters for a LabVIEW step, you delete rows or columns of a multi-dimensional array terminal in LabVIEW, and then you configure the current value to be the default value in the VI Parameter Table on the LabVIEW Module tab, the VI Parameter Table might stop functioning in TestStand. This issue occurs only if you expanded the elements of the deleted rows or columns before you deleted the rows or columns. | |
| 356920 | Selecting 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, the Watch View can error. An invalid watch expression displays an "X" icon to the left of the expression. When the error occurs, the Watch View pane displays the One or more errors have occurred. Please save your work and restart the application. error and you must restart TestStand. | |
| TestStand User Interface (UI) Controls | |||
| 54115 | 3BDELTRA | Navigating back or using links in the Report control might error | The sequence editor and user interfaces that include the Report control might return an error or reach an unusable state when you aggressively click links and navigate back on the Microsoft Internet Explorer control. This Internet Explorer issue is more likely to occur when the application runs more slowly, such as while debugging the application with LabWindows/CVI or another debugger. |
| User Interfaces | |||
| 37001 | 49GDNHG0 | Modifying the run mode of a step in a user interface in Operator Mode does not mark the sequence file as modified | Modifying the run mode of a step in a user interface in Operator Mode does not mark the sequence file as modified, even after you change the user interface to Editor Mode. This change does not have any effect in Operator Mode because you cannot save files. |