Archived: TestStand 4.1 Known Issues

NI does not actively maintain this document.

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


This document has been archived and is no longer updated by National Instruments.

This document contains the TestStand 4.1 known issues that were discovered before and since the release of the TestStand 4.1. 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.


Known Issues


Issue ID Description
  You cannot install TestStand using a network path or a mapped network path. You must install TestStand on a local computer.
  If TestStand does not uninstall, reinstall TestStand and then uninstall it.
  When you uninstall TestStand 2.0 on a computer where you also installed TestStand 4.x, the TestStand 2.0 uninstaller might incorrectly remove the National Instruments Session Manager 4.xfiles. Run the repair utility on NI Session Manager by using the National Instruments Software maintenance utility located in Add/Remove Programs on the Windows Control Panel to restore these files.
  Do not install the IVI components from the TestStand 2.0 CD after you install the IVI Compliance Package (ICP) from the NI Device Driver CD included with TestStand 4.x.

If you installed ICP 2.2 or later from the NI Device Driver CD before you installed TestStand 2.0, do not install the IVI components from the TestStand 2.0 CD. Disable the Basic IVI Class Drivers feature within the IVI Engine and Drivers feature during the installation of TestStand 2.0.

If you installed the TestStand 2.0 IVI components after you installed ICP 2.2 or later from the NI Device Driver CD, run the repair utility on the ICP product by using the National Instruments Software maintenance utility located in Add/Remove Programs on the Windows Control Panel to correct this incompatibility.
If you attempt to install TestStand 2.0.1 on a computer where you also installed the LabWindows™/CVI™ Run-Time Engine (RTE), which TestStand 4.x installs, the TestStand 2.0.1 installer returns an error while installing the engine. After the installation, TestStand 2.0.1 does not work correctly, and if installed, TestStand 4.x no longer works correctly even if you repair the TestStand 4.x installation. To restore the TestStand 4.x installation after failing to install TestStand 2.0.1, you must run the repair utility on the LabWindows/CVI RTE by using the National Instruments Software maintenance utility located in Add/Remove Programs on the Windows Control Panel and then use the TestStand Version Selector application to reselect TestStand 4.x as the active version.

Complete the following steps if you want to install TestStand 2.0.1 on a computer on which you also installed the LabWindows/CVI RTE.
  1. Navigate to Add/Remove Programs on the Windows Control Panel to uninstall the LabWindows/CVI RTE. You must uninstall any software that is dependent on the run-time engine before you attempt to uninstall the LabWindows/CVI RTE.
  2. Confirm that the following files and subdirectory were removed from the Windows\System32 directory: cvirt.dllcvirte.dllcvi95vxd.vxd, and \cvirte. If the files still exist, manually remove them. If you cannot delete the \cvirte subdirectory, delete the .dll files first, restart the computer, and then try to delete the subdirectory.
  3. Install TestStand 2.0.1.
  4. You can now reinstall the LabWindows/CVI RTE.

This issue also occurs when you install LabVIEW 6.0 on a computer on which you also installed the LabWindows/CVI RTE using TestStand 4.x.

Windows Vista

Issue ID Description
95329 Windows Vista introduced a change in behavior that can cause applications to receive WM_PAINT messages unexpectedly while performing ActiveX/COM calls from .NET components or .NET applications. This behavior change can cause applications, such as the TestStand Sequence Editor and applications that use the TestStand User Interface controls, to generate errors or possibly crash. To avoid these problems, you must create a custom compatibility database for TestStand applications using the Compatibility Administrator utility from the Microsoft Application Compatibility Toolkit for Microsoft Windows. Refer to National Instruments KnowledgeBase article 4KAD5TT3 located at for more information about the change in behavior and how to work around this issue.
53369 When you place a checkmark in the Don't remind me again until 7 days from expiration checkbox in the National Instruments License Manager dialog box, the dialog box continues to launch on Windows Vista.

TestStand Sequence Editor

Issue ID Description
By default, the TestStand Sequence Editor caches execution windows to work around an issue where the operating system occasionally leaks objects when you close windows. As a result of this caching, the sequence editor process holds on to Windows USER objects and GDI objects. The Windows Task Manager reports that the sequence editor does not release USER and GDI objects when you close execution windows, which is expected behavior because the sequence editor re-uses the USER and GDI objects in subsequent executions. By default, TestStand caches all execution windows until the number of available USER objects or GDI objects in the TestStand process is less than 1,000.

Typically, you do not need to change this limit, but you can specify the maximum number of windows in the cache by creating a DWORD registry value named SeqeditExeDocCacheSize under the HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\TestStand\4.x key. The recommended value is the number of execution windows you typically have open concurrently when running executions in the sequence editor. For example, if you typically run a batch process with 8 test sockets, specify a value of 9, which includes eight executions that correspond to the test sockets and one controlling execution. You might leak USER objects and GDI objects when the number of concurrent execution windows you create is greater than the number you specify in the registry. The registry entry is an unsigned integer. A value of 0 disables the cache. 

When the sequence editor attempts to open a new document and finds that there are fewer than 500 USER objects or GDI objects available, it clears the cache and returns a warning message.
51293 The TestStand Sequence Editor occasionally reports property object leaks when you use the Close item from the taskbar context menu to close the application and you enabled the Report Object Leaks option in the Debug Options dialog box you access from the Preferences tab of the Station Options dialog box.
44I6TCGH The TestStand Sequence Editor can hang when you right-click a file on the Workspace pane, select Show Differences from the context menu, and the difference and merge utilities that the source control provider specifies are not installed.
51301 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.
51062 The TestStand Sequence Editor incorrectly prompts you to unlock a file before launching the Sequence Properties or Sequence File Properties dialog boxes.
51030 Changing the step selection on the Steps pane of the TestStand Sequence Editor is slow when you select an element of a large array on the Variables pane.
51578 The LabVIEW Module tab incorrectly launches the Create Custom Data Type from Cluster dialog box multiple times when you select multiple steps and you click the Create Custom Data Type button. Instead, select only one step before you click the button.
47TENN00 Using Watch View pane expressions that modify the structure of objects, such as deleting subproperties or changing the size of an array, can prevent the Variables pane from refreshing correctly or can cause the Variables pane to generate errors.
42416 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.
102700 The Watch View pane does not refresh the value and remove the error icon in some cases after you modify the watch expression. You must single step or resume the execution to work around this issue.
104628 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.

TestStand User Interface (UI) Controls

Issue ID Description
  If you click TestStand User Interface (UI) Controls hosted in a .NET user control in the designer of Microsoft Visual Studio 2005, Visual Studio might crash. Refer to the Microsoft Knowledge Base article ID 916495, located at, for more information about the hotfix for this Visual Studio 2005 limitation.
50421 The VariablesView control can leak a Windows USER object when you use the keyboard to change a Boolean value.
50418 The SequenceView and ListBar controls can leak memory when you quickly launch and dismiss the context menu multiple times.
50235 You cannot use the keyboard to navigate to the adapter buttons within the InsertionPalette control for non-.NET applications.
51251 The CheckBox.Forecolor and CheckBox.BackColor properties do not change the appearance of a control when you set the CheckBox.Style property to CheckBoxStyle_Button.


Issue ID Description
47SHLAM0 TestStand supports Sequence File Translators built with LabVIEW only if built with LabVIEW 8.2 and later.
3P6H4CUZ If you uninstall LabVIEW 8.0 from a computer where you also installed LabVIEW 7.1.1, TestStand might return an error when executing a VI that uses a waveform data type. The error states that TestStand does not find a waveform interface. Run the repair utility on LabVIEW 7.1.1 by using the National Instruments Software maintenance utility located in Add/Remove Programs on the Windows Control Panel to correct this issue.
  TestStand does not support calling VIs on remote computers if you save a VI without the block diagram and the version of the VI is different than the active version of LabVIEW installed on the computer.
3QGCESYL LabVIEW user interface executables that do not use the TestStand ActiveX UI Controls might hang when launched. The hang occurs when TestStand loads the LabWindows/CVI RTE and both LabVIEW and the run-time engine access computer resources at the same time. You can prevent the hang by using a Call Library Function VI to invoke a function in the run-time engine to force LabVIEW to synchronously load the run-time engine into memory before creating the TestStand engine.
  A LabVIEW Run-Time Engine (RTE) cannot load a top-level VI when the LabVIEW RTE finds a subVI with the same name and the subVI was saved with a different version of LabVIEW. This behavior can occur when you try to run a VI you save in the <TestStand>\API directory and the <TestStand Public>\Examples directory, the directories contain VIs with the same names as the subVIs the VI uses, and the VIs were saved with a different version of LabVIEW. The <TestStand Public>\Examples directory is located at C:\Documents and Settings\All Users\Documents\National Instruments\TestStand x.x\Examples on Windows 2000/XP and at C:\Users\Public\Documents\National Instruments\TestStand x.x\Examples on Windows Vista. Save VIs in a working directory instead of using the TestStand directories to work around this issue.

Normally, the LabVIEW RTE can execute top-level VIs only when you save the VI with the entire VI hierarchy or if the LabVIEW RTE can locate the subVIs using the LabVIEW search directories. By default, the LabVIEW RTE does not search for required subVIs from the LabVIEW development system, such as files in vi.lib. However, when TestStand loads a LabVIEW RTE on a computer where you also installed the LabVIEW development system, TestStand automatically adds directories from the development system to the search paths for the LabVIEW RTE. Thus, when TestStand executes a top-level VI saved without its hierarchy, the LabVIEW RTE attempts to find subVIs by first searching the directory of the top-level VI and then searching the directories TestStand added. If the LabVIEW RTE finds a subVI saved by a different version of LabVIEW first, the LabVIEW RTE cannot load the subVI and does not load the top-level VI.
49856 LabVIEW does not call PreTranslateAccelerator for ActiveX controls, which prevents TestStand UI Controls in LabVIEW user interfaces from processing some key strokes, such as pressing <Tab> to autocomplete expressions or navigate within controls, pressing <Ctrl-Shift> to perform an operation, or pressing <Shift-Arrow> to select multiple items.
51302 A TestStand 3.5 operator interface built with LabVIEW 7.0 might not launch or can return a misleading error message if the LabVIEW 7.0 RTE is not installed. TestStand 4.x does not install the LabVIEW 7.0 RTE.
50897 The Help»Help Topic menu item is disabled in the TestStand LabVIEW User Interface after you use the command the first time. Press <Ctrl-F1> instead to work around this issue.
47T9I100 LabVIEW applications, such as a TestStand LabVIEW User Interface, can hang when you call a function in a LabVIEW-built DLL from the UI thread. For example, a TestStand LabVIEW User Interface can hang when you create the TestStand Engine and the engine loads a Sequence File Translator DLL built with LabVIEW. Create the TestStand Engine in a non-UI thread, such as Other 2, to work around this issue.
51491 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.
When you use the LabVIEW RTE to run a legacy VI the Convert LabVIEW Test Executive Sequence tool generates, the LabVIEW Adapter incorrectly copies the User Output element of the TestData cluster to the Step.Result.ReportText property and ignores the Comment element of the TestData cluster. Respecify the module call for these steps or select Tools»Update VI Calls in the sequence editor to update all the steps in the sequence file to work around this issue.
41665 LabVIEW 8.5.x returns a warning when you load the simple user interface example. The warning indicates that LabVIEW changed a constant wired to a Case structure to maintain compatibility with LabVIEW 7.1 and earlier. The warning does not prevent the user interface from working correctly.
97923 You cannot select an XNode-based Express VI from the most recently used list on the LabVIEW Module tab.
53736 You cannot access property pages from the context menu in LabVIEW 8.5 for TestStand controls, such as the InsertionPalette. Disable then re-enable the Advanced»Design Mode item in the context menu of the control to work around this issue.
49942 When you use a keyboard shortcut in the TestStand LabVIEW User Interface, LabVIEW correctly shows that the corresponding button has focus, but the tab order then becomes invalid.
40001 The LabVIEW Adapter returns an error when unpacking a LabVIEW 8.5 and later complex waveform data type.
51752 When you run a VI from TestStand and the VI contains a breakpoint, TestStand does not bring the VI window to the front when the VI reaches the breakpoint.
101510 A LabVIEW user interface reports object leaks on shutdown when you pass a TestStand object as the ActiveXData parameter of a UIMessage in the UIMessage callback VI. LabVIEW does not release the object reference until you unload the LabVIEW callback VI. Refer to the National Instruments KnowledgeBase article 4H6DULT3, located at, for more information about using a dynamically called VI to ensure that LabVIEW releases the object.
44772 A LabVIEW user interface can hang when a UIMessage callback VI dynamically calls a VI that requires the UI thread while you interact with controls on any VI.
44466 A VI that TestStand calls hangs immediately after you close the prompt the Browse button of a Path control launches if the version of LabVIEW that built the user interface is the same as the version of the LabVIEW RTE that TestStand uses. Interacting with the VI, such as moving, resizing, or clicking a scrollbar or another control, restores the VI to an active state.
35000 A LabVIEW user interface from an earlier version of TestStand might return an error if you mass compile and run the application with a newer version of TestStand because the user interface incorrectly links to earlier versions of the TestStand palette VIs. For example, the TestStand 2.0.1 style user interface generates the following error: "Unknown variable or property name 'logoutOnly'. Error accessing item 'logoutOnly'".
49503 You cannot use the LabVIEW RTE to load a VI when you add the VI to the LabVIEW library without saving the library. You must save the library first.
48357 The LabVIEW Adapter cannot browse to a VI in a LabVIEW library if the VI filename includes multibyte characters.
42811 A front panel control does not receive focus when TestStand calls the VI and the VI sets the Key Focus property on the control.
43509 A remote LabVIEW application crashes when a TestStand step calls a VI on the remote computer and you shut down the remote LabVIEW application before TestStand unloads the step.
100053 The Edit VI Call dialog box highlights expressions as an error for variables that have the same name as an enumeration value.


Issue ID Description
Data Execution Prevention (DEP) is a Windows security feature that prevents an application from executing dynamically loaded code. Calling LabWindows/CVI object and static library files from an executable with DEP enabled, such as a custom user interface, is not supported and results in an error.
39257 When you use the LabWindows/CVI Module tab in the sequence editor to create a LabWindows/CVI DLL, the Reload Prototype button on the LabWindows/CVI Module tab remains dimmed after you build the DLL in LabWindows/CVI.

Microsoft Visual Studio

Issue ID Description
98055 Stepping into a C++ or .NET code module results in an error if you already attached Visual Studio to the TestStand process and Visual Studio is not debugging native and managed code. The error message contains the text "Win32 error: 0x8971001e". TestStand fails when attempting to attach a new instance of Visual Studio to the process. You must specify to attach by debugging native and managed code types in Visual Studio to work around this issue.
50221 Visual Studio 2005 for C# might crash on exit when an inactive tab page on an open form in the designer includes certain ActiveX controls, such as when you exit Visual Studio with the main form open in the designer for the example in the <TestStand>\UserInterfaces\Full-Featured\CSharp directory. Close the form in the designer before you exit Visual Studio to avoid this harmless crash.
3WIBGCIF Visual Studio 2005 might crash when you rebuild a solution that uses the TestStand UI Controls and you try to view a Microsoft Windows Form in Design view. The Design view might not show the Windows Form, and you might receive error messages. Refer to the Microsoft Knowledge Base article 912019, located at, for more information about this issue.
51176 Visual Studio 2005 generates the error message "Parameter is not valid" when you attempt to select an icon file as the image for a TestStand UI Button control and the icon file contains only a 16-bit color image. Set the icon image programmatically at run-time or load an icon file that contains a 256-color image to work around this issue.
3I7D2U6I MFC-based applications, such as TestStand User Interfaces, can leak GDI objects on computers running Windows XP Service Pack 2 when the applications create and destroy child windows. Refer to the Microsoft Knowledge Base article 319740, located at, for information about how to resolve this known Microsoft bug.
51321 MFC-based TestStand User Interfaces can crash when you use the Workspace Browser dialog box with the Microsoft Team Foundation Server SCC provider. Programmatically install a different message filter to work around this issue. Contact NI Support for more information.
35150 If you use Visual Studio 2005 to step into C/C++ code from TestStand and then stop debugging in Visual Studio, future attempts to step into C/C++ code with Visual Studio 2005 generate a warning that TestStand will execute the step as if you executed a Step Over operation.
48970 TestStand ActiveX controls become invisible in the Visual Studio 2005 C# designer when you drag the controls into or out of a panel control. Close and reopen the designer to make the controls visible again.
51390 The .NET Adapter generates a run-time error when a step passes an empty array as a parameter. You must pass a non-empty array.
41350 The .NET Adapter Edit Code option does not work for functions with array parameters in Visual Basic projects.
41890 The .NET Adapter Edit Code option does not work for methods with enumeration parameters.
98173 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 indicates no source code is available for the current location.
98110 The .NET module Configure Class Constructor pane does not update parameters when the signature of the method changes while the step is selected. You must select a different step and reselect the step to refresh the pane.
98178 If a debugging session is already attached to TestStand, when you perform a step into operation for a .NET module from TestStand, TestStand instead performs a step over operation.
97704 The .NET Adapter specify module dialog box and panel do not handle array of enumeration parameters correctly. You cannot specify an argument for each individual item in the array or add new array elements.
52829 The C# and Visual Basic .NET user interfaces shut down without prompting to save when Windows shuts down.
95377 Loading and building the Visual Studio 2005 example .NET user interfaces in Visual Studio 2008 fail when the post-build action cannot locate mt.exe. Visual Studio 2008 includes a built-in feature for adding manifests to executables and no longer ships the mt.exe application that Visual Studio 2005 uses. Remove the post-build action and edit the project settings to embed the manifest in the executable.

TestStand Deployment Utility

Issue ID Description
Building a deployment fails when you include any VI that uses NI_AALPro.lvlib in its hierarchy and you previously installed LabVIEW 8.2.1 over LabVIEW 8.2. The deployment utility does not load broken VIs the library might use. To fix the broken VIs, run the repair utility on LabVIEW 8.2.1 by using the National Instruments Software maintenance utility located in Add/Remove Programs on the Windows Control Panel. You can also uninstall and reinstall LabVIEW 8.2.1 to work around this issue.
41133 The TestStand Deployment Utility does not deploy LabVIEW classes that include overridden methods because two different VIs with the same name cannot be loaded in memory at the same time. Instead of using the deployment utility to distribute the overridden VIs, create a source distribution and manually copy the source distribution to the destination.


Issue ID Description
  Applications that create and destroy the Microsoft Internet Explorer (IE) control might leak GDI memory, which can make the application and the computer unstable. The memory leak occurs when you run the application on Windows XP SP2 and you installed the Handwriting feature (Version 1.0.1038 of the Skchui.dll file) for a Microsoft Office product on the computer. For TestStand, the sequence editor creates new instances of the IE control for each new execution document, and each ReportView user interface control creates a new instance of the IE control. To prevent this GDI memory leak, uninstall the Handwriting feature for any Microsoft Office product and for any other product that uses this shared feature. Contact National Instruments or refer to the Microsoft Knowledge Base article 896429, located at, for more information about this issue.
The Microsoft IE control that TestStand applications use to show XML reports can leak handles or crash if the control cannot find the stylesheet you specify in the Report Options dialog box and the control shows XML report files using the default XML stylesheet.
48066 The Allow All Users Access from Remote Machines option on the Remote Execution tab of the Station Options dialog box does not work on some non-English Windows XP SP2 operating systems, such as German Windows XP. The option adds the built-in account name ANONYMOUS LOGON to the DCOM access permissions, but the account name ANONYMOUS LOGON is incorrect for some non-English operating systems. If you use a non-English Windows XP SP2 or later, refer to the Setting Windows System Security section of Chapter 5, Adapters, of the NI TestStand Reference Manual for more information about configuring Windows system security to allow users to access and launch the TestStand server remotely.
3JABQP3S XML reports might show a table of measurement data instead of a graph in the following situations:
  • The TSGraphControl.ocx ActiveX control, located in the <TestStand Public>\Components\Tools\GraphControl directory, is not installed or registered on the computer.
  • Internet Explorer security settings can prevent Web pages from using scripting to create and use an ActiveX control. When you view Web pages located on the computer, Internet Explorer uses the My Computer zone setting on the Security tab of the Internet Options dialog box. By default for Windows XP SP2, the security level for the My Computer zone is set to High, which prevents scripting from running locally. By default, the settings for the My Computer zone are not visible in the Internet Options dialog box of Internet Explorer. Refer to the Microsoft Knowledge Base, including articles 315933 and 182569, located at, for more information about altering the Windows registry to make the My Computer zone visible in the Internet Options dialog box of the version of Internet Explorer you use. When you have access to the My Computer zone settings in the Internet Options dialog box, enable scripting for the zone or change the My Computer security zone level to Medium.
35SF8377 ActiveX EXE servers that launch a dialog box and call any TestStand API function that launches a second dialog box while the first dialog box is still active must create the first dialog box in a thread initialized as single-threaded apartment for the TestStand dialog box to function correctly and to prevent TestStand from hanging.
3BAAMGM0 When executing sequences that use a custom process model, TestStand might return an error when the custom process model appends data to an existing XML report but does not correctly modify the root tags. Before the custom process model calls the Report.Save method, add a sequence call to Remove Root Tags From XML Report in ReportGen_XML.seq. After the custom process model calls the Report.Save method, add a sequence call to Add Root Tags To XML Report in ReportGen_XML.seq.
51040 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 you originally suspended at exceeds the number of steps in the new step group. When this error occurs, you must restart TestStand.
50593 The TestStand File dialog box can leak a Windows USER object.
51218 TestStand 4.x supports XML files, which are larger in size than INI files. TestStand might not save an XML file if the file is very large and the computer does not have enough memory. Change the file format to Binary or INI before you attempt to save the file to work around this issue.
47F9LFG0 McAfee ePolicy can cause TestStand to leak memory when you show XML reports in the sequence editor or a user interface that uses the ReportView control and the computer contains scriptproxy.dll Version, located in the C:\Program Files\Network Associates\VirusScan directory. Install a later version of this DLL, such as Version, to work around this issue.
Database logging and on-the-fly report generation slowly leak memory when executions use a Sequence Call step to create new threads.
35106 On-the-fly report generation incorrectly indents step results that follow a Sequence Call step that creates a new thread.
51295 When you enable the Report Object Leaks options in the Debug Options dialog box that you access from the Station Options dialog box, TestStand reports property object leaks if you call a remote sequence and a run-time error occurred because you passed extra parameters to the sequence.
51161 TestStand 4.1 and earlier do not call the SequenceFilePreInteractive and SequenceFilePostInteractive callbacks when running a step interactively using a process model.
51079 TestStand watch expressions do not suspend the execution if the expression returns a reference object and the previous value of the object returned Nothing. Use an expression that returns a Boolean value, such as Locals.Reference != Nothing, to work around this issue.
TestStand prompts you to reload files when source code control providers, such as MKS Source Integrity, Serena PVCS, and IBM Rational ClearCase, change the timestamp of files when you add the files to source control or check the files in or out of source control. TestStand might return errors for some operations when you reload the files.
35247 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. TestStand returns an error if you do not exclude these files from the check out operation.
50996 When you import a waveform while editing a Configure operation of an IVI Fgen step, the Edit IVI Fgen Step dialog box might not store the waveform data with the step. Immediately close the dialog box after you import the data to work around this issue.
50996 Executing an IVI Fgen step returns an error if the step configures the instrument to load a waveform using data stored with the step. Configure the step to load the waveform from a file to work around this issue. In addition, if you browse to a file to configure the step to load the waveform from a file, the step might not save the filename setting. You must edit the filename in the path control to ensure the step saves the changes to the filename setting.
51527 The Differ window in the sequence editor and the TestStand Differ application do not show differences between strings with different preceding and/or trailing quotation mark characters.
51427 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.
TestStand suspends an execution in a subsequence that the Post-Step callback calls when you disable tracing into callbacks.
102490 The Break on First Step debugging option in the Execute menu incorrectly performs a Step Into operation on the module the first step in a hidden execution calls.
45334 When you turn off the Windows BSTR cache by setting the system environment variable OANOCACHE to 1, IVI returns errors to TestStand when retrieving the names of IVI components.
48959 TestStand XML reports present 2D arrays as 1D arrays. Other report formats present 2D arrays correctly.
41730 When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box, TestStand returns a run-time error when the asynchronous thread continues to execute after the model entry point completes.
43782 TestStand XML reports that use the horizontal stylesheet do not reflect the setting of the Include Execution Times option on the Contents tab of the Report Options dialog box.
41115 TestStand HTML reports do not show the correct fonts in Mozilla Firefox.
96016 TestStand sometimes truncates the legend in the Sequence Hierarchy window when you save the hierarchy to disk.
52274 If you save a sequence file as TestStand 2.0.1 or earlier and the file contains Wait steps configured to wait on a thread or execution of a sequence call, when you execute the sequence file in the older version of TestStand, TestStand returns a run-time error that indicates the Wait step attempted to wait on a sequence call that has not yet run or that is not a multithreaded sequence call. Reconfigure the Wait steps manually to work around this issue.
98511 If you try to open a binary type palette or sequence file that includes a type that contains an array of objects and the root property of the array element prototype is marked as unstructured, TestStand might return an error that indicates not enough information exists to create an object for reading.
96511 Using remote execution to execute a sequence saved with an older version of TestStand might lead to unexpected errors because the remote TestStand Engine does not load type palette files. Save the remotely executed sequence files in the version of TestStand you are currently using to work around this issue.
46351 Applications that use msxml4.dll, such as the sequence editor, user interfaces, and XMLPack, might crash on shutdown when you install the patch specified in the Microsoft Knowledge Base article 936181, located at Install the patch in the Microsoft Knowledge Base article 941833  to work around this issue.
The sequence editor and user interfaces that include the Report control might return an error or reach an unusable state when you aggressively click links and navigate back on the Internet Explorer control. This Internet Explorer issue is more likely to occur when the application runs more slowly, such as while debugging the application with LabWindows/CVI or another debugger.
101285 The Configure operation for an IVI Dmm step fails if you enable the Temperature Measurement extension on the Extensions tab for the Configure operation of the Edit IVI Dmm Step dialog box and the instrument does not support all three temperature sub-extensions.
97938 Terminating execution while running the Java example from a user interface leaks a property object.
100723 TestStand crashes when loading a file if TestStand resolves a type conflict in such a way that the type contains an instance of itself.
44653 If TestStand opens a sequence file using a UNC path, such as \\server\directory\file.seq, and executes a .NET step that calls an untrusted assembly that references a trusted assembly, the .NET Adapter returns an error that indicates the assembly does not support partially trusted callers. Contact National Instruments for more information about this issue.
98882 Setting the User.LoginName property returns an error if the first character in the value is numeric.
102916 TestStand leaks 16 bytes for each call to an ActiveX method with an optional input parameter if you do not specify an argument expression and the ActiveX/COM Adapter uses dispatch interfaces because you call the Engine.SetInternalOption method to enable the InternalOption_AutomationAdapterUsesDispatchForDualInterfaces property.
103579 You cannot create a variable with the same name as an API method in an ExpressionEdit control.


Issue ID Description
  The following parts of the TestStand documentation set did not change for TestStand 4.1. Therefore, the content might not reflect changes made in TestStand 4.1.
  • NI TestStand System and Architecture Overview Card
  • NI TestStand User Interface Controls Reference Poster
  • NI TestStand API Reference Poster
  • NI TestStand VI and Function Help
  • Using the TestStand User Interfaces
  • Converting from the LabVIEW Test Executive to NI TestStand
  • Converting from the LabWindows/CVI Test Executive Toolkit to NI TestStand


Glossary of Terms


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