ID | Known Issue |
---|
35106
47FE0BG0
Return | Incorrect indentation might occur when you generate a report on-the-fly
When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box to generate a report on-the-fly, the report incorrectly indents step results that follow a Sequence Call step that creates a new thread.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
41115
4D59O7YL
Return | HTML reports do not display correctly in Mozilla Firefox
TestStand HTML reports do not show the correct fonts in Mozilla Firefox.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
41350
4D6GIVRA
Return | Cannot edit Visual Basic .NET projects when a function contains an array parameter
The .NET Adapter Edit Code option does not work for functions with array parameters in Visual Basic projects.
Workaround: N/A
Reported Version: 4.0.1 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
41730
4DQDAQYL
Return | Generating reports on-the-fly with asynchronous threads might cause an error
When you enable the On-The-Fly Reporting option on the Contents tab of the Report Options dialog box to generate a report on-the-fly, TestStand returns a run-time error when the asynchronous thread continues to execute after the process model entry point completes.
Workaround: N/A
Reported Version: 4.0.1 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
43782
4GGCQA00
Return | Module execution times are not included in an XML report
TestStand XML reports that use the horizontal style sheet do not reflect the setting of the Include Execution Times option on the Contents tab of the Report Options dialog box.
Workaround: N/A
Reported Version: 4.0.1 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
45334
4I5A0FOS
Return | Turning off BSTR cache causes IVI error
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. The IVI Compliance Package 4.0, which is installed with the August 2009 NI Device Drivers, fixes this issue.
Workaround: N/A
Reported Version: 4.1 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
48272
3QG976G0
Return | Incorrect suspension location when disabling tracing into callbacks
TestStand suspends an execution in a subsequence that the Post-Step callback calls when you disable tracing into callbacks.
Workaround: N/A
Reported Version: 3.1 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
48357
3RFG3UM0
Return | Cannot browse to a VI if the VI filename includes multibyte characters
The LabVIEW Adapter cannot browse to a VI in a LabVIEW library if the VI filename includes multibyte characters.
Workaround: N/A
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
48970
3WIAETIF
Return | TestStand ActiveX controls can become invisible in the Visual Studio designer
TestStand ActiveX controls become invisible in the Visual Studio 2005 or Visual Studio 2008 C# designer when you drag the controls into or out of a panel control. This issue is a known issue with Microsoft Visual Studio and ActiveX controls in general.
Workaround: Close and reopen the designer to make the controls visible again. If you are using ActiveX controls in a user control, you can call the Hide and Show methods on each ActiveX control in the OnCreateControl event.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
49481
3Z4EURMF
Return | LabVIEW user interface beeps when using menu accelerator keys
A LabVIEW user interface beeps when you press <Alt-F> or other menu accelerator keys.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
50996
46Q8EUIA
Return | IVI Fgen step might not store waveform data
- 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.
- Executing an IVI Fgen step returns an error if the step configures the instrument to load a waveform using data stored with the step.
- 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.
Workaround:- Immediately close the dialog box after you import the data to work around this issue.
- Configure the step to load the waveform from a file to work around this issue.
- You must edit the filename in the path control to ensure the step saves the changes to the filename setting.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
51030
46PDBH77
Return | Selecting different steps is slow when a very large array is expanded on the Variables pane
Selecting different steps on the Steps pane of the TestStand Sequence Editor is slow when you select an element of a large array on the Variables pane.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
51062
46QAPEG0
Return | You cannot view the Sequence Properties or Sequence File Properties dialog boxes without unlocking a file first
The TestStand Sequence Editor incorrectly prompts you to unlock a file before launching the Sequence Properties or Sequence File Properties dialog boxes.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
51176
478CHKRA
Return | Error when selecting a Button image
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 User Interface Button control and the icon file contains only a 16-bit color image.
Workaround: Set the icon image programmatically at run time or load an icon file that contains a 256-color image.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
51251
476DR6B8
Return | CheckBox control Color properties do not work when used as a button
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.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
51293
477DFO9Q
Return | Property object leaks reported when closing the TestStand Sequence Editor from the Windows taskbar
The TestStand Sequence Editor occasionally reports property object leaks when you select Close from the Windows 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.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
51752
491GSRM0
Return | VI breakpoint does not bring the VI window to front
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.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
52184
4ADMCJ77
Return | Building a deployment before LabVIEW completely launches might cause an error
Building a deployment can return an error when the output of the deployment generates LLB files before LabVIEW completely launches. This problem is known to occur in LabVIEW versions 8.5 or later.
Workaround: Launch LabVIEW and wait until LabVIEW has finished initializing before you build a deployment.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
52274
4AJA99YL
Return | Saving a sequence file with Wait steps as TestStand 2.0.1 or earlier might result in an error
If you save a sequence file in the TestStand 2.0.1 or earlier format 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 earlier 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.
Workaround: Manually reconfigure the Wait steps.
Reported Version: 3.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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
Reported Version: 4.1 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
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.
Reported Version: 4.1 | | Resolved Version: N/A | | Added: 05/26/2008 |
|
158407
Return | LabVIEW VI Server Exported VIs Setting Might Be Modified By Desktop Execution Trace Toolkit (DETT) 1.0
When the LabVIEW VI Server:Exported VIs list is the default of * (all VIs), the LabVIEW Desktop Execution Trace Toolkit (DETT) 1.0 installer creates an entry in the LabVIEW.ini file for the LabVIEW VI Server:Exported VIs list with only HighlightObject By Context-VI-UID.vi exported. This affects other programs such as NI TestStand, LabVIEW SignalExpress, NI Requirements Gateway (see complete list below) etc., which require certain VIs to be exported to work correctly with LabVIEW. The bug exists if you have installed DETT 1.0 through any one of the following distributions: 1) LabVIEW 8.6.1 Platform DVD 2) NI Developer Suite Q1 2009 DVD 3) LabVIEW Desktop Execution Trace Toolkit 1.0 CD
Reported Version: 4.2 | | Resolved Version: N/A | | Added: 02/06/2009 |
|
131253
Return | You cannot use variables with the same name as an expression constant in an expression
If you use a variable with the same name as an expression constant in an expression, TestStand returns a syntax error when evaluating the expression. The following constants are reserved names:- True
- False
- Nothing
- PI
- NAN
- IND
- INF
- Color constants, which follow the form ts<ColorName> and are less susceptible to this issue.
Workaround: Use the GetVal API functions in an expression to interact with objects that have the same name as expression constants, such as in the function Locals.PIValue = ThisContext.AsPropertyObject.GetValNumber("Step.Result.PI",0).
Reported Version: 3.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
131559
Return | When a run-time error occurs in a step, the module is not unloaded from memory when you select the Unload after step executes option
A run-time error in a step causes TestStand to skip the unloading of a module if you select the Unload after step executes unload option on the Run Options tab of the Step Properties dialog box, Run Options panel of the Properties panel on the Step Settings pane, or the General tab of the Sequence File Properties dialog box.
Workaround: Use another unload option such as Unload after sequence executes if you expect a step to return a run-time error.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
132872
Return | Property Loader step does not resize arrays when loading properties
The Property Loader step can load arrays but does not resize the PropertyObject when doing so. If the array in the file is larger than the TestStand array PropertyObject, an error occurs.
Workaround: Ensure the TestStand PropertyObject into which the array is being loaded is large enough to accept the array in the file. You can resize the array in a pre-expression of the Property Loader step if necessary.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.1 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
135514
415AQUM0
Return | TestStand Deployment Utility deploys files to an incorrect location if a file path contains multibyte characters and the installation language does not match the target computer language
If you choose to install files in a location that contains multibyte characters or if the filename contains multibyte characters, the files might be installed to an incorrect location under either of the following conditions:- If the installer language is set to English.
- If the installer language setting does not match the language setting of the target computer.
You cannot deploy multibyte file paths using an installer set to English.
Workaround: If you must deploy files with multibyte characters or if the install location contains multibyte characters, you must verify that the installer language matches the language setting of the target computer.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.1 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
138406
Return | The /run and /runEntryPoint command-line arguments are ignored when no user is logged in
The Application Manager control automatically handles the /run and /runEntryPoint command-line arguments to run a sequence when a user interface is started. However, if you set the ApplicationMgr.LoginOnStart property to False, the command-line arguments are ignored, even if you also set the StationOption.RequireUserLogin and StationOption.EnableUserPrivilegeChecking properties to False.
Workaround: Modify the user interface to automatically log in a user.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
141991
Return | TestStand Deployment Utility does not adequately document error codes -40 and -30
Error codes -40 and -30 can occur in the TestStand Deployment Utility when building additional NI installers into an installer. Refer to the National Instruments Web site at ni.com/ask to contact National Instruments Support for more information after attempting the workarounds documented below.
Workaround: If you receive the error "Error: Internal error. (Error code -40)" try removing or renaming the <National Instruments>\Shared\MDF\Manifests directory and repairing all installed NI software. If you receive the error "Error: Improper function call or command line argument. (Error code -30)" try deleting all cached installers in the <All Users>\Application Data\National Instruments\MDF\ProductCache directory.
Reported Version: 4.1 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.2 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
148697
Return | LabVIEW user interface might hang when using LabVIEW events
A LabVIEW user interface that registers ActiveX callbacks and uses an Event structure might hang when the user interacts with a LabVIEW control or indicator. The hang is rare, but when it occurs, TestStand User Interface Controls remain responsive, but all LabVIEW user interface elements appear frozen. LabVIEW 2009 fixes this behavior.
Workaround: Activate another application and reactive the LabVIEW user interface.
Reported Version: 4.1.1 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
149883
Return | Importing a property from a .xls file using a Property Loader step does not import the full property value if the cell contains comma
If a text cell in a Microsoft Excel spreadsheet has a value with a comma in it, the Property Loader step imports only the text after the last comma and not the full text of the cell. For example, if a cell contains the value 10,11,12,13 the Property Loader step imports only 13. This behavior occurs because the Property Loader step uses expressions to assign values, such as in Locals.myLocal = (10,11,12,13). However, the TestStand expression language uses commas to separate expressions within an expression, so numbers within the parentheses are considered a set of expressions separated by comma. When a series of expressions separated by commas exist within an expression, the result of evaluating the expression is the result obtained from evaluating the last expression. For example, if the last expression is the number 13, the value assigned to the property is 13.
Workaround: Add quotes around the string to force the Property Loader step to consider the text as a string instead of a series of expressions. When you use the Property Loader step to import text properties, the step imports the text as a string automatically.
Reported Version: 3.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
151624
Return | Deploying VIs in a LabVIEW class might not correctly link dependencies
If you deploy a LabVIEW 8.6.1 or later VI that is in a LabVIEW class, the TestStand 4.2 Deployment Utility might not correctly link dependencies of the VI. LabVIEW 2009 fixes this behavior. When using earlier versions of LabVIEW, refer to the National Instruments Web site at ni.com/info and enter the info code rdtsdiv to access the National Instruments KnowledgeBase article Building a TestStand Deployment that Includes VIs in a Class may Sometimes Produce a Bad Deployment for more information about deploying a VI in a LabVIEW class.
Workaround: Recompile the VI after you build the deployment.
Reported Version: 4.2 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.1 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
153518
Return | Configuring the Formula Express VI in a TestStand step results in error tones
Selecting the Formula Express VI for a step, launching its configuration dialog box, or selecting a step that specifies the Formula Express VI as its code module cause a series of system error tones.
Workaround: The tones are harmless and you can ignore them.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
157583
Return | Undoing changes from the Update Automation Identifiers tool makes all steps in the selected sequence disappear
If you undo changes from the Update Automation Identifiers tool, all steps in the selected sequence disappear from the Sequences pane.
Workaround: Click on a different sequence and then return to the original sequence to make the steps reappear. You can also close and reload the file to workaround this issue.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
158302
Return | Microsoft Visual Studio 2005 might hang while debugging a TestStand User Interface when loading symbols for Microsoft Internet Explorer 8
When you debug an application with Microsoft Visual Studio, you can define a symbol server from which Visual Studio can download module symbols. If Microsoft Internet Explorer 8 is installed, Visual Studio might hang when trying to download the debug symbols for rasapi32.dll while launching a TestStand User Interface.
Workaround: Complete the following steps to work around the issue.- In Visual Studio 2005, select Tools»Options to launch the Options dialog box.
- Expand the Debugging option and select Symbols to display the Symbols panel, and temporarily disable debug symbols.
- Launch the TestStand User Interface.
- In Visual Studio, enable debugging symbols when the user interface is running.
Reported Version: 4.2 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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
Reported Version: 4.2 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
158938
Return | Cannot pass struct containing an array of structs into a DLL built with LabVIEW
You can call a DLL built with LabVIEW using the C/C++ DLL Adapter in TestStand. However, for parameters that are structs containing an array of structs, TestStand does not allocate the memory properly, resulting in a TestStand Error: -17502 System Level Exception error.
Workaround: You can pass arrays of numbers, arrays of strings, or individual clusters as parameters to a DLL built with LabVIEW.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
159809
Return | Import/Export Properties dialog box does not persist some settings
When you close and then relaunch the Import/Export Properties dialog box, most settings are saved so you can easily export a limits file again. However, the Sequence option on the Properties tab does not persist correctly, which might cause an existing limits file to become invalid after exporting again.
Workaround: Verify that the Sequence option on the Properties tab is correct every time you launch the Import/Export Properties dialog box before you exporting the settings.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
160210
Return | TestStand Deployment Utility might appear to hang when building if the LabVIEW Build Specifications dialog box is open
As part of the build process, the TestStand Deployment Utility uses the LabVIEW application builder to create a source distribution of all VIs included in the distribution. If any build specification dialog box is open in the LabVIEW development environment, the Deployment Utility might appear to hang while the Build Status is "Processing VIs..."
Workaround: Close the open build specification dialog box to allow the TestStand Deployment Utility to continue the build process.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 3.0 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
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.
Reported Version: 4.0.1 | | Resolved Version: N/A | | Added: 05/18/2009 |
|
171168
Return | Installing LabWindows/CVI 9.0 Run-Time Engine can break TestStand 3.5 deployed components
The TestStand Message Popup steps, LabVIEW, and LabWindows/CVI user interfaces use the NI ActiveX Container. The LabWindows/CVI 9.0 and 9.0.1 Run-Time Engines install a version of the NI ActiveX Container without listing its dependencies to the Microsoft 2005 C Run-Time (CRT) DLLs, specifically MSVCP80.DLL and MSVCR80.DLL. Building a deployment in TestStand 3.5 does not include the necessary Microsoft 2005 CRT DLLs, which causes the previously mentioned components to break on the target computer. This problem does not exist in TestStand 4.0 and later. TestStand 4.2.1 includes an updated version of the LabWindows/CVI 9.0.1 Run-Time Engine that fixes the issue.
Workaround: Include a National Instruments component that lists the Microsoft 2005 CRT DLLs as dependencies in the TestStand 3.5 deployment.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 09/18/2009 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
172759
Return | Including the LabVIEW 8.5.1 _exclsub.llb file in a TestStand workspace along with a sequence file that contains a LabVIEW 8.5.1 code module that calls the Report Generation Express VI results in a TestStand Deployment Utility build error
When you include the LabVIEW 8.5.1 _exclsub.llb file in a TestStand workspace and that workspace also includes a sequence file that calls one or more LabVIEW 8.5.1 code modules that use the Report Generation Express VI, the TestStand Deployment Utility returns the following build error: "Error: The following VIs or Project Libraries have duplicate names. You must change the names or add them to project libraries: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\_office\_wordsub.llb\font.ctl while Processing VIs... C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\addons\_office\_exclsub.llb\font.ctl while Processing VIs...". However, you must include _exclsub.llb because the Report Generation Express VI dynamically calls VIs the LLB contains. The Express VI statically links to the font.ctl file, which causes a duplicate copy when you include the _exclsub.llb library in a TestStand workspace. LabVIEW 8.6 and later fix this issue.
Workaround: To build successfully, exclude the font.ctl file from the _exclsub.llb library in the Distributed Files tab of the TestStand Deployment Utility. LabVIEW 8.6 and later fix this issue.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
172792
Return | Uninstalling a TestStand deployment leaves the TestStand Engine and other additional components on the system
When you run a TestStand Deployment Utility installer that includes the TestStand Engine and other additional components, the installer adds two items to the Add/Remove Programs dialog box. The first item is the name of the TestStand system you defined when you configured the TestStand Deployment Utility. The second item is "National Instruments Software", which provides the functionality to modify, repair, or remove any installed National Instruments software, such as the TestStand Engine or other additional components that the TestStand Deployment Utility installer includes. Uninstalling the first item has no effect on the second item, thus leaving the TestStand Engine and other additional components installed on the computer.
Workaround: After you uninstall the TestStand system using the Add/Remove Programs dialog box, select the "National Instruments Software" item and manually uninstall the TestStand Engine and additional components.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
172793
Return | Leaving the Default Installation Subdirectory field empty in the Installer Options tab of the TestStand Deployment Utility results in a build error
If you leave the Default Installation Subdirectory field empty in the Installer Options tab of the TestStand Deployment Utility because you want the files to install in the base directory, the deployment utility returns the following message when you attempt to build: "The build contains one or more invalid paths: Invalid Default Installation Subdirectory: """
Workaround: Place a period in the Default Installation Subdirectory field to install files in the base directory.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
179186
Return | Configuring a MessagePopup step as a Modal or Floating popup hangs subsequent LabVIEW steps for which you enabled the Show VI Front Panel When Called option
If you enable the Make Modal or Make Floating option in the Dialog Options section of the Message Popup Layout edit tab and call LabVIEW code modules after you call the Message Popup step, the LabVIEW code modules hang if you enabled the Show VI Front Panel When Called option on the LabVIEW Module tab in the TestStand Sequence Editor or in the Edit LabVIEW VI Call dialog box in a TestStand User Interface for the LabVIEW steps. LabVIEW 2009 SP1 fixes this issue.
Workaround: Do not enable the Make Modal or Make Floating options of the MessagePopup Layout edit tab or create your own code module in LabVIEW to display the message you want. LabVIEW 2009 SP1 fixes this issue.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
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.
Reported Version: 4.2 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
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
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
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.
Reported Version: 3.5 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
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
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
188119
Return | TestStand is a 32-bit application and has limited support for LabVIEW 64-bit
Refer to the National Instruments KnowledgeBase article 50O9851O, Does TestStand support calling VIs using LabVIEW 64-Bit? on the National Instruments Web site for information about LabVIEW 64-bit support in TestStand.
Workaround: N/A
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
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.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 12/11/2009 |
|
189528
Return | Perforce 2009.1 and 2009.2 client causes TestStand to crash when closing a workspace file
If you configure source code control (SCC) to use the Perforce SCM Provider, TestStand loads the Perforce SCC DLL when you open a workspace file and unloads the DLL when you close the workspace file. If you use the Perforce 2009.1 client, TestStand might crash after unloading the Perforce SCC DLL when you close a workspace file. If you use the Perforce 2009.2 client, a delay might exist before a possible TestStand crash after you close the workspace file. Use the new Perforce 2010.1 client or the previous 2008.2 client to fix this issue.
Workaround: Use the new Perforce 2010.1 client or the previous 2008.2 client.
Reported Version: 4.0 | | Resolved Version: N/A | | Added: 12/11/2009 |
|