This document contains the TestStand known issues that were discovered before and since the release of TestStand 2024 Q4. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community; see Additional Resources.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
1440450 |
TestStand silently crashes when generating a test report for a large amount of dataWhen executing a test that generates a large amount of report data, TestStand may silently crash if you terminate the test after a significant amount of report data has been generated.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2020 Resolved Version: N/A Added: Oct 11, 2021 |
|
1530687 |
Execution report information for Sweep loop records do not match with the runtime values for capture value parameterIf a Sweep Loop step contains a parameter configured as a Capture Value parameter (Use Existing parameter prior to TestStand 2021), and a step within the Sweep Loop modifies the variable associated with the parameter, the updated value for this parameter is not reported in the execution report.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2019 Resolved Version: N/A Added: Oct 11, 2021 |
|
2802199 |
Customizing the step types menu results in wrong properties set for dragged menu itemDragging and dropping an item that is not the currently selected item in the Step Type Menu Editor dialog will result in the properties of the currently selected item to be applied on the dragged item.
Workaround:
|
Reported Version: TestStand: 2023 Q4 Resolved Version: N/A Added: Oct 11, 2024 |
|
2938931 |
Error -17502 encountered when using a custom step type that calls a .NET assembly as a Post-Step/Edit Substep with LabVIEW adapterWhen a custom step type calls into a .NET assembly using the Edit or Post-Step Substep and the Adapter is set as 'LabVIEW', error -17502 is encountered when accessing the .NET code for the Edit or Post-Step Substeps.
Workaround: Set the custom step type adapter to 'None'. |
Reported Version: TestStand: 2024 Q4 Resolved Version: N/A Added: Jan 31, 2025 |
|
2932135 |
Report generated by File Diff and Merge utility renders empty in a browserWorkaround: |
Reported Version: TestStand: 2024 Q4 Resolved Version: N/A Added: Jan 31, 2025 |
|
2958845 |
DAQmx .NET Framework Assembly does not load in TestStand .NET adapterCalling into the DAQmx .NET API using the TestStand .NET adapter step type throws an exception stating that the mixed assembly could not be loaded into a collectible AssemblyLoadContext. The TestStand .NET adapter tries to load the DAQmx .NET API assembly using the .NET 8 AssemblyLoadContext. This causes a failure as the .NET 8 AssemblyLoadContext does not support loading mixed-mode assemblies, and the DAQmx .NET API assembly is mixed-mode. The AssemblyLoadContext is collectible to allow unloading of assemblies that are loaded in the .NET adapter.
Workaround: There is currently no known workaround for this issue. |
Reported Version: TestStand: 2024 Q4 Resolved Version: N/A Added: Jan 31, 2025 |
Issues found in this section will not be listed in future known issues documents for this product.
Bug Number |
Legacy ID |
Description |
Details |
---|---|---|---|
1865161 |
TestStand Generic Insert (NI) database schema is filling Microsoft SQL database string entries with blanksWhen logging results to a Microsoft SQL Server using the Generic Insert (NI) schema in the TestStand database logging tool, TestStand fills each BSTR string entry with trailing blanks up to the varchar length of each entry.
Workaround: Create a copy of the Generic Insert (NI) schema and for each column/parameter where the Type is String (BSTR), change the value to String (VarChar). |
Reported Version: TestStand: 2021 Resolved Version: N/A Added: Apr 6, 2023 |
|
1945884 |
TestStand Deployment Utility cannot locate code modules when trying to deploy a workspace with TestStand environment specifiedWhen trying to deploy a TestStand workspace where a TestStand environment is specified, the TestStand Deployment Utility displays an error stating that it cannot find the code modules in the workspace. This occurs when code modules are not saved in the same folder or a subfolder of the workspace file.
Workaround: Save all the code modules in the same folder or a subfolder of the workspace file.
|
Reported Version: TestStand: 2020 Resolved Version: N/A Added: Apr 6, 2023 |
|
2186839 |
Error occurs when trying to create a deployment that uses an environment fileWhen trying to create a deployment that use an environment file, error -18360 occurs, stating that changing environments requires the ConfigEngine privilege. This happens when outside of TSDU, the Engine.StationOptions.RequireUserLogin = TRUE and ApplicationMgr.LoginOnStart = FALSE API calls are executed before the deployment is attempted.
Workaround: Do not have the Engine.StationOptions.RequireUserLogin = TRUE and ApplicationMgr.LoginOnStart = FALSE API calls executed in the system in which you are attempting to create the deployment through TSDU.
|
Reported Version: TestStand: 2020 Resolved Version: N/A Added: Apr 6, 2023 |
|
2187652 |
Extra rows get inserted when SQL INSERT statement contains 'OUTPUT INSERTED.id' clause in the "Open SQL Statement" stepUsing 'OUTPUT INSERTED.id' is used in an SQL's INSERT statement in TestStand's 'Open SQL Statement' step without using the INSERTED.id subsequently, results in additional rows getting inserted into the database table. Workaround: In the advanced tab of 'Edit Open SQL Statement' step set the Cursor Location to "Client'.
|
Reported Version: TestStand: 2019 Resolved Version: N/A Added: Nov 13, 2023 |
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country