Print
PDFOverview
This document contains the TestStand 2012 known issues
that were discovered before and since the release of
TestStand 2012. 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.
Each Issue appears as a row in the table and
includes these fields:
- Issue ID - the number at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
- Legacy ID (optional) - If an issue has a legacy ID from NI's legacy/deprecated bug reporting database, you will see it appear on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
- Issue Title: in italics - it describes the issue in one sentence or less
- Problem Description - a few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
- Workaround - possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
- Reported Version - the earliest version of TestStand the issue was reported in. If you discover the issue appears in an earlier version of TestStand than is reported in this field, you can report that to NI (contact information below) to have the field updated.
- Resolved Version - version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
- Date Added - the date the issue was added to the document
(not necessarily the reported date)
Document Organization:
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.
Contacting NI
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. Visit the NI Website to contact us. 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.
Known Issues by Category
The following items are known issues in TestStand 2012 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| .NET Adapter | ||||||
| 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
|
|||||
| 359373 Return |
You cannot close the Type Properties dialog box after you rapidly click the Specify Module button on the Substeps tab When you use the Substeps tab of the Type Properties dialog box to configure the substeps for a custom step type, clicking the Specify Module button multiple times before the Specify Module dialog box appears prevents you from closing the Type Properties dialog box. This issue occurs with .NET substeps in TestStand 2010 SP1 and with .NET and LabVIEW substeps in TestStand 2012. Workaround: To recover from this state, you must terminate the TestStand process using the Windows Task Manager facility. To prevent the behavior, ensure that you do not click the Specify Module button multiple times.
|
|||||
| 354252 Return |
An error can occur when you simultaneously modify the invocations of multiple .NET code modules If you select two or more .NET steps that use the same assembly and class and you then modify the calls within the .NET Invocation control on the .NET Module tab, an error similar to the following error can occur: Array offset 2 is out of range; range is 0..1 This error is more likely to occur if the invocations of the two selected steps specify a different number of calls.Workaround: Modify the invocations of .NET steps individually.
|
|||||
| 356096 Return |
An unhandled .NET error can occur when you use the /quit command-line flag to close TestStandAn unhandled .NET error can occur when TestStand exits and the following conditions are true:
Workaround: You can safely ignore this error. To prevent the error from displaying, disable just-in-time debugging in Visual Studio.
|
|||||
| 356700 Return |
Closing Microsoft Visual Studio after you debug .NET code from TestStand prevents Visual Studio process from exiting After you use Visual Studio to debug .NET code modules in TestStand, closing Visual Studio ends the TestStand process but does not end the VSdebugController process used to debug .NET code. If you launch TestStand again and attempt to debug .NET steps, you might receive the Error Code: -17502; System Level Exception error.Workaround: If you encounter this error, use the Windows Task Manager facility to terminate the VSdebugController process before you run the sequence. To prevent the error, ensure that you close TestStand instead of Visual Studio to correctly end the Visual Studio and the VSdebugController processes.
|
|||||
| 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.
|
|||||
| 255602 Return |
C/C++ DLL Adapter Create and Edit Code features return errors for functions that specify an array parameter The C/C++ DLL Adapter Create and Edit Code features return errors for functions that specify an array parameter. In the Create Code case, Visual Studio correctly launches and creates the new function, but TestStand is unable to find the function and returns an error. In the Edit Code case, TestStand returns an error. Workaround: You can ignore the error. In the Edit Code case, navigate to the function manually.
|
|||||
| 297248 Return |
The Log option in the Parameters Table for complex number parameters in C/C++ DLL steps can behave erratically If you configure a C/C++ DLL step and you add a CNiComplex or CNiComplexVector parameter, configuring the Log option in the Parameters Table for the real and imaginary components causes the logging behavior for the container or the components to change in an unexpected way. TestStand does not support logging only the real or imaginary portion of a complex number, and logging should be non-editable for the components. Workaround: Only enable the Log option for the complex number container and not the real or imaginary components.
|
|||||
| Database | ||||||
| 359126 Return |
Memory usage can increase when you use the SQL Server Stored Proc schema with the Microsoft OLE DB Provider for SQL Server Memory usage can increase when using the SQL Server Stored Proc schema and the database connection string uses the Microsoft OLE DB Provider for SQL Server. The memory usage appears to oscillate but shows growth over time. Workaround: Use the Microsoft SQL Native Client database provider to avoid this issue.
|
|||||
| 357315 Return |
An error can occur when you log binary data to an Oracle database You might encounter the following error when you log binary data to an Oracle database: An error occurred calling 'LogResults' in 'ITSDBLog' of 'zNI TestStand Database Logging'The error appears when all of the following conditions are true:
|
|||||
| 314113 Return |
An SQL Statement step returns an incorrect number of records selected when you calling a Microsoft SQL stored procedure When you call a Microsoft SQL stored procedure in an SQL Statement step, the Number of Records Selected parameter always returns -1. This behavior does not occur with other database providers, such as mySQL.Workaround: N/A
|
|||||
| Documentation | ||||||
| 365966 Return |
Help file index and search results do not display TSFundamentals.chm topicsUsing the index or search functionality in the TestStand 2012 version of the NI TestStand Help to find topics contained in the NI TestStand Fundamentals Help (located at <TestStand>\Doc\Help\TSFundamentals.chm) does not yield any results. The TestStand 2012 SP1 version of the NI TestStand Help fixes this issue.Workaround: Refer to the KnowledgeBase 609B37UB to fix this issue.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 360674 Return |
Measurement & Automation Explorer can display incorrect installed versions after uninstalling TestStand 2012 If you have both TestStand 2010 (not TestStand 2010 SP1) or earlier and TestStand 2012 installed, and then you uninstall TestStand 2012, the software section of Measurement & Automation Explorer (MAX) incorrectly indicates that TestStand 2012 is installed and TestStand 2010 or earlier is not installed. Workaround: You can safely ignore this issue, or you can fix the behavior by running a repair installation of TestStand 2010 or earlier.
|
|||||
| 361582 Return |
TestStand Version Selector incorrectly displays TestStand 2012 as an available version to activate after you uninstall TestStand 2012 The TestStand Version Selector incorrectly allows you to select TestStand 2012 in the Installed TestStand Versions combo box after you uninstall TestStand 2012. Workaround: You can fix this behavior by running a repair installation of an earlier version of TestStand that is also installed.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 158938 Return |
Cannot pass struct containing an array of structs into a DLL built with LabVIEW You can call a DLL built with LabVIEW using the C/C++ DLL Adapter in TestStand. However, for parameters that are structs containing an array of structs, TestStand does not allocate the memory properly, resulting in a TestStand Error: -17502 System Level Exception error. Workaround: You can pass arrays of numbers, arrays of strings, or individual clusters as parameters to a DLL built with LabVIEW.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 245655 Return |
Cannot call VIs from LabVIEW packed project libraries when the full path of the VI is longer than the maximum path length When you configure TestStand to call a VI from a LabVIEW packed project library and the full path of the VI is longer than the maximum path length, TestStand does not find the file or reports that the VI is an unexpected type. Workaround: Ensure that the full path of the VI you call is shorter than the maximum path length.
|
|||||
| 254553 Return |
TestStand might become unresponsive while LabVIEW launches a prompt to save a VI If you attempt to create or edit a VI from TestStand while the LabVIEW Development Environment launches a prompt to save a VI, TestStand might become unresponsive. Workaround: Close the LabVIEW dialog box to make TestStand responsive again.
|
|||||
| 279822 Return |
TestStand appears to hang when LabVIEW search dialog box does not come to front when browsing for a VI that is missing subVIs The LabVIEW search dialog box is not modal to a TestStand User Interface, so When you browse for a VI that is missing one or more subVIs, a maximized TestStand User Interface hides the LabVIEW search dialog box, and it appears that TestStand has hung and become unresponsive. Workaround: Minimize the TestStand User Interface window or make LabVIEW active to bring the LabVIEW search dialog box or open file dialog box to the front.
|
|||||
| 359373 Return |
You cannot close the Type Properties dialog box after you rapidly click the Specify Module button on the Substeps tab When you use the Substeps tab of the Type Properties dialog box to configure the substeps for a custom step type, clicking the Specify Module button multiple times before the Specify Module dialog box appears prevents you from closing the Type Properties dialog box. This issue occurs with .NET substeps in TestStand 2010 SP1 and with .NET and LabVIEW substeps in TestStand 2012. Workaround: To recover from this state, you must terminate the TestStand process using the Windows Task Manager facility. To prevent the behavior, ensure that you do not click the Specify Module button multiple times.
|
|||||
| 360969 Return |
An Index was out of range error occurs after you select certain parameters and then select another stepSelecting certain parameters in the Parameters Table and then selecting another step can put TestStand in a bad state. This issue can occur if you complete the following steps at edit time.
Error occurred while trying to refresh edit panel "SeqEdit.ba": Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index After you dismiss the error, the error continues to occur for any LabVIEW step you select until you restart TestStand.Workaround: Select a parameter in the Parameters Table of a newly selected step if you notice that multiple parameters are highlighted.
|
|||||
| 361649 Return |
LabVIEW code modules with a TDMS file reference in the connector pane can cause a generic error If you use a LabVIEW code module in a sequence that passes TDMS file references in or out of the VI, TestStand might return the following error: Error loading step '<name of step>' of sequence '<name of sequence>' in file '<name of sequence file>'. Failed to load VI <path of VI> in the 'LabVIEW Development System' version '11.0'. LabVIEW: Generic error. Error Code: -18002, LabVIEW reported an error. See 'LabVIEW: ' message for more details. Source: 'TSAPI'Workaround: You can prevent this issue by adding additional controls or indicators to the connector pane of the VI.
|
|||||
| 217346 Return |
Changing the size of a two-dimensional array in a LabVIEW code module can cause TestStand to crash If you resize a two-dimensional array in a LabVIEW code module when all of the following conditions are true, TestStand might behave unexpectedly or crash when you click the Reload Prototype button.
|
|||||
| 363405 Return |
TestStand incorrectly assigns timestamp data passed from and to a LabVIEW code module If a LabVIEW code module passes a timestamp as an output parameter to a string property, TestStand removes leading zeroes in the fractional seconds field. For example, the timestamp 01:35:45.005 is assigned to a string property as 01:35:45.5 in TestStand. If you pass a string timestamp value from TestStand to a timestamp in LabVIEW, TestStand adds leading zeroes to create the fractional field. For example, the string 01:35:45.5 is assigned as 01:35:45.005 in LabVIEW. However, if TestStand receives a timestamp value as an output parameter and passes the value back to LabVIEW as an input parameter, the correct value is maintained.Workaround: Convert the timestamp to string data before passing it between LabVIEW and TestStand. You can convert the timestamp to a string with the desired format using the Format Date/Time String VI on the Timing palette.
|
|||||
| 303452 Return |
Logging reference parameters in a LabVIEW step can cause an error If you call a LabVIEW code module that meets all of the following conditions, TestStand returns the Type of argument expression is incompatible with parameter. Expected Number, found Object Reference. [Error Code: -17313, Could not accept the parameter passed in.] error when the step executes:
Workaround: Specify a value or disable logging for the parameters.
|
|||||
| 339699 Return |
TestStand cannot find VIs in a packed project library that specifies a file path that includes multibyte characters On operating systems for languages that require multibyte support (such as Chinese versions of Windows), TestStand cannot find VIs in a packed project library that specifies a file path that includes multibyte characters. Workaround: Ensure that the path for the packed project library does not contain multibyte characters.
|
|||||
| 364787 Return |
TestStand cannot find VIs in a packed project library that specifies a file path that includes multibyte characters On operating systems for languages that require multibyte support (such as Chinese versions of Windows), TestStand cannot find VIs in a packed project library that specifies a file path that includes multibyte characters. Workaround: Ensure that the path for the packed project library does not contain multibyte characters.
|
|||||
| LabWindows/CVI | ||||||
| 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.
|
|||||
| 317729 Return |
Changes to enumeration values in LabWindows/CVI code modules are not reflected in steps that call the code modules If you call a LabWindows/CVI code module that has an enumeration as an input parameter, TestStand displays the enumeration constant names in the Parameters Table. The step data stores the value this constant represents. If you make a change to the value associated with an enumeration constant in the code module, steps that use the enumeration do not reflect this change and continue to use the previous value for the enumeration constant. Workaround: Recreate any steps that use the enumeration after you make any changes to the values of enumeration constants you have already defined.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 250286 Return |
devenv.exe process continues to run after you close Microsoft Visual Studio 2010 using the close (X) button Devenv.exe process continues to run after you close Visual Studio 2010 using the close (X) button if TestStand launched the application when you clicked the Step Into button on the Debug toolbar in the sequence editor. Workaround: Stop debugging before you close Visual Studio, select File>Exit to close Visual Studio, manually attach Visual Studio to TestStand before you perform the Step Into operation, or manually close the devenv.exe process using the Microsoft Windows Task Manager.
|
|||||
| 287170 Return |
You might receive Error 1 "Interop Type Cannot Be Embedded" when referencing the TestStand API in Visual Studio 2010 Refer to the National Instruments KnowledgeBase article 5LQFBDUB, Error 1 "Interop Type Cannot Be Embedded" When Referencing the TestStand API in a New Visual Studio 2010 Project that Targets the .NET 4.0 Framework, located at http://digital.ni.com/public.nsf/allkb/4EA929B78B5718238625789D0071F307, for more information about this issue. Workaround: Refer to the National Instruments KnowledgeBase article 5LQFBDUB, Error 1 "Interop Type Cannot Be Embedded" When Referencing the TestStand API in a New Visual Studio 2010 Project that Targets the .NET 4.0 Framework, located at http://digital.ni.com/public.nsf/allkb/4EA929B78B5718238625789D0071F307, for information about workarounds for this issue.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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 |
Property Object leak occurs when calling a remote sequence that errors When you enable the Report Object Leaks options in the Debug Options dialog box that you access from the Preferences tab of the Station Options dialog box, TestStand property objects leak if you call a remote sequence and a run-time error occurred because you passed extra parameters to the sequence. Workaround: N/A
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 130730 Return |
Property Loader step results in error -17304 when attempting to read a Unicode file TestStand returns the following run-time error if you configure the Property Loader step to read a Unicode file: "Error -17304; Unrecognized value. Cound not find the start of data marker in the limit file." The Import/Export Properties tool also returns an error when you attempt to read from or write to an existing Unicode file. Workaround: N/A
|
|||||
| 205554 Return |
Microsoft Windows 7 Most Recently Used (MRU) list for pinned TestStand application includes all files opened with the Open File dialog box When you pin a TestStand application, such as the sequence editor or a user interface, to the Taskbar in Windows 7, the MRU list includes any files you opened with the Open File dialog box in the application. Workaround: N/A
|
|||||
| 213835 Return |
Using foreign characters in XML report style sheets might result in errors during report generation Using some foreign characters in the XML report style sheets might result in the error "An invalid character was found in text content." Workaround: Use the HTML code equivalent for the foreign character or add the appropriate encoding attribute to the <xsl:output> tag of the style sheet.
|
|||||
| 216539 Return |
Using the Property Loader step to import two or more step properties with the same name but different type or representation results in a type mistmatch error If a sequence contains 2 or more steps that contain a property with the same name but different type or representation and you use the Property Loader step to import the property, TestStand returns a type mismatch error because TestStand sets the expected type and representation of the property to the type and representation of the property found in the first step in the sequence. Workaround: N/A
|
|||||
| 301259 Return |
TestStand 2010 SP1 Migration Utility does not support redirecting paths that exist within a string when the string is not a valid path The TestStand 2010 SP1 Migration Utility does not support redirecting paths that exist within a string when the string is not a full or valid path. For example, the migration utility does not redirect the path C:\Program Files\National Instruments\TestStand 2010 in the string "foo C:\Program Files\National Instruments\TestStand 2010". Workaround: N/A
|
|||||
| 35026 47LCM4G0 Return |
On-the-fly database logging leaks memory when an execution repeatedly creates new threads On-the-fly database logging slowly leaks memory when executions repeatedly use a Sequence Call step to create new threads. Workaround: N/A
|
|||||
| 360245 Return |
The TestStand Sequence Analyzer does not honor code module load and unload settings When analyzing a sequence file, the TestStand Sequence Analyzer loads code modules as part of the analysis process. However, the analyzer does not honor any load or unload options for the code modules. Instead, the analyzer preloads all code modules before analysis and does not unload them after analysis completes. This can cause an error in the following scenarios:
Workaround: You can avoid the second scenario by disabling the Analyze File Before Executing option in the Sequence Analyzer Options dialog box. If you analyze the sequence manually, be sure to select File»Unload All Modules before executing.
|
|||||
| 360808 Return |
Errors exist in the Parallel Execution, Property Loader, and Dynamic Client Sequence File example programs that ship with TestStand Refer to the following National Instruments support documents for more information about the errors in the Parallel Execution, Property Loader, and Dynamic Client Sequence File example programs that ship with TestStand: Workaround: N/A
|
|||||
| 363354 Return |
The TestStand Sequence Analyzer reports an internal error when analyzing expressions with an incorrectly indexed array If you analyze a sequence that contains an expression that references an array with the incorrect number of indexes, such as the expression array[0] for a two-dimensional array, the sequence analyzer reports the Internal Error: Fatal error occurred during analysis error.Workaround: Correct any expressions with incorrectly indexed arrays.
|
|||||
| 363524 Return |
The += operator might not function correctly for appending elements to an arrayWhen you use the += operator to append to an array, TestStand might not correctly set the parent of the added elements, which can cause errors when you attempt to access or delete the elements. This behavior occurs when the following conditions are true:
Locals.myArray += {Locals.myNumber}.Workaround: To append an element to an array, use the SetNumElements expression to increase the size, and then set the newly created element to the desired value, as shown in the following example expression: SetNumElements(Locals.myArray, GetNumElements(FileGlobals.DynamicArray) + 1), Locals.myArray[GetNumElements(Locals.myArray) - 1] = Locals.DemoStructure
|
|||||
| 312695 Return |
The Tcl example step might return error -14004 when executed from TestStand Refer to the National Instruments KnowledgeBase article, http://digital.ni.com/public.nsf/allkb/120923C96FEBBDA6862579910074AB9F?OpenDocument, for more information about this error. Workaround: N/A
|
|||||
| 345032 Return |
TestStand cannot save a TestStand Sequence Analyzer project file if the file specifies the Hidden attribute in the Windows file system If you attempt to save an existing sequence analyzer project file, TestStand displays a access denied error if the file specifies the Hidden attribute in the Windows file system.Workaround: Ensure that the sequence analyzer project file does not specify the Hidden attribute in the Windows file system when you save the project file.
|
|||||
| 348612 Return |
A warning can appear when you first launch TestStand after you use the TestStand Migration Utility After using the migration utility to migrate settings to a newer version of TestStand, TestStand might display the Toolbar data out of date in file: C:\Users\Username\AppData\Local\National Instruments\TestStand 2012\layout_current.bin error when you first launch TestStand. After you dismiss the warning, TestStand launches with the correct imported layout despite the warning.Workaround: To avoid this warning, deselect layout_current.bin when you use the migration utility. If you do encounter the warning, you can safely ignore it.
|
|||||
| Reports | ||||||
| 358354 Return |
The offline results processing utility can crash if launched while another instance of the utility is closing If you launch the offline results processing utility while another instance of the utility is closing, the new instance of the utility might crash. Workaround: Launch the offline results processing utility again.
|
|||||
| 206892 Return |
Enabling the Log option in the VI Parameter Table does not log LabVIEW analog waveform parameters If a LabVIEW code module specifies an analog waveform output parameter, enabling the Log option in the VI Parameter Table does not log the parameter if you do not provide an argument in the Value column of the VI Parameter Table. Workaround: Ensure that any waveform parameters for which you enable the Log option also specify an argument in the Value column.
|
|||||
| 357691 Return |
ATML reports generated on non-English operating systems contain an improperly formatted start date The ATML Test Results and Session Information schema requires that timestamps use the yyyy-mm-ddThh:mm:ss format. On a computer with a non-English operating system, the localized date is not properly converted to the English format the ATML Test Results and Session Information schema requires.Workaround: Modify the ATML style sheet you are using to correctly display the start date.
|
|||||
| 358127 Return |
An error can occur when generating an On-The-Fly report when a sequence call uses a new thread and executes a post action The Error -17500: Operation Failed error can occur when you run a sequence in which all of the following conditions are true:
|
|||||
| 224640 Return |
Terminated subsequences called in a new execution have a status of Passed If you call a sequence and select the Use New Execution execution option on the Sequence Call Module tab, you can obtain the results of the called sequence by using a Wait step. However, if the called sequence execution is terminated, the Wait step reports the sequence result as Passed instead of Terminated. Workaround: N/A
|
|||||
| 322859 Return |
The TS.StartTime property is incorrect when used with remote instances of the TestStand EngineThe TS.StartTime property in the ResultList array contains the time in seconds since the creation of the TestStand Engine. However, when you execute steps in a remote instance of the TestStand Engine, this property uses the creation time of the remote engine rather than the local engine, which can cause calculations of absolute time to be incorrect if the calculation is based on the engine creation time obtained from the Seconds() function.Workaround: N/A
|
|||||
| 347289 Return |
XML reports might display an incorrect number of results and incorrect failure chain information When you generate a XML report and do not use on-the-fly report generation, the Number of Results value and the failure chain information can be incorrect if the sequence file uses Engine callbacks. The report includes the steps in these callbacks in the Number of Results value but does not include the results for the steps in the report. In addition, the failure chain in the report might also incorrectly contain references to steps in the Engine callbacks. Workaround: Enable on-the-fly reporting for the XML report, or use a different report format.
|
|||||
| 347733 Return |
The TestStand Offline Results Processing Utility loads slowly when the inbox or outbox contains a large number of files If the inbox or outbox of the offline results processing utility contains 50,000 or more files, the utility can appear unresponsive and slow. The severity of the problem increases as the number of files increases. Workaround: If the inbox contains a large number of files, allow the utility time to process the files or move the files to another location on disk. If the outbox contains a large number of files, move the files to another location on disk.
|
|||||
| 347941 Return |
The offline results processing utility does not reload modified result processing plug-in files If you make changes to a result processing plug-in while the offline results processing utility is open and the utility loaded the plug-in before you made the change, the utility does not reload the new version of the file. Workaround: Close and reopen the offline results processing utility to load the most recent version of the plug-in.
|
|||||
| 348820 Return |
The offline results processing utility can hang when you use a result processing plug-in that causes a run-time error If you use a result processing plug-in that causes a run-time error in the PreBatch callback with the offline results processing utility, the utility appears to hang with no indication that an error has occurred. Workaround: Process the TestStand result file ( .tsr) directly from the TestStand Sequence Editor. TestStand displays the standard run-time error dialog box to help you debug the plug-in.
|
|||||
| TestStand Deployment Utility | ||||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 252650 Return |
July 29, 2012TestStand Deployment Utility does not update the workspace path if you save the deployment and workspace files to the desktop then move the files When you save workspace and deployment files on the desktop, move the files to a new location, and then load the deployment file in the TestStand Deployment Utility, the Workspace Path control expects the workspace file to be located in the Desktop directory. Workaround: Browse to the new workspace file location.
|
|||||
| 276342 Return |
TestStand Deployment Utility fails when you build a Packed Project Library with source if a project with the same path is already in memory The TestStand Deployment Utility incorrectly returns the following error: "Internal error code 1357 Processing VIs... Could not process LabVIEW VIs. Fix any broken VIs before rebuilding." when you build a Packed Project Library and include the source files when a project with the same path is already in memory. Workaround: Close LabVIEW to remove all projects from memory and build the deployment again.
|
|||||
| 277891 Return |
TestStand Deployment Utility returns an error when building if the TestStand directory and its VIs do not exist in the vi.lib\addons directory If the TestStand directory and its contents does not exist in the vi.lib\addons directory of the current LabVIEW version, the TestStand Deployment Utility returns the following error when building a deployment that includes LabVIEW files: "Error: Unable to find all subVIs from saved VIs. Either a subVI is missing or the VI is not saved in the current LabVIEW version." Workaround: If the error lists a call chain that includes the "TestStand - Deployment Utility Splash Screen.vi", close TestStand and the deployment utility and use the TestStand Version Selector to make that version of TestStand active again. Check the vi.lib\addons directory of the current version of LabVIEW to ensure that the TestStand directory exists before attempting to build the deployment again.
|
|||||
| 249171 Return |
A warning can occur when you build a deployment that includes VIs that contain unsupported Microsoft Windows characters If a deployment contains VIs that use characters that are not valid for Microsoft Windows files, such as the slash ( /) or question mark (?) character, and you enable the Output VIs to Packed Project Library option in the LabVIEW VI Options dialog box, the TestStand Deployment Utility returns a warning similar to the following warning when building the deployment: Warning: Cannot update VI Path: Step '<stepName>', sequence '<sequenceName>', sequence file '<sequenceFilePath>' If you install the deployment on a target computer, the step the warning references does not not execute. This issue occurs because the paths for VIs contained within a packed project library must use only valid Windows filename characters, which is not the case for VIs within LLBs or LabVIEW libraries.Workaround: Use only valid Windows filename characters when naming VIs and virtual folders.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 207535 Return |
Using the RunEntryPoint command-line argument returns an error when the entry point you specify is defined in the process model associated with the sequence file but not in the station model Using the RunEntryPoint command-line argument returns an error when the entry point you specify is defined in the process model associated with the sequence file but not in the station model. Workaround: Change the station model to the process model that defines the entry point you want to use.
|
|||||
| 232693 Return |
Batch synchronization behaves incorrectly when you set a SequenceCall step and the steps within the subsequence to serial batch synchronization When you configure a SequenceCall step for serial batch synchronization and also configure the steps of the subsequence for serial batch synchronization, the execution behaves unexpectedly when the steps the subsequence calls include a For Loop. Workaround: Configure batch synchronization only for the SequenceCall step or only for the steps the subsequence calls. Do not configure batch synchronization for both.
|
|||||
| 248782 Return |
Custom type container becomes incompatible with its own type when you use a field of the custom type container as the current element of a For Each loop When you use a field of a custom type container as the current element of a For Each loop and then attempt to assign the custom type container to a container of the same type, TestStand returns the following run-time error: "Variable or property types do not match or are not compatible." Workaround: N/A
|
|||||
| 250674 Return |
Making the return value of the PropertyObject.GetValVariant method a 64-bit integer causes an edit-time error The TestStand Sequence Analyzer returns an edit-time error when you make the return value of the PropertyObject.GetValVariant method a 64-bit integer. However, the sequence executes successfully. Workaround: You can ignore this error.
|
|||||
| 250700 Return |
Message Popup step leaks memory when you enable Display Image or Web Page option The Message Popup step leaks memory when you enable the Display Image or Web Page option and the file is not a .ico or .bmp file. Workaround: N/A
|
|||||
| 254341 Return |
Creating an attribute for a parameter of a substep code module results in an error When you specify the module for a substep and attempt to create an attribute for a parameter of the code module, the Attributes dialog box returns the "One or more errors have occurred. Please save your work and restart the application." error. This behavior does not occur for substeps that use the .NET Adapter. Workaround: Do not edit or create attributes for parameters of substep modules.
|
|||||
| 298378 Return |
TestStand Engine File dialog box does not display correctly and is unusable when you set the font size to 150% DPI on Windows 7 On Windows 7, when you set the font size to 150% DPI, the OK, Cancel, and Help buttons, the File Name field, and the Files of Type filter are not visible in the TestStand Engine File dialog box. Workaround: Use a font size up to 125% DPI.
|
|||||
| 306233 Return |
Disabling the Edit Module Prototype option for a step type might not restrict changes to the module of a step instance Disabling the Edit Module Prototype option on the Disable Properties tab of the Type Properties dialog box for a step type does not restrict you from making changes to the module of a step instance if you configured the step to use the LabVIEW, .NET, or ActiveX/COM Adapter. Workaround: N/A
|
|||||
| 359021 Return |
The PropertyObject.CreateReportSection method does not function properly with default input values The PropertyObject.CreateReportSection method returns an error if you do not directly specify the Format parameter. This behavior occurs because the default value of this parameter is an empty string, but the only supported value is XML.Workaround: Ensure that you pass the value XML for the Format parameter. You can pass an empty string for the DefaultName and FormatSting parameters to specify their default values.
|
|||||
| 359900 Return |
An error occurs when you select multiple Sequence Call steps and the steps have different values for CanEditModulePrototype setting TestStand returns the Error occurred while trying to refresh edit panel 'SeqEdit.y': Object Reference not set to an instance of an object. error when all of the following conditions are true:
Workaround: To prevent the error, do not enable the Edit Module Prototype option for any custom step types that can potentially use the Sequence Adapter.
|
|||||
| 360098 Return |
The Sequence.GetEffectiveType method returns incorrect values when called from a running sequence The Sequence.GetEffectiveType method always returns the value 0 when called using a reference to a running copy of a sequence, such as the RunState.Sequence.GetEffectiveType() call.Workaround: Call the method on the edit copy of the sequence to obtain the correct value, such as RunState.SequenceFile.Data.Seq["MainSequence"].GetEffectiveType().
|
|||||
| 360746 Return |
A type conflict can occur when you save a sequence file after you change the station model A type conflict can occur when you save a sequence file after you complete the following steps.
Failed to save sequence file '<sequenceFilePath>'. Type '<typeName>' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the files with conflicting types in the Sequence Editor, resolve the conflicts and resave the updated files.Workaround: To prevent this behavior, save any new sequence files before changing the station model.
|
|||||
| 360941 Return |
Using the Find/Replace dialog box can modify locked types If you use the Replace operation in the Find/Replace dialog box to change the value of a property within a locked type, TestStand makes the change without prompting for the password for the locked type. Workaround: N/A
|
|||||
| 361039 Return |
Terminating a remote Call Executable step might cause a system-level error When you configure a Call Executable step to run the executable on a remote computer, terminating the step might cause the -17502; System Level Exception error. TestStand reports this error only when you configure the standard input, standard output, or standard error to non-default settings.Workaround: You can safely ignore this error, or you can prevent the error from displaying by configuring the Call Executable step to ignore run-time errors. To handle other errors encountered in the Call Executable step, add a step after the call to handle the error information if the execution is not terminating.
|
|||||
| 322852 Return |
Enabling the Log option for parameters of a substep can cause an error When you configure the code module for a substep of a custom step type, enabling the Log option for any parameter on the Module tab of the Step Settings pane can result in a run-time error similar to the following error: Error executing substep '<substepName>'. Parameter <parameterName>': The following error occurred while logging additional result '<parameterName>': Array offset -1 is out of range; range is 0..1. This error occurs because substeps do not support logging additional results.Workaround: To log substep parameter data, store the data in a custom step property within the Result container of the step, and enable the IncludeInReport flag for the property.
|
|||||
| 334986 Return |
LabVIEW Edit substeps do not support LabVIEW class output parameters If you select a code module for an Edit substep you define for a custom step type and the code module specifies a LabVIEW class reference as an output parameter, TestStand returns the following error when calling the code module: Error Executing substep 'Edit'Workaround: Refer to the TestStand 4.2.1 section of the National Instruments KnowledgeBase article, Using LabVIEW class References with TestStand National Instruments KnowledgeBase article, located at http://digital.ni.com/public.nsf/allkb/EE3EA0A08FBB6E4A862573A9004C5A07?OpenDocument, for information about how you can pass a LabVIEW class reference as an output parameter for the code module of an Edit substep
|
|||||
| 347220 Return |
Modifying properties within an ExpressionEdit control on the Module tab of the Step Settings pane for a LabVIEW Edit substep can cause TestStand to hang TestStand and LabVIEW hang when all of the following conditions are true:
Workaround: If you encounter this hang, you must end the TestStand process and restart it to recover. To prevent the hang from occurring, ensure that the Module tab is not active on the Step Settings pane when you launch the Edit substep code module that contains an ExpressionEdit control by using the Substeps tab of the Step Type Properties dialog box to launch the substep.
|
|||||
| 51052 473EH1YL Return |
You receive an error when you attempt to directly pass TestStand API objects to a sequence you call on a remote computer When you use a Sequence Call step to call a sequence on a remote computer and you specify an expression that contains TestStand API calls for the value of an object reference parameter, TestStand might display the -17308: Specified value does not have the expected type. error.Workaround: Create a local variable or other property to assign the TestStand API property you want to pass to the remote sequence and use this property in the Parameter Table of the remote Sequence Call step.
|
|||||
| 346934 Return |
The comparison function can yield different results when operands are swapped if one operand is zero When using the comparison operator in TestStand to compare a value of magnitude 1e-14 or smaller to exactly zero, swapping the operands can yield different result. For example, the comparison 0 == 1e-14 returns True but the comparison 1e-14 == 0 returns False. The same difference in behavior occurs with the not equal (!=) and greater and less than (< and >) operators. This issue will be fixed in a future version of TestStand.Workaround: When comparing a small number to zero, ensure that the zero is the second operand in the comparison function.
|
|||||
| TestStand Sequence Editor | ||||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 248968 Return |
Watch View pane returns an error when you drag an object held by a reference onto the pane For an Object Reference called Ref that references a TestStand property called Foo, when you drag Foo to the Watch View pane, TestStand populates the watch expression with Ref.Foo and returns an error. Workaround: Drag the Object Reference into the Watch View pane and expand it to get to the property you want.
|
|||||
| 359036 Return |
An error can occur when you use the Find/Replace in Files dialog box in sequence files with a SequenceFileLoad Engine callback When you use the Find/Replace in Files dialog box to replace text in an unopened sequence file, the following error can occur if the sequence file contains a SequenceFileLoad Engine callback: Replacing the matched text in the value of object <object> with <string> failed. This error occurs because the callback executes when the Find/Replace in Files dialog box opens the sequence file, which blocks the Find/Replace in Files dialog box from editing the sequence file.Workaround: Open in the sequence editor any sequence files that use the SequenceFileLoad callback before you use the Find/Replace in Files dialog box to modify them.
|
|||||
| 354474 Return |
Cannot drag and drop array elements when sorting is enabled on any column on the Variables pane Refer to the National Instruments KnowledgeBase article, http://digital.ni.com/public.nsf/allkb/5F08134811CB6B0A86257A2300574A03?OpenDocument, for more information about this issue. Workaround: N/A
|
|||||
| 356920 Return |
Selecting multiple watch expressions can cause the Watch View pane to error in certain cases If you select multiple watch expressions on the Watch View pane and some expressions you select are valid but others are invalid, the Watch View can error. An invalid watch expression displays an "X" icon to the left of the expression. When the error occurs, the Watch View pane displays the One or more errors have occurred. Please save your work and restart the application. error and you must restart TestStand.Workaround: Ensure that you do not simultaneously select valid and invalid watch expressions.
|
|||||
| 308947 Return |
An error occurs when you use the Paste function in an array of object references If you copy an object reference property to the clipboard and then attempt to paste the object reference into an array of object reference properties, TestStand returns the Expected Container found Object Reference. Error Code: -17308, Specified value does not have the expected type error.Workaround: Use the Insert Element or Resize Array functions to add elements to an array of object references instead of using the Copy and Paste functions
|
|||||
| 314004 Return |
You can cannot edit the struct and cluster passing setting after you set the data type as hidden If you set a container data type to be hidden using the PropFlags_Hidden or PropFlags_HiddenInTypes flags, you cannot edit the struct and cluster passing setting. This behavior only occurs if the struct and cluster passing setting is disabled before you set the data type as hidden. If the struct and cluster passing setting is enabled, you can continue to edit the setting even after you set the data type as hidden.Workaround: To change the struct and cluster passing setting of a hidden data type, unhide the data type, change the struct and cluster passing setting, and then rehide the data type.
|
|||||
| 350367 Return |
The Module tab on the Step Settings pane does not display in certain cases after you change the type for a step The Module tab on the Step Settings pane does not display when you complete the following steps. You cannot configure the code module and its parameters for the step.
Workaround: To recover from this issue, save the sequence file and restart TestStand. You can avoid the issue by creating a new step instead changing the type of an existing step.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 298496 Return |
Expression Browser dialog box elements do not display correctly if the font size is set to 150% DPI If the font size of Windows 7 is set to 150% 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.
|
|||||
| 301993 Return |
TestStand ActiveX user interface buttons connected to the CommandKind_Edit commands might exhibit unexpected behavior If you use a button to trigger a CommandKind_Edit command, such as CommandKind_Edit_Delete, clicking the button does not result in a delete operation. This unexpected behavior occurs because clicking the button moves the focus from the TestStand User Interface control that you want to delete to the button, and TestStand cannot determine which control to delete. Workaround: Use shortcut keys or other events that do not remove focus from the TestStand User Interface control to trigger CommandKind_Edit commands.
|
|||||
| 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.
|
|||||
| 255848 Return |
You cannot paste additional results in user interfaces other than the TestStand Sequence Editor In the sequence editor, you can cut or copy an additional result and paste the result in the same step or in a different step. In a user interface, the AdditionalResults cut, copy, and delete context menu options work, but the paste option does not. Workaround: Manually create the additional result you were trying to paste.
|
|||||
| 256758 Return |
Using the keyboard to select multiple variables in the Variables View control does not work in the MFC, LabWindows/CVI, or LabVIEW UIs In the Microsoft Foundation Classes (MFC), LabWindows/CVI, or LabVIEW Editor UIs, you cannot select multiple variables by holding down the <Shift> key and using the up or down arrow keys on the keyboard. This issue does not exist in the .NET Editor UIs. Workaround: Use the mouse along with the <Shift> key to select multiple variables in the Variables View of the MFC, LabWindows/CVI, or LabVIEW Editor UIs.
|
|||||
Document last updated on 8/13/2012
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).