This document contains the TestStand known issues that were discovered before and since the release of TestStand 2017 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.
The following items are known issues in TestStand 2017 SP1 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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 characters.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 192254 Return | Destination directories for files you do not select in the TestStand Deployment Utility may 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 may 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
|
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 250674 Return | Expression checking reports an error when you assign the return value of the PropertyObject.GetValVariant method to a 64-bit integer The TestStand Sequence Analyzer reports an error when you assign the return value of the PropertyObject.GetValVariant method to a 64-bit integer. However, the sequence executes successfully. Workaround: You can ignore this error.
| |||||
| 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
| |||||
| 252650 Return | TestStand 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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. <ol> <li>Create a new sequence file, and override the PreUUT or PostUUT callback in the sequence file.</li> <li>Change the station model.</li></ol> In this case, TestStand returns an error similar to the following error: <strong><code>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.</code></strong> Workaround: To prevent this behavior, save any new sequence files before changing the station model.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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: <strong><code>Array offset 2 is out of range; range is 0..1<br /> Error Code: -17324, Array index out of bounds</code></strong> 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.
| |||||
| 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
| |||||
| 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 <strong><code>Error -17500: Operation Failed</code></strong> error can occur when you run a sequence in which all of the following conditions are true: <ul><li>You enable report generation and you enable the <strong>On-The-Fly Reporting</strong> option on the Contents tab of the Report Options dialog box</li> <li>The sequence contains a Sequence Call step configured to use a new thread</li> <li>You configure a post action for the Sequence Call step to call a subsequence</li> 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.
| |||||
| 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 (<code>/</code>) or question mark (<code>?</code>) character, and you enable the <strong>Output VIs to Packed Project Library</strong> option in the LabVIEW VI Options dialog box, the TestStand Deployment Utility returns a warning similar to the following warning when building the deployment: <strong><code>Warning: Cannot update VI Path: Step '<stepName>', sequence '<sequenceName>', sequence file '<sequenceFilePath>'</code></strong> 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.
| |||||
| 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 <strong><code>Type of argument expression is incompatible with parameter. Expected Number, found Object Reference. [Error Code: -17313, Could not accept the parameter passed in.]</code></strong> error when the step executes: <ul> <li>The code module contains a reference parameter that is represented as a numeric (such as a VI refnum).</li> <li>You enable the Log option in the Parameters Table for the parameter.</li> <li>You do not specify a value for the parameter.</li> </ul> Workaround: Specify a value or disable logging for the parameters.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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: <ul><li>You configure the LabVIEW Adapter to use the LabVIEW Development Environment</li> <li>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</li> <li>You launch the Edit substep for the selected step using the context menu while the Module tab is active on the Step Settings pane</li> <li>You attempt to modify, add, or remove a property through the VariablesView window of the ExpressionEdit control in the Edit substep code module.</li></ul> 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 202206 Return | Error -17500 occurs when you execute .NET code modules that deserialize types Workaround: N/A
| |||||
| 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.
| |||||
| 327928 Return | TestStand does not update to display changes to MAX 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.
| |||||
| 334946 Return | TestStand can hang when you use modal dialog boxes in a LabWindows/CVI or LabVIEW out-of-process code module Workaround: N/A
| |||||
| 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.
| |||||
| 381042 Return | Processing Offline Result files on a separate machine can cause a "Drive Not Ready Error" error when generating reports configured to use client sequence file location 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.
| |||||
| 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 <strong><code>File Not Found</code></strong> error when all of the following conditions are true: <ul><li>A LabVIEW project contains the VI and a TestStand step specifies the project</li> <li>The LabVIEW project file is saved in the <code>instr.lib</code> or <code>vi.lib</code> directory</li> <li>You configure the LabVIEW Adapter to use the LabVIEW Run-Time Engine</li></ul> This error occurs because TestStand incorrectly generates the VI file path by replacing <code>LabVIEW\</code> with <code>TestStand\bin\</code>. 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 not specify a project path.
| |||||
| 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
| |||||
| 397556 Return | Keyboard entry is ignored when editing a code module from User Interface run in LabVIEW When you use a TestStand User Interface run in LabVIEW and you click the <strong>Edit VI</strong> button on the Module tab to edit a VI code module, you cannot use the keyboard when editing the code module. You can successfully initiate the operation to Edit Vi when running the TestStand User Interface as an executable. Workaround: Open and edit the VI directly in LabVIEW. Do not use the Edit VI button to open the VI.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 408196 Return | Installing a TestStand deployment does not report an error in some cases when importing an unsupported IVI configuration If you attempt to install a deployment importing 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
| |||||
| 409938 Return | ATML reports that use tr5_horizontal.xsl and tr6_horizontal stylesheet do not display icons correctly when report path contains Japanese characters When you execute a sequence file on a Japanese operating system and the report path contains Japanese characters, the ATML report stylesheet tr5_horizontal.xsl and tr6_horizontal cannot load the images for the expand/collapse button and the error icon. TestStand 2013 fixes this issue for all other stylesheets. Workaround: Click on expand/collapse button twice.
| |||||
| 413438 Return | LabWindows/CVI Adapter does not recognize object array or void* parameter types with fixed array size If you load a LabWindows/CVI 2013 or later built DLL code module that uses object array or void* parameter types with fixed array size, TestStand returns a warning to indicate that the prototype of the function cannot be read. Workaround: Manually configure the prototype on the Module tab or change the prototype in the code module to avoid object array or void* parameter types with fixed array size to work around this issue.
| |||||
| 194456 Return | Attempting to debug .NET steps from a TestStand UI built with only native debugging results in vague error message If you are attempting to debug .NET code modules using the TestStand debugging features and you are using a TestStand User Interface built with native-only debugging (managed debugging disabled), TestStand returns the following vague error: <br><br>The Step Into operation failed for the following reason: 'Win32 error: 0x8971001e' <br><br>In this case, the code module executes correctly, but you cannot debug the code. <br><br>Note: This is expected behavior. The error does not correctly indicate what is causing debugging to fail. Workaround: Ensure that mixed-mode debugging is enabled for any TestStand User Interface in which you need to debug .NET steps to work around this issue.
| |||||
| 444028 Return | LabVIEW code modules that use an identical name for a control and an indicator may cause unexpected behavior when used in a LabVIEW step If you create a LabVIEW VI where a control and an indicator use the same name (for example, a control and an indicator both named "Numeric"), unexpected behavior may occur when you use that VI in a LabVIEW step. This behavior could include errors in the parameter list or a message stating that the parameter list does not match the VI prototype. In some cases, the behavior may change when you save and re-open the sequence file. Workaround: National Instruments recommends that you rename controls and indicators in the VI so that no duplicate names exist.
| |||||
| 445032 Return | Report generation errors may occur if Sequence Call steps are filtered out of an ATML Report with on-the-fly logging enabled When generating ATML reports with On-The-Fly logging enabled, specifying a result filtering expression that excludes Sequence Call steps will return an "Index Out of Range" error and prevent the report from generating properly. Workaround: Change the result filtering expression to include either all Sequence Call steps or all steps with a "Running" status. The following example shows this modification for the "Exclude Passed/Done" result filtering setting: Result.Status == "Passed" || Result.Status == "Done" || Result.Status == "Running"
| |||||
| 425989 Return | File Diff/Merge Utility may report conflicts when subproperties are edited in one file and deleted in another If you use the File Diff/Merge Utility to compare two files, modify a subproperty in File 1, and delete the subproperty's parent property in File 2, the Merged File will display the parent property as deleted and report a conflict for the modified subproperty from File 1. You cannot directly right-click on the subproperty to resolve the conflict. Workaround: Use the right-click context menu options for the parent property to resolve the conflict.
| |||||
| 443554 Return | TestStand user interface control scrollbars may appear narrow or not display properly when font size is set to greater than 100% TestStand Sequence Editor and user interface control scrollbars may appear narrow or not display properly when when font size is set to greater than 100% on a high-DPI monitor. Workaround: Set font size to 100% or a value where scrollbar display is acceptable.
| |||||
| 460419 Return | Running Sequence Analyzer may result in prototype mismatch errors for string arguments in C/C++ DLL code modules Analyzing a sequence file with the Sequence Analyzer may result in a prototype mismatch error for certain C/C++ DLL call steps with a string argument. The issue is most likely to occur when the code module prototype specifies a buffer size for a string argument, such as char[256]. If TestStand has a different buffer size listed for the string parameter, such as a size of 1024, the mismatch error may occur. This issue can be resolved by clicking the red error icon, which updates the TestStand parameter settings to match those of the DLL function prototype. The TestStand 2013 process models contain steps that contain this prototype mismatch. Workaround: Click on the error icon to refresh the prototype for steps reporting the error. This action reloads the prototype and eliminates the error message.
| |||||
| 470651 Return | Attempting to perform a Step Into operation while paused at breakpoints in two threads will result in a Step Over operation being performed instead If you are paused at breakpoints in two threads and attempt to Step Into one of the threads, a Step Over operation will be performed instead. This issue occurs only when execution is paused at multiple breakpoints simultaneously. Workaround: Remove or disable breakpoints that could be encountered in threads other than the one you are currently debugging.
| |||||
| 478648 Return | The Offiline Results Processing Utility will not maximize from the system tray while it is displaying a recurring error notification In some cases, the Offline Results Processing Utility might start display notifications in the system tray, such as when it is attempting to process a read-only file. If the utility is minimized to the system tray when these errors occur, you cannot maximize the utility by clicking its icon in the tray. Workaround: You can execute only one instance of the Offline Results Processing Utility at a time, so opening the utility again will maximize the current instance. You can launch the Offline Results Processing Utility either from the Start menu or from the Tools menu in the TestStand Sequence Editor.
| |||||
| 478779 Return | An error may result when multiple threads access and save a LabVIEW class reference stored in a StationGlobal or shared FileGlobal variable When multiple threads access a LabVIEW class reference from a shared variable, such as a StationGlobal, and save the class reference back to the variable after a Class Member Call, an error may occur due to a race condition. This error occurs because the LabVIEW class reference may change during the Class Member Call, causing the previous class reference to be released. This outcome can result in other threads attempting to access a LabVIEW class reference that no longer exists. A -18001 error code is most commonly seen with this issue, but other error codes may also appear. Workaround: Use one of the following workarounds to resolve this issue: <ul> <li>Use local variables to store LabVIEW class references.</li> <li>Do not save the LabVIEW class reference back to a shared variable after a Class Member Call step.</li> </ul>
|
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 482840 Return | The ListBox UIControl does not correctly refresh data when connected as an ExecutionList of Execution View Manager. When creating a TestStand UI using a TestStand ListBox that is connected to an ExecutionList of the Execution View Manager, the control does not always show the correct list of executions. This problem is more noticeable for user interfaces that use the batch process model. Workaround: Complete either of the following to work around this issue: <ul> <li>Use a ComboBox.</li> <li>Implement the ExecutionList functionality with a ListBox in the native language of the UI.</li> </ul>
| |||||
| 484775 Return | -A -18002 type mismatch error may occur on a LabVIEW adapter step with parameters set to use a default value when the RunState.Execution.SetSequenceDefaultValues() TestStand API method is used in the execution. When a LabVIEW code module is dynamically loaded but not dynamically unloaded and the RunState.Execution.SetSequenceDefaultValues() method is used to set default values for the sequence, the -18002 error will occur if the parameters for the LabVIEW code module are configured to pass a default value to the code module. This issue usually occurs when restarting an execution after a previous execution completes. Workaround: Configure the LabVIEW adapter step to unload after the step executes. Additionally, you can prevent this issue from occurring by not restarting a completed execution.
| |||||
| 491296 Return | On-The-Fly ATML reports will not show the updated serial number if the serial number is changed after the PreUUT callback. When you are generating an ATML report with On-The-Fly reporting enabled, and you change the UUT serial number after the PreUUT callback, the serial number will not be updated in the report header. Workaround: N/A
| |||||
| 493571 Return | LabVIEW code modules with a NI VeriStand .NET type definition reference as a VI parameter will fail to load in TestStand when the LabVIEW Development System is active. This issue only occurs when using the Workspace Manager or Project reference from the NI VeriStand API. These references are .NET objects type definitions in LabVIEW. Workaround: There are two ways to prevent this issue from occurring: <ul> <li>Configure the LabVIEW adapter or the step to use the LabVIEW Runtime rather than the LabVIEW Development System.</li> <li>In LabVIEW, disconnect the .NET reference from the LabVIEW type definition.</li> </ul>
| |||||
| 498737 Return | Using the <xsl:output method="xml"> statement in a report stylesheet to transform report XML into a custom XML format will cause the report to not display properly after execution. When displaying a report which uses a stylesheet with this statement in a TestStand ReportView control, such as in the Sequence Editor or a TestStand user interface, the report will not display properly. However, the report will appear properly when displayed in Internet Explorer. Workaround: There are two ways to resolve this issue: <ul> <li>Use the custom stylesheet to transform the XML format and set the output XML from this transform as the report string in the Report object within the Report result processing plugin.</li> <li>Create a custom model plugin to generate the XML directly in the format you prefer to use.</li> </ul>
| |||||
| 509895 Return | A type conflict dialog box generates when a file is loaded which contains a modified version of CommonResults or NI_UserCustomPrivileges types. This issue occurs when the first file which uses one of the modified types is loaded, and occurs even if the Allow Automatic Type Resolution station option is set to Never. Workaround: Complete either of the following steps to workaround this issue: <ul> <li>Avoid modifying the CommonResults or NI_UserCustomPrivilege types.</li> <li>Avoid using the Never option for the Allow Automatic Type Resolution station option. The Only if Type Palette file has the Higher Version option will not automatically resolve conflicts between two sequence files unless the type is also stored in a type palette file.</li> </ul>
| |||||
| 51517 47SGL33Q Return | Passing the FileGlobals PropertyObject as a parameter to a subsequence in the Batch process model will cause a PropertyObject leak warning dialog to appear when the TestStand Engine is shut down. This issue only occurs if the entire FileGlobals container is passed as a parameter into a subsequence, such as Single Pass -- Test Socket Entry Point. Workaround: Create a container within the FileGlobals container to hold the properties you wish to pass into the subsequence, and pass this container instead of the top-level FileGlobals container.
| |||||
| 516361 Return | Expression error will occur when attempting to store a System.Object[] return value from a .NET code module into an array of 64-bit integers in TestStand. When a .NET code module returns an array of 64-bit numbers as a System.Object[] data type, specifying a TestStand variable which is an array of 64-bit integers in the parameter expression for the return value will result in an expression error during sequence analysis. Workaround: It is safe to ignore this error. The data is stored correctly in the TestStand array when the sequence is executed.
| |||||
| 535022 Return | Editing a localized expression in the Variables View does not properly unlocalize the expression before storing the value back into the variable. For example, editing an expression in the Variables View that is localized to use commas as decimal points will lead lead to unexpected token errors when the commas are stored instead of periods. Workaround: Do not use the Variables View to edit expression values when using localized OS and TestStand settings, or turn off the localized decimal point option in OS or TestStand.
| |||||
| 507397 Return | TestStand cannot find class definition in source files for VB.NET classes in Visual Studio If you have configured your .NET step to use a VB.NET project and source file, and try to click the Edit Code button, TestStand will throw the following error: "The class definition for '<NameOfClass>' cannot be found in the specified source file or project." even though the class is defined in your source file. Workaround: Navigate to the class definition manually.
| |||||
| 544646 Return | Error -17313 or -18005 occurs when passing a .NET refnum constant in a cluster from newer versions of LabVIEW into TestStand If a LabVIEW VI with a cluster that contains a .NET refnum is passed into TestStand, then error -17313 or -18005 may occur. An example of this type of refnum would be when you create a constant from a .NET terminal in LabVIEW. Workaround: Construct the .NET object from a constructor node in LabVIEW, bundle it into a cluster, and pass that cluster out of LabVIEW.
| |||||
| 547957 Return | LabVIEW "key down?" event is not triggered when using the space or enter keys for TestStand ActiveX button controls LabVIEW UI event structures do not trigger a "key down?" or "key down" event on TestStand ActiveX Buttons, but other keystrokes do fire an event. Workaround: Use a LabVIEW button and bind it to TestStand functionality.
| |||||
| 555104 Return | Error -18005 occurs when passing a LabVIEW "Not a Path" constant from TestStand into LabVIEW Passing a "Not a Path" constant from LabVIEW to TestStand and then passing that constant back from TestStand to LabVIEW in the LabVIEW RTE results in the following error: -18005; Failed to convert a TestStand type to a LabVIEW type or vice versa. Workaround: Use an empty string instead of the "Not a Path" constant.
| |||||
| 566400 Return | LabVIEW VI absolute path check does not handle PPLs properly At load time, when the LabVIEW Adapter checks VI paths to make sure they are not pointing to two different copies of VIs with the same name, the code does not properly account for PPLs. If two steps reference a VI with the same name in the same PPL located in different places on disk, the first VI loaded should be used for both VI calls. However, because the function that checks the VI paths does not correctly handle PPLs, an error is generated. Workaround: Ensure that you only include and invoke one copy of the PPL in your test system. Alternatively, to prevent the error from occurring, you can manually load the PPL from the location on disk that you want to use. You can do this either by calling a dummy VI in the PPL or by using Open VI Reference in a user interface and then leaking the reference.
| |||||
| 589962 Return | Expand and Report stylesheets for ATML 5.00 and ATML 6.01 Standards Report Document can display subsequent step results as indices results If you configure the Looping section for a step without enabling the "Record Result of Each Iteration" option, an ATML 5.00 or 6.0.1 Standards Report Document that uses the Expand or Report stylesheets incorrectly displays the results for subsequent steps as the indices results for the looping step. Workaround: Enable the "Record Result of Each Iteration" option, or use the Horizontal style sheet instead.
| |||||
| 607873 Return | Database Viewer does not support viewing of an Oracle database through ODBC driver. When you use Database Viewer to access an Oracle database through an ODBC driver, it results in an error that states "ORA-01406: fetched column value was truncated". Workaround: Use an OLE DB provider to access the Oracle database, instead of an ODBC driver. Refer to the TestStand Help topic "Configuring Connection Strings" for examples of OLE DB connection strings and required Oracle client components for Oracle databases.
| |||||
| 607455 Return | Database logging hangs and eventually errors when connection string uses Microsoft Access 2016 (ACE.OLEDB.16.0) provider The error returned is -2147352567. Workaround: 1) For 32-bit TestStand, use the Microsoft Access JET provider. 2) For 32-bit or 64-bit TestStand, use the ACE.OLEDB.15.0 or ACE.OLEDB.12.0 provider (as long as ACE.OLEDB.16.0 is not installed).
| |||||
| 598272 Return | Redesigned Property Loader does not allow you to undo an action when importing from Legacy Property Loader source When importing from a legacy source in the redesigned Property Loader, undo items are not added to the undo stack of the sequence file. Workaround: N/A
| |||||
| 615962 Return | Limits for Numeric Limit Test and Multiple Numeric Limit Test steps do not show EQT comparison options when the comparison type is specified by an expression or when you are editing multiple steps If the comparison type is specified by an expression or if you have selected more than one of these steps, the Limits tab options display only the non-EQT comparison types, which do not show Threshold Type and Nominal Value. Workaround: Change expression to "EQT", set Threshold Type and Nominal Value, then switch Comparison Type back to combined expression.
| |||||
| 632567 Return | LabVIEW operator interfaces built in LabVIEW 2016 might be slow to exit When you exit a LabVIEW operator interface built in LabVIEW 2016, the operator interface might be slow when exiting the process. Workaround: Rebuild the operator interface in LabVIEW 2015 SP1 or earlier.
| |||||
| 632793 Return | Adding StationGlobals in Variables pane does not refresh the Property Selector view of a Property Loader step If you add a new StationGlobal variable while the Step Settings for a Property Loader step are open on the Target File and Source Settings tab, the new variable is not automatically added in the Property Selector view. Workaround: Switch tabs to refresh the Property Selector control.
| |||||
| 643628 Return | Attempting to log INF, NAN, or IND values to a Microsoft SQL Server database results in an error. Microsoft SQL Server FLOAT data type does NOT support storing +INF, -INF, NAN and IND as defined by IEEE 754. Workaround: Update your schema to use a precondition expression to not log a value for non-finite values.
| |||||
| 663020 Return | Tab order is incorrect in the LabVIEW NXG Simple User Interface. N/A Workaround: Fix the tab order in LabVIEW NXG and rebuild the executable.
| |||||
| 664496 Return | Selecting a file path longer than 256 characters in the LabVIEW NXG Adapter will cause unexpected behavior. N/A Workaround: Do not use a file path longer than 256 characters.
| |||||
| 678105 Return | The TestStand Deployment Utility returns the error -19062 when deploying components to a local repository or package installer. If the "NI Certificates Installer" package is not installed on the system, and NI Package Manager cannot locate the package on one of its feeds, when the TestStand Deployment Utility attempts to include NI Certificates package in the distribution, the build returns "error -19062: Could not calculate EULA dependencies". Workaround: You can do one of the following: 1) Open NI Package Manager after installation which will register the required feeds with ni.com. 2) Manually install the "NI Certificates Packages" on the system 3) Disable the option "Include NI Certificates Package" on the Configure Package Attributes dialog.
| |||||
| 655076 Return | The /Version command line argument for the TestStand Version Selector does not work with minor versions. When using a minor version, such as 16.1 (TestStand 2016 SP1) with the /Version argument, the TestStand Version Selector unregisters the active version, does not register any new version, and does not report any errors. Workaround: Use the major version. For example, 16.0 instead of 16.1.
| |||||
| 658107 Return | Invalid paths for non-LabVIEW steps do not migrate properly when using the TestStand LabVIEW NXG Conversion Utility. If a step that does not use the LabVIEW adapter contains an invalid path in the original sequence file, the converted file will contain an empty string for the path. Additionally, absolute paths for the PropertyLoader steps will be unchanged by the conversion utility, instead of updating to a new absolute path to the converted output. Workaround: N/A
| |||||
| 658319 Return | Connector panes that reference large LabVIEW class hierarchies reload the entire hierarchy when selecting a step. If a LabVIEW step references a VI whose connector panes uses data value references or directly uses a large LabVIEW class, the TestStand Sequence Editor reloads the step and all of its dependencies each time the step is selected. Workaround: In the sequence file properties, set the Load Option to Preload when opening sequence file.
| |||||
| 662205 Return | Unable to update existing type definition for an array of clusters containing an enum from a LabVIEW NXG code module. The Create/Update Custom Data Type dialog box's option to "Update an Existing Type" will not update the TestStand type definition from LabVIEW NXG if the type has an array of clusters that contains an enum. After pressing the "Update an Existing Type" button you will see that no changes to the TestStand type definition were made. Workaround: You can manually update the TestStand type definition, or delete the existing type and create a new type definition in TestStand.
| |||||
| 665065 Return | LabVIEW Full-Featured UI hangs while running in the development environment while it loads a code module in a LabVIEW Project. When running" Full UI - Top-Level VI.vi" from the LabVIEW Full-Featured UI example project in the LabVIEW Development Environment, a hang occurs when attempting to execute a sequence that contains a code module that loads from a separate LabVIEW project. Workaround: The hang only occurs when running the UI in the LabVIEW Development Environment. Build the UI into TestExec.exe before executing the sequence.
| |||||
| 669606 Return | Analog Waveform variables that contain attributes generate a run-time error when passed to LabVIEW NXG. If a local variable of an Analog Waveform is passed to a LabVIEW NXG code module and has one or more attributes, then a run-time error is generated when executing the step in the LabVIEW NXG Development Environment. The error will not occur when executing with the LabVIEW NXG Run-Time Engine. Workaround: Set adapter configuration to use LabVIEW NXG Run-Time Engine.
| |||||
| 669830 Return | The "Undock Labview NXG Help" button is missing from User Interfaces when they are in editor mode. In the step settings pane of a LabVIEW NXG step, the "Undock LabVIEW NXG Help" button is missing in a User Interface when it is in editor mode. Workaround: N/A
| |||||
| 671819 Return | When overwriting a LabVIEW NXG Project through TestStand, a new instance of LabVIEW NXG is launched with the same project name while the original project is still loaded in the first LabVIEW NXG instance. When using the "Create New LabVIEW NXG Project..." option to overwrite an existing project, TestStand launches a second instance of LabVIEW NXG with the same name instead of replacing the existing LabVIEW NXG instance. Workaround: Close the first instance of the LabVIEW NXG project or use LabVIEW NXG to overwrite a project.
| |||||
| 675567 Return | LabVIEW NXG does not support a container with an array element of containers. If a parameter for a LabVIEW NXG VI is a container with an element that is an array of containers, the step will not be configurable and will result in a compatibility error. Workaround: N/A
| |||||
| 675658 Return | The Conversion Utility reports "Conversion of Files Completed", when no files have been converted. If the user has read-only access to the output directory, the conversion utility will report "Conversion of Files Completed", but will also report the error "failed to copy files to target location". Workaround: Use a directory with write access.
| |||||
| 676017 Return | The Edit Code button for a C++ DLL does not work with Visual Studio 2017. The Edit Code button will not work when targeting a C++ DLL project built with Visual Studio 2017. Workaround: Manually open the Visual Studio 2017 project.
| |||||
| 683498 Return | Common Parameters are Disabled When Selecting Multiple LabVIEW NXG Steps When selecting multiple LabVIEW NXG steps to edit common properties, all properties will be disabled rendering them unable to be edited. Workaround: Edit step properties individually.
| |||||
| 684110 Return | Clicking on the filter icon for the file column in the log window of the TestStand LabVIEW NXG Conversion Utility throws an exception. When pressing the filter icon button in the TestStand LabVIEW NXG Conversion Utility, the exception "Object reference not set to an instance of an object." occurs. Workaround: N/A
| |||||
| 600209 Return | Logging the default value of a LabVIEW complex number parameter fails When the default value box for a LabVIEW complex number parameter is checked and logging for the parameter is enable, this will fail with an error stating "Unable to find variable or property". Workaround: Uncheck the default value box and manually enter the default value.
| |||||
| 687192 Return | Comments for a variable do not show up in ATML and XML reports When logging variable to an ATML or XML report, the comments added to a variable are not written to the report. Workaround: Customize the report or use HTML or ASCII report options
| |||||
| 710154 Return | Editing a Sequence Analyzer rule that references a LabVIEW NXG code module crashes the Sequence Analyzer dialog If a rule has been created in the Sequence Analyzer that refers to a LabVIEW NXG code module, then when the "Edit Rule" button is hit it will cause the Sequence Analyzer Available Rules dialog to crash. Workaround: N/A
| |||||
| 711553 Return | Changing base destination of a packed project library in the TestStand Deployment Utility causes the build to fail When building a packed project library with the Deployment Utility, you can select the .lvlibp item in the distributed files tab and change the base destination of the library. If you do so, the VIs in the library are incorrectly configured to have a destination subdirectory which matches the library name. This invalid setting causes the build to fail. Workaround: To fix the error, the setting to build a packed project library must be disabled, remove the folder destination from the files, then re-enable the setting. You can successfully change the library destination by configuring the base destination of VIs within the library individually, or by changing the base destination of a parent directory of the library.
| |||||
| 716835 Return | Time Stamp conversion fails intermittently when value passes between TestStand and LabVIEW At random times when Time Stamps are passed back and forth between TestStand and LabVIEW, TestStand sends a Time Stamp string with a resolution of 0.0001 seconds instead of 0.001 seconds. This causes LabVIEW to dafault to an emtpy "00:00:00.000 PM MM/DD/YYYY" Time Stamp. Workaround: Add error checking code in TestStand to make sure the Time Stamp string has a correct format before passing it to LabVIEW.
| |||||
| 718241 Return | Sequence Analyzer errors With "Invalid Escape Sequence in Expression" when using "\xNN" or "\NN" TestStand recognizes "\xNN" or "\NN" as valid special string characters and will support them at run-time. At edit-time the Sequence Analyzer will throw an error when handling strings with these characters. Workaround: You can use Chr(0x30) as a substitute. Longer strings can be concatenated together via "&", Chr(0x30) & Chr(0x31) & Chr(0x32). Or the Sequence analyzer rule can also be configured to be ignore.
| |||||
| 718635 Return | TestStand Diff and Merge Utility produces unreadable XML report when analyzing sequences with invalid characters The utility will produces an unreadable XML report when processing strings that contain characters outside of the XML valid character range, such as ASCII control characters. This can commonly occur in situations where raw data is stored in a string. Workaround: Remove invalid characters from the sequence.
| |||||
| 720840 Return | Create Code for DLL Step does not work with Visual Studio and unspecified source files For a DLL step that is configured to "Create and Edit Code in Visual Studio" and a source file is not specified, when the "Create Code" button is pressed a "File not found" error will pop-up. Workaround: Create code with LabWindows/CVI, a plain text file, or specify source files.
| |||||
| 720987 Return | Error OUT or INOUT argument 1 for routine 'stored procedure name' is not a variable or NEW pseudo-variable in BEFORE trigger occurs when using a stored procedure with an Out parameter in a MySQL database This error occurs in custom schemas that use out parameters in stored procedures. This is a known MySQL bug: Out parameters error on second call when statement is a prepared statement. Note, the first stored procedure call will be successful, but the subsequent call will fail with this error. Workaround: N/A
| |||||
| 722577 Return | Random function in TestStand expressions can return the same value if re-seeded on every call When looping over the Random() function in a TestStand expression, if the random value is re-seeded on every call to the function over time it can return the same value on repeated calls. In general, re-seeding a pseudo-random number generator is something that should be done once, or at least rarely, for the lifetime of the use of that generator because it resets the pseudo-random number distribution. Workaround: Only re-seed the number once, not on every call.
| |||||
| 722820 Return | "Generate SQL" button of the Database Results Processor will output SQL of previous database connection string If the configuration of the database connection string is changed in the Database Results Processor, then the "Generate SQL" button is pressed, the SQL output will still be for the previous configuration of the database connection string. Workaround: Save changes to connection string and reopen dialog before using Generate SQL button.
|
Document last updated on 1/28/2019