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 contains the TestStand 4.2.x known issues that were discovered before and since the release of TestStand 4.2. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.
Known Issues by Date
For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted only by date the issue was added to the document.
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The following items are known issues in TestStand 4.2.x sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| .NET Adapter | ||||||
| 131626 Return | .NET Adapter disposes all parameters if a method throws an exception If you call a method that uses the .NET Adapter, and the method throws an unhandled exception, TestStand catches the exception, returns a runtime error, and incorrectly releases object references passed to the method. Workaround: N/A
| |||||
| 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
| |||||
| 155330 Return | TestStand returns an error or crashes when using an array of paths instead of an array of strings for a .NET assembly parameter The TestStand PropertyObject type Path is interchangeable with the basic String type. However, if you try to pass an array of paths for a .NET String[ ] parameter, TestStand returns the following error: "TestStand Error: -17502; System Level Exception." If you specify a return value of type String[ ] stored into an array of paths, the Microsoft Visual C++ Runtime Library returns an error, followed by a Windows notice that TestStand has encountered a problem and needs to close. Workaround: Create a new array of strings PropertyObject. Use this variable to pass information into the .NET assembly. If necessary, after calling the method copy the information from the array of strings back into the array of paths.
| |||||
| 184828 Return | TestStand crashes when you pass an array of object references with at least one element equal to Nothing to a .NET code module that accepts an array of objects If a .NET code module includes a method with object[] or params object[] as a parameter, passing an array of object references that contains an element set to Nothing from TestStand to the method crashes TestStand. Workaround: Ensure that none of the elements of the TestStand array of object references are set to Nothing.
| |||||
| 185775 Return | Returning null from a .NET code module to TestStand results in Error -17500 If you call a .NET assembly from TestStand and the assembly returns null to TestStand, TestStand returns Error -17500: "The value for the .NET parameter 'Return Value' could not be returned. Object reference not set to an instance of an object." Workaround: Modify the existing assembly to prevent null returns or create a wrapper to handle the null return of the existing assembly.
| |||||
| 188919 Return | TestStand does not properly set the lower bound of a one-dimensional array when you pass the array into a .NET code module When you create a one-dimensional array in TestStand, set the lower bound to a value other than zero, and then pass the array into a .NET code module, TestStand sets the lower bound of the array to zero within the .NET code module. This behavior exists only for one-dimensional arrays passed in as inputs. TestStand properly sets the lower bounds of multi-dimensional arrays and array output parameters. Workaround: N/A
| |||||
| ActiveX/COM Adapter | ||||||
| 44060 4GQ7M6JO Return | Cannot specify underlying data type when passing a Variant parameter using ActiveX 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 Adapter and API in expressions do not support specifying the underlying data type of variant parameters. Workaround: N/A
| |||||
| 177062 Return | Cannot specify the data type for VARIANT parameters in the ActiveX/COM Adapter 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.
| |||||
| C/C++ DLL Adapter | ||||||
| 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.
| |||||
| Database | ||||||
| 107649 Return | Logging binary data to a database from a large number of sockets might return an out-of-memory error Database logging schemas that use stored procedures reserve memory to buffer the logging of large binary column values. If you configure database logging to open a separate connection for each socket and you use the Parallel or Batch process models with a high number of test sockets, database logging can report an out-of-memory error. Workaround: Enable the Share Data Link Between Executions option on the Data Link tab of the Database Options dialog box, or lower the limit on the size of binary data that TestStand logs for each binary column.
| |||||
| 159752 Return | On-the-fly database logging reports an error when the MainSequence does not generate step results On-the-fly database logging reports an error when the MainSequence in a client sequence file does not generate at least one step result. The MainSequence returns no step results when the sequence is empty or when you disable result logging for the sequence or each step in the sequence. An error does not occur if you disable all result logging in the Station Options dialog box. Workaround: Add at least one step that generates a result to the sequence.
| |||||
| 159755 Return | Logging a waveform to a database as an additional result might result in an error if you do not also log all waveform subproperties The default TestStand database schema logs analog and digital waveform data to specific tables, PROP_ANALOGWAVEFORM and PROP_DIGITALWAVEFORM, respectively. The schema expects that all waveform subproperties, such as t0, dt, and Y, exist. However, when you include a waveform as an additional result, the subproperties of the waveform might not be included, which causes a run-time error when TestStand attempts to add a record to the database. Workaround: Log all properties of a waveform when you include a waveform as an additional result.
| |||||
| 190031 Return | TestStand incorrectly logs database timestamps as "AM" when the timestamp text contains "PM" instead of the localized symbol the regional settings of the operating system specify If a string timestamp contains non-localized "PM" characters and the regional settings specify a localized symbol other than "PM", database logging does not recognize the "PM" characters and assumes "AM" instead, causing the value stored in the database to be off by 12 hours. Workaround: N/A
| |||||
| 190038 Return | Format field on the Columns/Parameters tab of the Database Options dialog box appears empty when viewed after previously changing the value to a non-default value If you edit the Format field on the Columns/Parameters tab of the Database Options dialog box to contain a non-default value, when you close and re-open the Database Options dialog box, the Format field is empty. If you modify any of the column settings, the empty value persists. TestStand 4.2.1 fixes this behavior. Workaround: N/A
| |||||
| IVI | ||||||
| 116096 Return | IVI step types pass IVI session name to InitWithOptions() instead of IVI logical name TestStand IVI step types pass the IVI session name to the InitWithOptions() function rather than the specified IVI logical name, which causes an error and fails to initialize the IVI session for some instruments. Workaround: N/A
| |||||
| 197656 Return | Session Manager correlates logical names and driver sessions mapped to a particular IVI software module only to the type of instrument listed first in the list of published APIs for a software module If an IVI software module publishes APIs for multiple types of instruments in Measurement & Automation Explorer (for example, IviDmm, IviFgen, IviSwtch), the Session Manager associates driver sessions and logical names that use the software module only to the type of instrument that appears first in the list of published APIs. For example, if a software module publishes APIs for IviDmm and IviFgen and you use an IviFgen step in TestStand, the Logical Name list does not include the driver session and logical name associated with the software module. If you use an IviDmm step in TestStand instead, the Logical Name list does include the driver session and logical name associated with the software module. Workaround: Remove the published APIs for the types of instruments that you do not use or create multiple copies of the software module and publish a specific API for each individual copy.
| |||||
| Installation | ||||||
| 164423 Return | Uninstalling TestStand 2.0 from a computer with TestStand 4.x installed removes NI Session Manager files. When you uninstall TestStand 2.0 from a computer on which you also installed TestStand 4.x, the TestStand 2.0 uninstaller might incorrectly remove the NI Session Manager 4.x files. Workaround: Navigate to Add/Remove Programs on the Windows Control Panel and use the National Instruments Software maintenance utility to repair the NI Session Manager and restore the files.
| |||||
| 164424 Return | Installing IVI components from TestStand 2.0 after installing IVI components from TestStand 4.0 causes errors Do not install the Interchangeable Virtual Instrument (IVI) components from the TestStand 2.0 CD after you install the IVI Compliance Package (ICP) from the NI Device Driver CD or DVD included with TestStand 4.x. If you installed ICP 2.2 or later from the NI Device Driver CD or DVD 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 when you install TestStand 2.0. Workaround: If you installed the TestStand 2.0 IVI components after you installed ICP 2.2 or later from the NI Device Driver CD or DVD, navigate to Add/Remove Programs on the Windows Control Panel and use the National Instruments Software maintenance utility to repair the ICP product and correct this incompatibility.
| |||||
| 182438 Return | Uninstalling TestStand 4.2 breaks the TestStand 4.2 Version Selector Uninstalling TestStand 4.2 removes a dependency of the TestStand 4.2 Version Selector. In this situation, using the TestStand 4.2 Version Selector to make previous versions of TestStand active or launching a previous version of the TestStand Sequence Editor or TestStand Deployment Utility results in Just-In-Time Debugging prompts. Workaround: Keep TestStand 4.2 installed.
| |||||
| 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.
| |||||
| LabVIEW | ||||||
| 100053 Return | Enumerations with the same name as a constant show as an error The Edit VI Call dialog box highlights expressions as an error for variables that have the same name as an enumeration value. Workaround: Ignore error.
| |||||
| 101510 Return | LabVIEW user interface reports object leaks on shutdown when using ActiveX Variants in ActiveX callbacks 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. Workaround: Refer to the National Instruments KnowledgeBase article, located at http://www.ni.com/cgi-bin/redirect.cgi?dest=infcoprod&src=help&openagent&code=rdlug3, for more information about using a dynamically called VI to ensure that LabVIEW releases the object.
| |||||
| 114668 Return | LabVIEW user interface built with earlier version of LabVIEW crashes when calling newer VI that makes .NET calls A LabVIEW user interface running in the LabVIEW development environment can return an error after an execution uses the LabVIEW Run-Time Engine (RTE) to call a VI that uses .NET and the version of the LabVIEW RTE is later than the version of the LabVIEW development environment. Workaround: N/A
| |||||
| 119019 Return | VI parallel sections run sequentially LabVIEW serializes calls to the same VI from multiple TestStand threads when you set the execution system of the VI to Same as Caller or to UI. Workaround: Set the Execution System to anything other than "UI" or "Same as Caller"
| |||||
| 125375 Return | LabVIEW user interface freezes when you move splitter bars A LabVIEW user interface front panel might hang within LabVIEW if you move a splitter bar while an execution is tracing. LabVIEW 2009 fixes this behavior. Workaround: N/A
| |||||
| 127465 Return | Error when calling a VI that instantiates an ATL server that does not implement IDispatch LabVIEW 8.6 returns an error when TestStand runs a VI that instantiates an ATL server that does not implement the IDispatch interface. Workaround: N/A
| |||||
| 128144 Return | Problems with LLBs in TestStand workspaces You cannot manually add a VI in an LLB to the workspace. Additionally, the LabVIEW Module panel returns an error when you use the path control to select a VI and the current workspace contains a VI with invalid Windows path characters. Workaround: Select Insert Code Modules from the Workspace pane context menu to include the VI a sequence file calls.
| |||||
| 164429 Return | LabVIEW User Interface executables that do not use TestStand UI Controls might hang when launched LabVIEW User Interface executables that do not use the TestStand User Interface (UI) Controls might hang when launched. The hang occurs when TestStand loads the LabWindows/CVI Run-Time Engine and both LabVIEW and the run-time engine access computer resources simultaneously. Workaround: You can prevent the hang by using a Call Library Function VI to invoke a function in the LabWindows/CVI Run-Time Engine to force LabVIEW to synchronously load the run-time engine into memory before creating the TestStand Engine.
| |||||
| 164430 Return | Calling a LabVIEW-built DLL from the user interface thread that create the TestStand engine might cause the application to hang LabVIEW applications, such as a TestStand LabVIEW User Interface, might hang when you call a function in a LabVIEW-built DLL from the user interface 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. Workaround: Create the TestStand Engine in a non-user interface thread, such as Other 2, to work around this issue.
| |||||
| 40001 4APBA700 Return | Error when using a complex waveform data type The LabVIEW Adapter returns an error when unpacking a LabVIEW 8.5 or later complex waveform data type. Workaround: N/A
| |||||
| 41665 4DQCFCB8 Return | LabVIEW 8.5 or later returns a warning when you load the simple user interface example When you load the LabVIEW simple user interface example using LabVIEW 8.5 or later, LabVIEW returns a warning indicates that LabVIEW changed a constant wired to a Case structure to maintain compatibility with LabVIEW 7.1 and earlier. Workaround: The warning does not prevent the user interface from working correctly.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 49856 41AHCIMF Return | TestStand UI Controls do not process some key strokes in LabVIEW user interfaces 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. Workaround: N/A
| |||||
| 49942 41QFPFGH Return | Invalid tab order when using a keyboard shortcut in the LabVIEW user interface When you use a keyboard shortcut in the built-in LabVIEW user interface, LabVIEW correctly shows that the corresponding button has focus, but the tab order becomes invalid. Workaround: N/A
| |||||
| 50897 46PA3DMF Return | Help Topic menu item is disabled If a TestStand UI Control loses focus, the Help»Help Topic menu item is disabled in the TestStand LabVIEW User Interface. Workaround: If the Help»Help Topic menu item is disabled, click a TestStand UI Control to re-enable the menu item.
| |||||
| 51302 47IATQJ6 Return | A TestStand 3.5 operator interface might not lauch 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. Workaround: You can resolve this problem by installing the LabVIEW 7.0 RTE or rebuilding the executable.
| |||||
| 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
| |||||
| 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
| |||||
| 93531 4I5FL800 Return | Running a converted LabVIEW Test Executive sequence in TestStand incorrectly handles parameters 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. Workaround: Respecify the module call for the steps or select Tools»Update VI Calls in the sequence editor to update all the steps in the sequence file.
| |||||
| 128016 Return | Cannot open VI in LLB from TestStand workspace Double-clicking a VI file in an LLB from a workspace returns an error. Workaround: Manually browse to the VI from the LLB and open it that way.
| |||||
| 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 Workaround: N/A
| |||||
| 130303 Return | LabVIEW and TestStand incorrectly pass binary strings if the operating system uses a multibyte default language LabVIEW stores binary strings as arrays of unsigned characters, and when TestStand transfers this data with LabVIEW, the data is incorrectly translated using the default code page, which can result in modified data. Workaround: N/A
| |||||
| 136500 Return | LabVIEW arrays of complex numbers that specify individual elements are not logged correctly to additional results You can choose to pass an entire array or specify individual elements to pass to a VI when an array is on a LabVIEW connector pane. If the array is an array of complex numbers and you are logging the array as an additional result of the step, and if you specify individual elements instead of the entire array, the array will not be logged to the report as an additional result. Workaround: Specify the entire real and imaginary arrays instead of individual elements.
| |||||
| 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.
| |||||
| 137482 3NPETI3S Return | Errors occur when TestStand calls a VI that uses the DAQ assistant When calling the DAQ assistant, the DAQ assistant uses the LabVIEW first call primitive to determine if a task already exists. If the first call primitive is False, the DAQ assistant runs the task assuming the task is valid. However, the first call primitive is reset to True when the VI is no longer reserved, while DAQ tasks clean themselves up when the VI idles. This behavior can occur under any of the following conditions:
Workaround: Select File»Unload All Modules to unload all VIs from memory to ensure the DAQ assistant properly creates tasks on the next use. Alternatively, you can configure steps to dynamically load and unload the VI for each call.
| |||||
| 141998 Return | LabVIEW numeric value cast to Boolean value might have different values in TestStand depending on LabVIEW Adapter setting When you cast a numeric value to a Boolean value in LabVIEW and the number contains more than 8 bits, LabVIEW uses the upper byte of the number and discards the remaining bytes. This operation does not always leave the remaining Boolean value as 0 or 1. If you use the LabVIEW development environment from TestStand, LabVIEW checks only the first bit of the Boolean value to determine if it is true. If you use the LabVIEW Run-Time Engine, TestStand determines if a LabVIEW Boolean value is true by comparing it to a constant (unsigned char) 1, which results in different behavior between the run-time engine and the development environment, even if you use the same numeric value. Workaround: Instead of casting a numeric value to a Boolean value, manually convert the numeric value to a Boolean value by comparing it to a number. For example, you can compare the number to 0.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 158183 Return | LabVIEW parameter default values might be incorrect for binary strings with ampersand characters You can pass a string from a LabVIEW VI to TestStand via the LabVIEW Adapter as a normal or a binary string. Binary strings can contain any character; however, when reading a string with an ampersand character, TestStand incorrectly escapes the character, leading to an incorrect default value. Workaround: N/A
| |||||
| 158938 Return | Cannot pass 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 arrays 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 167774 Return | Cannot call a VI remotely if that VI is part of a LabVIEW project library TestStand 4.2 stores the namespace of a VI to avoid loading the wrong VI into memory. If you attempt to remotely execute a VI that is part of a LabVIEW project library, TestStand returns an error. Workaround: N/A
| |||||
| 168117 Return | The front panel of a VI code module can receive duplicate user keystrokes when the calling LabVIEW user interface and the VI use the same LabVIEW Run-Time Engine If you build a TestStand User Interface executable in LabVIEW and then execute a sequence that calls a LabVIEW code module that does not display a titlebar and runs in the same LabVIEW Run-Time Engine version as the user interface executable, user keystrokes within numeric and string controls on the code module front panel are duplicated. LabVIEW 2009 fixes this behavior. Workaround: Configure the Code Module VI to display the title bar by going to VI Properties»Window Appearance»Customize, or build the User Interface executable and Code Module VI in different versions of LabVIEW, or upgrade to LabVIEW 2009.
| |||||
| 175068 Return | Loading a VI with a large number of controls or indicators wired to the connector pane might return an error or crash TestStand An error or crash can occur when TestStand loads a code module VI that contains a large number of controls or indicators wired to the connector pane. A TestStand error occurs when loading the VI using a LabVIEW 8.0 or later version of the run-time engine or development environment. TestStand or LabVIEW can crash when using the LabVIEW 7.1.1 run-time engine or development environment. Workaround: N/A
| |||||
| 179186 Return | Configuring a MessagePopup step as a Modal or Floating popup hangs subsequent LabVIEW steps configured to Show VI Front Panel When Called If you enable the Make Modal or Make Floating option in the Dialog Options section of the MessagePopup Layout edit tab and call LabVIEW code modules after you call the MessagePopup step, the LabVIEW code modules hang if they are configured to Show VI Front Panel When Called. 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 190040 Return | TestStand Deployment Utility and default LabVIEW User Interface executables fail to launch after uninstalling all other applications dependent on the LabVIEW 8.2.1 Run-Time Engine The TestStand Deployment Utility and the default LabVIEW User Interface executables use the LabVIEW 8.2.1 Run-Time Engine (RTE) and fail to launch if the LabVIEW 8.2.1 RTE is not installed. The installers for TestStand 4.1 and later do not properly establish dependencies on the LabVIEW 8.2.1 RTE. Uninstalling all other National Instruments software dependent on the LabVIEW 8.2.1 RTE can incorrectly remove the LabVIEW 8.2.1 RTE. This issue affects the TestStand Development System, not deployed systems created using installers the TestStand Deployment Utility builds. Workaround: Manually install the LabVIEW 8.2.1 RTE located at http://joule.ni.com/nidu/cds/view/p/id/550/lang/en.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 190260 Return | Calling an assembly built with LabVIEW 2009 from TestStand and unloading the assembly from memory crashes TestStand when you perform the same steps a second time When you call an assembly built with LabVIEW 2009 from TestStand, unload the assembly from memory, call the assembly from TestStand a second time, and unload the assembly from memory again, TestStand crashes because the reference count is not properly incremented. Workaround: N/A
| |||||
| 191239 Return | The LabVIEW Module panel returns an error message for some LabVIEW 7.1.1 VIs when LabVIEW 2009 is the active development environment If you configure the LabVIEW Adapter to use the LabVIEW 2009 development environment, the LabVIEW Module panel returns an error message for some LabVIEW 7.1.1 VIs incorrectly stating that the VI prototype has changed. Workaround: Reload the VI prototype by clicking the error message or run the Update VI Calls tool introduced in TestStand 4.1.
| |||||
| 191678 Return | When you use LabVIEW 2009 to build the LabVIEW Simple User Interface, the user interface remains open if you do not move the mouse after closing the user interface If you rebuild the LabVIEW Simple User Interface with LabVIEW 2009 and then run the executable, failing to move the mouse after clicking the close button on the title bar or clicking the Exit button causes the user interface to remain open. When you move the mouse, the user interface closes successfully. This behavior does not exist with the LabVIEW Full-Featured User Interface. Workaround: Move the mouse after you click the close or Exit button or change the Preferred Execution system from "user interface " to "standard " in the Execution page of the VI Properties dialog box.
| |||||
| 191741 Return | Clicking a LabVIEW step when TestStand is configured to use the LabVIEW 7.1.1 Run-Time Engine, results in a Fatal Error: "LABVIEW.LIB could not locate "FResDir"" This error occurs when the LabVIEW 2009 Run-Time Engine is loaded into memory after the LabVIEW 7.1.1 Run-Time Engine has already been loaded into memory. When you configure the LabVIEW Adapter to use the LabVIEW 7.1.1 Run-Time Engine, TestStand loads the LabVIEW 7.1.1 Run-Time Engine into memory. Selecting a LabVIEW step causes TestStand to attempt to load the LabVIEW 2009 Run-Time Engine into memory to use it to perform a checksum of the VI connector pane, which results in a Fatal Error: "LABVIEW.LIB could not locate "FResDir" ". Workaround: Configure the LabVIEW Adapter to use the LabVIEW development environment instead of the LabVIEW 7.1.1 Run-Time Engine.
| |||||
| 193129 Return | Calling assemblies built with LabVIEW 2009 from the LabVIEW development environment causes a hang Calling an assembly built with LabVIEW 2009 from a LabVIEW code module that uses the LabVIEW development environment to execute causes LabVIEW to hang. Additionally, calling the assembly as a .NET code module from any of the LabVIEW User Interfaces running in the LabVIEW development environment hangs LabVIEW while attempting to run the .NET step. Workaround: When calling the assembly inside of a LabVIEW code module, use the LabVIEW Run-Time Engine to call the code module. When calling the assembly as a .NET code module and using a LabVIEW User Interface, use the LabVIEW Run-Time Engine to run the user interface executable.
| |||||
| 193418 Return | Calling the GetComplexRealPartElement or GetComplexImaginaryPartElement methods from the LabVIEWParameter or LabVIEWParameterElement classes of the TestStand API returns an invalid reference in C++ If you use #import to access the TestStand LabVIEW Adapter API in C++, calling the LabVIEWParameter.GetComplexRealPartElement, LabVIEWParameter.GetComplexImaginaryPartElement, LabVIEWParameterElement.GetComplexRealPartElement, or LabVIEWParameterElement.GetComplexImaginaryPartElement methods returns an invalid reference. Workaround: Call QueryInterface on the returned reference.
| |||||
| 198301 Return | Calling a LabVIEW 2009 built assembly from TestStand results in an error when you pass a struct that contains arrays as a return value and you do not assign a variable to the return value If a LabVIEW 2009 assembly passes a struct that contain arrays as the return value, calling the assembly from TestStand without assigning a variable in which to store the return value results in "Error 17500: Operation Failed. Object reference not set to an instance of an object." Workaround: Assign a variable to the return value parameter in TestStand.
| |||||
| 198467 Return | Calling a LabVIEW 2009 built assembly from TestStand results in an error when you pass a struct that contains an unsigned integer as an output parameter or return value If a LabVIEW 2009 assembly passes a struct that contains an unsigned integer as an output parameter or return value, calling the assembly from TestStand results in "Error 17500: Operation Failed. Object of type 'System.Int32' cannot be converted to type 'System.UInt32'&auot This situation also affects LabVIEW clusters that contain enum and ring indicators because enums and rings use unsigned integers by default. Workaround: Use something other than an unsigned integer to represent numeric, enum, or ring indicators contained within clusters when you build a LabVIEW 2009 assembly and pass the struct to TestStand as an output parameter or return value.
| |||||
| 198789 Return | Activating the LabVIEW Module tab for a step that calls a VI located within an LLB crashes the TestStand Sequence Editor if the LLB no longer contains that specific VI If you configure a LabVIEW step to call a VI contained in an LLB and you later remove that specific VI from the LLB, when you return to the Sequence Editor and activate the LabVIEW Module tab for the step that calls that VI, TestStand crashes. This behavior does not exist in the Specify Module dialog box. Workaround: Select another and then navigate to the Properties tab of the Step Settings pane for the temporary step. Select the problematic LabVIEW step. At this point you should see the Properties tab of the problematic LabVIEW step. You can now delete the step and recreate it or manually edit the value of the Step.TS.SData.ViCall.VIPath hidden property in the Property Browser panel of the Properties pane.
| |||||
| LabWindows/CVI | ||||||
| 127639 Return | Parameters included as additional results do not update when a type changes in function The type of parameter displayed on the Additional Results panel for a LabWindows/CVI DLL does not always update after you change the parameter type on the LabWindows/CVI Module tab in the sequence editor or in the Edit LabWindows/CVI Module Call dialog box. Workaround: Respecify the step.
| |||||
| 36951 49GAQ5G0 Return | Error when loading a TestStand 4.0 or later user interface when TestStand 3.5 is the active version LabWindows/CVI returns an error when you load a TestStand 4.0 or later user interface and TestStand 3.5 is the registered active version of TestStand. Workaround: N/A
| |||||
| 39257 48IACA9Q Return | Reload Prototype button remains dimmed after building a DLL When you use the LabWindows/CVI Module tab on the Step Settings pane 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. Workaround: On the LabWindows/CVI Module tab, click the File Browse button and select the DLL again.
| |||||
| 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.
| |||||
| 177213 Return | Calling TS_ExprCtrl_Create() in LabWindows/CVI leaks an object handle The TS_ExprCtrl_Create() LabWindows/CVI TestStand Utility function places a control on the panel and creates three object handles in the process. Using the DiscardPanel() function to discard the panel properly discards two of the object handles but not the third object handle. Workaround: Call CA_DiscardObjHandle() in the TS_ExprCtrl_CreateActiveXControl() function manually.
| |||||
| 128752 Return | The function prototype for the TS_ExecutionGetResultObject function of the LabWindows/CVI TestStand API library is incorrect The prototype of the TS_ExecutionGetResultObject function of the LabWindows/CVI TestStand API library incorrectly expects a TSObj_PropertyObject variable for the ResultObject parameter. Allowing LabWindows/CVI to automatically declare a variable for the ResultObject parameter from within the TS_ExecutionGetResultObject function panel also incorrectly creates a variable of type TSObj_PropertyObject. When you right-click TSObj_PropertyObject and select Go To Definition from the context menu, LabWindows/CVI displays a message that TSObj_PropertyObject is not defined. This also results in a compile error. Workaround: The prototype of the TS_ExecutionGetResultObject function expects a variable of type TSObj_Property for the ResultObject parameter. Use the TSObj_Property identifier instead of TSObj_PropertyObject to declare the variable you intend to pass to the ResultObject parameter.
| |||||
| 197844 Return | Clicking the Verify Prototype button on the LabWindows/CVI Module tab results in a prototype conflict when the function call contains parameters of type int or unsigned int When you click the Verify Prototype button on the LabWindows/CVI Module tab to verify the function prototype of a LabWindows/CVI code module and the function prototype contains parameters of type int or unsigned int, the Prototype Conflict dialog box prompts you to handle a conflict even though the prototype on the LabWindows/CVI Module tab exactly matches the prototype in the source file. Workaround: Use a type of long or unsigned long instead of int or unsigned int.
| |||||
| Microsoft Visual Studio | ||||||
| 109366 Return | Calling a .NET module as an OnNewStep custom substep can error TestStand returns an error when calling an OnNewStep custom substep that calls a .NET WinForm that requires an STA thread. Workaround: N/A
| |||||
| 115665 Return | Passing an array of ActiveX objects to a .NET code module might crash TestStand Calling a .NET code module can crash TestStand if the call passes ActiveX objects in an array of objects. Workaround: N/A
| |||||
| 127370 Return | Invalid XML documentation comment in .NET assembly causes methods to not appear in TestStand The .NET Adapter does not display any methods of a Microsoft Visual Basic .NET assembly if an invalid XML documentation comment appears before a function or sub, the comment starts with three apostrophes, and the function or sub contains at least one parameter. Workaround: Begin non-XML comments with one apostrophe instead of three.
| |||||
| 127991 Return | Receiving UI events in a .NET class that is not created in the UI thread might cause errors Registering a .NET class to receive UI events from a TestStand UI Control, such as the Application Manager control, can cause unexpected re-entrancy issues when the .NET class is not created in the UI thread. Workaround: N/A
| |||||
| 164428 Return | Clicking a TestStand UI Control in a custom .NET user control might cause Microsoft Visual Studio to crash If you click a TestStand User Interface (UI) Control hosted in a .NET user control in the Design view of Microsoft Visual Studio 2005, Visual Studio might crash. Visual Studio 2008 fixes this issue. Workaround: Refer to the Microsoft Knowledge Base article ID 916495, located at http://support.microsoft.com/?kbid=916495, for more information about the hotfix for this Visual Studio 2005 limitation.
| |||||
| 164431 Return | Microsoft Visual Studio 2005 might crash when viewing a form in Design view after rebuilding a solution that uses TestStand UI controls Microsoft Visual Studio 2005 might crash when you rebuild a solution that uses the TestStand User Interface (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. Workaround: Refer to the Microsoft Knowledge Base article 912019, located at http://support.microsoft.com/kb/912019/en-us?spid=3041, for more information about this issue.
| |||||
| 35150 48483R00 Return | Warning when stepping into code using Visual Studio 2005 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. Workaround: N/A
| |||||
| 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
| |||||
| 41890 4E2GE8JO Return | Cannot edit .NET code when methods contain enumeration parameters The .NET Adapter Edit Code option does not work for methods with enumeration parameters. Workaround: N/A
| |||||
| 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.
| |||||
| 50221 43FB4RYL Return | Visual Studio 2005 for C# can crash on exit when using the TestStand UI Controls 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. Workaround: Close the form in the designer before you exit Visual Studio to avoid this harmless crash.
| |||||
| 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.
| |||||
| 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.
| |||||
| 51390 47Q9EUH8 Return | Error when passing an empty array to a .NET code module The .NET Adapter generates a run-time error when a step passes an empty array as a parameter. Workaround: You must pass a non-empty array.
| |||||
| 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
| |||||
| 95377 Return | Building the example .NET user interfaces in Visual Studio 2008 fails Loading and building the Visual Studio 2005 example .NET user interfaces in Visual Studio 2008 fails when the post-build action cannot locate mt.exe. Visual Studio 2008 includes a feature for adding manifests to executables and no longer ships the mt.exe application that Visual Studio 2005 uses. TestStand 4.2.1 includes native Visual Studio 2008 projects for the .NET and C++ MFC user interfaces. Workaround: Remove the post-build action and edit the project settings to embed the manifest in the executable.
| |||||
| 98055 Return | Stepping into C++ or .NET code might result in an error Stepping into a C++ or .NET code module results in an error if you already attached Visual Studio to the TestStand process and if 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. Workaround: You must specify to attach by debugging native and managed code types in Visual Studio.
| |||||
| 98110 Return | Parameters of class constructor do not update The .NET code module Configure Class Constructor pane does not update parameters when the signature of the method changes while the step is selected. Workaround: You must select a different step and reselect the step to refresh the pane.
| |||||
| 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.
| |||||
| 98178 Return | Cannot step into a .NET code module if a debugging session is already attached to TestStand If a debugging session is already attached to TestStand when you perform a step into operation for a .NET code module from TestStand, TestStand instead performs a step over operation. Workaround: N/A
| |||||
| 97704 Return | .NET Adapter does not handle arrays of enumerations correctly The .NET Adapter Specify Module dialog box and panel do not handle arrays of enumeration parameters correctly. You cannot specify an argument for each individual item in the array or add new array elements. Workaround: N/A
| |||||
| 156580 Return | Stepping into a .NET assembly with Microsoft Visual Studio 2008 might not pause execution after you have previously stepped out of .NET code When you step into .NET source code using TestStand, Microsoft Visual Studio becomes the active application and execution pauses on the first line of the called method. In some cases in which this operation has completed successfully and the user has returned execution to TestStand, subsequent Step Into operations cause Visual Studio to become the active application, but execution of the method does not pause. Workaround: Add a breakpoint to a line of source code in Visual Studio to always force the execution to pause on the line if Visual Studio is attached to the TestStand process, regardless of whether a Step Into operation occurred.
| |||||
| 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.
| |||||
| 158837 Return | Installing National Instruments Measurement Studio 8.6 after you install TestStand removes the NI TestStand Help from the documentation table of contents in Visual Studio 2008 TestStand and Measurement Studio install help files for use with Visual Studio 2008. If you install Measurement Studio 8.6 after you install TestStand, the TestStand documentation disappears from the documentation table of contents in Visual Studio 2008. Measurement Studio 2009 fixes this behavior. Workaround: Complete the following steps to merge the NI TestStand Help and restore its location in the table of contents.
| |||||
| 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
| |||||
| Miscellaneous | ||||||
| 100723 Return | Loading a type with a reference to itself causes a crash TestStand crashes when loading a file if TestStand resolves a type conflict in such a way that the type contains an instance of itself. Workaround: N/A
| |||||
| 101285 Return | Configure operation for an IVI Dmm step might fail when using the Temperature Measurement extension 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. Workaround: N/A
| |||||
| 102490 Return | Break on First Step incorrectly causes Step Into The Break on First Step debugging option in the Execute menu incorrectly performs a Step Into operation on the module that the first step in a hidden execution calls. Workaround: N/A
| |||||
| 102916 Return | TestStand leaks small amount of memory when leaving blank an optional parameter of an ActiveX method 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. Workaround: Specify a value for the parameter.
| |||||
| 103579 Return | Cannot create variables that have the same name as an API method You cannot create a variable with the same name as an API method in an ExpressionEdit control. Workaround: N/A
| |||||
| 106387 Return | Types window does not refresh after editing type palettes programatically The Types window and Insertion Palette pane in the sequence editor do not refresh after you call the Engine.UnloadTypePaletteFiles method. Workaround: Right-click the Types window and select Customize Types Palette from the context menu and then click OK.
| |||||
| 114687 Return | Enabling ExecMask_TraceAllThreads can cause memory leak The TestStand Sequence Editor and TestStand UI Controls do not support executions that enable ExecMask_TraceAllThreads. Enabling ExecMask_TraceAllThreads results in memory leaks. Workaround: Remove the ExecMask_TraceAllThreads flag
| |||||
| 124968 Return | Error when running two instances of the Java example step type asynchronously Running the Java example step type in two executions can generate an error if the first execution that uses the step type completes after the second execution that uses the step type. Workaround: N/A
| |||||
| 126503 Return | NI Switch Executive 3.0 returns incorrect route state When you use NI Switch Executive 3.0, the SwitchFindRoute expression function incorrectly returns available for the routeCapability parameter when the route is already connected. Workaround: N/A
| |||||
| 128019 Return | Workspace File Documentation tool incorrectly specifies a modification date for VIs in LLBs The Workspace File Documentation tool incorrectly indicates a modification date of 12/31/1600 6:00:00 PM for VIs that reside in LLBs. Workaround: N/A
| |||||
| 164437 Return | Internet Explorer control TestStand uses might leak handles or crash if the control cannot find the XML style sheet The Microsoft Internet Explorer control that TestStand applications use to display XML reports might leak handles or crash when the control cannot find the style sheet you specify in the Report Options dialog box and the control attempts to display XML report files. Workaround: N/A
| |||||
| 164491 Return | ActiveX EXE servers that launch dialog boxes can cause TestStand to hang if TestStand also launches a dialog box 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. Workaround: N/A
| |||||
| 35009 47FEKD00 Return | Database logging and on-the-fly report generation can leak memory Database logging and on-the-fly report generation slowly leak memory when executions repeatedly use a Sequence Call step to create new threads. Workaround: N/A
| |||||
| 35081 47DD4PIA Return | Incorrect prompt for reload with source code control TestStand prompts you to reload files when source code control (SCC) 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. Workaround: N/A
| |||||
| 35106 47FE0BG0 Return | Incorrect indentation when using on-the-fly report generation On-the-fly report generation incorrectly indents step results that follow a Sequence Call step that creates a new thread. Workaround: N/A
| |||||
| 35247 46REB4YL Return | Error when checking out a project file When you check out a project file, TestStand incorrectly attempts to check out files under the project file in the workspace that are not under source code control (SCC). TestStand returns an error if you do not exclude these files from the check out operation. Workaround: N/A
| |||||
| 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
| |||||
| 41730 4DQDAQYL Return | Using on-the-fly reporting with asynchronous threads can cause error 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. Workaround: N/A
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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
| |||||
| 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
| |||||
| 48066 3PIA7EYL Return | Automatic setup of remote execution does not work for non-English Windows XP SP2 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. Workaround: If you use a non-English Windows XP SP2 or later, refer to the Setting Windows System Security section of Chapter 5, Module Adapters, of the NI TestStand Reference Manual for more information about configuring Windows system security to allow users to remotely access and launch the TestStand server.
| |||||
| 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
| |||||
| 48959 3WJCMJOF Return | XML reports display 2D arrays incorrectly TestStand XML reports present 2D arrays as 1D arrays. Other report formats present 2D arrays correctly. Workaround: N/A
| |||||
| 50593 45KK5S00 Return | File dialog box can leak a USER object The TestStand File dialog box can leak a Windows USER object. Workaround: N/A
| |||||
| 50996 46Q8EUIA Return | IVI Fgen step might not store waveform data
Workaround:
| |||||
| 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.
| |||||
| 51079 46QBMLRA Return | Watch expressions do not suspend when reference object set TestStand watch expressions do not suspend the execution when the expression returns a reference object and the previous value of the object returned Nothing. Workaround: Use an expression that returns a Boolean value, such as Locals.Reference != Nothing.
| |||||
| 51161 47BK2TUZ Return | SequenceFilePreInteractive and SequenceFilePostInteractive callbacks do not run TestStand does not call the SequenceFilePreInteractive and SequenceFilePostInteractive callbacks when running a step interactively using a process model. Workaround: N/A
| |||||
| 51218 47EFL3MF Return | Saving large XML files might run out of memory 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. Workaround: Change the file format to Binary or INI before you attempt to save the file to work around this issue.
| |||||
| 51295 47891JJ6 Return | Incorrect property object leaks when calling a remote sequence 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 reports property object leaks if you call a remote sequence and a run-time error occurred because you passed extra parameters to the sequence. Workaround: N/A
| |||||
| 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
| |||||
| 51527 47PIG6MF Return | TestStand Differ does not show differences in strings with leading or trailing quotation marks The Differ window in the sequence editor and the TestStand Differ application do not show differences between strings with different preceding or trailing quotation mark characters. Workaround: N/A
| |||||
| 52274 4AJA99YL Return | Saving a sequence file with Wait steps as TestStand 2.0.1 or earlier might result in error 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. Workaround: Manually reconfigure the Wait steps.
| |||||
| 54115 3BDELTRA Return | Navigating back or using links in the Report control might error 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. Workaround: N/A
| |||||
| 96016 Return | Legend in the Sequence Hierarchy window is cut off TestStand might truncate the legend in the Sequence Hierarchy window when you save the hierarchy to disk. Workaround: N/A
| |||||
| 98511 Return | Opening a file with an array of unstructured containers might error 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 that not enough information exists to create an object for reading. Workaround: N/A
| |||||
| 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.
| |||||
| 132943 Return | XML Packaging Utility fails on a multibyte OS with English (US) regional settings Using the XML Packaging Utility to package a TestStand XML report and its style sheet returns an error if you are using a multibyte operating system, but have the English (US) regional settings selected. Workaround: Change to the native regional settings to prevent this error.
| |||||
| 133255 Return | HTML and XML reports display graphs of 2D arrays of numbers differently In HTML reports, a 2D array appears as multiple 1D arrays and is plotted as one new plot per column of data. In XML reports, a 2D array appears as multiple 1D arrays and is plotted as a new plot for each row. Workaround: You can transpose a 2D array to plot it correctly in XML reports.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 150427 Return | Switching from a literal path to an expression in the Configure Call Executable dialog box does not refresh the found path display If you specify a path literal in any of the path controls in the Configure Call Executable dialog box in a TestStand User Interface, the found path control, located below the File Pathname control, updates to show the full path. If you enable the Specify File Path by Expression option, specify a new expression or modify an existing expression, and then disable the Specify File Path by Expression option, the found path control does not update but continues to show the previous full path. This issue affects all path controls that have a found path control below them in the Configure Call Executable dialog box. This behavior does not occur on the Call Executable edit tabs on the Step Settings pane in the sequence editor. Workaround: Close and relaunch the Configure Call Executable dialog box to refresh the full path display or edit the path again, and tab off of the control.
| |||||
| 153401 Return | HTML report generated on-the-fly incorrectly indents steps placed after a skipped Sequence Call step in a group If you have a Sequence Call step that is skipped inside of a group, such as between a While step and the corresponding End step, the report TestStand generates indents all steps after the skipped Sequence Call step by one position too many. Workaround: You can remove the skipped sequence or run it normally to prevent this behavior.
| |||||
| 153501 Return | TestStand Differ application cannot undo an operation by reloading files that are already loaded The TestStand Differ application does not support the undo operation. If you want to undo a change, you must reload the files. However, directly reloading the files does not revert the change. Workaround: Swap the order of the files in the File Open dialog box to force a reload, or shut down and restart the Differ application.
| |||||
| 154954 Return | Expression Browser dialog box elements do not display correctly if the font size is set to 120 DPI If the font size of Windows XP or Windows Vista is set to 120 DPI, the Replace and Insert buttons, descriptions, and variable names on all tabs of the Expression Browser dialog box do not display correctly or at all. Workaround: You can still use the Expression Browser dialog box by double-clicking on an element. If you do not select any text, double-clicking an element inserts the element in the expression control at the bottom of the current cursor position. If you do select text, double-clicking an element replace the existing text with the element. Hovering over an element launches the context help, which contains almost all the information that is this display issue hides.
| |||||
| 158138 Return | Call Executable step does not report an error when TestStand cannot create a remote stdout file If you use the Call Executable step type to run an executable on a remote computer and save the standard output to a remote file, TestStand does not report an error if the designated directory does not exist, if the file path is incorrectly formatted, or when writing to read-only or locked files. Workaround: N/A
| |||||
| 159453 Return | Loading a TestStand 2.0 sequence file that contains ActiveX Adapter steps results in an error after running a user interface in LabVIEW more than once Loading a TestStand 2.0 sequence file that contains steps configured to use the ActiveX Adapter can generate an "Unknown type name 'AutomationStep' " error after running a user interface in the LabVIEW development environment more than once. The error occurs because the TestStand Engine does not properly reregister required types to open the older sequence file. Workaround: Shut down LabVIEW before running the user interface and opening the older file.
| |||||
| 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.
| |||||
| 164489 Return | XML reports might not display graphs correctly XML reports might display a table of measurement data instead of a graph under the following conditions:
Workaround: Refer to the National Instruments KnowledgeBase article, located at http://www.ni.com/cgi-bin/redirect.cgi?dest=infcoprod&src=help&openagent&code=rdgxml, for more information about altering the Windows registry to make the My Computer security zone visible in the Internet Options dialog box.
| |||||
| 50771 469ETBS5 Return | Changing Windows themes while the sequence editor is open corrupts the display of the Step Settings pane for a Call Executable step If you change the Windows theme while the sequence editor is open, the display of text boxes and expression edit controls on the Step Settings pane for a Call Executable pane is corrupted. Control outlines might not be drawn and icons might not display properly. Workaround: Restart the sequence editor after changing the theme.
| |||||
| 170121 Return | The XML Packaging Utility removes the encoding attribute from generated XML file The XML Packaging Utility incorrectly removes the encoding attributes from the generated XML file. Without the encoding attributes, XML files that were generated using a multi-byte language do not display properly. Workaround: Manually add the encoding attribute back into the XML file.
| |||||
| 181116 Return | Using the <UUTStatus> macro to specify the report file path by expression does not generate the report in the correct location when you enable On-The-Fly Reporting and Conserve Memory and Only Display Latest Results options If you select Specify Report File Path by Expression from the File Name/Directory Options ring control of the Report File Pathname tab of the Report Options dialog box and the expression uses the <UUTStatus> macro as part of the path, TestStand does not generate the report in the directory the macro specifies when you enable the On-The-Fly Reporting and the Conserve Memory and Only Display Latest Results options on the Contents tab of the Report Options dialog box. Workaround: N/A
| |||||
| 183939 Return | Modifying a report file path expression in the ReportOptions Callback causes error -17500 If you modify a report file path expression from within the ReportOptions Callback, TestStand returns error -17500 ("Operation Failed"). This error also occurs if you try to enable report generation in the ReportOptions Callback. Workaround: After modifying the expression or enabling Reporting from within the ReportOptions Callback, call an Expression Statement step with the expression Parameters.ReportOptions.CheckIfMacroListIsUnchanged = False.
| |||||
| 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.
| |||||
| 189528 Return | Perforce 2009.1 client causes TestStand to crash when closing a workspace file If you configure source control to use the Perforce SCM Provider, TestStand loads the Perforce SCC DLL when you open a workspace file. When you close the workspace file, TestStand then unloads the Perforce SCC DLL. If you use the Perforce 2009.1 client, TestStand might crash after unloading the Perforce SCC DLL when you close a workspace file. Workaround: Use the Perforce 2008.2 client or the 2009.2 client when available. You can prevent TestStand from unloading the p4scc.dll from memory by calling the LoadLibrary Windows SDK function before unloading a workspace file that uses Perforce SCM as the SCC provider.
| |||||
| 190645 Return | Using the example Java step types to call a Java method that does not take any parameters and returns a string results in error -17502 "System Level Exception" If you define a Java method with no parameters and a string return value, calling the method from the example Java Action step or String Value Test step results in error -17502 "System Level Exception". Debugging the Java step type source code, JavaCall.dll, in LabWindows/CVI results in a Fatal Run-Time Error: "Dereference of null pointer". This behavior exists for static and non-static method calls. Workaround: This error occurs during an attempt to dereference a null pointer when calling a Java method that returns a string value but does not take any parameters. To correct this behavior, use LabWindows/CVI to open JavaCall.cws in the <TestStand Public>\Examples\Java directory, replace lines 683 and 684 of the InvokeJavaMethod() function and lines 1040 and 1041 of the InvokeStaticJavaMethod() function with the following: If(stringRef !=NULL) { stringRef[refCount] = retVal; refCount++; }
| |||||
| 192247 Return | When you enable On-The-Fly reporting and TestStand records a result after the MainSequence completes, the report shows the UUTStatus as "Running" When you enable On-The-Fly reporting, if the process model executes steps that are configured to record results, if the sequence calling the steps does not enable the Disable Result Recording for All Steps option, and if the steps execute after MainSequence completes executing, the report shows the final UUT Status as "Running". Workaround: Enable the Disable Result Recording for All Steps option of the Sequence Properties dialog box for any sequence or subsequence in a client sequence file that MainSequence does not call.
| |||||
| 194532 Return | Reloading a code module prototype from within the Sequence File Differ results in an error if no step differences exist between the two sequence files after you reload the prototype When you diff two sequence files that are identical in every way except for a code module parameter setting and the prototype of that code module changed since the last time you loaded the sequence files, the Sequence File Differ returns an "Object reference not set to an instance of an object" error when you reload the code module prototype of both sequence files from within the Sequence File Differ and no remaining step differences exist between the two files. Workaround: Ensure that all code module prototypes remain valid and reload those that are not before you diff two sequence files, or navigate to the individual sequence files and reload the prototype directly from the sequence file, not from within the Sequence File Differ.
| |||||
| 198427 Return | TestStand returns an error when you record Additional Results for a subset of the parameters of a SequenceCall step configured to loop, you enable the Record Result of Each Iteration option, and the subset of parameters does not start with the first parameter If you configure a SequenceCall step to loop and record Additional Results for a subset of the SequenceCall parameters, an error occurs if you enable the Record Result of Each Iteration looping option and the subset of parameters does not start with the first parameter. For example, if the SequenceCall step includes 5 parameters, and you select to record Additional Results only for parameters 3, 4, and 5, an error occurs. The error also occurs when you select to record Additional Results for parameters 1, 3, and 4. However, if you select to record Additional Results for parameter 1, or parameters 1 and 2, or parameters 1, 2, and 3, and so on, the error does not occur. Workaround: Disable the Record Result of Each Iteration looping option or do not use the Looping property of the step and use a While loop or For loop instead.
| |||||
| 198622 Return | TestStand shows the Report Tab after an execution completes for ASCII and HTML report formats even when you disable report generation If you select ASCII Text File or HTML Document as the Report Format in the Report Options dialog box and you enable the Disable Report Generation option, when you select Test UUTs or Single Pass from the menu bar, the Report tab becomes active at the end of the execution and includes the text "Report generation is disabled." This behavior does not exist for the XML Document or ATML Report Document report formats. Workaround: If you do not want to generate a report for an execution and do not want the Report tab to display at the completion of the execution, modify the Report Options dialog box to disable the Disable Report Generation option, change the Report Format to XML Document or ATML Report Document, and then enable the Disable Report Generation option again.
| |||||
| 200206 Return | Significant decrease in performance occurs when using NI-488.2 for Microsoft Windows and LabVIEW Real-Time You might experience significant loss of GPIB performance after installing or updating NI software on systems using PCI, PCI Express, PMC, or PXI GPIB interface types or built-in interfaces on PXI and VXI controllers. All other GPIB interfaces are not affected. Refer to the KnowledgeBase article at http://digital.ni.com/public.nsf/websearch/DD67839852DCF8FA8625768D007A8474?OpenDocument for more information about this issue. NI-488.2 version 2.7.3 fixes this behavior. Workaround: Refer to the KnowledgeBase article at http://digital.ni.com/public.nsf/websearch/DD67839852DCF8FA8625768D007A8474?OpenDocument for more information about this issue.
| |||||
| TestStand Deployment Utility | ||||||
| 128535 Return | TestStand Deployment Utility is slow when accessing the NI Device Driver CD or DVD on a network drive Launching the TestStand Deployment Utility is slow to initialize and enabling options in the Drivers and Components dialog box is slow to respond when the NI Device Driver CD or DVD is located on a slow network drive. Workaround: N/A
| |||||
| 52184 4ADMCJ77 Return | Building a deployment before LabVIEW completely launches might cause 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 and newer. Workaround: Start LabVIEW and wait until initialized before building a deployment.
| |||||
| 96388 Return | Deploying State Chart VIs can hang Building a deployment can hang if the deployment includes VIs that call LabVIEW State Chart VIs. Workaround: N/A
| |||||
| 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:
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.
| |||||
| 140095 Return | TestStand Deployment Utility cannot deploy VIs that use LabVIEW 8.6.x Report Generation Toolkit VIs Due to incompatibilities between LabVIEW and TestStand, the TestStand Deployment Utility cannot deploy any VI that uses LabVIEW 8.6.x Report Generation Toolkit VIs. Workaround: Refer to the National Instruments Web site at ni.com/info and enter the info code rdtslv86 to access the National Instruments KnowledgeBase article "How to Successfully Deploy a TestStand System with LabVIEW 8.6 and Report Generation Toolkit" which contains more information about possible workarounds when you want to deploy VIs and you are using LabVIEW 8.6.x.
| |||||
| 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.
| |||||
| 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.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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.
| |||||
| 169447 Return | Deployment utility hangs when you use invalid characters in the name of a step that calls an Express VI The TestStand Deployment Utility uses the step name and unique ID to build a wrapper VI for steps that call Express VIs. If the name of a step that calls an Express VI contains invalid characters, such as ?, @, <, >, and so on, the deployment utility hangs during build. Workaround: Avoid using invalid characters, such as ?, @, <, >, and so on, in step names.
| |||||
| 174588 Return | VIs that are members of the same LabVIEW project library but deployed to separate target destinations cannot simultaneously exist in memory If you build a deployment with TestStand 4.2 and LabVIEW 8.6.1 or later and specify different destination directories for VIs that are members of the same LabVIEW project library, you cannot simultaneously load the VIs into memory once you deploy the VIs to the target computer. Workaround: Add the LabVIEW project library that contains the VIs to the TestStand workspace.
| |||||
| 176525 Return | Enabling the Remove Unused VI Components LabVIEW option disconnects control type definitions from the connector pane when building a deployment When you use the TestStand Deployment Utility to build a deployment, enabling the Remove Unused VI Components option in the LabVIEW Options dialog box disconnects type definitions from the VI connector pane and leaves the type definitions out of the deployment. This VI connector pane change requires TestStand to reload the prototype for each call to the VI. Workaround: Do not enable the Remove Unused VI Components option in the LabVIEW Options dialog box.
| |||||
| 180839 Return | Building TestStand deployments fails on a non-English Microsoft Windows OS that has a non-English LabVIEW installed Building a TestStand deployment on a non-English Windows OS that has a non-English LabVIEW installed results in the "Internal Error Code -4500 Processing VIs... AB_API: Destination label not found." error. Workaround: Use an English Windows OS or an English LabVIEW.
| |||||
| 181041 Return | Deploying VIs that call .NET assemblies in the GAC might cause Internal Error Code 1 Using the TestStand 4.2 Deployment Utility with LabVIEW 8.6 or earlier to deploy a VI that calls a .NET assembly from the global assembly cache (GAC) might result in Internal Error Code 1. Workaround: N/A
| |||||
| 189592 Return | Deploying a <TestStand Public> directory that contains a custom-format sequence file results in a "Could not open the following sequence files" error If you use a sequence file translator to interpret a custom-format sequence file and save the file in the <TestStand Public> directory, when you build a deployment and include the <TestStand Public> directory, TestStand returns the "Could not open the following sequence files" error. Workaround: N/A
| |||||
| 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. Workaround: To build successfully, exclude the font.ctl file from the _exclsub.llb library in the Distributed Files tab of the TestStand Deployment Utility.
| |||||
| 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.
| |||||
| 181541 Return | The TestStand Deployment Utility selects the wrong file after you modify the destination directory when multiple source files have the same filename If a TestStand workspace contains multiple files with the same filename and you use the Distributed Files tab of the TestStand Deployment Utility to modify the destination directory of one of the files, the deployment utility redraws the view after the edit and might incorrectly re-select one of the other files with the same filename. The edit you made to the destination directory persists correctly, but you need to re-select the correct file to confirm. Workaround: Manually re-select the file for which you modified the destination directory.
| |||||
| 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.
| |||||
| 191976 Return | TestStand Deployment Utility does not properly update TestStand Deployment (TSD) file paths that contain user names when you move the files and a different user loads the TSD file If file paths of a TestStand Deployment (TSD) file, such as the Workspace File Path, contain a user name (User A's Desktop) and you move the files to a path that does not contain the user name (C:\), when a different user loads the TSD file, the TestStand Deployment Utility incorrectly updates the file paths to point to the previous path using the new user name (User B's Desktop) instead of pointing to the correct path (C:\). Workaround: Do not store the files in paths that contain user names, such as Desktop or My Documents. Alternatively, when you move the files from a path that contains user names to a path that does not contain user names, load the TSD file with the same user to correctly update the paths.
| |||||
| 192115 Return | TestStand 4.0 or earlier TestStand Deployment Files configured to install User directory files to the Installation Directory incorrectly map the files to the <TestStand Public> directory when you re-analyze the files in TestStand 4.1 or later TestStand 4.1 introduced a directory restructure to support Windows Vista. In TestStand 4.1, the TestStand User directories were consolidated and moved to the <TestStand Public> directory. If you saved a TestStand Deployment (TSD) file in TestStand 4.0 or earlier and configured the file to install User directory files to a destination other than the User directory on the target computer, when you open the TSD file in TestStand 4.1 or later and re-analyze the source files, the TestStand Deployment Utility maps the destination of the User directory files to the <TestStand Public> directory instead of the destination you previously specified. Workaround: Manually respecify the destination settings for any affected User directory files.
| |||||
| 192254 Return | Destination directories for files you do not select in the TestStand Deployment Utility appear distorted when you convert TestStand Deployment files from an older version of TestStand to a newer version When you load a TestStand Deployment file that was saved in a previous version of TestStand into the TestStand Deployment Utility, the destination directories on the Distributed Files tab appear distorted for files that you have not selected. Workaround: Select and then revert the selection for the file to update the Distributed Files tab with the correct destination directory but leave the file excluded from the deployment.
| |||||
| TestStand Engine | ||||||
| 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:
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).
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 176666 Return | Wait steps configured to wait for a constant time period hang when computer returns from Standby mode If you run a sequence that contains a Wait step configured to wait for a constant amount of time and the computer enters and returns from Standby mode, the Wait step hangs because when the computer returns from Standby mode, Windows resets the counter TestStand queries to determine the current time. Workaround: Restart TestStand.
| |||||
| 177288 Return | Pressing the <Delete> key while editing an attribute value deletes the attribute When you rename or edit the value of an attribute in the Attributes dialog box, pressing the <Delete> key removes the attribute from the attributes list. Workaround: Use the Backspace key to delete characters.
| |||||
| 178238 Return | Windows Vista x64 permissions prevent Call Executable step types from executing on remote computers A permission constraint might exist on some Windows Vista x64 computers that prevents the Call Executable step type from executing steps on a remote computer. Workaround: N/A
| |||||
| 182836 Return | Version Selector does not properly set Microsoft Visual C++ include paths on some non-English operating systems If a non-English operating system localizes the name of the Local Settings or Application Data directories, the TestStand Version Selector does not add TestStand directories to the Microsoft Visual C++ include paths. Workaround: Manually configure the include paths in Visual Studio.
| |||||
| 189417 Return | Closing TestStand can sometimes cause an error when a station global variable contains a reference to an execution Using a Sequence Call step to execute a sequence in a new execution and storing the execution reference in a station global variable causes a race condition that might result in a Microsoft Visual C++ run-time error ("R6025 - pure virtual function call") when you close TestStand. Workaround: To avoid this race condition, you can either store the execution reference in something other than a StationGlobal or you can assign Nothing to the StationGlobal storing the reference when the execution has completed.
| |||||
| 190647 Return | Sequence Call Module tab incorrectly displays an error provider to reload the prototype for Sequence Call steps if the called sequence parameters are passed by value and the sequence file was generated in TestStand 4.0 or earlier When you use TestStand 4.2 to open a sequence file created in TestStand 4.0 or earlier and that sequence file includes a Sequence Call step that calls a sequence file that includes parameters passed by value, the Sequence Call step Module tab in the TestStand Sequence Editor returns an error stating that "The parameters specified by the step do not match the sequence parameters." TestStand can run the step sucessfully if you do not update the prototype. Workaround: Click the error provider to reload the sequence prototype or click the Use Prototype of Sequence checkbox twice.
| |||||
| 193203 Return | An access denied error can occur when TestStand attempts to create a file and a file with the same file path was recently deleted Windows might return an error when you attempt to create a new file with the same file path as a file that was recently deleted. This unexpected failure occurs more frequently on Windows 7 but can also occur on Windows Vista and Windows XP. TestStand 4.2.1 implements workarounds to prevent this failure when generating on-the-fly reports, calling the Engine.GetTempFile method, and creating INI files, such as when creating the TestExec.ini file when launching a TestStand application. Workaround: Ignore the error and retry the failing operation if possible.
| |||||
| 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
| |||||
| 175722 Return | Calling the TestStand API StepType.RemoveSubstep method results in error Calling the StepType.RemoveSubstep method to programmatically remove a substep from a step type results in "Error -17331; Item is locked, protected, or in use and cannot be deleted." Workaround: Use the PropertyObject API instead. For example, to remove the first substep in the list, use the following API call: StepType.AsPropertyObject.GetPropertyObject("Substeps", 0).DeleteElements(0, 1, PropOption_OverrideNotDeletable)
| |||||
| 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.
| |||||
| TestStand Sequence Editor | ||||||
| 102700 Return | Watch View pane displays an incorrect value and icon after fixing the expression that was displaying an error The Watch View pane does not refresh the value and remove the error icon in some cases after you modify the watch expression. Workaround: Single-step or resume the execution.
| |||||
| 104628 Return | Some dynamically defined toolbar items disappear on refresh If you drag a dynamically created submenu item to the TestStand toolbar, the item you added might disappear from the toolbar when you refresh the menu by pressing the <Ctrl> key. Workaround: N/A
| |||||
| 164425 Return | Sequence editor caches Execution windows By default, the 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 caching, the sequence editor process holds on to Windows USER and GDI objects. 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 reuses 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 1000. 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 eight 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, the sequence editor clears the cache and returns a warning message. Workaround: N/A
| |||||
| 164426 Return | Selecting the Show Differences option in the Workspace pane context menu can result in a hang if source code control diff or merge utilities are not installed If you right-click a file on the Workspace pane and select Show Differences from the context menu, the TestStand Sequence Editor might hang if the difference and merge utilities the source control provider specifies are not installed. Workaround: N/A
| |||||
| 164427 Return | Watch expressions that modify objects can cause errors on the Variables pane Using watch expressions that modify the structure of objects, such as deleting subproperties or changing the size of an array, might prevent the Variables pane from refreshing correctly or cause the Variables pane to generate errors. Workaround: Do not use watch expressions that modify the structure of objects.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 51578 47RDI9YL Return | Create Custom Data Type from Cluster dialog box appears multiple times when multiple steps are selected 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. Workaround: Select only one step before you click the button.
| |||||
| 133228 Return | Using the mouse wheel while renaming a step discards any changes When you scroll the mouse wheel while editing the name of a step, TestStand does not save any changes you make. Workaround: Press <Enter> or select another step to accept the changes before you use the mouse wheel.
| |||||
| 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.
| |||||
| 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.
| |||||
| 143199 Return | Watch expression displays ellipses as a value for an expression that was previously not found and becomes valid You can define an expression for a variable that does not exist in a watch expression. If TestStand cannot evaluate the watch expression because a value is not found, but the value later exists, the Value column of the Watch View pane displays ellipses (...) instead of the correct value. Workaround: You must use one of the following methods to force a refresh of the Watch View pane to display the correct value:
| |||||
| 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.
| |||||
| 153495 Return | Syncing files with a Source Code Control system from the TestStand Differ application in the sequence editor returns an error If you try to diff files in the sequence editor with a workspace file open, TestStand prompts you to edit the current files, sync the files with a Source Code Control (SCC) system first, or cancel the operation. If you choose to sync the files first, TestStand returns the following error: "One of more errors have occurred. Please save your work and restart the application." Workaround: Close the Differ application and sync the files before rediffing the files.
| |||||
| 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.
| |||||
| 159800 Return | Loading or saving a workspace with a project that has lots of subdirectories might cause an Out of Memory error When loading or saving a TestStand workspace (.tsw) file that contains a TestStand project (.tpj) file with hundreds of folders or subfolders, the sequence editor might report an Out of Memory error. Workaround: Re-organize your workspace into multiple projects with fewer folders to work around this issue.
| |||||
| 162044 Return | Sequence editor layout files cannot be migrated from earlier versions of TestStand The sequence editor persists layout information in .bin files, which include step list configuration, step pane settings, step module pane configuration settings, pane docking states, toolbar positions, and toolbar customizations. Although you can load sequence editor .bin files from previous versions of TestStand with the current version, some settings such as toolbar and pane docking settings do not load. Workaround: Re-customize the sequence editor with the options that were lost.
| |||||
| 173800 Return | Sequence editor does not launch if user does not have read permissions to registry keys If a user does not have Read permissions to the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\USERProcessHandleQuota, or if the registry keys do not exist, the TestStand Sequence Editor fails to launch and returns the error "An error occurred while initializing. You might be trying to run a sequence editor which is incompatible with the currently registered engine. This is not supported. You can use the TestStand Version Selector to change the active TestStand engine version if you have more than one version of TestStand installed." This issue does not affect custom TestStand User Interfaces. Workaround: Create the two registry keys if necessary and enable Read permissions for the user.
| |||||
| 180479 Return | A corrupted layout_current.bin file causes the sequence editor to crash and return an error similar to "No assembly ID for object type... " A corrupted layout_current.bin file causes the sequence editor to crash and return an error similar to "No assembly ID for object type... ". Uninstalling and re-installing TestStand does not correct the behavior. You must delete or rename the layout_current.bin file located in the C:\Documents and Settings\<user name>\Local Settings\Application Data\National Instruments\TestStand x.x directory to resolve this issue. Workaround: Delete or rename the layout_current.bin file located in Documents and Settings\<user name>\Local Settings\Application Data\National Instruments\TestStand x.x
| |||||
| 191643 Return | Selecting an Express VI step in a sequence of a deployed sequence in the Sequence Editor incorrectly deletes the deployed wrapper VI from the <SupportVIs> directory When a LabVIEW step calls an Express VI, TestStand embeds a wrapper VI in the step. When you deploy a sequence file that contains a step that calls an Express VI, the TestStand Deployment Utility extracts the embedded wrapper VI, saves the wrapper VI in a source distribution in the <SupportVIs> directory, and updates the VI Path for the step to call the wrapper VI. If you open the deployed sequence file in the TestStand Sequence Editor, selecting the step incorrectly deletes the wrapper VI from the <SupportVIs> directory when the LabVIEW module pane updates, which breaks the step and causes the error provider to display a "Could not find file" message on the Module pane the next time you reselect the step. Workaround: N/A
| |||||
| 189663 Return | TestStand Sequence Editor returns an error message when you configure a LabVIEW code module to "Always Run VI in LabVIEW Run-Time Engine" and you configure the LabVIEW Adapter to use a different version of the run-time engine When you configure a LabVIEW code module step to "Always Run VI in LabVIEW Run-Time Engine" in the LabVIEW Advanced Settings dialog box and you set the LabVIEW Adapter to use a different version of the LabVIEW Run-Time Engine, when you select the step in the TestStand Sequence Editor, TestStand returns an error message that states that the LabVIEW code module could not be loaded because it was compiled with a different version of the LabVIEW Run-Time Engine than the one selected in the LabVIEW Adapter Configuration dialog box. This edit-time error does not affect the execution of the sequence. Workaround: You can ignore the error message because TestStand uses the appropriate LabVIEW Run-Time Engine to call the LabVIEW code module at execution time.
| |||||
| 51939 49O5JI9Q Return | TestStand Sequence Editor seems to hang when launching the Customize Toolbar dialog box after changing the number of monitors in the system The Customize Toolbar dialog box is a modal dialog box. If you configured a system to use multiple monitors, opened the Customize Toolbar dialog box, then moved the dialog box to a secondary monitor screen before closing the dialog box, when you remove the additional monitor(s) from the system, the TestStand Sequence Editor appears to hang the next time the Customize Toolbar dialog box launches. This occurs because the Customize Toolbar dialog box tries to display on a monitor that no longer exists in the system. Workaround: If you experience this apparent hang, press the <Enter> key to close the modal Customize Toolbar dialog box. Configure the system to use multiple monitors, launch the Customize Toolbar dialog box, move the dialog box to the primary monitor, and then close the dialog box. If you remove the additional monitor(s) from the system, subsequent launches of the Customize Toolbar dialog box display the dialog box on the primary monitor.
| |||||
| TestStand User Interface (UI) Controls | ||||||
| 127509 Return | Application Manager control might hang if TestStand is not licensed If you do not activate TestStand properly, the Application Manager control can hang after you call the Start method. Workaround: N/A
| |||||
| 50235 43FETR00 Return | Cannot navigate to adapter buttons with the keyboard within the InsertionPalette control You cannot use the keyboard to navigate to the adapter buttons within the InsertionPalette control for non-.NET applications. Workaround: N/A
| |||||
| 50418 44CB5HGH Return | SequenceView and ListBar controls can leak memory The SequenceView and ListBar controls can leak memory when you quickly launch and dismiss the context menu multiple times. Workaround: N/A
| |||||
| 50421 44BDJQRA Return | VariablesView control can leak a Windows USER object The VariablesView control can leak a Windows USER object when you use the keyboard to change a Boolean value. Workaround: N/A
| |||||
| 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
| |||||
| 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.
| |||||
| 191243 Return | Attributes are read only in the Variables pane of an execution In the Variables pane of an execution, when you pause the execution, you can edit the value, comment, flags, and numeric format (for numeric properties) of a variable, but you cannot edit the attributes of the variable. Workaround: N/A
| |||||
| 193358 Return | Button controls truncate multibyte character strings TestStand ActiveX User Interface Button controls truncate multibyte character strings on multibyte operating systems. Workaround: Append additional space characters to the end of the button text when running on a multibyte OS.
| |||||
| 197369 Return | Typing the "]" character incorrectly autosizes columns for some non-English operating systems If the default keyboard mapping of a non-English operating system requires you to press the <AltGr> + <+> keys to type the "]" character, using this key combination for code module parameters or properties in the VariablesView control autosizes the columns instead of entering the "]" character. The <AltGr> + <+> key combination for a default keyboard mapping of a non-English operating system corresponds to the <Ctrl+Alt> + <+> key combination for the default keyboard mapping of English operating systems. <Ctrl+Alt> + <+> corresponds to a keyboard shortcut for autosizing the columns of code module parameters and the columns in the VariablesView control. Workaround: You can open the Expression Browser and press the <AltGr> + <+> keys to enter the "]" character, or you can press the <Alt+93> keys on the number pad of the keyboard.
| |||||
| 199119 Return | Clicking a step icon deselects all other selected steps If you select multiple steps to move within a sequence or to move from one sequence to another sequence, clicking a step icon deselects all the other selected steps. This behavior does not occur if you click anywhere else in the highlighted region. Workaround: Hold or key when clicking, or click any part of the highlighted region other than a step icon to drag and drop a collection of steps.
| |||||
| 52249 4ADBS5B8 Return | ActiveX controls located within user controls, such as tabs or panels, on a .NET form might disappear A known issue with ActiveX controls in the .NET Designer results in the disappearance of ActiveX controls. This behavior might occur at edit time when you move ActiveX controls into or out of the user control, or it might occur at run time when you programmatically create or move ActiveX controls within the user control. Workaround: If the ActiveX controls disappear in the .NET Designer at edit time, close and reopen the form. If the ActiveX controls disappear at run time, override the OnCreateControl event to call the Hide and Show methods on each ActiveX control.
| |||||
| User Interfaces | ||||||
| 164433 Return | TestStand MFC user interface might leak GDI objects when creating and destroying child windows on Windows XP SP2 MFC-based applications, such as TestStand User Interfaces, might leak GDI objects on computers that run Windows XP SP2 when the applications create and destroy child windows. Windows XP SP3 fixes this issue. Workaround: Refer to the Microsoft Knowledge Base article 319740, located at http://support.microsoft.com/kb/319740, for information about how to resolve this known Microsoft issue.
| |||||
| 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.
| |||||
| Visual Studio 2008 - Documentation | ||||||
| 192052 Return | Installing Measurement Studio and TestStand 4.2 on a machine with Visual Studio 2008 can cause help topics to disappear. If you install TestStand 4.2 first and then Measurement Studio, the TestStand 4.2 help will be removed from the Visual Studio Table of Contents. If you install Measurement Studio first, and then TestStand 4.2, the Measurement Studio help will be removed from the Visual Studio Table of Contents. Workaround: You must remerge the help to fix this. To remerge the help do the following:
| |||||
Document last updated on 12/11/2009