Archived: TestStand 4.0 Bug Fixes

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.

Overview

The following items are notable issues fixed between the release of <product> <version-1> and <product><version>, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of <product><version>.

The following items are changes from TestStand 3.5 to TestStand 4.0, unless otherwise specified.

Bug IDFixed Issue
Sequence Editor
3PKEGNRAFixed an issue where the Filter tab of the Find in Files dialog box incorrectly excluded adapters that you configured as hidden.
3709SIG0Fixed an issue where sending a UIMsg_OpenWindows message for an unsaved file to the sequence editor failed to open a window for the file and the sequence editor displayed an error indicating that the directory could not be found.
3KEET8MT
3LGDNHMF
Fixed an issue where the sequence editor did not update the execution entry points in the Execute menu when you changed the default process model in the Station Options dialog box or when the model file was loaded when previously not found.
3Q9F1FJ6Fixed an issue where the sequence editor would hang or crash when creating code for a LabVIEW step.
3R0L6HG0Fixed an issue where the Watch View incorrectly removed carriage-return characters from a watch expression when selecting the expression.
3QIEFC26Fixed an issue where the sequence editor crashed when you attempted to open a large number of files.
3BK9B0B8Fixed an issue where the sequence editor did not refresh execution windows to reflect breakpoint changes when you loaded a different workspace.
39693SB8Fixed an issue where attempting to edit extremely large string values in the sequence editor made the application hang.
3U5F2PNXFixed an issue where TestStand prompted you to save a type palette file when closing the sequence editor, even after previously saving the file.
3K3DSTGHThe LabWindows/CVI 8.0 and later Run-Time Engine fixed an issue where the sequence editor leaked memory every time it was deactivated and reactivated.
3RE8S6FKFixed an issue where TestStand displayed an error when you tried to save a sequence file after editing a custom data type.
3KL7QKUZFixed an issue where inserting code modules on a sequence file in a workspace incorrectly added temporary VIs to the workspace when steps in the sequence file called Express VIs.
3A8CDMRAFixed an issue where the Watch View did not highlight a watch expression in red when the 'On True' watch breakpoint setting suspended the execution.
3ALCSSRAFixed an issue where the Watch Expression Settings dialog box discarded changes when you enabled Exist Only in Specified Scope but you did not specify a sequence file.
47F9LFG0Fixed an issue where the sequence editor and the Report View control leaked memory when displaying XML reports.
User Interfaces
36PAB7G0Fixed an issue where an open VB.NET and C# TestStand operator interface cancelled a request to shut down Windows 2000.
45FLMBG0Fixed an issue where TestStand did not prevent you from attempting to run a second TestStand UI application in the LabVIEW development environment while another TestStand UI application was already running.
UI Controls
TestStand 3.5 and later fixed an issue where the ApplicationMgr.OpenSequenceFile threw an exception if a type conflict occurred. The method now returns NULL, and TestStand fails to load the file.
3A8AQQLWFixed an issue where a call to SequenceFileViewMgr.Refresh removed highlighting for the currently selected steps.
3ERB3NYLFixed an issue where TestStand did not trace execution of the LoginLogout callback when you enabled the Trace Into Separate Execution Callbacks station option.
3M7F4U3Fixed an issue where TestStand failed to process the command-line arguments when ApplicationMgr.LoginOnStart was False.
3O4E4UMT
3H6F9DMT
Fixed an issue where the TestStand UI Controls did not display tip strips when used in a LabVIEW operator interface.
3O4D5BMTFixed an issue where the ReportView control did not display an empty report when you called Report.Reset("").
3W4BN7B8Fixed an issue where TestStand UI Controls on LabWindows/CVI child panels moved off screen when resizing the control using their borders.
3OO153MFFixed an issue where the SequenceView UI control did not auto-size the Description column when double-clicking the column divider.
LabVIEW
3QG9N300Fixed an issue where a small memory leak occurred when TestStand used the LabVIEW 8.0 Run-Time Engine to call a VI that displays and closes its front panel. Use LabVIEW 8.0.1 to prevent this memory leak. Alternatively, you can call the VI without displaying the front panel, or you can configure the LabVIEW Adapter to execute VIs using the LabVIEW 8.0 development system.
3Q9CKF00Fixed an issue where TestStand could not use LabVIEW 7.1.1 or earlier to call a remote VI that has a TestData control wired to its connector pane. Use LabVIEW 8.x to resolve this issue.
464C8S77The LabVIEW 8.0 Run-Time Engine and later fixed an issue where TestStand crashed when attempting to load a DLL created in LabVIEW 7.0, the LabVIEW 7.0 Run-Time Engine was not installed, and the DLL incorrectly used a different LabVIEW Run-Time Engine. This issue does not occur if you create the DLL using LabVIEW 8.0 or later.
3M1B99RRFixed an issue where an error occurred and closed the LabVIEW Specify Module dialog box when adding elements to a 1D cluster array.
3VQCBA5EFixed an issue where the LabVIEW Adapter could not call VIs that wire Generic IO references to the connector pane because the LabVIEW Adapter incorrectly interpreted the terminals as Number (U32).
3IOEG84EFixed an issue where the LabVIEW Adapter incorrectly created a new data type for cluster parameters that contained an array of clusters.
3BK9OBGH
3KRG3RGH
Fixed an issue where the LabVIEW Specify Module dialog box did not allow you to specify a value for a required parameter if the step was previously configured to pass a default value when the parameter was not required.
3ZGG3300Fixed an issue where you could not edit array elements previously specified on the LabVIEW Specify Module dialog box after decreasing the default array size on the control in the VI and reloading the VI prototype.
3A9AG8J6Fixed an issue where the LabVIEW Adapter parameter mapping feature no longer worked for a step when the step type used a default Express VI as its module and you deleted mapped values applied to the step the last time you configured the step.
3BRCHDRAFixed an issue where TestStand would hang while executing a VI that called Exit and the LabVIEW Adapter was running VIs in the LabVIEW development environment.
3B0L59UZFixed an issue where the LabVIEW Adapter waited until shutdown to clean up temporary wrapper VIs that were created when configuring and running Express VIs.
3BLANJB8Fixed an issue where the LabVIEW Adapter incorrectly removed the variable prefix from a property in a parameter expression when configuring an Express VI.
3B791NB8TestStand 3.5 and later fixed an issue where the LabVIEW Specify Module dialog box silently discarded parameter values when reconfiguring an Express VI and the parameter names for the VI changed.
3WD79II0Fixed an issue where the LabVIEW Specify Module dialog box incorrectly decremented the enumeration value of a parameter of a VI for digital display controls.
3R2FCL4EFixed an issue where TestStand always displayed a type conflict when opening a file that used a data type that contained a LabVIEWClusterArray property and the same data type was already loaded.
3WIC6UQ2Fixed an issue where the LabVIEW Adapter could not pass an array of Data Log File references to a VI.
3W64RRCM
3WA6QKPT
Fixed an issue where TestStand would hang or crash when calling a LabVIEW VI that included a control inside a tab and the control was wired to the connector pane.
3ZIBR00  Fixed an issue where the LabVIEW Adapter did not remap parameter values correctly after changing wired terminals for the VI and reloading the prototype.
3X98OGW3  Fixed an issue where calling a LabVIEW VI using a LabVIEW Run-Time Engine generated an error if the step passed a string value that started with "LVSTR:".
3RFD033SFixed an issue where the LabVIEW Adapter returned an error when using the LabVIEW development system to call VIs that returned a Modular Instruments session.
3V67T88PFixed an issue where TestStand would hang or crash when calling a VI in which the label for a wired control or indicator of the VI ended with a space character.
3TUC02W3Fixed an issue where calling a LabVIEW VI using a LabVIEW 8.0 Run-Time Engine generated an error if the step returned a VISA session.
3S1CPSBKFixed an issue where TestStand crashed if you terminated the LabVIEW 8.0 development system while executing a VI.
3KS9OKGHFixed an issue where the LabVIEW Specify Module dialog box did not clear the description and context help link text when changing an Express VI call to a standard VI call.
3ZHCQT00Fixed an issue where the LabVIEW Specify Module dialog box did not check the data type of parameters that TestStand passed to 2D array indicators.
3JNAHRJ6Fixed an issue where TestStand crashed when you attempted to create code using the LabVIEW Adapter and the LabVIEW development system was not installed.
3KRFO2GHFixed an issue where the LabVIEW Specify Module dialog box incorrectly reported an error when you did not specify an expression for the Element1 property of a DynamicData parameter.
3ZBF9800Fixed an issue where the LabVIEW Specify Module dialog box cleared the expressions specified for real or imaginary elements of complex parameters when reloading the prototype for the VI.
3ZCIH077Fixed an issue where the LabVIEW Adapter did not filter out HTML tags, such as bold, from error messages.
3OUFPBG0Fixed an issue where the LabVIEW Specify Module dialog box incorrectly displayed "1D Array" for the real and imaginary elements of a 2D (or more) complex array parameter.
3QBCKO77Fixed an issue where the LabVIEW Adapter did not release a reference to a remote VI after unloading all modules.
3PLEDUM0Fixed an issue where calling the Read From Measurement File Express VI returned error code 100.
3QHH3RGHTestStand 3.5 and later fixed an issue where the LabVIEW Specify Module dialog box displayed an error when adding elements to any array item within a 2D array of clusters.
2YGG9200LabVIEW 8.2 and later fixed an issue where ActiveX controls, such as the TestStand UI controls, did not respond to mnemonic keys.
2ZM2FG0Fixed an issue where the LabVIEW Adapter leaked memory calling VIs with waveform parameters.
46R964UZFixed an issue where the LabVIEW Adapter reset the Propagate to Subsequence and Allow Propagation from Caller properties on local variables when assigned a waveform value returned from a VI.
40TE6O3QFixed an issue where the LabVIEW Specify Module dialog box cleared parameter expression values of cluster elements after configuring the Express VI.
3BND14GHFixed an issue where a LabVIEW operator interface would hang if an execution preloaded a module for a remote VI call when starting the execution.
3BE9KPB8LabVIEW 7.1.1 and later fixed an issue where LabVIEW lost focus when dismissing a property page for a TestStand UI control.
41JGQ1BUFixed an issue where a LabVIEW operator interface executable would hang closing the application if you previously executed a remote VI call.
3ZDCENI0Fixed an issue were the LabVIEW Adapter reported an error when calling a VI that contained a String control that you changed to a Path control.
3ZIA9VOFFixed an issue where the LabVIEW Specify Module dialog box generated an error when attempting to create a TestStand data type for a parameter that contained an array of LabVIEW I/O controls.
461A6654Fixed an issue where the LabVIEW Adapter reported an error when trying to call a VI on a LabVIEW 8.0 Real-Time Module system.
43JJT1M7Fixed an issue where the LabVIEW Adapter incorrectly passed double-byte Japanese string data between TestStand and VIs when executing VIs using the LabVIEW Run-Time Engine.
41J1LKL3LabVIEW 8.2.1 fixed an issue where TestStand UI controls became hidden on LabVIEW front panels that you edit if TestStand previously executed a step that called a VI that used a TestStand UI control.
3Q3DRE77LabVIEW 8.2.1 fixed an issue where TestStand would hang when executing the Undeploy operation of a Deploy Variables step in multiple threads.
LabWindows/CVI
2XIC109QFixed an issue where the LabWindows/CVI ADE required you to select Continue after you attempted to step into a DLL and LabWindows/CVI could not find the specified source file on disk.
3QIC1VRAFixed an issue where the LabWindows/CVI Specify Module dialog box initiated editing in the Function Call control when you entered lowercase "step" or "locals" as an argument for a parameter.
3BEB5HRAFixed an issue where expression combo boxes in LabWindows/CVI dialog boxes showed a display value in the control instead of the actual value when you used a mnemonic key to give it focus.
3P0LAMGHFixed an issue where the LabWindows/CVI Specify Module dialog box read DLL export information and incorrectly interpreted CAObjHandle parameters as integer and incorrectly displayed type names for enum parameters.
C/C++ DLL Adapter
3QIDDO6IFixed an issue where the C/C++ DLL Adapter did not update prototypes when you changed how a struct was passed, for example, pass by pointer and pass by value.
3AD8KU6AFixed an issue where the C/C++ DLL Adapter could not edit code if the function definition in the source file used macros.
3P8CRURAFixed an issue where the C/C++ DLL Adapter sometimes failed to properly insert code using Visual Studio when the function already existed as the last line and you inserted code below it.
3BQ8TAYLFixed an issue where the C/C++ DLL Adapter reported an error when generating code with a _bstr_t parameter.
ActiveX/COM Adapter
3T39G9BKFixed an issue where the ActiveX/COM Adapter incorrectly reported an error when the interface call returned FALSE and no error object was returned.
.NET Adapter
3QIGDN6IFixed an issue where the .NET Adapter incorrectly inserted an Imports statement before Option statements when generating code.
39Q7ESYLFixed an issue where stepping into C# code while running multiple executions caused a system-level exception.
3QIENBYLFixed an issue where Edit Code with the .NET Adapter did not work if the source code had duplicate TestStand API "using" statements.
41BLCE00Fixed an issue where the .NET Specify Module dialog box did not allow you to specify default parameters for a constructor.
45PBKPOFFixed an issue where the .NET Adapter leaked memory when calling .NET assemblies that returned arrays.
40M9KPUZFixed an issue where the .NET Specify Module dialog box displayed 1D arrays of classes, structs, or enums as 2D arrays.
40LF7LUZFixed an issue where the .NET Adapter generated a system-level exception when calling a module where you specified to use the default value for an in/out parameter.
4709M2YLFixed an issue where the .NET Specify Module dialog box displayed duplicate enum values using the name of the first value.
Deployment Utility
2XMAA1G0Fixed an issue where the Deployment Utility taskbar item was not visible when you opened a modal dialog box.
3RFBRPM0Fixed an issue where the Deployment Utility did not interpret paths properly for files located in the desktop, program menu, and startup directories on foreign operating systems.
2XQEKRM0Fixed an issue where running the Deployment Utility crashed when running more than one instance of the application.
3V0D5JI0Fixed an issue where the Deployment Utility could not deploy a VI Template when you configured the Deployment Utility to lock the block diagram of the VI.
3SS8GQF5TestStand 3.5 and later fixed an issue where the Deployment Utility logged an error when building a deployment if you used Insert Code Modules on the sequence files in the workspace and the workspace included a sequence file that called an Express VI and another sequence file that called the first file.
3BBGP2MFFixed an issue where the Deployment Utility did not prompt to save a modified .tsd file when loading another .tsd file using the MRU list of the Load button.
3QDGFQGHFixed an issue where the TestStand Deployment Utility did not properly update the paths to the source files when you copied or moved a .tsd file to a new location and you opened and resaved the .tsd file without performing an analysis of the source files.
3P5FG56IFixed an issue where the Deployment Utility did not reload updated TestStand search paths from disk before performing an analysis operation.
3Q2HHRRAFixed an issue where the Deployment Utility erroneously logged a warning indicating that an LLB file could not be found when the path in the workspace for the file was an absolute path.
3LC85AIAFixed an issue where entering a network path in the Installer Directory control displayed an error while typing.
3N5DKQM0Fixed an issue where the Deployment Utility did not list the National Instruments directory as a target for deploying files.
3OSGP7G2Fixed an issue where the Deployment Utility did not allow you to create non-English based installers.
3BBERU6ATestStand 3.5 and later fixed an issue where the Hide License option in the Deployment Utility did not appear enabled when loading a .tsd file.
40KMM4M7Fixed an issue where the Deployment Utility failed to warn you when you attempted to include files with dual-byte character names in an English installer.
3RDE1RM0Fixed an issue where the Deployment Utility did not properly update VI module paths in steps when the called VI contained dual-byte characters.
Miscellaneous
42BCLS00Fixed an issue where loading protected files generated unexpected type conflicts or unknown type name errors.
47EGAK3SFixed an issue where an execution appeared to leak memory if a Sequence Call step executed a sequence in another file and the step was set to unload the module after the step executed. TestStand did not free the file globals for the sequence file that the step called.
373B4HG0Fixed an issue where TestStand listed the "Containing project directory" as an option in the Edit Search Directories dialog box. The workspace uses the relative path from a file to the project file if valid.
3KEBH1B8Fixed an issue where the Expression Browser dialog box did not allow you to insert subproperties into a container property.
3DRA52MTFixed an issue where the Preconditions dialog box deleted an "AllOf" function if you entered a C++ style comment in an expression element of the precondition.
3O4ESKMTFixed an issue where an Expression control incorrectly highlighted the FindFile function as an error when you passed a property that evaluated to an empty string at edit time.
3EAAP8W3Fixed an issue where the Sequence Properties dialog box incorrectly attempted to validate expressions that apply only when the file type is a model.
3SE2O1LLFixed an issue where the Preconditions dialog box prevented you from selecting a step that had a large number of characters in its name.
3F5HE48AFixed an issue where TestStand incorrectly displayed the Advanced button when calling DisplayPropertiesDialog on a User object and you passed PropDlgOption_DisableAdvancedButton to the options parameter.
3YFED9AFFixed an issue where selecting Loop on Selected Steps executed the steps inside a For Loop only once if the last selected step was the End step.
3CUCA96IFixed an issue where TestStand did not update all expressions in a sequence that referenced a step when you changed the name of the step.
39HFRT00Fixed an issue where TestStand did not allow you to replace an existing file when you attempted to save the file for an earlier version of TestStand.
3BLFB8B8Fixed an issue where the Workspace Browser dialog box did not open non-sequence files in an external program when you double-clicked the file.
3D6E7RZ8Fixed an issue where the For Each step did not assign a value to the current element value if the property was an instance of a custom data type.
3UQ1CD8PFixed an issue where TestStand suppressed run-time error handling in 'Not Viewable' protected files by not calling PostStepRuntimeError callbacks until the run-time error propagated to a non-protected file.
3YLABIONFixed an issue where the privileges of a user became enabled when a user who did not have administrator privileges updated their password.
3VU43BQWFixed an issue where the expression values on the Text and Buttons Tab of the Message Popup dialog box mirrored value changes you made to the Response String Length control on the Options Tab.
3TFAHFI0Fixed an issue where the data for the graph control in TestStand XML reports did not appear because the Y axis range was incorrect.
3YKAULUUFixed an issue where looping on a Sequence Call step and disabling Record Result of Each Iteration on the step caused the expand.xsl style sheet to incorrectly indent step results in the report.
3VRGAGT3Fixed an issue where on-the-fly XML reporting failed to update the interim report unless the call stack depth was less than 3.
3R0A3CG0Fixed an issue where the AddRootTagsToXMLReport function in ModelSupport.dll incorrectly changed CRLF to CRCRLF, which resulted in odd formatting when viewing the XML file.
3U8DHRB8Fixed an issue where TestStand crashed when you changed the ExecutionViewMgr.StepGroupMode property while running.
3QDBPHB8Fixed an issue where executing an AutoSchedule step a second time while running a sequence would hang if while running the first time you exited the block without completing the block normally.
3QBE2DRAFixed an issue where clicking <Enter> on some of the secondary dialog boxes that the Database Options dialog box displayed closed the dialog boxes without committing the changes.
3T8D6AB8Fixed an issue where TestStand crashed when calling Engine.GetInternalOption(InternalOption_ApplicationManager).
3P79DDB8Fixed an issue where TestStand crashed when you compared two context property values in an expression.
3K7DD4MFFixed an issue where the CommentOf expression function returned an empty string when called on SequenceFile objects.
3QIDL2RAFixed an issue where the Database Options dialog box discarded edits to a schema comment if you tabbed off the control.
4661QKIZFixed an issue where a Property Loader step failed when importing from a file that contained import data for a large array or container property.
421D7CYLFixed an issue where TestStand reported property object leaks after a Sequence Call to a remote computer failed to access the system.
425APA00Fixed an issue where Message Popup steps returned an error when executed on a remote computer that you call using a Sequence Call step.
467AHKYLFixed an issue where the array data was incorrectly interpreted when displayed in the graph of an XML report on a system configured to use commas as decimal points.
43JFG3B8Fixed an issue where a Do While step incorrectly evaluated its condition for its first loop if you previously executed the loop and you branched out of the loop to restart the loop again.
44IDMK7KFixed an issue where the TestStand Database Viewer displayed an empty error message when attempting to open an invalid data link.
46PF9MUUFixed an issue where XML reports that used the horizontal stylesheet did not display if a Multiple Numeric Limit Test step returned an empty array with no measurements.
41E86U77Fixed an issue where the Property Loader incorrectly created database columns using the varchar data type instead of a numeric data type.
41HCK7G0Fixed an issue where the ApplicationMgr generated an error when returning from a UIMessageEvent event for a custom UIMessage.
447GTM7Fixed an issue where an error occurred in process models when attempting to generate a report if the sequence file pathname contained specific Japanese characters and TestStand was generating the report in the same directory as the sequence file.
35BG11B8Fixed an issue where TestStand supported only 256 colors for icons. TestStand now supports 16-, 24-, and 32-bit icons.
3Z6AH8CNFixed an issue where the IVI-C Switch step used a semicolon instead of a comma as a delimiter for Init options when trying to simulate the instrument, which resulted in the step using the real instrument when present.
3V9G93IFThe LabVIEW 8.0 Run-Time Engine fixed an issue where Visual Studio displayed the following prompt: "Managed Debugging Assistant 'LoaderLock' detected a problem in SeqEdit.vshost.exe" when the sequence editor loaded the LabVIEW 7.1 Run-Time Engine while debugging TestStand with Visual Studio and you enabled Managed Debugging Assistant on the Exception dialog box in Visual Studio.
47L5HNMFixed the documentation for the Replace expression function, which incorrectly stated that the function returned the modified string.
TestStand 3.1 and later fixed an issue from TestStand 2.0.x where the DLL Flexible Prototype Adapter incorrectly handled calls to AddRef() and Release() on references in structure parameters or arrays of structure parameters when the value of a reference that was passed to the code module was different than the value the code module returned. If you attempt to run the TestStand 2.0.x example located in <TestStand>\Examples\StructPassing\C or any code module based on this example in TestStand 3.1 and later without properly handling references, TestStand might crash. The TestStand 2.0.x version of this example failed to properly call AddRef() and Release() on references in structure parameters that the code module used. The C/C++ DLL Adapter in TestStand 3.1 and later resolves this issue, and the TestStand 3.1 and later examples properly demonstrate how to use references within structure parameters.
TestStand 3.0 and later fixed an issue where for steps run in a root interactive execution, the order of execution for the Pre and Post Interactive callbacks in TestStand 2.0 was Setup Step Group, Pre Interactive Callbacks, Selected Steps, Post Interactive Callbacks, and Cleanup Step Group. In TestStand 3.0 and later, the order of execution is Pre Interactive Callbacks, Setup Step Group, Selected Steps, Cleanup Step Group, and Post Interactive Callbacks.
TestStand 3.5 and later fixed an issue where the Edit String Value Test dialog box persisted <Ctrl-Enter> as "\r\n" in the Expected String Value control. TestStand now persists "\n" instead.
TestStand 3.1 and later fixed an issue where the Microsoft Internet Explorer ActiveX control TestStand used to display HTML and XML reports in the sequence editor report tab and the Custom UI Report did not always release its internally allocated memory each time the Internet Explorer control updated the report. If you update the control continuously over an extended period of time, the TestStand process memory use increases. TestStand 3.0 used the control in such a way that the failure to release memory occurred more often. TestStand 3.1 and later contain workarounds that limit the amount of memory the control fails to release. When you use on-the-fly reports, TestStand uses the Internet Explorer control only when the control is visible.
320FDRMTTestStand 3.1 and later fixed an issue introduced in TestStand 3.0 where if you opened a TestStand 2.x sequence file that contained a custom step type in TestStand 3.0, TestStand 3.0 incorrectly turned off the Instance Default Flag, PropFlags_SharedAtRunTime, for the Step.TS property. A side effect of this change is that in TestStand 3.0, instances of this type ignore run time changes to built-in step properties and code module settings. For example, if a step altered the precondition of another step at run time, the precondition change was ignored.

TestStand 3.1 and later fix this issue by reverting the flag back to its proper state when loading a TestStand 3.0 file. TestStand does not mark the step type as modified.

To prevent the fixed version of a step type in TestStand from being used in or accidentally propagating back to earlier TestStand sequence files, enable the Set Earliest TestStand Version that can Use this Type setting on the Version tab of the Step Type Properties dialog box and set the earliest version to the current version of TestStand.
NI-VISA 3.1 or later and NI-DAQmx 7.2 or later fixed an issue where the NI-PAL Service Manager (nipalsm.exe) generated an error each time you restarted the system.

 

Glossary of Terms

 

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