NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
This document contains the LabVIEW 2010 known issues that were discovered before and since the release of the LabVIEW 2010 Development System. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.
The LabVIEW 2010 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
There are two versions of the known issues list available:
Known Issues by Category
Known Issues by Date
Please refer to Developer Zone Article "LabVIEW Known Issues Categories Defined" for an explanation of the categories.
The following items are known issues in LabVIEW 2010 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| ActiveX and .NET | ||||||
| 187247 Return | ActiveX functions return error 1 if using a 64-bit integer LabVIEW invoke nodes can be configured to invoke functions containing 64-bit integers parameters, but when executing the invoke node it always fails with error 1. Workaround: N/A
| |||||
| 248065 Return | Application Builder fails with Error 74 with upgraded .NET and a dll call It is possible that upgraded .NET code will fail to build if the build also contains a dll. This is caused by the linker information that stores where the .NET nodes find their actual assembly. Workaround: Completely delete the .NET code from your program (whole project). Save the project, close and reopen it. Add the nodes back to your program. Do NOT copy and paste the nodes from other VIs.
| |||||
| 221992 Return | LabVIEW Constructor node cannot load dlls written in .net 4.0 LabVIEW supports the .NET Framework 2.0. It does not support the new features of .NET past 2.0. Many applications built with the .NET Framework 3.0 or 3.5 would still use mscorlib 2.0 which hadn't changed versions since .NET 2.0. With Visual Studio 2010 and .NET 4.0, Microsoft replaced mscorlib 2.0 with mscorlib 4.0. Because of this LabVIEW cannot load assemblies compile for the .NET Framework 4.0 Workaround: N/A
| |||||
| 191423 Return | LabVIEW does not execute properly when certain .NET properties are changed on the .NET RichTextBox control The HideSelection, WordWrap, and ScrollBars .NET RichTextBox properties don't execute correctly, and cause display update issues on some versions of LabVIEW. Workaround: N/A
| |||||
| 245359 Return | Selecting a newer version of a .NET assembly does not reload assembly Changing a constructor from an old version of a .NET assembly to a newer version at edit time does not cause the new assembly to be loaded and consequently none of the new functionality is available. Workaround: 1. Remove the old assembly so the .NET Runtime is not able to find it. It will then return the updated version to LabVIEW.2. Load the new assembly in a blank VI before opening your existing VI. This will load the new version into memory prior to you requesting the older version.
| |||||
| Analysis | ||||||
| 292464 Return | The function GaussHG returns NaN for X values less than 0. Workaround: N/A
| |||||
| Analysis and Math | ||||||
| 174929 Return | Repeated Loading & Unloading of the Analysis Library Generates Exception This problem has only been reproduced on Linux using the latest versions of MKL v10.x, and has been reported to Intel as 545399. Some analysis VIs in LabVIEW use Intel's Math Kernel Library (MKL) internally to compute results. Opening these VIs or using them on another VI's diagram loads the MKL library. When all references to these analysis VIs are closed, the MKL library is unloaded from memory.When working with a VI that use these analysis VIs, the following development patterns can lead to this problem:1. Dynamically opening and closing references to the VI while no references to the analysis VIs are in memory.2. Iteratively opening and closing the VI while no other analysis VIs are loaded in memory.3. Using the File >> Close All operation in between editing one or more VIs that use the analysis VIs. Workaround: To avoid the exception, the MKL library must remain in memory during the entire LabVIEW session. You can achieve this in many ways:1. Open the front panel of an analysis VI that loads MKL and keep it open until exiting LabVIEW.2. Open a reference to an analysis function that loads MKL and close the reference before closing LabVIEW.The A x B.vi from the Mathematics >> Linear Algebra palette is an example of analysis function that serves this purpose.
| |||||
| 169840 Return | Large matrix operations that utilize the Intel MKL on Linux may crash LabVIEW When one or more matrix operations consumes most of the system resources, the Intel MKL library produces an unhandled exception that results in a LabVIEW application crashing.This Intel library is used to accelerate fundamental linear algebra operations performed under Linux operating systems. This issue has been reproduced outside the LabVIEW execution environment and a bug report has been submitted to Intel.Because the crash is tied to system resources, it can manifest itself in many ways. For example, we have reliably reproduced the problem by:1. Decomposing a large matrix into multiple large matrices.Specific example: Computing the singular value decomposition (SVD) of a 2500-by-2500 matrix on a system with 256M RAM.2. Simultaneously computing multiple matrix operations using relatively small matrices.Specific example: Computing 30 matrix expressions using 300 x 300 matrices on a system with 512 MB RAM. Workaround: If you have identified one or more matrix operations in your application that exhibit this behavior, you have multiple options to avoid crashing.1. Serialize the matrix operations so that they are not consuming resources in parallel.2. Replace affected matrix arithmetic functions using Basic Linear Algebra Subroutine (BLAS)functions found on the BLAS palette.3. Structure your application so that these operations are not competing with other functions for system resources.
| |||||
| 244148 Return | Certain Trigonometric Functions Return Incorrect Results in LabVIEW 2010 when Using Extended Precision Inputs In LabVIEW 2010 certain trigonometric functions will return incorrect results when using extended precision inputs to the functions. The affected functions are sec(x), csc(x), cot(x), acos(x), asec(x), sinc(x) Workaround: This has been fixed in the LabVIEW 2010 f2 Patch
| |||||
| Building and Distributing LabVIEW Applications | ||||||
| 51179 47B12U5U Return | Error 6 occurred at Create Folder in Create Directory Recursive.vi when building an application (EXE), shared library (DLL), source distribution or web service When building a Build Specification, the build process fails with Error 6 at Create Folder in Create Directory Recursive.vi. This usually happens if the path one of the files generated by the build (temporarily during the build process or as part of the output) is too long. The operating system requires paths for files to be less than 255 characters. Workaround: 1. Use a shorter path for your build destination (i.e. c:\build\) and if necessary copy the output to the final location you need.2. A. For application (EXE) and shared library (DLL) build specifications, place a checkmark in the Use LabVIEW 8.x file layout checkbox on the Advanced page of the Properties dialog box.2. B. For source distribution or web service build specifications, uncheck the Preserve disk hierarchy checkbox on the problem Destination on the Destinations page of the Properties dialog box.
| |||||
| 208364 Return | LabVIEW built installers created on a 32-bit machine will not install most drivers when run on a 64-bit machine If you build an installer using LabVIEW on a 32-bit machine that contains National Instruments drivers, the corresponding drivers will not be installed if the installer is run on a 64-bit machine. Drivers such as NI-DAQ, NI-Sync etc. are affected by this issue. Installation on 32-bit machines are not affected by this bug. Workaround: On the deployment 64-bit machine, download and install the missing drivers from the ni.com Drivers and Updates page
| |||||
| 212136 Return | "The VI is not executable. The full development version of LabVIEW is required to fix the errors" dialog on a built app If you have a built application that contains a polymorphic VI in a LabVIEW library which has an instance VI that is private, and a VI outside the LabVIEW library calls the polymorphic VI, this error might occur in the built application. Workaround: In App Builder, under "Additional Exclusions", uncheck the "Remove unused polymorphic VI instances" option.
| |||||
| 223244 Return | "File is not a resource file." popup on a built app If the startup VI of a built app does not have the ".vi" extension, this error might occur in the built application. Workaround: Change the startup VI to have a ".vi" extension.
| |||||
| 198955 Return | Default Parameters cannot be deleted from .NET assembly parameter list The .NET interop assembly utility's Define VI Prototype Dialog Box states that 'return value' is the only parameter that cannot be deleted, but any value connected to the connector pane is included by default, and none of these can be deleted. The X (delete) button is disabled. Workaround: None - building a wrapper around the built DLL to only expose the parameters desired, or not allowing the parameter to be default (disconnect from connector pane)
| |||||
| 164604 Return | Calling LabVIEW built .NET Interop Assembly from same version of LabVIEW causes a hang If you build a .NET Interop Assembly and try to call it in the same version of LabVIEW, it will hang at the constructor node Workaround: Create the .NET Interop Assembly in a different version of LabVIEW.
| |||||
| 227609 Return | Statically linking a LabVIEW built DLL in a C++ project results in error 998 if the DLL is not added to the Delay Loaded DLLs list Workaround: Go to the Project Property Pages, Configuration Properties»Linker»Input and add the name of your DLL to the Delay Loaded DLLs list.
| |||||
| 192280 Return | Open UFF58 VI will cause a hang if built into an application If you use the UFF58 functions and build them into an application the called DLL does not get pulled into the application. Workaround: Create an always included VI that specifically uses the UFF58 dll in a Call Library Function Node. This will cause application builder to pull in the dll.
| |||||
| 248965 Return | Deploying an executable that uses SSL with the HTTP Client API will error out To use SSL with the HTTP Client API you have to purchase an internet toolkit license. This issue with this is if you build a LabVIEW application (EXE) that uses this functionality the user will receive an error 1380 Workaround: Manually install and activate internet toolkit license file on the deployment machine
| |||||
| 242600 Return | A search dialog can appear when building a source distribution where the main destination is a library Building a source distribution with the following options set will display a dialog searching for unused VIs in libraries in the original project:- Remove unused library members- Main destination is a library Workaround: N/A
| |||||
| 254821 Return | LabVIEW built executable with network streams won't exit process LabVIEW built executables that load the the network streams dll will not dispose of it properly when finished. The executable's process will remain in the task manager Workaround: Manually kill the process after completion.
| |||||
| 300558 Return | LabVIEW built executable with network streams won't exit process LabVIEW built executables that load the the network streams dll will not dispose of it properly when finished. The executable's process will remain in the task manager Workaround: Manually kill the process after completion.
| |||||
| 300592 Return | LabVIEW built executable with network streams won't exit process LabVIEW built executables that load the the network streams dll will not dispose of it properly when finished. The executable's process will remain in the task manager Workaround: Manually kill the process after completion.
| |||||
| 251951 Return | HTTP Client VI calculates wrong dll path when built into a built app on LV RT If you build using the http client api Open Handle.vi into a startup application it will return error 7. Workaround: N/A
| |||||
| 255617 Return | Error 1502 can occur if dependencies are placed in non executing case structures In previous versions of LabVIEW you could place VIs in a case structure with a constant wired the the case selector. This would load the VIs at runtime. If you have this pattern and attempt to build an executable you could receive error 1502 Workaround: Don't use unreachable code
| |||||
| 282737 Return | Applications with Chinese characters in the executable name will throw fatal error on English Windows 7 Workaround: Use a different name for the executable.
| |||||
| 308464 Return | LabVIEW cannot build some large applications because it fills the image table. LabVIEW cannot build some large applications. If you try to build a large application it will fail. An internal warning is thrown during the build stating that the image table has been filled. Workaround: This issue has been fixed in the LabVIEW 2011 f2 Patch.
| |||||
| 187412 Return | Custom RTM will incorrectly link to the source location when built into an executable If you have a custom Run-Time Menu you can include it in an executable. When we build the executable we incorrectly link to the original location of the RTM file instead of the one being brought into the build. Workaround: Save the original RTM files in a location that you can distribute. For example if you save them in the "Data" directory that is next to where the executable will be saved this will work and create a package that isn't terrible to distribute.
| |||||
| 186525 Return | 'visarc' file included in source distribution even when excluding vi.lib If you are using VISA and build a source distribution you get a copy of the visarc file with your source distribution and your VIs link to that copy. Workaround: 1. Delete the visarc file made by the build2. Add visarc to the project under My Computer. In the build spec, add the file as Always Excluded.
| |||||
| 286917 Return | DSC Periodic I/O Servers run as SYSTEM and creates a security vulnerability Period I/O server runs within the Shared Variable Engines (tagsrv.exe) in the SYSTEM security context. Any user on the machine (excluding guests), regardless of security level (administrator, user, power user, etc...) can deploy a Periodic I/O server to be run by the Shared Variable Engine. This makes it possible for a non-priviledged user to run LabVIEW code at a higher permission level than they are allowed. This is commonly know as a priviledge escalation vulnerability. (This does not apply to guest users as they seem to be unable to deploy LabVIEW Web services)This is dangerous as the Application Web Server is automatically installed and enabled (at least in LabVIEW Beta 2), allowing any user on the machine to use this vulnerability to execute code in the SYSTEM security context without having to enable or modify anything. This invalidates Windows user security. Workaround: 1. Open the Service Control Manager (in Vista and Win 7 simply type "Services" in the "Search for Programs and Files" box in the start menu.2. In the service control manager, find "National Instruments Variable Engine" 3. Right click and select "Properties" in the popup menu.4. Click on the tab labeled "Log On"5. In the dialog, click on the radio button labeled "This account:"6. Select a user account on your machine or domain that does not have administrator privileges on the machine itself.7. Click OK8. Restart the service by right clicking on it in the service control manager again and selecting "Restart".
| |||||
| 367445 Return | Source distribution of a class which uses dynamic dispatch can become broken looking for a missing subVI if you build a source distribution and a dynamic dispatch node is wired with a child class, the node can fail to be renamed and the code is thus broken looking for a missing subVI Workaround: Create the distribution without renaming, and then rename it after creation
| |||||
| 445175 Return | Two or more Static VI References between the same VIs with different strictness can result in broken executables from Application Builder The broken executable displays the error message: "This VI is not executable. The full development version of LabVIEW is required to fix the errors." Workaround: There are multiple potential workarounds:1. In the exectuable's build spec, uncheck the "Remove unused polymorphic VI instances" option under Additional Exclusions2. Use the old method of calling a VI using the Run VI method3. Use a Strict type specifier VI refnum instead of a Static VI reference connected to the Open VI Reference
| |||||
| Controls and Indicators | ||||||
| 219819 Return | Center justified tables display improperly when overlapping with the front panel origin When you add a table control to the front panel so that it overlaps with the vertical origin of the front panel, LabVIEW displays center justified columns off center when you type text. The cells appear to float or move horizontally until aligned with the vertical origin. Formerly tracked as 50061 and 42NAR8SA Workaround: Move the table away from the front panel's vertical origin.
| |||||
| 51311 477DKPBQ Return | LabVIEW does not maintain child-only item setting when dragging an item within a tree If you have a tree item with the child-only setting, and then drag it within the tree, LabVIEW loses the child-only setting. Workaround: Use tree events to (1) get the child-only flag setting when the user begins a drag, and (2) reset the child-only flag after completing a drop.
| |||||
| 52297 4AIFC0R0 Return | Internal error related to locked tab control at fpsane.cpp line 369 and line 367. If you lock a tab control that is already locked using Group»Lock, you might see two internal errors and LabVIEW may crash. Workaround: Do not lock a control that is already locked.After the fact: copy the Tab Control from the block diagram into a new VI. It will show up unlocked in the new VI.
| |||||
| 91672 477M7K00 Return | Large amounts of data in combo box can appear to hang LabVIEW. If you place a large amount of data in a combo box, on the order of megabytes, LabVIEW appears to hang by taking a long time to calculate wrapping. Workaround: N/A
| |||||
| 43109 4FRF0826 Return | Cannot customize plot legend with background image in LabVIEW You cannot configure a plot legend with a custom background image in LabVIEW. Workaround: Make the color of the plot legend transparent, and place the image behind it. This only works if your plot legend remains a fixed size in a fixed location.
| |||||
| 45133 4I0976O4 Return | The coercion of an enum through its digital display behaves differently in the development environment than in a LabVIEW executable. The coercion of an enum through its digital display behaves differently in the development environment than in a LabVIEW executable. Neither produce an out of range value, but one coerces to the last entry in the enum, the other leaves the enum unchanged. Workaround: Use an event structure to capture value change filter events and restore the enum to the value you choose. You can also disable the digital display for the enum.
| |||||
| 118949 Return | Tab control local variables generate value change events when you use a multi-column ListBox A value change event is generated when a Tab Control local variable's value is changed in an Event Structure that was triggered by a double-click/ value Change on a multi-column ListBox. Workaround: Use Value Property Node for the Tab Control instead of Local Variable to change the Tabs.
| |||||
| 45360 4I0EE2BQ Return | Localization Codes do not Function for Timestamp Controls According to the help, localization codes are available for format strings. They allow to specify the decimal separator and override the system decimal separator. However, this doesn't work for the Timestamp "advanced format" option. Workaround: If you would like to discuss this issue and possible workarounds, please visit the NI Discussion Forums
| |||||
| 164268 Return | Tab control incorrectly displays ComponentWorks 3D Graph when other tabs are selected "Page Labels Display" Tab Controls display remnants of ComponentWorks 3D graph when toggling through the pages using Page Labels Display. The issue does not occur when manually clicking on the Page names, or when changing the value of the tab with the tab's terminal, a local variable, or a Value property node. Workaround: Change the value of the tab directly on the terminal, with a local variable, or a Value property node.
| |||||
| 167056 Return | Wiring cluster of fixed point values to waveform chart causes a broken arrow Workaround: Change the representation of the number wired into the cluster to something like I64, then back to FXP
| |||||
| 208088 Return | Updating the Labels of a Cluster Written to a Chart Does Not Update the Cluster Used for Chart History Changing the Label of elements in a cluster written to the Waveform Chart does not update the label of the cluster when read from the Waveform Chart Data History Property. Workaround: Temporarily wire up a completely different data type to the Waveform chart indicator and then rewire the original cluster. The changes will now propagate to the Chart History.
| |||||
| 185890 Return | Text on a VI can be mutated to appear as Unicode After building a project into an executable, various text for controls and indicators changes languages. It appears that the text was interpreted as Unicode.We have not been able to reproduce this in house to find a definite cause. Because of this we will leave this CAR open even though we have created code to recover from the corruption if it happens.Previously tracked as CAR 179683 Workaround: Upgrade the VI to LabVIEW 2011. In 2011 we put in code to only view text on VIs as unicode if the UseUnicode=True is in the LabVIEW .ini file. Previously this would only switch on the ability to change something to unicode.When the VI is upgraded to 2011 it should be saved and then saved for previous to return it to the original version.
| |||||
| 176848 Return | Picture Control Stops Updating After Setting Properties to Default. Once the picture control's values have reinitialized to default by selecting Data Operations»Reinitialize to Default or programmatically using the method Reinitialize to Default, the mouse position property node stops updating. Workaround: Replace the picture control with a new one from the palette.
| |||||
| 236377 Return | Dropping XControl from public library breaks XControl When adding an X control from a public library into the controls palette, it become broken when dropped down to the front panel from the controls palette. Workaround: Include a merge VI in the functions palette
| |||||
| 248914 Return | Changing the order of controls or deleting controls in a type def cluster can change references When you create a reference for a control in a type defined cluster LabVIEW uses the cluster order to determine what control the reference is referring to. Say you have a type defined cluster with elements A, B, C and D with cluster order 1,2,3 and 4 respectively. On the block diagram of a VI you have control references to each of the controls. If you open the type def and delete control C the block diagram of the VI will only contain 3 references. Moreover, the reference that used to be for control C will now reference control D. This is because the control is based on cluster order Workaround: N/A
| |||||
| 251229 Return | Adjusting X-Scale Multiplier Property Affects Graph Annotations When adding annotations to a graph they can appear on the Y-axis instead of above the data. Workaround: N/A
| |||||
| 250588 Return | Warning Generated in a Method or Property of an XControl Appears as an Error in the Top Level VI If you create a method or a property in an Xcontrol in which you have implemented code to generate a warning it is transformed into an error in the calling VI. Workaround: In the VI look for specific error and transform back to a warning
| |||||
| 277049 Return | Changing a missing Type Definition Control to a constant crashes LabVIEW Workaround: Disconnect from Type Def before changing to constant.
| |||||
| 252270 Return | Stacked chart will not update all points if Digital Display is visible and on top of the chart Workaround: Move all Digital Displays off of the graph itself
| |||||
| 292599 Return | Using Array Selection Size[] or Selection Start[] Properties can crash LabVIEW 64-bit Workaround: N/A
| |||||
| 338840 Return | Shortcut Menu Activation Interferes with Independent Autoscale Y Settings in Waveform Chart or Graph with Multiple Plots The Autoscale Y setting is not remembered for each plot when a waveform chart that contains multiple plots also contains a Shortcut Menu Activation as a Dynamic Event Registration. By changing the setting of one axis, it becomes altered on another. Workaround: None
| |||||
| 342148 Return | Boolean reference as first item in cluster can causes LabVIEW crash Workaround: Change the order of the cluster so the boolean is not first.
| |||||
| 218947 Return | IO Variable items under copy-pasted C Series modules lose custom names & configuration When pasting a cRIO module that has variables under it, the variables are always pasted with the default name and configuration (just as if the module was being created new instead of pasted). Workaround: Drag or control-drag the module to where you want to paste it.
| |||||
| 241160 Return | Multiple Instances of a control in an unbundle by name function causes indicators not to update If you have a cluster wired to an unbundle by name function, and you unbundle the same control twice with the same unbundle by name VI you will sometimes not be able to rebundle the value back into a bundle by name function. The value will not go into the bundle function. Workaround: Do not use the same control twice on an unbundle by name function.
| |||||
| 239719 Return | Property page doesn't update when Adapt to Source is coerced to off If you have a FXP constant with Adapt to Entered Data set and make any modifications to the display format, the resulting constant will not be set to adapt. The property page will not reflect this change before it is closed. Workaround: Always double-check condition of Adapt To Entered Data.
| |||||
| 365679 Return | LabVIEW 3D Picture control does not work with certain AMD video card drivers The 3D Picture control will appear black, or with bands of black, if running on a computer that has an AMD graphics card, and a version of the driver software after Catalyst 11.5. Workaround: Roll back display drivers to AMD Catalyst Display Drivers version 11.5 or previous. This issue is fixed in LabVIEW 2012 f2.
| |||||
| 184689 Return | UI Performance degredation when displaying NaN values on 3D Surface Graph in LabVIEW N/A Workaround: N/A
| |||||
| DataSocket | ||||||
| 206944 Return | Version in DataSocket Server About Box is incorrect The About Box of the DataSocket Server always displays version 4.5, regardless of the installed DataSocket Version (4.5/4.6/4.7). Workaround: N/A
| |||||
| Distributed System Manager | ||||||
| 237673 Return | Refreshing Distributed System Manager with an item selected will remove the item from the display When an item within a process such as a Shared Variable or a I/O channel is highlighted and the user refreshes the display the high lighted item will be removed from the display. This will not remove the items from Shared Variable Engine be inaccessable from hardware or other applications. Workaround: Highlight a system or process and click refresh. This should restore the missing item to the display.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| External Code | ||||||
| 207352 Return | Moving a .NET Assembly while LabVIEW is open will cause an error the next time it is called from LabVIEW. Changing the location of a .NET DLL causes the following error to occur when calling the DLL with a .NET constructor node:Error 3 occurred at Constructor Node in [VI name]Possible reason(s):LabVIEW: Internal error. Wrong memory zone accessed. Workaround: Close LabVIEW and then move the assembly. You will have to relocate it when opening LabVIEW. Note: It is always recommended to use a project when using .NET code in LabVIEW. You should only have the relocated the assembly in the project.
| |||||
| 153731 Return | Unhandled Exception can occur if absolute path for system DLL used in CLFN If you use a specific path to a system DLL (C:\windows\system\user32.dll) and build your VI into an application it will create a copy of the DLL inside the application. This can cause an unhandled exception when running Workaround: LabVIEW searches in the system directory when looking for DLLs. If you are using a system DLL simply put the name in the in DLL Path box in the CLFN properties. In the example above you would simply put "user32.dll"
| |||||
| File I/O | ||||||
| 47819 3N68LE00 Return | 2GB file size limit of datalog files The maximum size of datalog files is 2 GB. Workaround: N/A
| |||||
| 243468 Return | Default Namespaces not supported in XML Parsing VIs When trying to work with XML Parsing VIs you will get error -2768Possible reason(s):LabVIEW: The XPath expression does not conform to XPath syntax. Refer to the W3CXPath Web site at http://www.w3.org/TR/xpath for more information about XPath syntax. Workaround: Remove the default namespace (example: remove xmlns="http://www.ieee.org/ATML/2007/TestResults"),
| |||||
| 247628 Return | Reading a TDMS file written using DAQmx Configure Logging VI may result in an out of memory error. If a TDMS file was written using the DAQmx Configure Logging VI, reading channels from the TDMS file without specifying the count input of the TDMS Read functions may result in LabVIEW trying to load the entire file into memory. Depending on the DAQmx scaling used during logging, the memory needed for scaled data values might be a multiple of the actual file size. If the available memory is not sufficient, LabVIEW returns an error about how memory is full. Workaround: This has been fixed in the LabVIEW 2010 f2 Patch
| |||||
| 285210 Return | Read from Measurement File Express VI can read incorrect data If you use a Write to Measurement File Express VI to write an LVM file, the data can be misinterpreted from the Read from Measurement File Express VI if the LVM file has headers. The file is correctly written; however, it is just read incorrectly. Workaround: Don't write headers in the LVM file
| |||||
| 276334 Return | On VxWorks targets, the TDMS Defragment VI shows Error 6 and deletes the file it is operating on in the U:\ drive TDMS Defragment VI shows Error 6 and deletes the file it is operating on when told to operate on a TDMS file that is located on the U:\ drive of a VxWorks Real-Time target. (U:\ drive is a USB drive) Workaround: Use the TDMS Defragment VI on a TDMS file that is located on the C:\ drive. Then move the defragmented file to the U:\ drive.ORA copy of the degramented TDMS file from the U:\ drive can be found in the temp directory (for cRIO it's c:\temp). Note: The temp file gets overwritten every time the TDMS Deframent VI is used, so only the latest file is available in the temp folder
| |||||
| 276928 Return | Opening a TDMS file with LabVIEW 2010 can produce error -2503 More information and a workaround can be found in this KnowledgeBase Workaround: See KB
| |||||
| 236193 Return | Crash with invalid input (o or negative values) of "samples per channel" when misusing TDMS Set Channel Information There are some situations if you set the value of "samples per channel" of TDMS Set Channel Information as 0 or negative values (invalid values), which could cause a crash. Workaround: Avoid using 0 or negative values as "samples per channel".
| |||||
| 112702 Return | Cannot read file that shows up as zero bytes. Linux, Unix and Macs can have files that show up on disk as zero bytes but actually have data that can be read. If you use a Read Binary File primitive on these files you will return an empty string. Workaround: Read a large number of bytes and handle the end of file error that you will receive.
| |||||
| 239631 Return | Memory Growth with TDMS Write With the standard TDMS API, when TDMS Write VIs are executed the API will build a cache in memory. This may present as a memory leak, as this memory is only cleared in specific situations. Workaround: See KnowledgeBase 5WQD51YS: Memory Growth with TDMS Write for more information.
| |||||
| 303503 Return | When a LVM file is read by the Read from Measurement File Express VI, the Y Unit attribute is ignored. Workaround: N/A
| |||||
| 257506 Return | Write Binary on array of extended / complex extended with no array size information writes invalid data when set to write native byte ordering. If you write an extended array with no dimension size in native byte ordering (not big or little endian, but only native ordering) using Write to Binary File, the data is output as 10 byte values instead of 16 byte values. Workaround: n/a
| |||||
| 372668 Return | The channel order is incorrect for the first TDMS group after using NI_MinimumBufferSize property. Workaround: Do not wire group and channel information to the TDMS Set properties function when setting NI_MinimumBufferSize.
| |||||
| Functions, VIs, and Express VIs | ||||||
| 37575 3PD8N0M8 Return | LabVIEW uses large amounts of memory when reading an entire wave file at once The Sound File Read VI uses large amounts of memory to read an entire .wav file. Workaround: Read the data from the .wav file in sections rather than in one large file.
| |||||
| 39161 401FEQTL Return | The device ID input of the Play Sound File VI does not work on Windows On Windows, LabVIEW ignores the device ID input of the Play Sound File VI. This VI plays sound only on the default sound card. Workaround: Use the Sound Output Configure VI and the Sound Output Write VI with the Sound File Open VI and the Sound File Read VI or the Sound File Simple Read VI. Refer to the Sound File to Sound Output example VI for an example of this workaround.
| |||||
| 39604 49UBP4LE Return | Write to Clipboard Method consumes 100% of CPU for several minutes If you try to copy a large amount of data from LabVIEW to the clipboard, LabVIEW slows significantly and might become unresponsive.This was previously tracked as CAR 90497 and 3YJ87JCM Workaround: N/A
| |||||
| 48016 3P7CBB4Q Return | Unsigned int32 loses value in formula node when you write to the most significant bit If you wire a hex value greater than x7FFFFFFF as an unsigned, 32-bit integer to a Formula Node, LabVIEW coerces the value to 0. If you use a negative number for U32 input/output variable, LabVIEW will coerce the value to 0. Workaround: 1. Use the Mathscript node or LabVIEW code for the operation that involves an unsigned, 32-bit integer.2. Use signed 32-bit integers instead of unsigned 32-bit integers in the formula node.
| |||||
| 50420 44CG88SN Return | Update the Pulse Transition Measurement Express VI The terminology and measurement definitions for the Transition Measurements VI comply with IEEE Standard 181-2003, IEEE Standard on Transitions, Pulses, and Related Waveforms. However, the Timing and Transition Measurements Express VI does not comply with this IEEE Standard. Workaround: The Slew rate refers to the transition slope. The Preshoot refers to the pre-transition undershoot (rising pulse) or the pre-transition overshoot (falling pulse). The Overshoot refers to the post-transition undershoot (rising pulse) or the post-transition overshoot (falling pulse).
| |||||
| 45802 4IDA53I0 Return | Using VI Server Get/Set [Variant] Control Values on Clusters with Fixed Size Arrays creates error 2 The VI Server get/set [variant] control values if used on a cluster with fixed sze arays, results in an error. This is expected as LabVIEW core does not support fixed size arrays. Fixed size arrays are meant to be used only with LabVIEW FPGA. Workaround: Pull the array outside the cluster for running on the development computer.
| |||||
| 118106 Return | Variant To Flattened String and Flattened String To Variant Do Not Support Fixed Point Data Type The Fixed Point data type is not supported by the Variant To Flattened String and Flattened String to Variant functions. You may see a crash when trying to unflatten this datatype in conjunction with an empty fixed point array. Workaround: Either use a supported datatype or do not use the Variant.
| |||||
| 120686 Return | Write to LabVIEW Measurement Files (LVM) using Express VIs takes up a lot of memory The "Write to Measurement File" Express VI consumes a large amount of memory when writing to a Text File (LVM). However, the memory usage is smaller when the same Express VI is used to write a TDM/TDMS File Workaround: Use general LabVIEW VIs (and not Express VIs) to perform an LVM write for large amounts of data. The other option would be to write in smaller chunks.
| |||||
| 122057 Return | Joining Numbers of Different Widths Produce Unexpected Values The Join Number VI produces different results when the inputs are of different widths/sizes. Workaround: Explicitly cast to same size before joining.
| |||||
| 124783 Return | Sound Input Read VI does not return samples requested If the user inputs a value of "number of samples/ch" into the Sound Input Read VI and the waveform that this returned is only 75% of the samples. Workaround: N/A
| |||||
| 162800 Return | "Wait on Notification from Multiple" returns inconsistent results when multiple refnums refer to same named notifier When using the "Wait On Multiple Notifications" primitive, problems have been observed if two refnums in the input array refer to the same named notifier. These problems apply if the exact same refnum is included multiple times or if different refnums to the same notifier are included. If the Wait node executes and there is already a notification available then the output refnum array will include every refnum that refers to the underlying notifier (including multiple copies of the same refnum) and there will be N copies of the notification in the output notification array, one for each output refnum. If the Wait node does have to go to sleep, when Send Notification executes, the Wait will wake up but will return an array containing only a single refnum and one copy of the notification. Workaround: You can use Notifier Status function on each of the refnums passed as input to the Wait function in order to get the names of all those notifiers. When the Wait function returns its results, use the Notifier Status function to get the name of the returned notifier, then search the original list for all refnums that have the same name as the one returned. This allows you to identify the original refnums that should have been returned.
| |||||
| 158446 Return | When comparing a sub array created through the Array Subset Function with an identical Array the result is false. Workaround: 1. Place after the "Array Subset" function a "Reshape Array" function.2. Replace the "Array Subset" function through "Delete from Array" function3. Turn off auto-preallocate arrays and strings.
| |||||
| 176856 Return | VI Snippet of a VI with Dynamic inputs results in a LabVIEW crash Previously tracked as CAR 182023 Workaround: N/A
| |||||
| 213279 Return | Some nodes may crash or yield incorrect/inconsistent results when Inlined An Inline public methodVI calling a private-scope method VI, inlined into a non-class caller may give a runtime error when trying to call the private method from the inlined code in the non-class caller. Workaround: Do not try to Inline VIs with these nodes.
| |||||
| 231877 Return | Polymorphic VIs with "Adapt to Type" set can choose wrong instance VI With a polymorphic VI with instance VIs that take a floating point type and an integer type, the "Adapt to Type" mechanism may incorrectly choose the integer type instance VI when a floating point type with more precision is wired in. For example, if a polymorphic VI has one instance VI that takes an I32 and one that takes a Single Precision floating-point number, when wiring in a Double Precision floating-point number the polymorphic VI will choose the I32 version. Workaround: Coerce the input data type to correspond to the desired instance VI.
| |||||
| 227030 Return | Wait on Notification from Multiple function has unexpected behavior when ignoring previous input. Workaround: See KB
| |||||
| 237587 Return | Using "^" in an Expression Node will result in a broken VI Using "^" operand in an Expression node will cause a VI to fail to compile. This is not the correct operand to use if you want to use exponents. Use a double asterisk "**" instead as it is the correct syntax Workaround: Use "**" instead of "^"
| |||||
| 231024 Return | Network Streams do not support Fixed Point range and delta Network Streams strip FXP range and delta from data types because LogosXT currently does not support them. Workaround: N/A
| |||||
| 233205 Return | Network Streams do not support enums, data types w/ units, substrings, subarrays, & fixed-size arrays The Network Streams API does not support all LabVIEW data types. In an unsupported data type is used as an input to the data type terminal of a Create Stream Writer Endpoint VI or Create Stream Reader Endpoint VI error -314304 will occur. Workaround: N/A
| |||||
| 233209 Return | An array of Stream refnums can incorrectly display access type An array of Stream refnums with different access types will incorrectly display acces type if the array is created with the build array function. Workaround: To to create a control or indicator compatbile with your array, you have create an array of this type on a diagram, create a control or indicator from that array wire, and then copy the control or indicator to the place you want to use it.
| |||||
| 235019 Return | OpenSSL fatal error when LabVIEW exits The OpenSSL fatal error possibly occurs when using Search features in LabVIEW for the first time after installation. Workaround: Launch LabVIEW and exit when Getting Started Window opens. The error now goes away in future launchings.
| |||||
| 246593 Return | Power of X and Y-th Root of X returns incorrect result when using single precision numbers When using the Power of X or Y-th Root of X functions with single precision number the output will be incorrect. These functions will always return a value of one if X is positive and NaN if X is negative. Workaround: This has been fixed in the LabVIEW 2010 f2 Patch
| |||||
| 196607 Return | DTbl Replace Subset VI behavior change between LabVIEW 8.6.1 and 2009 The start input indexes from the replacement data instead of the existing data Workaround: Set the index of data to replace from 0
| |||||
| 196742 Return | Load STL Geometry VI cannot load binary STL files Workaround: Use a different type of STL file.
| |||||
| 226840 Return | Formula VI does not execute pow(x,y) function Workaround: Use the formula node to use the pow(x,y) function. If you need to change this programmatically, use the Power of X function in G code.
| |||||
| 322914 Return | Formula VI does not execute pow(x,y) function Workaround: Use the formula node to use the pow(x,y) function. If you need to change this programmatically, use the Power of X function in G code.
| |||||
| 248421 Return | Bitshift does not work correctly in Expression Nodes and Formula Nodes with a data type smaller than I32 Workaround: N/A
| |||||
| 251094 Return | HTTP Post Reports Error 42 When Executing a FSWS Download with a 1MB File Workaround: Ignore the error 42
| |||||
| 258485 Return | FTP VIs do not close session if there is an error If any of the high level FTP Functions such as FTP Get File.vi and FTP Get Buffer.vi experiences an error within the VI, the FTP session stays open and the user remains logged into the FTP server. This seems to be because the FTP Close.vi within it does not execute if there is an error. Workaround: N/A
| |||||
| 277392 Return | Typecast of object with different binary size may crash LabVIEW If you attempt to typecast a data type into a new data type with a different size, especially if it is smaller, you may crash LabVIEW at that time, or later, when you attempt to use the new item. Workaround: Do not typecast using inputs and outputs of different sizes.
| |||||
| 255466 Return | Shared variable moved from a project directly to a tab control is not added to the active page. Workaround: After dragging the variable to the tab control. Reselect it and drag it slightly until the dotted lines appear around the tab control page and then drop it. The shadow is then removed because the variable has been added to the active page.
| |||||
| 192804 Return | Error 91 occurred at the Variant To Data node Variant To Data sometimes throws an error 91 when running in a built executable in LV 2009"Error 91 occurred at ...Possible reason(s):LabVIEW: The data type of the variant is not compatible with the data type wired to the type input." Workaround: 1) Update the variant type by generating a new one. (In an empty VI wire the typedef into the "data to variant" prim and run the VI. Then create a constant from the indicator and use this constant as the new type for the variant.)OR2) Use a Flatten Variant to String and then an Unflatten from String (not the variant version). If you wire in the control you're trying to extract from the variant, it will work like a charm.
| |||||
| 289842 Return | Get Variant Attribute VI returns wrong value if attribute not found The default value that's returned by the Get Variant Attribute VI is not blank when nothing is wired to the default value terminal. The Get Variant Attribute instead seems to return the last/previous value it returned as the default value. Workaround: Use the Found? output and logic to return a blank variant if necessary
| |||||
| 306205 Return | Error 1003 when building an executable with OpenTrace.vi within a LabVIEW Class If you are building a stand alone LabVIEW executable that has the polymorphic OpenTrace.vi within a LabVIEW class error 1003 will occur during the build. Workaround: Call the individual instance of the OpenTrace VI (Open Trace (Numeric), Open Trace (Logical), etc) instead of the polymorphic VI. These VIs can be found at C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\lvdsc\historical.
| |||||
| 279373 Return | SMTP has been updated to use port 587; LabVIEW makes use of legacy port 25 The SMTP has been updated to use port 587 instead of port 25. LabVIEW still makes use of port 25 with its SMTP VIs. Workaround: Open any SMTP VI, and find the SMTP_CreateSession.vi. Open that VI, you will find a numeric constant on the block diagram that is set to 25.
| |||||
| 202192 Return | LabVIEW UDP broadcast is inconsistent across different OS's. If the UDP Open VI has 0.0.0.0 wired to the Net Address terminal, the behavior varies with OS. Windows XP and NI ETS will send on all interfaces, while Windows Vista, Windows 7, VxWorks, and Linux will send on the default interface. Workaround: N/a
| |||||
| 465817 Return | LabVIEW converts a Double Precision numeric "NaN" value to integer data types differently since LabVIEW 2010 For example, when converting to U32, LabVIEW 2009 converts a "NaN" Double Precision numeric to 0. In LabVIEW 2010, "NaN" is converted to 4294967295 for a U32. Workaround: Check if the numeric is NaN with the "Not a Number/Path/Refnum?" Function.
| |||||
| I/O Servers | ||||||
| 286917 Return | DSC Periodic I/O Servers run as SYSTEM and creates a security vulnerability Period I/O server runs within the Shared Variable Engines (tagsrv.exe) in the SYSTEM security context. Any user on the machine (excluding guests), regardless of security level (administrator, user, power user, etc...) can deploy a Periodic I/O server to be run by the Shared Variable Engine. This makes it possible for a non-priviledged user to run LabVIEW code at a higher permission level than they are allowed. This is commonly know as a priviledge escalation vulnerability. (This does not apply to guest users as they seem to be unable to deploy LabVIEW Web services)This is dangerous as the Application Web Server is automatically installed and enabled (at least in LabVIEW Beta 2), allowing any user on the machine to use this vulnerability to execute code in the SYSTEM security context without having to enable or modify anything. This invalidates Windows user security. Workaround: 1. Open the Service Control Manager (in Vista and Win 7 simply type "Services" in the "Search for Programs and Files" box in the start menu.2. In the service control manager, find "National Instruments Variable Engine" 3. Right click and select "Properties" in the popup menu.4. Click on the tab labeled "Log On"5. In the dialog, click on the radio button labeled "This account:"6. Select a user account on your machine or domain that does not have administrator privileges on the machine itself.7. Click OK8. Restart the service by right clicking on it in the service control manager again and selecting "Restart".
| |||||
| Installation and Activation | ||||||
| 166253 Return | LabVIEW.app does not show up after LabVIEW 2009 Installation Workaround: This is only an issue for customers who installed the LabVIEW 2009 Beta for Mac. Delete /Library/Receipts/LabVIEW*9.0.pkg before running the LabVIEW 2009 installer for Mac OS.
| |||||
| 235446 Return | LabVIEW Installer doesn't install .NET support if only .NET 4.0 is installed. If you are using a machine that ONLY has .NET 4.0 our installer will not install .NET support. This should only be a problem with Window XP as later version of Windows install .NET 3.5 by default Workaround: Install .NET 3.5 and restart the installation
| |||||
| LabVIEW Environment | ||||||
| 36543 4039KEG8 Return | Edit-time crashes when many modules, drivers, and toolkits are installed Edit-time crashes during various operations (right-click menu selection, VI save, moving a VI from one block diagram to another, building an application [executable], shared library, or source distribution, etc.) can result from LabVIEW's image table overflowing from large amounts of palette icons being loaded in memory due to many installed modules, drivers, and toolkits. In this scenario, may receive LabVIEW error log files reporting "You filled the image table" in image.cpp. Workaround: In Tools->Options->Controls/Functions Palettes, change the Palette Loading from "Load palettes in background" (default behavior) to "Load palettes when needed" and restart LabVIEW. This workaround does not work if you: 1. Perform a palette search. 2. Click "place me on diagram/front panel" from the LabVIEW Help.
| |||||
| 105509 Return | The "do not save automatic changes" setting does not affect libraries The "do not save automatic changes" options setting does not affect any type of library, including classes. Workaround: N/A
| |||||
| 117209 Return | Bundle by Name does not break VI when fields from the input cluster's typedef are deleted Workaround: Change the data type (numeric to string, string to numeric) of the cluster element to be deleted to force breakage at all references to that member. Repair the broken VIs and then remove the cluster element. Or you can delete the cluster element, save (keeping the control open), then mass compile.
| |||||
| 43671 4GID11F2 Return | Opening VI Properties Window takes a long time When I try to open the VI properites window of a VI it takes a very long time to open. This can occur when you are using a network shared printer (as printer default), and that printer is offline. Workaround: Set default printer to "Microsoft Office Document Image Writer" for example.
| |||||
| 148149 Return | Event Structure Cases can Incorrectly Remap to Other Dynamic Events When deleting a user event refnum from a cluster which is input to a Register For Events Function, the associated Event Structure cases can be swapped. Workaround: Make sure User Events registered multiple times like this have unique names. On the attached VI, all the User Events have the same name "Event A". Popup on each Event refnum control, choose "Show Control", then show the control's label and renamed it to match the top-level type name, or some other unique name.
| |||||
| 173963 Return | Pressing "Stop" while dropping Snippet with SubVI that cannot be located hangs LabVIEW Workaround: Do not press Stop, use Ignore instead.
| |||||
| 154260 Return | Context Help does not update for controls or indicators placed in a tab control on front panel Workaround: Right click on the item in the tab control and go to Properties»Documentation and add a custom Description for that item. Doing so will then allow the custom description and the data type to be shown in the context help when mousing over the item.
| |||||
| 95055 Return | Save for previous fails if file path is too long Save for previous copies the folder being saved to a temp location; if the resulting file paths exceed the limit defined by the OS, the function fails. Workaround: Copy the folder being saved to the root directory to reduce the file path length and Save for Previous from that location.
| |||||
| 185226 Return | FXP configuration diffs don't show up when comparing VIs Front panel type differences will be reported, but not node configurations Workaround: Manually Inspect
| |||||
| 243625 Return | Nested libraries cause unnecessary dirty dot. If you have nested libraries and load the child library the higher level libraries will open with a dirty dot. This applies to classes as well Workaround: N/A
| |||||
| 256141 Return | Windows 7 often shows "(Not Responding)" and will bring other windows to the front during expensive operations If Windows 7 if a window is unresponsive to user input (e.g. mouse clicks) for five seconds it will ghost the window and display "(Not Responding)".Some operations in LabVIEW run in the UI thread. This is to prevent different operations from happening in parallel (e.g. compiling, edit operations, saving, drawing, etc.). Because large block diagrams can take longer than five seconds to compile or run clean up on Windows can tag LabVIEW as Not Responding.In some cases the ghosted window can move behind the other open windows when it finishes it task. Workaround: Wait until the expensive task as finished before trying to interact with the window.
| |||||
| 250119 Return | LabVIEW crashes if you delete a compound arithmetic primitive with a breakpoint Workaround: Remove breakpoint first, then delete.
| |||||
| 258758 Return | Setting digits of precision in Distributed System Manager has no effect. Workaround: N/A
| |||||
| 277283 Return | When creating a VI Snippet with code that contains a tab control, the snippet does not properly save the contents of each tab. Workaround: N/A
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 245609 Return | Swapping Connector Pane terminals loses Required status If you use the switcheroo tool to switch connector pane terminals this will re-categorize the terminals as Recommended. Previously tracked as CAR 277047 Workaround: Set the status of the terminals after switching.
| |||||
| 257275 Return | Format Into String does not work with the %d format for numbers larger than I32 The Format Into String VI does not correctly format numbers outside the 32-bit integer (I32) range when using the '%d' format. When the number is outside the I32 range, the resulting string displays either -2147483648 or 2147483647 depending on if the number is negative or positive. Workaround: Use %.0f instead of %d as the format string.
| |||||
| 254317 Return | LabVIEW can crash when deleting broken wires. LabVIEW will sometimes crash when deleting sections of block diagram code that contain broken wires. Workaround: Use Ctrl+B to delete broken wires
| |||||
| 276766 Return | Flat Sequence Structure leak GDI Objects, wasting memory and eventually crashing LabVIEW This leak occurs when the Flat Sequence Structure is moved. Using the keyboard create many different moves of a small distance. Using the mouse creates one move of a larger difference. Workaround: Use data flow and case structures to force execution order
| |||||
| 278029 Return | Changing an case selector from I64 to U32 can cause a corruption If you originally have an I64 wired to a case selector terminal and then change it to U32 the case structure will become corrupt and will eventually thrown an insane object error. Workaround: If the real need for change is the source and not the case structure itself, drop a conversion bullet in front of the Case structure so the input to the case structure is not changed.
| |||||
| 281124 Return | Nested diagram disable structures can cause LabVIEW to no compile. If you place a diagram disable structure with both cases disabled on your block diagram, you get an broken run arrow and an error from LabVIEW saying "Diagram disable structure has no active diagram".However, If you place a diagram disable structure with both cases disabled inside the disable case of another diagram disable structure you don't get a broken run arrow. When you try to run the VI you get the error message, "LabVIEW Needs more memory to compile". Workaround: N/A
| |||||
| 238713 Return | 3D Picture Controls can display transparently or crash LabVIEW on certain graphics cards The 3D Picture Control is built on a OpenSceneGraph which uses OpenGL. Several reports of the 3D picture control crashing LabVIEW have been reported. In almost all cases it was an Intel integrated graphics card involved. This crash is caused by an incompatibility of the graphics hardware.Note: Many of the 3D Graphs use the 3D Picture Control Workaround: There have been several things that have worked for users:
| |||||
| 305928 Return | Saving a VI that has separated compiled code will leak memory When you save a VI that has Separate compiled code from source file selected it will leak memory the same size as the source VI. Workaround: N/A
| |||||
| 250532 Return | ConnectorPane.cpp can cause a VI to be unable to load This internal warning can cause a VI to have a corrupt connector pane. If this occurs you will get Error Code 3: Cannot load front panel, when you attempt to open the VI. Workaround: For more information, see KnowledgeBase 520GHNKU: LabVIEW Load Error Code 3: Could Not Load the Front Panel in the Development Environment.
| |||||
| 321876 Return | VI Password Protection can be defeated It is possible for an attacker to defeat a VIs password protection. This issue will be marked as fixed when the information is in the LabVIEW Help. Workaround: Use Remove Block Diagram for maximum protection.
| |||||
| 244551 Return | Editing large strict type definitions can take a long time to update When large type definitions are updated, all instances in memory require an update. This update can take many minutes for very large type definitions. Workaround: Use smaller type definitions, or consider using LabVIEW classes to contain your type data.
| |||||
| 358049 Return | When a specific VI is opened, and then closed, LabVIEW remains in the task bar, with no windows open. n/a Workaround: Do not set a VI to "Open front panel on load" and "Run when opened" at the same time. If you must do this, do not use it as a subVI.
| |||||
| 359369 Return | Application Font change not applied correctly when pasting text n/a Workaround: Set the font manually before pasting text.
| |||||
| 369142 Return | Front Panels may stop updating with 3+ monitors with Windows Aero enabled With Windows Aero enabled on a machine with 3 or more monitors the front panel may stop drawing. This issue has been seen in limited cases and is usually after hours of operation. The application itself continues to run. Moving or minimizing the window causes it to start updating again. Workaround: Disable Windows Aero by selecting a non-Aero theme.
| |||||
| 305978 Return | Save As Duplicate with Include All Dependencies makes a Copy of the instr.lib Folder. Include All Dependencies option in Save As does not ignore files from laview\instr.lib folder. Workaround: Choose "Select contents to copy" and uncheck instr.lib
| |||||
| 408790 Return | Palette Editor Cannot Add LabVIEW Classes LabVIEW Classes are an available option to be added to palettes, but adding them will not take effect. Workaround: If your goal is to allow dropping of the class control or constant, you can create a custom control (not a typedef) that has the class on it's panel and add the custom control to the palettes. If your goal is to add the LabVIEW Class as a linked library, you can do so programmatically with Write Palette.vi.
| |||||
| 453896 Return | Error message encountered during TestStand Deployment Utility build process may show incorrect list of VIs If a VI linking error occurs while building a TestStand deployment, an error message is generated with a list of VIs causing the error. In some cases, this list may be incorrect or incomplete. Workaround: This issue is fixed in the LabVIEW 2013 SP1 f2 Patch
| |||||
| LabVIEW Object Oriented Programming | ||||||
| 52027 4A4GRP00 Return | Cannot use the 'New>>VI for Override...' dialog to create override of password-protected VI unless you have the password You use the 'New>>VI for Override...' dialog to override an ancestor VI in a LabVIEW class if the VI you want to override is password-protected. Workaround: Make a public VI which wraps the functionality of the private VI, and instruct others to override the public VI.
| |||||
| 178273 Return | "Must Override" doesn't break descendant classes if ancestor implementation is renamed On a parent class, mark one dynamic dispatch VI as "Must Override". Now add an override VI in the child classes so that the hierarchy is not broken. Now do Save As:Rename on the parent VI. The child classes should be broken because they no longer have an override for the VI that changed its name, but they are not broken. Workaround: Unloading the classes and reloading them will correctly break the classes.
| |||||
| 185059 Return | Member VIs of a class that is a member of a project library have a red X on them in the palettes Normally this red X only appears when you put private or unlicensed VIs into the palettes. VIs marked with this red X still drop on block diagrams successfully. Workaround: You can create a set of Merge VIs that are not part of the class that have just a single subVI on their block diagram that is the class VI you wanted to drop.
| |||||
| 103315 Return | Creating a circular link between an Xcontrol and a LVClass can crash LabVIEW. The circular load leads to VIs that are permanently broken and no matter what you do the run arrow will not become fixed. Workaround: Do not create a circular link from your XControl to your class. In other words, write your class completely and then write your XControl using the class. Do not put the XControl or any property/invoke node for the XControl into member VIs of the class.
| |||||
| 246263 Return | LabVIEW Class Properties don't output or produce invalid input in LabVIEW, crash or produce invalid output in built applications Some VIs that use Dynamic Dispatch LabVIEW Class Properties may crash or produce invalid data. This is caused by an incorrect behavior in associating property nodes with the properties represented in the LabVIEW Classes. Workaround: In some cases changing the property accessor's class input and output terminals to static and then back to dynamic dispatch will help. In other cases there is no work around.
| |||||
| 255982 Return | Child Class Property Node does not output until deleting and rewiring any part of the VI This issue pertains to Object-Oriented Programming in LabVIEW. Essentially upon creating a Parent class and Child class, we are unable to read the child class properties in the main VI through property nodes unless we have changed the VI recently (i.e. unwire & rewire). Workaround: The workaround for this issue is to use subVIs created from 'VI for Dynamic Dispatch Template.' Within the subVIs you are able to unbundle and bundle the object.
| |||||
| 278559 Return | Nested classes in a packed project library breaks a VxWorks VI. When building a packed project library that includes nested classes for a VxWorks target, the VIs in the built library are broken. However if you build for a PharLap or Windows target, there aren't any issues. Workaround: Use a debuggable packed library
| |||||
| 279298 Return | Deploying a VI with OO Accessors can cause internal error 1394 Certain LabVIEW classes can cause deployment errors if they contain accessor methods that are available as property nodes. The possible errors that occur are internal error 1494 or an RTEmbEditor.cpp DWarn at line 105. Workaround: Recompiling the VI may offer a temporary solution but replacing the property nodes with regular accessor methods should fix the problem.
| |||||
| 245148 Return | Class Properties dialog sometimes throws timeout error 123 when opening and must be restarted In LV 2010, there appears to be a timing race condition in the Class Properties dialog for LabVIEW classes. Every once in a while if you try to launch the dialog, the dialog will throw an error dialog reporting error 123 that the dialog has timed out while trying to launch. After you dismiss the dialog, you may see a secondary error dialog. Once you dismiss that, you can relaunch the Class Properties dialog and will generally succeed. There is no danger to your class and no corruption to you class file has occurred. It is solely a bug in trying to launch the dialog. Workaround: Hit Continue or OK button to dismiss all error dialogs that come up then retry opening the Class Properties dialog.
| |||||
| 283943 Return | Many VI Server methods work across contexts and use variants, which can crash LabVIEW when provided with context sensitive data (such as LabVIEW Classes). Writing a VI which passes or returns variants with a VI Server method or property to interact with a VI open in another context can crash LabVIEW when using context sensitive data (such as LabVIEW Classes). Workaround: Make sure that any interaction with context sensitive data is performed by a VI loaded in the same context as the target. If you need to give commands to a target in another context, you may need to load a helper VI in the target's context and use simpler datatypes to instruct the helper VI how to interact with the target.
| |||||
| 284936 Return | Breaking one Override VI in LVOOP shows all siblings as broken but does not explain why When using OOP in LabVIEW, breaking the connector pane of a child class Override VI will make all of its sibling override VI's appear broken even though they are not broken. Hitting run on the broken Run Arrow of any child class Override VI will list all of the child class VIs in the list of "Items with Errors", but none of them will have an error associated with it except for the broken ones. Workaround: Use the red X in the errors window to find the actual broken VI
| |||||
| 293342 Return | Preallocated reentrant LabVIEW Class Property accessors cause LabVIEW to crash When you change a LabVIEW Class Property accessor to preallocated reentrant, LabVIEW may crash. The crash will be soon after making the change. The crash only occurs when there is an open VI which uses that property more than once. Workaround: N/A
| |||||
| 294981 Return | Creating a copy of a class and adding it to the current project from the Save As dialog may crash LabVIEW A bug exists in LabVIEW which may cause it to crash when using "Save As" to create a copy of a class and add it to the current project at the same time. If you have a class that has LabVIEW class properties and that class contains a VI which uses those properties, LabVIEW may crash when adding that class to the project. This only occurs when you use the check box in the Save As Dialog that says "Add copy to XYZ.lvproj" Workaround: Don't add the class to the project from the Save As dialog. Once you've saved a copy, add it to the project separately.
| |||||
| 179603 Return | Call Parent Node input must be the same as dynamic dispatch terminal. When using the call parent node in a VI with dynamic dispatch terminals, the data must flow from the terminal to the Call Parent Node. If not the VI should break. In LabVIEW 2010 and previous this doesn't break. However this will break in LabVIEW 2011 with the error message: "The data from the dynamic input must flow to the Call Parent Node; however, you can modify the data along the way. In this error, there is no wire path that leads from the dynamic input front panel terminal to the dynamic input of the Call Parent Node. Without such data flow, a child class may violate the functionality contract established by its parent class." Workaround: Turn off the output's "Dynamic Dispatch Output" option.
| |||||
| 233061 4AQA5L00 Return | LabVIEW crashes after working with Simulation Subsystem using a LabVIEW Class Sometimes LabVIEW will crash after working with a Simulation Subsystems that has a LabVIEW Class as one of its controls or indicators on its connector pane. Usually it is only a problem when working with the Subsystem's caller within a LabVIEW Project. The crash will occur after closing the project, while returning to the initial LabVIEW window. Workaround: Save all work before closing the LabVIEW Project when using LabVIEW Simulation and Classes together.
| |||||
| LabVIEW Project | ||||||
| 163371 Return | "Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner library Old Description :"Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner libraryIf you have a nested library, a library that is owned by another library, and you use Save As:Copy, there is an option to add the duplicate library to the original owner library. If you use this option, the member VIs of the duplicate library are all broken because they are not correctly named as members of the owning library.This bug affects all types of libraries, .lvlib, .lvclass, .xctl and .lvsc. Workaround: Option 1: Do not use the "add to owning library" option and instead add the duplicate library to the owner manually after the copy. Option 2: After the copy operation, open and close one of the new VIs and then move the duplicate library out of the owner library. Browse to any missing VIs that pop up a browse dialog. Move the duplicate library back into the owner library.
| |||||
| 232348 Return | Changes to a library item's access scope sometimes do not update broken callers. Changing a library item's access scope sometimes does not update callers which are broken only because they were attempting to access an item which was out of scope to them. Workaround: Force recompile (ctrl+click on the run arrow) any VI which incorrectly believes that access scope forbids access to it's dependency. Changing the access scope to another value, then back to the desired value while the VI is open will also fix the issue.
| |||||
| 242778 Return | Library (or class or XControl) may become corrupted by saving a reference to non-existant untitled VI If you create a new, untitled VI in a library (including .lvlib, .lvclass and .xctl files) and then disconnect the untitled VI from the library but keep the VI open in memory, the library will often not actually disconnect entirely from the VI, and when you save the library, it will be saved with a reference to a non-existent untitled VI. When you later load that library, the blank VI will be recreated, but the library will report itself as broken because of a missing VI, and the library will have no obvious way to be fixed short of recreating the library from scratch. Workaround: Open the library file in a text editor. Find an tag where the Name attribute refers to an untitled VI. Delete that tag (everything from the to the ) and save the library file. This fixes the corrupt part of the library.
| |||||
| 257735 Return | Class VIs that call shared variables in a library in an auto-populating folder will not be loaded If a VI in a class calls a shared variable that is in a library in an auto-populating folder, it will not find the shared variable when the project is loaded Workaround: Make the folder a snapshot instead of auto-populating and reopen the project
| |||||
| Logging | ||||||
| 318415 Return | Error reading LVM file "Incorrect file type" If you save data to a LVM file using the "Overwrite once, then append to file" mode, you can potentially get an error when reading this file back. The error will show up as "incorrect file type". The problem is that the step reads back the file in 65K chuncks and if this chunk happens to end in the middle of a header section, the step will give this error. Workaround: A potential workaround is to add a few extra lines in the beginning of the file and thus shifting where the next 65k chunk starts. Also, in general, the LVM file type is not the best file format for overwriting the file with multiple sections, thus it's better not to use this mode
| |||||
| Miscellaneous | ||||||
| 249370 Return | In LabVIEW 2010 on a Mac, you cannot save VIs with the .vit and .ctt file extensions (Mac OS Only) In LabVIEW 2010 on a Mac, you cannot save your VIs as .vits or .ctts. (Saving to .ctl works) Workaround: Rename the VI on disk unless the VI or Control is a member of a library. If it is a member of a library, move it out of the library (in the project tree) first, then save it, remove it from the project, change its name on disk, and finally move it back into the library.
| |||||
| 247384 Return | TestStand Error -18004 When Attempting to Configure or Execute LabVIEW 2010 VIs While Debugging My LabVIEW User Interface in LabVIEW 2010 If you are using TestStand 4.x with LabVIEW 2010, and have installed the LabVIEW 2010 Compatibility patch for your version of TestStand as suggested by KnowledgeBase 5BRA2TXU: NI TestStand 4.x patches required for compatibility with LabVIEW 2010 and later. When debugging your TestStand User Interface in the LabVIEW Development System, if you select Specify Module for a LabVIEW step, or if you execute a LabVIEW step, you will receive Error -18004 . Workaround: This has been fixed in the LabVIEW 2010 f2 Patch
| |||||
| 249566 Return | LabVIEW 2010 crashes with fpsane.cpp line 442 when "Modifications:Front Panel (or Block Diagram) Mods Bitset" property is used LabVIEW 2010 will crash, if you use the VI Modifications Bitset property node with a case structure (the output of the property node wired to the case selector) and then change the property node to be Front Panel Mods Bitset (or Block Diagram Mods Bitset). LabVIEW will crash if you try to save the VI or if you select the broken run arrow. Previously 276039 Workaround: Delete the existing case structure and replace it with a new one from the palette.
| |||||
| 244158 Return | LabVIEW 2010 crashes with image2.cpp line 250 when opening a VI with a constant set to 'View As Icon' If you create a (strict) type definition of a cluster and put a constant which is linked to this typedef on the Block Diagram with the View As Icon set, LabVIEW 2010 will crash if the typedef on disk is deleted and the VI containing the constant is opened again. You will get a Fatal Internal Error: image2.cpp line 250 Workaround: Do not use the 'View As Icon' option for constants if you intended to delete the typedef ctl file
| |||||
| 392232 Return | Autopreallocate Arrays and Strings VI Property Can Crash LabVIEW when not in FPGA Context Changing an FPGA VI to run in a context other than FPGA does turn off the VI property to Autopreallocate arrays and strings if it was previously turned on. Running a VI that has this property on and manipulates arrays or strings can cause LabVIEW to crash. Workaround: Uncheck the Autopreallocate arrays and strings VI property for the VI.
| |||||
| Operating System Specific | ||||||
| 157246 Return | The Property Node "Bring to Front" doesn't work in Windows Vista Workaround: N/A
| |||||
| 230799 Return | Crash on exit in process which calls a LabVIEW-built shared library on Linux A process which calls a LabVIEW-built shared library may crash on exit in some cases because the LabVIEW runtime engine is still trying to clean up while the process is shutting down. This usually happens only when the main process links directly to the LabVIEW-built shared library or when the shared library is loaded dynamically and then unloaded just before exiting. This should not happen if sufficient time passes between the unloading of the shared library and exiting the process. Workaround: Load the LabVIEW-built shared library dynamically using dlopen, close it using dlclose, and then sleep for around 100ms (ex, usleep(100000); ) before exiting the process.
| |||||
| 242799 Return | Code generation of DAQmx Assistant for Modular Instrument Express VIs fails on second attempt in LabVIEW 64-bit When dropping a DAQmx Assistant or or a Modular Instrument Express VI, everything, including code generation, works the first time, but if another Express VI is dropped, the config page appears, but no code is generated when the user presses [OK]. Workaround: For all versions of LabVIEW 32-bit on the 64-bit machine, disable the VI Server TCP/IP checkbox, exit, and try the code generation again in LabVIEW 64-bit.
| |||||
| 235775 Return | LabVIEW crashes in assembly deployment if lkads.exe is not running on Vista/Windows 7 If you try to connect to a target running the controller engine without the National Instruments PSP Server Locator service (lkads.exe) running, LabVIEW will crash. Workaround: Start the service.
| |||||
| 284688 Return | Japanese LabVIEW 2010 SP1 fails to launch when a third party toolkit is installed. If a third party toolkit using SoftKey licensing is installed on the system, Japanese LabVIEW 2010 SP1 will fail to launch. Workaround: Apply the LabVIEW 2010 SP1 f1 Patch.
| |||||
| 283709 Return | Logos Sockets should broadcast on all available NICs The behavior of a UDP broadcast on a machine with multiple network adapters has changed between Windows XP and Windows 7. It's not clear at the moment whether this change was introduced in Windows 7 or Windows Vista. In Windows XP, if a UDP socket is not bound to a specific NIC, a broadcast packet would be sent on all available adapters. In Windows 7, only one adapter is used (the one with the lowest numeric IP address, which is essentially random). This link gives further details:http://serverfault.com/questions/72112/how-to-fix-the-global-broadcast-address-255-255-255-255-behavior-on-windows Workaround: Setting the "ServiceBindTo" INI token to the MAC of the primary NIC will guarantee that broadcasts happen on that NIC. See this KB:http://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019MrxSAEHowever, this will not allow broadcasting on multiple subnets, and it will make the chosen NIC the only NIC which can perform Logos Sockets communication. New Logos XT communication will be unaffected, but this could be important for legacy apps. Note, however, that Logos Sockets can only ever use a single NIC, so any legacy app running on a mult-NIC machine has likely already bound all Logos communication to the appropriate NIC.
| |||||
| 306797 Return | Cannot create indicator/control/constant for refnum datatypes from XML property and invoke nodes LabVIEW for Linux cannot create indicators, controls, or constants for refnum datatypes from the XML Parser property or invoke nodes Workaround: N/A
| |||||
| 333279 Return | Calling the System Exec VI after calling the Pipe VI in LabVIEW for Linux will Hang LabVIEW. Workaround: Do not call the System Exec VI after calling the Pipe VI.
| |||||
| 286917 Return | DSC Periodic I/O Servers run as SYSTEM and creates a security vulnerability Period I/O server runs within the Shared Variable Engines (tagsrv.exe) in the SYSTEM security context. Any user on the machine (excluding guests), regardless of security level (administrator, user, power user, etc...) can deploy a Periodic I/O server to be run by the Shared Variable Engine. This makes it possible for a non-priviledged user to run LabVIEW code at a higher permission level than they are allowed. This is commonly know as a priviledge escalation vulnerability. (This does not apply to guest users as they seem to be unable to deploy LabVIEW Web services)This is dangerous as the Application Web Server is automatically installed and enabled (at least in LabVIEW Beta 2), allowing any user on the machine to use this vulnerability to execute code in the SYSTEM security context without having to enable or modify anything. This invalidates Windows user security. Workaround: 1. Open the Service Control Manager (in Vista and Win 7 simply type "Services" in the "Search for Programs and Files" box in the start menu.2. In the service control manager, find "National Instruments Variable Engine" 3. Right click and select "Properties" in the popup menu.4. Click on the tab labeled "Log On"5. In the dialog, click on the radio button labeled "This account:"6. Select a user account on your machine or domain that does not have administrator privileges on the machine itself.7. Click OK8. Restart the service by right clicking on it in the service control manager again and selecting "Restart".
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Performance | ||||||
| 256928 Return | LabVIEW crashes when closing a VI reference to a reentrant VI with shared clones when using TestStand LabVIEW crashes when a VI reference to a reentrant VI which shares clones between instances in the following scenario:TestStand's VI deployment tool is used to package VIs and create packed project libraries. In order to add the VIs to a packed library the tool will open references to all the VIs, add them to a library, save the library and all the files, then it adds the library to the project and closes the VI references. When the reference to the reentrant VI is closed LabVIEW crashes. Workaround: N/A
| |||||
| 256238 Return | Last iteration of parallel for loop may not execute in parallel when it has non-indexing output tunnels The last iteration of a parallel for loop may execute serially after all of the other iterations are finished when the loop has at least one non-indexing output tunnel. This can be particularly noticeable when the loop executes a small number of iterations and each iteration performs a large amount of work. Workaround: Remove all non-indexing output tunnels from the loop.
| |||||
| 289559 Return | Dynamically launching reentrant VIs is slower and requires more memory. If you dynamically launch a reentrant VI it will take approximately 2x more memory and be 2x slower than in LabVIEW 2009. Workaround: N/A
| |||||
| 389991 Return | Memory leak when calling LabVIEW DLLs from C with new threads. Workaround: This issue has been fixed in the LabVIEW 2012 SP1 f3 Patch
| |||||
| Remote Panels | ||||||
| 97181 Return | On a Mac, a VI that writes waveform data to a chart on the Web Server crashes the Web browser when accessed from a PC When posting a VI that writes waveform data to a chart inside a loop on the Web Server for remote front panels on a Mac, accessing the remote front panel from a PC may crash the Web browser. Workaround: Use graphs instead of charts. If chart functionality is necessary, you can programmatically create a history of data that gets plotted to the graph on each plot.
| |||||
| 181687 Return | Web publishing tool fails without error The web publishing tool may fail to start the web server if the port is already reserved, yet not return an error. Workaround: Ensure that the port to be used by the web server is not in use.
| |||||
| 202702 Return | RT Remote Panel license is not released when tab or browser window is closed Attempting to connect to remote front panel on real-time target from multiple tabs or windows in a browser causes remote front panel to exceed the connections. Closing these tabs or windows does not release the license connection. Therefore the exceeded connection limit message persists until the target is rebooted. Workaround: Reboot the RT target to reconnect to the remote front panel.
| |||||
| 136677 Return | Remote panels do not work if Internet Explorer is embedded in an ActiveX or .NET Container If a remote panel is built in LabVIEW 8.6 and embedded in an ActiveX or .NET Container in a LabVIEW 8.6 VI it will not display correctly Workaround: Use a remote subpanel. This is actually the recommended way to accomplish this task
| |||||
| 255627 Return | Remote Panels not working in LV 2010 built executables Remote panels work with regular VIs but when they are built into an executable they will not work. Workaround: N/A
| |||||
| 251105 Return | S&V XControls built as Remote Panel crashes LabVIEW. Remote panels do not reliably support the Sound and Vibration XControls. Workaround: Use another mechanism for remote viewing.
| |||||
| 258226 Return | Remote Panels cannot be viewed by Safari for Mac OS X 10.6 or later Versions of Safari that shipped with Mac OS X 10.6 or later do not allow plugins that make use of older graphics API's. This means that the Remote Panels plugin needs to be rewritten to work in current versions of Safari. Workaround: Use Firefox, or connect directly to the Remote Panel from within LabVIEW via the Operate » Connect to Remote Panel menu.
| |||||
| Shared Variables | ||||||
| 141699 Return | NI Distributed System Manager does not show deployed libraries if they contain non-Latin characters. If a library with non-Latin characters (such as Japanese, Chinese, or Korean) is deployed, it will not show up in the NI Distributed System Manager tree view. Workaround: Rename the library using only the Latin alphabet and re-deploy the library.
| |||||
| 128059 Return | Shared variable bindings in the same library are not updated properly when copying/renaming the library If you have shared variables in a library which are bound to I/O servers or other variables that are also in the same library, and you rename or save a copy of the library, the bindings still refer to the original library name. Workaround: Manually rebind the variables after copying or renaming the library.
| |||||
| 173080 Return | When a project that contains variables with binding is created in one language and opened in a different language, variables may fail to deploy Workaround: Open the project in the desired language, double-click on the variables with binding, and re-bind the variables.
| |||||
| 168005 Return | Dynamic Variable API Does Not Support I/O Servers that Use Ranges You cannot use the Variable classes, properties, and methods or the associated Shared Variable functions (Dynamic Variable API) to dynamically read and write PSP items published by an I/O Server that uses a Range item. For example, Modbus I/O Servers and Lookout Ranges are affected by this issue. Workaround: If you want to use the Dynamic Variable API to read or write one of these PSP items, you can create a network-published shared variable and bind it to the PSP item. Then you can use the Dynamic Variable API to read and write the bound shared variable.
| |||||
| 232466 Return | Replace with Programmatic Access is misleading for RT FIFO Enabled Shared Variables The Programmatic Shared Variable API does not support RT FIFOs for network-published Shared Variables. If a network-published Shared Variable with RT FIFOs enabled were to be converted from a static node to programmatic access using the "Replace with Programmatic Access" option from the right-click menu the generated code would not be functionally equivalent. Workaround: N/A
| |||||
| 186808 Return | Shared Variable library on PC is undeployed if the a V in the same project is programmatically deployed to a Real-Time target When programmatically deploying a VI to a Real-Time target the Shared Variable library residing in the same project as the deployed VI will be undeployed. Workaround: Programmatically deploy the shared variable library on the PC after deploying the VI to the real-time controller.
| |||||
| 284289 Return | Source distributions with block diagrams removed prevents the use of static Shared Variable nodes. Source distributions that include static Shared Variable nodes with block diagrams removed will return the following error at run-time, "VI has a bad connection to or cannot find a subVI or external routine." Workaround: Use the Programmatic Shared Variable API or do not remove the block diagrams.
| |||||
| 284802 Return | Programmatically enabling shared variable alarm leads to deployment error and mismatch between shared variable properties and the multivariable editor. When programmatically generating shared variables and enabling specific alarms (HiHi, LoLo, etc.), the shared variable properties do not match the multivariable editor Workaround: Programmatically generate the shared variables and manually enable the specific alarms using the multivariable editor.
| |||||
| 294285 Return | Type Defined Shared Variable not found in Executable When a VI is made with the following conditions:1) Uses a Shared Variable attached to a type definition2) The type defined control (attached to the shared variable) is not in the main project directory (ie, it is in a different folder)3) The VI uses dynamic data (or waveform to dynamic data function)A created executable seems to not include the *.ctl file defining the shared variable type. This missing type definition causes the run time engine, when starting the executable, to search for and (if the control is not located in the searched directories) fail to find the *.ctl file. If the location of the *.ctl file is specified, the executable runs without issues. Workaround: Disconnect from Type Def during the build.
| |||||
| 288455 Return | Shared Variable Not Updated When Changing Representation See KB 56PCQ3RR: Why Is My Shared Variable Not Updated When I Change Representation? for more information. Workaround: First Undeploy and then Deploy your variables again. A simple Deploy action will not have the required effect.
| |||||
| 257735 Return | Class VIs that call shared variables in a library in an auto-populating folder will not be loaded If a VI in a class calls a shared variable that is in a library in an auto-populating folder, it will not find the shared variable when the project is loaded Workaround: Make the folder a snapshot instead of auto-populating and reopen the project
| |||||
| Source Code Control | ||||||
| 123313 Return | Unnecessary IAK file checked into source code control When NI-FieldPoint is installed, and source code control is configured for LabVIEW, when you check in projects to source control the source code provider attempts to check in an IAK file for the project, even if one does not exist. Workaround: If a dialog appears when checking in file, do not check in the iak file if it is not necessary for that project.
| |||||
| 229641 Return | Hang can occur when deploying RT project that has not been check out of VSS When using VSS source code control for a real time project and trying to deploy code that has not been checked off the deployment window blocks a pop up from VSS saying that the code has not been checked out. The deployment status window is modal so it does not allow you to select to proceed in the VSS window. Workaround: In the LabVIEW project properties disable the prompts from source code control. Or you could make sure that the VIs are saved prior to deploying.
| |||||
| Toolkit - Report Generation | ||||||
| 188911 Return | Control image alignment incorrect when "new report page" VI is used When using Append Control Image to Report.vi, the alignment of some images are ignored when New Report Page.vi is used between appended images. This problem only exists with Office 2007. Other versions - Office 2003 and Office 2010 do not exhibit this behavior. Workaround: Use a New Report Line.vi between appending the image and the New Page.vi
| |||||
| Upgrade - Behavior Change | ||||||
| 51185 47FGSQCS Return | Cannot save VI as the same name as missing library member VI If a library contains a VI and the VI is missing, you should be able to save a VI as the same name as the missing VI in order to rebuild the missing VI. Currently, LabVIEW does not allow this. Workaround: Delete the item from the library, save the new VI as the same name as the missing VI and then move the VI into the library.
| |||||
| 52263 4AJA41TQ Return | Some operations on integer waveforms lose dt value Some functions, such as Absolute Value and Logarithm Base 10 operate as you expect with DBL Waveforms, but when you apply the same functions to an I16 waveform, for example, the Absolute Value function works as you expect while the Logarithm Base 10 function loses the sampling interval dt value. LabVIEW resets the sampling interval dt value to 1.00. If the input waveform to the log function has a time stamp for t0, that value is also lost. Workaround: Extract the Y-array of the waveform and perform the needed operations on Y before re-building the waveform.
| |||||
| 119444 Return | Multi-column listbox format lost on upgrade A Multicolumn listbox created in LV 7.1 may lose its format when opened in LV 8.5 or later. Column headers lose their 3D appearance and font formatting might be lost. Workaround: Replace the Listbox and recreate all customizations
| |||||
| 119204 Return | Plot Legend Does Not Update When Using Property Nodes When the properties of a plot legend are changed by property node or by a reference and a property node, the legend does not redraw. Workaround: A redraw can be forced by changing the property node Plot.Name, changing the property node Legend.Visible, or a mouse movement over the plot legend.
| |||||
| 198717 Return | Unflatten From XML fails for cluster and arrays that consist of variants Creating a cluster that contains a variant or building an array of variants, and then trying to flatten it to XML using the Flatten To XML VI and then unflattening it using the Unflatten From XML VI will throw error 1106 Workaround: N/A
| |||||
| 218083 Return | VIs with errors may show additional errors for code in disabled frames of Conditional Disable Structure If you have a VI that has errors in it, there may be additional errors shown. The errors will be in code that is inside of a disabled frame of the Conditional Disable Structure (in the "Default" or "Windows" frame when on RT). Workaround: Fix the other errors in the VI, and the additional errors should go away.
| |||||
| 221113 Return | CLFN with the wrong calling convention may silently crash LabVIEW LabVIEW 8.5 through 2009 could adjust the calling convention at run time if the user selected the wrong option. In 2010 this no longer happens. More information is found in KnowledgeBase 59KB14WI Workaround: Use the correct calling convention
| |||||
| 242603 Return | LabVIEW 2010 crashes on compile if you have a divide primitive with dominator less than 1 wired to the for loop count terminal (N) LabVIEW 2010 will crash on save, or load from a previous version (pre-2010) of any VI that meets all of the following conditions:1. Contains a For Loop with an upstream computed constant expression wired to N2. The computed constant expression must contain a divide primitive somewhere3. The computed denominator must be a floating point value that would coerce to an integer value of zero (-0.5 < x < 0.5) Workaround: This has been fixed in the LabVIEW 2010 f2 Patch
| |||||
| 243106 Return | Broken wires or bad terminals with Insert Into Array primitive crashes LabVIEW 2010 Certain cases such as broken wires or bad terminals associated with the Insert Into Array primitive results in a crash when upgrading code from LabVIEW 2009 (or earlier) to LabVIEW 2010 Workaround: This has been fixed in the LabVIEW 2010 f2 Patch
| |||||
| 251397 Return | Broken wires or bad terminals with Insert Into Array primitive crashes LabVIEW 2010 Certain cases such as broken wires or bad terminals associated with the Insert Into Array primitive results in a crash when upgrading code from LabVIEW 2009 (or earlier) to LabVIEW 2010 Workaround: N/A
| |||||
| 246966 Return | Write to Text File output changed from LabVIEW 2009 to 2010 if the user selects cancel in the file dialog In LabVIEW 2009, canceling the file dialog when you leave the Write to Text File function's 'path' input unwired returns Error 43, "Operation cancelled by user," and the 'cancelled' output is TRUE. In LabVIEW 2010, canceling the file dialog when you leave the Write to Text File function's 'path' input unwired returns various undefined errors, and the 'cancelled' output is always FALSE. Workaround: N/A
| |||||
| 276831 Return | Output of zero generated from the multiply node with certain DAQmx properties and VIs when using highlight execution Workaround: Use indicators for debuging
| |||||
| Upgrade - Migration | ||||||
| 138552 Return | Load VRML File.vi missing "error in" terminal In LabVIEW 8.6, the "error in" terminal was removed from the Load VRML File.vi. LabVIEW 8.2/8.5 has this terminal. Thus, if a VI that has the Load VRML File VI is upgraded to 8.6, the previously working VI will be broken. Workaround: Place a case structure around the Load VRML File VI to handle the error manually.
| |||||
| 147187 Return | Crash using Xscale Info or YScale Info graph properties Graph properties Xscale Info and YScale Info available in LabVIEW 6.0 are no longer available. Using these properties will cause your VI to crash when executed. Workaround: Use newer individual properties XScale.Range etc. to adjust your graph properties.
| |||||
| 246375 Return | Unexplained broken wire when local variable of Chart control interacts with uninitialized shift registers A Chart changes its type to match the type of the wire connected to its FPTerminal. If you create a local variable of the Chart, that local variable will also change its type to match the FPTerminal. If both the local variable and the FPTerminal are inside the same loop AND the wire going into the FPTerminal is coming from an uninitialized shift register, then there are rare situations in LabVIEW 2010 where the wire going into the local variable will end up broken and complaining about incompatible types even though the types on both ends of the wire are identical. This bug does not exist in LV 2009 or earlier. Workaround: Set the type going into the FPTerminal explicitly instead of relying upon the type calculated by the uninitialized shift register. Methods for doing this will vary greatly between diagrams.
| |||||
| 257197 Return | Error Constant erroneously added to Variant to Data Workaround: Fix the diagram after upgrading.
| |||||
| Web Server/Web Services | ||||||
| 243004 Return | Web Method VIs' Boolean Control Terminals are Inverted when Web Service is Called Web method VIs in 2010 have an issue effecting Boolean inputs. If a Boolean control is an input of a web method VI the value of this Boolean is the inverted when the web method is called. Workaround: This has been fixed in the LabVIEW 2010 f2 Patch
| |||||
| 234411 Return | RT Web Service Build error 1502 When building a web service for an RT Target error 1502 can occur. This error can occur when building a web service with a web method that contains a VI from the Web Services Palette. Workaround: Check the "Remove unused member of project libraries" in the Additional Exclusions category of the Web Service build specification.
| |||||
| 236817 Return | NI-Auth does not work with Firefox Web Services using NI-Auth work incorrectly in Firefox. A user's log in credentials will never be accepted. Workaround: Use Internet Explorer
| |||||
| 246540 Return | NI-Auth permissions get reset in build specification When setting NI-Auth permissions for a directory in a Web Service Build Specification the permissions do not persist between closing and opening the Web Service Build Specification Workaround: N/A
| |||||
| 256559 Return | Including .vi in web method name and using "?" as a query separator causes app web server to crash Workaround: Do not ever use .vi in the web method name in the URL
| |||||
| 246681 Return | lvwsdsc not generated correctly unless your VI is in your project directory If your web service VI is in a subdirectory under your project, then the lvwsdsc file does not generate the sections under each . This causes the Web UI Builder to not generate these as inputs to the generated wrapper VIs. Workaround: Use the 8.x file layout
| |||||
| 327431 Return | Import WebService Tool doesn't work for HTTPS protocol Web Services cannot be imported if they are on an HTTPS server. The same web service can be imported if it is on an HTTP server Workaround: Use an HTTP server
| |||||
Document last updated on 7/31/2014