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 2012 known issues that were discovered before and since the release of the LabVIEW 2012 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 2012 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 2012 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| ActiveX and .NET | ||||||
| 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.
| |||||
| 355840 Return | "Get Image" method is unreliable on .NET controls in LabVIEW (64-bit) Calling the 'Get Image' method on a .NET control works correctly on 32-bit versions of LabVIEW, but will fail to return an image intermittently when LabVIEW (64-bit). Workaround: n/a
| |||||
| 381128 Return | The MonthCalendar .NET control automatically resizes to the incorrect size when the VI is run N/A Workaround: At the beginning of the code write to the Container Bounds property node "ContBounds" for the .NET container. While the code is running the calendar will have the right size
| |||||
| 380475 Return | Data returned from a LabVIEW built .NET Assembly that unbundles a cluster is incorrect Calling a LabVIEW built .NET Assembly in LabVIEW occasionally returns incorrect values when the values come from an unbundled cluster inside of the assembly, and the assembly received the cluster from the calling VI. Workaround: N/A
| |||||
| 410479 Return | Grouping ActiveX containers removes inserted ActiveX objects When populated ActiveX containers are grouped with other front panel objects, the inserted ActiveX object will be removed. Workaround: Re-insert the ActiveX object after it has been grouped with another object, or group a blank ActiveX container, then insert the object.
| |||||
| 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.
| |||||
| 361311 Return | "Natural log of 1 + x" primitive incorrectly returns NaN for small positive values n/a Workaround: n/a
| |||||
| 368375 Return | Compound Arithmetic node will produce incorrect results when operating on units in LabVIEW 2012 The Compound Arithmetic node will mistakenly square the first input if the wire has a unit attached. Workaround: This issue is fixed in the LabVIEW 2012 f2 patch.
| |||||
| 388446 Return | Eval Parsed Formula Node.vi returns incorrect results Incorrect results are possible if preceding Parse Formula Node.vi contains too many C-style comments. Workaround: Reduce the amount of comments used in formula input to Parse Formula Node.vi
| |||||
| 408891 Return | Getting an Entire Column of Data from a 2D Array in the MATLAB® Script Node Returns Only 1 Element In the context of the MATLAB® Script Node, attempting to return an entire column of data from an array using a command like "column1 = array2D(:,1);" returns only a single element. This same operation on a row "row1 = array2D(1,:);" , returns the entire row successfully. Workaround: Transpose the array, and get the data in it's context as a row.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 320485 Return | User Events Created from Objects Cause Broken Packed Library VIs If you are using an object as a user event, it works fine while in the LabVIEW environment. However, when compiled into a packed library, the user event refnum has a broken wire. Workaround: N/A
| |||||
| 351741 Return | Panes 'Top' pixel coordinates will vary when Windows 'Aero' is enabled/disabled If the Windows Vista/7 option to "Use visual styles on windows and buttons" is enabled, a VI property node for Front Panel Window:Panel Bounds will return a different 'Top' value. Workaround: If you are calculating the position of elements within your VI based on this value, check the deployed OS, and subtract an offset value.
| |||||
| 346295 Return | You can't create a negative user-defined error codes in the Edit Error Code Assistant. n/a Workaround: Edit the Error file directly with Text-Editor
| |||||
| 347272 Return | Executables built (without SSE2) in LV 2011 on an Intel Core Duo machine throw Error 57 when run on a machine with an AMD Athlon 3200+ processor. n/a Workaround: Build the executable on the Athlon 3200+ computer.
| |||||
| 368396 Return | Certain applications built with Application Builder fail to launch Application will fail to launch with an error "Top level VI(s) could not be opened." Workaround: This issue is fixed with the LabVIEW 2012 f2 patch.
| |||||
| 385212 Return | Adding and removing a registry key from a build specification can cause the build specification to become corrupt N/A Workaround: Open the lvproj file with an editor and remove lines values referring to RegGroup and RegData manually
| |||||
| 362366 Return | Packed Project Library deployment fails on Real-Time targets Workaround: This issue has been fixed in the LabVIEW 2012 f1 patch.
| |||||
| 373150 Return | Error code 3 when running LabVIEW 64-bit applications using NI_AALBase.lvlib, that were installed with installers built in 64-bit LabVIEW Application Builder N/A Workaround: Include the 2009 Run Time Engine in your installer
| |||||
| 377164 Return | The Unlock file and folder attribute in an installer specification has no effect in LabVIEW 2012 N/A Workaround: N/A
| |||||
| 384576 Return | NI SSL Libraries not installed for LabVIEW Runtime Engine on Mac OS X Building an application with HTTP functions in Mac OS X throws error -1967362015 because the SSL Libraries are not installed Workaround: This issue has been fixed in the LabVIEW 2012 SP1 f3 Patch. Alternatively you can do the following:Rename "/Library/Frameworks/LabVIEW\ 12.0\ Runtime.framework/resource/ni_httpClient.framework" to "/Library/Frameworks/LabVIEW\ 12.0\ Runtime.framework/resource/ni_httpClient.framework.bak"
| |||||
| 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
| |||||
| 334314 Return | Creaing an Override VI for a child class that has a parent in a Packed Project Library gives error 1035 If creating an Override VI in a child class which has a parent in a Packed Project Library that the child is not part of, LabVIEW will throw error 1035 Workaround: Select VI for Dynamic Dispatch, and change the connector pane terminals and VI name to match the VI you are overriding
| |||||
| 374196 Return | A Call Library Function Node referencing a function that does not exist within an existing DLL will attempt to load despite being in a diagram disable structure. A Call Library Function Node that is within a diagram disable structure will load anyway if it is referencing a DLL that does exist, but a function within that DLL that does not exist. This will break the run arrow with no listed errors. Workaround: Open the VI and make any change to the block diagram, the error will go away until the next time it is loaded into memory.
| |||||
| 401421 Return | Updates to Global Variables Not Visible when Remote Debugging a LabVIEW Built Stand-Alone Application If the updates occured before connecting to the Remote Application with the debugger, the updates won't be visible. Updates to the Global Variable after connection with the debugger is establish will be visible. Workaround: Change the build specification for the stand-alone application to wait for debugger on launch, so no Global Variable updates can happen until a debug session is started.
| |||||
| 423616 Return | If a LabVIEW executable containing .NET is included in an installer, it will fail to run when installed If a LabVIEW executable contains .NET functions and is included in an installer with the LabVIEW Run-Time Engine, it will fail to run if it is installed on a system that has no National Instruments software on it. An error message will appear saying "The VI is not executable. The full development version of LabVIEW is required to fix the errors." Workaround: Either manually install the LabVIEW Run-Time Engine or install the National Instruments License Manager on the deployment system.
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 275961 Return | Silver style Thermometer frame doesn't resize correctly when control is resized. Workaround: N/A
| |||||
| 290105 Return | Text Labels in Silver Control are not in silver style Workaround: N/A
| |||||
| 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
| |||||
| 306025 Return | Changing Front Panel object's font properties affects all objects that were created after it Editing the font properties of graph objects on the Front Panel (Waveform Chart, Waveform Graph, XY Graph) changes the font properties of other Front Panel objects, not just the selected object. Any object that was added to the front panel after the selected graph object will also have its text properties (font, color, size, etc) changed as well. Workaround: Copy the control to a blank VI, make your changes, copy, select the control in the original VI and paste - it will replace the original control with the edited control and not affect other controls.
| |||||
| 314062 Return | Silver Listbox Control Does not Grey Disabled Item The silver listbox control behaves differently than previous listbox controls in LabVIEW. When you disable one or more items in the silver listbox it does not change their appearance to show that they are unselectable. You can not select them but, but it is not obvious to the user. Workaround: Make the background color of the cells white instead of transparent.
| |||||
| 314082 Return | Listbox Control With Transparent Cell Background Does not Grey Disabled Item n/a Workaround: Make the background color of the cells match the background of the panel, instead of making them transparent.
| |||||
| 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.
| |||||
| 363464 Return | Plots with reversed X axis display extraneous horizontal line On plots with a reversed X axis (e.g. 10 .. 1), an extra horizontal line is drawn on the graph. Workaround: This issue has been fixed in the LabVIEW 2012 f1 patch.
| |||||
| 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.
| |||||
| 361839 Return | Boolean constant & string constants grow to length of label when cluster is type defined n/a Workaround: n/a
| |||||
| 364462 Return | Crash when changing value of numeric within a typedef constant that was moved out of an array constant If you put a typedef that contains a Numeric (including sub-items, e.g. a cluster of numerics) into an array constant and then you move (or copy) the typedef out of the array, the Numeric will be corrupted. Workaround: Delete the corrupted element and create a new instance.
| |||||
| 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.
| |||||
| 366331 Return | Dynamic event registration of an array of controls fails with Error 1 When dynamically registering events for an array of controls, you will get an "Error 1 occurred at Register For Events" Workaround: N/A
| |||||
| 377021 Return | Primitives are not correctly overloaded for Silver Matrix controls Math primitives treat the Silver Matrix datatype as a 2D array, and will compute values element wise, instead of as matrices. Workaround: Use the Modern Matrix control.
| |||||
| 184689 Return | UI Performance degredation when displaying NaN values on 3D Surface Graph in LabVIEW N/A Workaround: N/A
| |||||
| 364845 Return | Streaming data to a Digital Display Chart data occasionally incorrectly displays zero even when the data is non-zero N/A Workaround: N/A
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 367249 Return | It is not possible to customize the Run-Time Shortcut menu of a 3D Graph N/A Workaround: N/A
| |||||
| 367463 Return | References returned by Property: Controls[] of a pane containing type definitions do not match VI Server References to the control N/A Workaround: N/A
| |||||
| 368466 Return | Plot visibility check box can not be toggled for plot 0 on an XY Graph N/A Workaround: Left-click on the legend icon for Plot 0 and toggle the "Plot Visible" property
| |||||
| 368973 Return | Editing the scale on a numeric control or indicator within an array causes LabVIEW 2012 to crash Workaround: Change the scale using the properties window
| |||||
| 376379 Return | Graphs and charts have slow performance with thick line style and large data range in LabVIEW 2012 N/A Workaround: N/A
| |||||
| 364607 Return | Invalid Network VISA reference causes DAQmx calls to slow in different loop Having an invalid Networked VISA reference and a DAQmx task in different loops causes the DAQmx loop to slow down to roughly the timeout of the VISA loop. Workaround: N/A
| |||||
| 375872 Return | Setting a floating point numeric control to Inf, -Inf, or NaN when it is configured for relative time display format crashes LabVIEW Workaround: Use a property node to set the value
| |||||
| 376714 Return | Using the Merge VIs utility with VIs that contain a tab control causes LabVIEW to hang Workaround: Manually edit the VI to include all the changes made in Theirs, and Yours.Do not use the Tab Controls shown in the attached VIs.
| |||||
| 398998 Return | 3D Surface Axis Labes not Visible when Dialog Font Changed Some fonts cause the Axis Labels to be visible on 3D Surface controls when the Dialog Font is changed from default. For example MS Sans Serif causes the issue. Workaround: Use a Dialog font that doesn't cause the issue.
| |||||
| 399068 Return | Double Numeric Slide can not be Set to 0 when it has Defined Limits with Mouse A user can not slide a Double Numeric Slide to 0 when it has defined increment, maximum, and minimum properties. Instead of 0, a value very close to 0 will be entered ie: 5.55112E-16. Workaround: Do not set both defined maximum and minimum for the slide. Instead, change one of them to Inf or -Inf. Also a value of 0 can be entered into the digital slide.
| |||||
| 407614 Return | Control.Delete Method Crashes LabVIEW When Used on Grouped Pictures and Free Labels LabVIEW will crash when VI scripting method Control.Delete is invoked on pictures or Free Labels that are grouped on the front panel. Workaround: N/A
| |||||
| 420965 Return | Adding a tooltip for a tab control after configuring the tab to show text and image can cause the tooltip to appear in the wrong position If you configure a tab control for text-image content, and then add an image and change the tooltip, the tooltip will appear far away from the tab control. Workaround: View the tooltip after adding the image and before changing the default tooltip
| |||||
| 414839 Return | Complex to Re/Im VI outputs incorrect value if the input is a complex waveform unless both terminals are wired Workaround: Wire the Im output
| |||||
| 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
| |||||
| 370957 Return | Specific type of cluster sent over the network may produce incorrect results Reading or writing data from LabVIEW for Windows (64-bit) via shared variables or network streams, or from LabVIEW for Mac or Linux via DataSockets, to an array of clusters that contain only numerics, may produce incorrect results. Workaround: This issue was fixed in the LabVIEW 2012 f3 patch.
| |||||
| External Code | ||||||
| 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"
| |||||
| 389295 Return | LabVIEW 2012 SP1 breaks custom prototypes in DLLs that contain LabVIEW classes This issue is fixed in the LabVIEW 2012 SP1 f1 Patch Workaround: N/A
| |||||
| 374196 Return | A Call Library Function Node referencing a function that does not exist within an existing DLL will attempt to load despite being in a diagram disable structure. A Call Library Function Node that is within a diagram disable structure will load anyway if it is referencing a DLL that does exist, but a function within that DLL that does not exist. This will break the run arrow with no listed errors. Workaround: Open the VI and make any change to the block diagram, the error will go away until the next time it is loaded into memory.
| |||||
| 429726 Return | LabVIEW crashes when .NET event callback calls a VI that has already been deregistered in LabVIEW. Workaround: This issue is fixed in the LabVIEW 2013 f2 Patch
| |||||
| 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"),
| |||||
| 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
| |||||
| 437390 Return | File Path control does not display "Browse" dialog if Start Path is an invalid network path. LabVIEW may hang while waiting for Windows to locate an invalid network directory. The control's owning VI may hang while it searches for the directory, or it may appear that the "Browse" button does not have any affect and does not invoke a dialog. This can happen if the Start Path input in Browse Options... is an invalid path or if the Start Path in blank and the control's value is invalid. Workaround: Make sure the Start Path input is valid before selecting the Browse button. If the Start Path input is blank, change the File Path control's value to a known valid path before browsing.
| |||||
| 464572 Return | Reading a datalog file truncated from more than 128 records returns error 4 "End of file encountered" 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).
| |||||
| 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.
| |||||
| 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.
| |||||
| 227030 Return | Wait on Notification from Multiple function has unexpected behavior when ignoring previous input. Workaround: See KB
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 295415 Return | Error message for External Data Value Reference is incorrect You may see an error message "This External Data Value Reference contains an unsupported type". on VIs that have other errors and use a DVR. This error message is invalid and will go away if you fix the other errors in your VI. Workaround: Fix the other errors in your VI and this error will go away.
| |||||
| 310513 Return | LabVIEW can crash when aborting a VI using Asynchronous Call by Reference In some cases, LabVIEW can crash when aborting a VI that contains a Wait On Async Call node before calling the Wait On Async Call Node. Workaround: Implement a stop functionality to your code and don't use an abort.
| |||||
| 359662 Return | Some dotted scripting property calls can crash LabVIEW if earlier properties error If you access the property LinkedControl.ClassName on an object that does not have a linked control error 1308 will be thrown. If you access the property 3 times, LabVIEW will crash. Workaround: Separate into two calls; e.g. change a property of LinkedControl.ClassName into a call to LinkedControl, which emits a reference and, if successful, wire that to a second property node to get ClassName.
| |||||
| 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
| |||||
| 321293 Return | Event structure: OldVal Event Data Node incorrect with combobox control events n/a Workaround: n/a
| |||||
| 335576 Return | Play Waveform Express VI gives error 4803 with Sample Rate 3125, 6250, 12.5K, 25K, 50K, 100K, 200K Hz n/a Workaround: Instead of using the "Play Waveform" Express VI, use the code from the example Generate Sound.vi.
| |||||
| 346762 Return | [Mac] Sound VI's Device ID doesn't correctly route audio to non-default output devices. Sound VI's can only output audio to Device ID 0 (usually the internal speakers), and can not successfully output audio to USB audio devices. Workaround: n/a
| |||||
| 353261 Return | Conditional Indexing Terminal on Parallel For Loop with Shift Registers Runs with "Memory is Full Error" Workaround: Use the Build Array in a Case structure
| |||||
| 371733 Return | Passing array data to a Formula Node may produce incorrect results or cause LabVIEW to crash. N/A Workaround: This issue was fixed in the LabVIEW 2012 f3 patch. For more information about the steps that are requires to ensure your code reflects the fix, see KB 629E67YS: LabVIEW 2012 f3 Patch Details.
| |||||
| 367468 Return | Wiring multiple inputs to Split Signals.vi causes LabVIEW to crash Under certain circumstances multiple inputs are incorrectly able to be wired to the Split Signals.vi causing LabVIEW to crash. Workaround: Do not wire multiple inputs to Split Signals.vi
| |||||
| 378888 Return | The Mixed Signal Graph does not correctly label plots in LabVIEW 2012 The Mixed Signal Graph in LabVIEW 2012 only correctly labels the first plot from NI-DAQ waveform attributes. Additional plots will not automatically have the correct labels Workaround: Use Property Nodes to set the plot names
| |||||
| 378947 Return | MD5Checksum File.vi returns the wrong value for files larger than 4GB N/A Workaround: N/A
| |||||
| 379444 Return | Register Event Callback does not function in LabVIEW 2012 Base Edition N/A Workaround: N/A
| |||||
| 382333 Return | The Match Regular Expression VI in LabVIEW 2012 on Linux crashes when the screen's color depth is set to 16-bit N/A Workaround: Change the color depth to "millions of colors" in the display user interface
| |||||
| 385324 Return | The Max&Min VI incorrectly compares NaN values in arrays of 16 or more With arrays of 16 or larger, the Max&Min VI will return NaN as both the Max and Min when NaN is compared with any value. With smaller arrays, the non NaN number is returned Workaround: Use the Max&Min function in a for loop so that it is comparing single values instead of arrays
| |||||
| 364281 Return | Specifying a file path with HTTP GET.vi using an upper case C:\ returns error 363510 N/A Workaround: Use lower case c:\
| |||||
| 372644 Return | Saving a VI that contains conditional tunnels for Previous Version in LabVIEW 2012 creates an uninitialized shift register N/A Workaround: N/A
| |||||
| 381656 Return | Adding or subtracting timestamps causes a conversion to double and precision loss N/A Workaround: Cast the timestamps to clusters of U64 'seconds since epoch' and I64 'fractions of a second' before the operation and then cast back to timestamp after the operation
| |||||
| 369833 Return | LabVIEW Draw VIs will sometimes create corrupt PNG images when used with the LV Image to PNG Data VI This occurs if a drawing VI is used to create a LabVIEW picture with data in negative coordinates. Workaround: Use the rect parameter of Picture to Pixmap VI to specify bounds that are in the positive coordinate system.
| |||||
| 391784 Return | Memory Lead when Sound VIs are Called Dynamically Sound Input Configure.vi and Sound Input Clear.vi leak memory when called dynamically Workaround: Use a static call to these VIs.
| |||||
| 392545 Return | Timed Loop crashes LabVIEW after exiting A timed loop that meets these criteria can crash LabVIEW after finishing execution.1) The Timed Loop must write to the "Offset" input node inside the loop2) The Timed Loop must have set the "Mode" input node to anything else other than "No Change" or "Discard missed periods, ignore original phase" before the loop begins Workaround: Configure the Timed Loop once at the beginning of execution instead of each iteration.
| |||||
| 401689 Return | Constrained Non-Linear Optimization VI has Potential for Infinite Loop Depending on the function data, Constrained Non-Linear Optimization can execute indefinitely. No checks are done in subVI for infinite loop. Workaround: Enter in your own check to see infinite loop is occurring.
| |||||
| 404038 Return | Unevenly Sampled Signal Spectrum VI Uses Incorrect Sample Weighting The Unevenly Sampled Signal Spectrum VI should use Sample Weighting for it's standard deviation, but instead uses Population Weighting. Workaround: Open Unevenly Sampled Signal Spectrum VI's block diagram, change enum constant input to Standard Deviation and Variance from Population to Sample.
| |||||
| 406311 Return | VI.Control Value.Set will Crash LabVIEW When Value Non-Variant Data is Used for Value Parameter The crash will happen when VI.Control Value.Set is invoked upon a VI reference that has been opened by Open VI Reference. Workaround: Cast data to variant before wiring to Value parameter.
| |||||
| 406710 Return | LabVIEW Crash when Inlined SubVI with Feedback Node inside of Parallel For Loop is called. Feedback Nodes are not allowed inside of Parallel For Loops, and will cause a VI to be broken. When a VI is set to execute inline, the VI won't break and report the mistake. Calling a VI that contains this broken code will crash LabVIEW. Workaround: Disable inline execution to see incorrect code, then fix broken code.
| |||||
| 407633 Return | Set Cell Value Method Returns Error 1604 Set Cell Value method for tables returns error 1604 if method executes at the same time that a user changes the value of a Picture Ring Control. Workaround: Architect code so table is not updating continuously to reduce risk that user changes Picture Ring value at the same time that Set Cell Value is executing.
| |||||
| 409768 Return | Array Subset Can Cause LabVIEW 64bit to Crash In LabVIEW 64bit manipulating arrays with the Array Subset node can cause LabVIEW to crash. Workaround: Rewrite the "Array Subset" function by using For loops and "Index Array" function.Attached: manual_array_subset,viEnabling iteration parallelism will additionally speed up the execution.
| |||||
| 410733 Return | Ramp Pattern VI does not produce expected results Ramp Pattern VI does not produce all of the expected data points. The final data point in array output will be missing when producing decimal point ramp data. Workaround: Scale the limits so that delta can be equal to 1, then re-scale the ramp data.
| |||||
| 410904 Return | Print.VI to Printer Method Always Prints Header in LabVIEW Built Applications The Page Headers? parameter for Print.VI to Printer is always true when running as a LabVIEW Built Application. The parameter is used properly when the method is ran in the LabVIEW development environment. Workaround: 1. Select Operate»Print at Completion to print the front panel of a VI when it finishes running.2. Select File»VI Properties.3. Select Print Options from the Category pull-down menu.4. Place a checkmark in the Automatically Print Panel Every Time VI Completes Execution checkbox.5. Uncheck Print header (name,date,page number) box6. Click the OK button.
| |||||
| 425562 Return | Scan from String requires a space between modifiers when using SI notation Scan from String requires a space between the modifier and the unit. For example, %pV will throw an error with an input string of 10mV, but it works correctly with %p V and an input string of 10m V. Workaround: Add an additional space after the modifier
| |||||
| 412979 Return | Flatten to XML String does not properly escape single and double apostrophes in a string input (' and ") These should be escaped to "apos" and "quot" but are not. Other special characters including &,<, and > are correctly escaped. Workaround: Parse the string manually for apostrophes to escape them
| |||||
| 416470 Return | Using the Get Waveform Attribute in a subVI can cause incorrect data to be returned to the main VI If using Get Waveform Attributes in a subVI, if the input to the subVI is wired into the default value input of Get Waveform Attributes, the values output will be the correct value, but in the main VI, the returned value will be the default data value of that data type. Workaround: Put an Always Copy function either on the input wire or on the output wire.
| |||||
| 390021 Return | An inlined VI can not be placed on the block diagram of a VI with subroutine priority unless it also has subroutine priority Inlined VIs should ignore the Priority setting in VI properties, however an inlined VI dropped in a subroutine priority VI will break the run arrow unless the inlined VI is also set to subroutine priority. Workaround: Set the inlined subVI to subroutine priority
| |||||
| 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.
| |||||
| 465422 Return | In certain cases, LabVIEW Crashes When Deleting a Subdiagram Label From a Merged Flat Sequence Structure Workaround: Do not merge frames with Subdiagram Labels or hide the labels before merging.
| |||||
| 384591 Return | A password protected VI accessing a password protected community scoped VI is broken if the VIs are set to separate compiled code from source code This only happens if the VI source-only option set to true: Tools -> Options -> Environment Settings -> Separate Compiled Code from New Files set to true, or via the VI Properties window Workaround: Do not separate the compiled code from the source code or remove the password
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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.
| |||||
| LabVIEW Environment | ||||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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:
| |||||
| 257194 Return | Connector pane of a VI can change from LabVIEW 2009 to LabVIEW 2011 If you have a VI with no items in the connector pane and upgrade it straight form LabVIEW 2009 to LabVIEW 2011 then the connector pane may change Workaround: Open in LabVIEW 2010 first
| |||||
| 303342 Return | Choose Environment dialog exit behavior is bad When launching LabVIEW with multiple modes available, you can select the Choose Environment window. Clicking the Exit button brings up a new dialog saying "Quitting will abort all running VIs". If you click the Quit button, LabVIEW exits. If you click the Cancel button, LabVIEW goes back to the default Getting Started Window. Workaround: N/A
| |||||
| 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
| |||||
| 312130 Return | Show Buffer Allocation tool shows that all inlined VIs are inplace The Show Buffer Allocations tool will always show inlined VIs as not having any buffer allocations. Just because a VI is inlined does not mean the inputs are inplace with the outputs. Workaround: See if the subVI is inplace if it isn't inlined.
| |||||
| 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: N/A
| |||||
| 322188 Return | VI Revision History "prompt for comment when a VI is closed" doesn't save comment If you select the "prompt for a comment when the VI is closed" option on VI Revision History, the comment will not save. The dialog box will appear and everything will look correct but when you open the VI again the history is lost. Workaround: Use "prompt when saved" or enter revision notes before closing
| |||||
| 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.
| |||||
| 362925 Return | Crash when dragging instance of Polymorphic VI from dialog to block diagram. Dragging an instance of a Polymorphic VI from the Polymorphic VI configuration dialog, will crash LabVIEW. Workaround: This issue has been fixed in the LabVIEW 2012 f1 patch.
| |||||
| 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.
| |||||
| 316641 Return | LabVIEW does not limit DWarn prints (to the log file) in LV 2011 LabVIEW usually limits warning messages from being written to the lvlog.txt more than 100 times each. This issue means that a repetitive warning message may cause the log file to grow without bound. Workaround: n/a
| |||||
| 357219 Return | Pasting into the Icon Editor stretches the clipboard image in the x and y direction. n/a Workaround: Import from .png file instead.
| |||||
| 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.
| |||||
| 374828 Return | Updating a Library Icon and applying to existing VIs, removes custom icons from VIs N/A Workaround: N/A
| |||||
| 375002 Return | Old library icon template persists on lower layer of VI icon after making library icon changes N/A Workaround: Open each VI icon with the Icon Editor and select OK
| |||||
| 379023 Return | Items with colons in their localized names do not drop with Quick Drop in LabVIEW German N/A Workaround: Select these items from the Function Palette
| |||||
| 315663 Return | Files inside a NIER Report have the incorrect date N/A Workaround: N/A
| |||||
| 382333 Return | The Match Regular Expression VI in LabVIEW 2012 on Linux crashes when the screen's color depth is set to 16-bit N/A Workaround: Change the color depth to "millions of colors" in the display user interface
| |||||
| 376574 Return | Launching the Getting Started Window repeatedly can launch a blank VI instead of the Getting Started Window N/A Workaround: Disable ni.com updates through Tools>>Options>>Environment or wait 30 seconds before trying to launch the Getting Started Window again
| |||||
| 387557 Return | LabVIEW 2012 uses 100% of one core after being open for over a day N/A Workaround: Relaunch LabVIEW
| |||||
| 376714 Return | Using the Merge VIs utility with VIs that contain a tab control causes LabVIEW to hang Workaround: Manually edit the VI to include all the changes made in Theirs, and Yours.Do not use the Tab Controls shown in the attached VIs.
| |||||
| 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.
| |||||
| 423373 Return | Under certain conditions, a compiler optimization will cause array shift registers to share memory space. Workaround: This issue has been fixed in the LabVIEW 2013 f1 Patch
| |||||
| 445636 Return | Postscript printing of graphical elements on the front panel fails Printing VI front panels with a postscript printer fails to print Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f1 Patch
| |||||
| 433622 Return | LabVIEW can crash if a VI is unloaded from memory before closing its VI references N/A Workaround: This issue is fixed in the LabVIEW 2012 SP1 f8 Patch
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 356466 Return | Stopping VIs and immediately closing project may crash LabVIEW The crash can occur if any Asynchronous Call by Reference VIs finish during the time the "Closing will abort running VIs" dialog appears on the screen. Workaround: Allow your running VIs to stop completely before closing the project. Alternately, close the project window to abort any running VIs, instead of stopping them first.
| |||||
| 356656 Return | Crash when compiling VIs that call into a certain class based VI hierarchies Some VIs that call into a formerly non-dynamic dispatch member of a class whose parent is missing may crash when saved or mass compiled. Workaround: Open the class first, then open the VI and save it.
| |||||
| 361666 Return | Tools >> Actor Framework Message Maker... is missing in Linux N/A Workaround: This issue is fixed in the LabVIEW 2012 f1 patch.
| |||||
| 366921 Return | Community scoped VIs within classes in a LabVIEW library will break a packed project library and cause Error 3 N/A Workaround: N/A
| |||||
| 334314 Return | Creaing an Override VI for a child class that has a parent in a Packed Project Library gives error 1035 If creating an Override VI in a child class which has a parent in a Packed Project Library that the child is not part of, LabVIEW will throw error 1035 Workaround: Select VI for Dynamic Dispatch, and change the connector pane terminals and VI name to match the VI you are overriding
| |||||
| 391455 Return | Applying an icon to LabVIEW class overwrites the icons of its methods The icon for a LabVIEW class appears to be only the banner, but when it is applied it overwrites the entire icon of the method VIs Workaround: N/A
| |||||
| 406658 Return | LabVIEW Crash when VI for Override is Created from a Class that is Open in Two Projects. When two LabVIEW projects are open that contain the same LabVIEW Class, it will be in memory for both projects. When a new VI for override is created on a new LabVIEW class that inherits from the shared parent class, LabVIEW will crash. Workaround: Close LabVIEW projects that are not in use if it references the same files as another currently open LabVIEW project.
| |||||
| 410360 Return | LabVIEW Classes Become Corrupt When Multiple Files With Same File Name are Added to the Class When a LabVIEW Class is saved with multiple files sub-files that have the same file name, the .lvclass file will become corrupt. Workaround: N/A
| |||||
| 360229 Return | Class VI ,with source only turned on, loaded before a property accessor for a dynamic property it uses is broken on load Workaround: This issue is fixed in the LabVIEW 2012 SP1 f5 Patch
| |||||
| 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.
| |||||
| 381905 Return | LabVIEW Projects will not open from disk after a crash with autosaved VIs In certain circumstances, after a project has crashed while VIs are autosaved, the project will throw a Noncontinuable Exception (0xC0000025). Workaround: Open LabVIEW and open the project through LabVIEW (not from disk) and resolve the Resolve Conflicts Dialog. The project will now open as usual.
| |||||
| 361793 Return | I/O tags with names that are the same apart from case behave different in a built application I/O tags that are the same (with different case) are treated as different in LabVIEW, but when built into an application they are treated as the same Workaround: Avoid giving the tags such similar names
| |||||
| 377385 Return | Error 1390 on Dynamic VI Call to Friend Library The error is returned when two Community scoped LabVIEW Libraries are Friends to each other, and one Library performs a dynamic call to a VI in the other Library. Workaround: Change the dynamic call to a static call, or change the scope to Public on the Library containing the callee VI.
| |||||
| 385212 Return | Adding and removing a registry key from a build specification can cause the build specification to become corrupt N/A Workaround: Open the lvproj file with an editor and remove lines values referring to RegGroup and RegData manually
| |||||
| 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
| |||||
| 334314 Return | Creaing an Override VI for a child class that has a parent in a Packed Project Library gives error 1035 If creating an Override VI in a child class which has a parent in a Packed Project Library that the child is not part of, LabVIEW will throw error 1035 Workaround: Select VI for Dynamic Dispatch, and change the connector pane terminals and VI name to match the VI you are overriding
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 408391 Return | Non-printable Characters in the Description of Will Corrupt LabVIEW Classes and Libraries Non-printable characters can be inserted into the description of LabVIEW Classes and Libraries with the Description Property Node. This will corrupt the .lvclass or .lvlib file. Workaround: The .lvclass or .lvlib file can be opened in a text editor, and the description can be manually deleted to recover the files.
| |||||
| Miscellaneous | ||||||
| 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.
| |||||
| 403727 Return | Repeated Dynamic Calls to VI in Packed Project Library Can Cause Error in VI Call After over a million Dynamic Calls to a VI contained in a Packed Project Library, a error can be thrown that LabVIEW attempted a recursive call. Workaround: The error does not occur on regular project libraries.
| |||||
| 415924 Return | Double precision numeric constants set to "bar" units sometimes use Pa units Double precision numeric controls and indicators using "bar" units work correctly, but block diagram constants use Pa instead of bar. Workaround: Create the constant from a control with "bar" units and then change the unit label from Pa to bar to get a constant that uses bar.
| |||||
| NI Services | ||||||
| 364338 Return | "Error while retrieving database: Forbidden" connecting to a RT target via the web configuration. If you change the admin password for an RT target and reboot the target before saving, you may receive the error "Error while retrieving database: Forbidden." Workaround: Refresh the web page hosting the web configuration.
| |||||
| 392446 Return | Installing LabVIEW on a Windows Laptop Decreases Battery Life Even with NI applications closed, services installed by LabVIEW request high resolution timers. These timers prevent the hardware from sleeping, and requires more power. Workaround: N/A
| |||||
| Operating System Specific | ||||||
| 157246 Return | The Property Node "Bring to Front" doesn't work in Windows Vista Workaround: N/A
| |||||
| 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
| |||||
| 351506 Return | [Mac] Test Device option on Play Waveform Express VI Configuration page doesn't output test tone N/A Workaround: N/A
| |||||
| 403182 Return | Sound Output.vi Does Not Support more than 2 Audio Channels on Windows 7 Error 4811: "can not support sound format" will be returned from the VI when executed on Windows 7. Workaround: More than 2 Channels are supported on Windows XP.
| |||||
| 405271 Return | Boolean Mechanical Actions Don't Work as Expected on Windows 8 Touch Screen Switch Until Released and Latch Until Released don't behave as expected for touch and hold gesture. Boolean controls will not toggle on touch and hold gesture, until finger is dragged outside the bounds of the control. Other Boolean mechanical actions behave as expected. Workaround: N/A
| |||||
| Performance | ||||||
| 352146 Return | In Actor Framework based projects, interacting with the front panel of an aborted actor may cause the VI to become nonresponsive. In Actor Framework based projects, if the user stops an actor using the LabVIEW abort button while there are still other actors running, clicking on any controls registered for static events of the aborted VI may cause the VI to become nonresponsive. Workaround: Instead of aborting a single actor, send out a stop or emergency stop message to every actor that is running. For example, in the Feedback Evaporative Cooler project, use the "Stop All" button or the "Emergency Stop" button to stop the actors.If an aborted actor is already in this state, closing the project will close all the actors, including the nonresponsive ones.
| |||||
| 371714 Return | Slow load time when adding a VI to the Exported VIs List for a DLL N/A Workaround: N/A
| |||||
| 387557 Return | LabVIEW 2012 uses 100% of one core after being open for over a day N/A Workaround: Relaunch LabVIEW
| |||||
| 376379 Return | Graphs and charts have slow performance with thick line style and large data range in LabVIEW 2012 N/A Workaround: N/A
| |||||
| 381707 Return | The Render to Image method for 3D picture controls demonstrates slow performance Render to Image method for 3D picture controls executes slow for complicated scenes. This can impact the update rates of 3D picture controls if the method is inside of the loop as the 3D picture terminal. Workaround: This issue has been fixed in the LabIVEW 2012 f5 Patch, but the fix is not part of LabVIEW 2012 SP1. The fix will be included in the first patch released for LabVIEW 2012 SP1.
| |||||
| 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
| |||||
| 396984 Return | Sequential For Loops structures will sometimes execute incorrectly when VI property "Allow Debugging" is unchecked. Workaround: This issue has been fixed in the LabVIEW 2012 SP1 f3 Patch
| |||||
| 408844 Return | Memory growth observed when using Asynchronous Call By Reference node in long running loop. N/A Workaround: This issue was fixed in the LabVIEW 2012 SP1 f4 Patch.
| |||||
| 408845 Return | Measurement speed can degrade when using Asynchronous Call By Reference node in long running loop. N/A Workaround: This issue was fixed in the LabVIEW 2012 SP1 f4 Patch.
| |||||
| 429724 Return | Under certain circumstances an internal race condition can cause the LabVIEW UI thread to stop updating front panel objects Workaround: This issue is fixed in the 2013 f2 Patch.
| |||||
| 429726 Return | LabVIEW crashes when .NET event callback calls a VI that has already been deregistered in LabVIEW. Workaround: This issue is fixed in the LabVIEW 2013 f2 Patch
| |||||
| 390021 Return | An inlined VI can not be placed on the block diagram of a VI with subroutine priority unless it also has subroutine priority Inlined VIs should ignore the Priority setting in VI properties, however an inlined VI dropped in a subroutine priority VI will break the run arrow unless the inlined VI is also set to subroutine priority. Workaround: Set the inlined subVI to subroutine priority
| |||||
| Remote Panels | ||||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 306189 Return | Deploying a Variable Library with an IO Alias to a RT Target Programmatically Returns Error 1 Deploying a Variable Library containing an IO Alias to an RT target from the host programmatically fails with error 1. The deployment is performed using the Deploy Library method. Workaround: Manually deploy the project library from the LabVIEW Project Explorer window.
| |||||
| 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.
| |||||
| 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.
| |||||
| 310077 Return | Variable Browse Dialog doesn't show any deployed IOVs The browse dialog isn't displaying IOVs in the deployed tree view. It shows IOV containers, but they always appear empty. Workaround: Use the project view of the tree if possible. This may not work that well for remote targets. Or, type the URL directly into the I/O control without using the browse feature.
| |||||
| 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.(KB: http://digital.ni.com/public.nsf/websearch/E18E53A7CE29EEDD862576D6006CB176)
| |||||
| 362742 Return | Updating multiple shared variables' Networking Published: Binding Project Path crashes LabVIEW If you use the multiple variable editor to update the network binding path of more than one shared variable LabVIEW may crash. This crash will only occur when selecting the column header first to select all shared variables and then edit one of the variables network binding path. Workaround: Change the network binding path of a single shared variable then double click the column header to update all shared variables.
| |||||
| 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
| |||||
| 394454 Return | Data Binding: Path property can change bindings in other VI clones Writing to a Data Binding: Path can change binding path for other instances of the control if clones of the VI are already open Workaround: Use programmatic Shared Variable access to update front panel controls instead of Data Binding.
| |||||
| Source Code Control | ||||||
| 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 - Desktop Execution Trace Toolkit | ||||||
| 412912 Return | LabVIEW Crash when VI has String Control Wired to Generate User-Defined Trace Events is Traced. If a VI contains Generate User-Defined Trace Events primitive with Trace String input connected to the VI's connector pane, LabVIEW will crash when the VI is traced by Desktop Execution Trace Toolkit Workaround: Insert the "Always Copy" primitive on the string wire input to the "Generate User-Defined Trace Event" primitive. This primitive is located in the Functions palette >> Application Control >> Memory Control.
| |||||
| Toolkit - Other | ||||||
| 356420 Return | Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name Workaround: Move the manifest file to a new location
| |||||
| 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
| |||||
| 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.
| |||||
| 378888 Return | The Mixed Signal Graph does not correctly label plots in LabVIEW 2012 The Mixed Signal Graph in LabVIEW 2012 only correctly labels the first plot from NI-DAQ waveform attributes. Additional plots will not automatically have the correct labels Workaround: Use Property Nodes to set the plot names
| |||||
| 396984 Return | Sequential For Loops structures will sometimes execute incorrectly when VI property "Allow Debugging" is unchecked. Workaround: This issue has been fixed in the LabVIEW 2012 SP1 f3 Patch
| |||||
| 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.
| |||||
| 362018 Return | Crash when loading some VIs, saved in a previous version of LabVIEW, into LabVIEW 2012. N/A Workaround: This issue has been fixed in the LabVIEW 2012 f1 patch.
| |||||
| Web Server/Web Services | ||||||
| 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
| |||||
| 278730 Return | Web Services ignore No App switch on RT targets After deploying the web service to a RT target, it become like a start up executable. Any time the target is reboot, the web services re-starts automatically. However, unlike with start up executables, the web service can't be turned off by the No App switch. Workaround: N/A
| |||||
| 374195 Return | Report Gen VIs fail with Office 2010 when built into Web Service Building a web service that contains Report Gen VIs that communicate with Office 2010 causes MS Word to throw exceptions. No errors appear from the development environment or as an executable, the problem is specific to web services. Workaround: Use Office 2007
| |||||
| 311279 Return | Deploying a web service will fail When deploying a Web Service you may fail with the following error:Error LabVIEW: (Hex 0xFFFEFA45) LabVIEW Web Services: Call to create a VI reference failed The target might not support SSE2 optimization. Disable SSE2 optimization on the Advanced page for the Web Service Properties dialog box before proceeding. Workaround: This issue has been fixed in the LabVIEW 2011 f2 Patch
| |||||
| 368115 Return | HTTP POST VI will always timeout when POSTing to a Web Service using NIAuth N/A Workaround: This issue is fixed in the LabVIEW 2012 f2 patch.
| |||||
| 390386 Return | LabVIEW HTTP Client does not implement Curl Rewind causing authentication errors for auth-basic. Workaround: This issue has been fixed in the LabVIEW 2012 SP1 f3 Patch
| |||||
Document last updated on 7/31/2014