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 2013 known issues that were discovered before and since the release of the LabVIEW 2013 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 2013 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 White Paper "LabVIEW Known Issues Categories Defined" for an explanation of the categories.
You can contact us by phone, email, or the discussion forums.
The following items are known issues in LabVIEW 2013 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
| |||||
| 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.
| |||||
| 445027 Return | Calling multiple LabVIEW built .NET assemblies from any .NET language fails with Error 1 It is not possible to call multiple LabVIEW built .NET assemblies from any .NET language. When the second assembly loads it will fail with Error 1. Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f4 Patch.
| |||||
| 445981 Return | A memory leak occurs when calling a custom ActiveX Control function which returns a UInt64 Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f1 Patch
| |||||
| 468139 Return | .NET Callback Event VI keeps the Callback VI reserved even after calling a Close Reference VI is called For example, when running the "Passing data to a .NET Event Callback.vi" example, after stopping the main example VI, the "Callback - EventHappened.vi" is still reserved. Workaround: I've come up with a work around for this problem. GC.Collect() can be called manually from the invoke node in a separate VI(Or the user could call it after un-registering the callback). This would un-reserve the callback VI. Steps : 1. Drop an invoke node in an empty VI 2. Right click on the node and in the menu under "Select Class" -> ".NET" choose Browse. 3. In the Class browser dialog navigate to mscorlib(4.0.0.0) assembly in the drop down 4. Once selected in the list below expand the system namespace and choose GC class. 5. Once this is done you can choose the Collect() static method. 6. You can unreserve the callback VI by running this VI.
| |||||
| 480386 Return | ActiveX call to open PDF (Adobe Reader 11.0.07) results in LabVIEW crashing More information at https://forums.adobe.com/message/6396203#6396203 Workaround: Downgrade to an earlier versions of Adobe Reader (11.0.6 and earlier)
| |||||
| 460106 Return | In certain cases, there is a memory leak when a .NET object is used in a LabVIEW Interop Assembly Workaround: N/A
| |||||
| 473514 Return | TestStand ActiveX invoke nodes may not return the expected error 97 ("LabVIEW: A null or previously deleted refnum was passed in as an input.") when a null reference is used. If a null reference is wired into an Active X node and the error wire is not wired , the node may not correctly return error 97 ("LabVIEW: A null or previously deleted refnum was passed in as an input."). Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f4 Patch.
| |||||
| 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
| |||||
| 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.
| |||||
| 471675 Return | Inverse FFT Function is very slow if inputs have NaN values Workaround: Programmatically detect if the array has NaN in it by using the "NaN Path Refnum?" VI and a OR Array Elements and case structure the inverse FFT function.
| |||||
| 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 ni.com
| |||||
| 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 For more information see this KnowledgeBase 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 429282 Return | In LabVIEW 2013, including VIs from some libraries causes building an installer to fail with error 1 "Error Generating Preview" Including VIs from libraries that have unsatisfied dependencies will cause building an installer to fail with error 1 "Error Generating Preview" Workaround: See the Knowledgebase Article for Error Generating Preview
| |||||
| 422680 Return | Deploying a Web service to the Application Web Server gives an error "NI Application Web Server service is still starting" When deploying a Web service to the Application Web Server from with a WiFi adapter enabled will give an error regarding the Application Web Server Workaround: This issue has been fixed in the LabVIEW 2013 f1 Patch
| |||||
| 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.
| |||||
| 426140 Return | Building an installer with VIs that contain unsatisfied dependencies within diagram disable structures fails with Error Generating Preview N/A Workaround: N/A
| |||||
| 443165 Return | Modifying the dependencies of a Packed Project Library (PPL) may cause LabVIEW to crash N/A Workaround: To avoid the crash, rebuild the PPL after modifying the dependencies.
| |||||
| 439026 Return | Building an Application with Enable ActiveX server selected will crash all localized versions of LabVIEW In any non-English version of LabVIEW, building an application with the Enable ActiveX server setting selected will crash LabVIEW. This setting is located in the Advanced tab of the build specification. Workaround: N/A
| |||||
| 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
| |||||
| 476714 Return | The INI file created for a LabVIEW built executable contains a truncated list of VIs in the "server.vi.access=" line when enabling TCP/IP with multiple Exported VIs Workaround: Manually list the missing VIs in the INI file
| |||||
| 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.
| |||||
| 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
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 367249 Return | It is not possible to customize the Run-Time Shortcut menu of a 3D Graph N/A Workaround: N/A
| |||||
| 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
| |||||
| 409825 Return | Control.Delete Method Crashes LabVIEW When Used on a XControl LabVIEW can crash when VI Scripting Control.Delete method is used on a XControl Workaround: If a small delay is added before the Delete method, it will prevent the crash.
| |||||
| 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
| |||||
| 422507 Return | Entering an integer into a numeric control that has a time display format does not update the control Double clicking inside a time display numeric control and typing a new value does not update to the new value, and the control reverts to its original value. This happens for controls with a display format of either %t or the default Relative Time format. Workaround: If the display format is %t, enter values with a decimal point after the number (as a double)If the display format is the default Relative Time, single click on the hour or minute fields and update individually or enter the value in the format HH:MM with the colon to successfully update
| |||||
| 428515 Return | On Scientific Linux 6.3 with updated Mesa Drivers, 3D Picture Controls display an inverted image Workaround: Downgrade the Mesa drivers or manually invert the image.If your 3rd-Party Mesa driver version is between 7.11 and 9.2.1, you need to add the LabVIEW INI token "Invert3DPictImage=True". Driver version 7.11 and earlier, and version 9.2.1 and later, do not need the INI token.
| |||||
| 425313 Return | Selecting the option to hide grid lines when using Export Simplified Image with a waveform graph will not hide all grid lines when using multiple axis When using the waveform graph right-click option to Export Simplified Image with the option to hide grid lines, some of the grid lines will still be visible if there are multiple axis Workaround: Disable the grid of the additional axis through the scale tab of the graph properties
| |||||
| 432182 Return | Custom labels on a 3D bar chart do not display properly in a 2D view Custom labels on a 3D bar chart will revert to a numeric value when viewed in a 2D Projection Workaround: N/A
| |||||
| 428914 Return | The Y-Axis of a Mixed Signal Graph will not correctly scale when the graph is set to "Scale Object with Pane" and the user decreases the size of the VI Front Panel. Increasing the size of the pane will result in the graph growing and scaling its axes correctly, but decreasing the size of the pane will only shrink the graph without scaling the Y-Axis. The Y-Axis will now have a scroll bar due to not scaling. Workaround: Use the "Plot Area" Property Node to shrink the graph to appropriate size.
| |||||
| 433596 Return | The 3D Surface Plot does not draw correctly when the input data is an array of the same value The plot is completely blank if the array contains only the same value. Changing one value correctly draws the 3D Surface Plot Workaround: Manually or programmatically toggle the Z-Axis range, or turn off Auto Scaling on Z-Axis, and the plot will appear
| |||||
| 477864 Return | When a number of controls are grouped on a tab control page, switching to that page takes a long time, proportional to the number of controls grouped Workaround: Ungroup controls on tab pages
| |||||
| 399117 Return | In rare cases, Mixed Signal Graph and Digital Waveform Graph cause a memory leak Workaround: N/A
| |||||
| 438751 Return | Renaming a group in a Mixed Signal Graph crashes LabVIEW once there is a plot containing data Workaround: Create a Strict Type Definition from a new Mixed Signal Graph. Change and update the Type Def to change the name of the group
| |||||
| 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
| |||||
| 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"
| |||||
| 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.
| |||||
| 424382 Return | Path controls in LabVIEW for Mac OS X treat .app files as folders instead of files Workaround: None
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 400736 Return | Error -4403 returned from Write Palette.vi for Template VIs Template VIs can not be added to the palettes with the Write Palette.vi, error -4403 will be returned. Workaround: Add Template VIs to the palettes manually through Tools»Advanced»Edit Palette Set...
| |||||
| 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.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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.
| |||||
| 417953 Return | LabVIEW will crash on run if array on connector pane is wired to Flatten to JSON primitive N/A Workaround: Remove array from connector pane, or wrap array in a cluster. Alternatively, add an Always Copy primitive before calling Flatten to JSON.
| |||||
| 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
| |||||
| 425800 Return | Calling Quit LabVIEW.vi will not quit LabVIEW if the calling VI also contains an event structure handling the Application Instance Close Event If a VI has both the Quit LabVIEW.vi and an event case handling the Application Instance Close event, the Quit LabVIEW.vi will not close LabVIEW. Workaround: Remove the Application Instant Close event from the event structure
| |||||
| 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.
| |||||
| 430579 Return | The Cubic Spline Fit does not output a linear function when the balance parameter is zero and the input arrays are less than seven elements N/A Workaround: N/A
| |||||
| 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
| |||||
| 461196 Return | Scan From String VI returns Error 1 with "%t" as the format string input Workaround: Use the Search/Split String VI to scan the string for the desired values
| |||||
| 437814 Return | Open Sessions VI from visa.llb does not work properly in LabVIEW 2013 No open sessions are returned even if there is a session open Workaround: Use VISA Find Resources to obtain a list of all resources available. Attempt to open each resource as a duplicate. If the the VISA Resource Name output of the VISA Open is a duplicate, then the session was already open
| |||||
| 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
| |||||
| 424089 Return | The advanced analysis Kummer Function returns 'NaN' instead of correct values for certain combinations of input parameters. Check the following forum for more information and a possible workaround Workaround: Check the following forum for more information and a possible workaround:http://forums.ni.com/t5/LabVIEW/Bug-in-the-Kummer-Function/m-p/2387522#U2387522
| |||||
| 476710 Return | Opening a VI Server Reference to two or more identically named VIs, contained in separate LabVIEW libraries in a running executable, can result in Error 1031 From a LabVIEW development environment, opening a VI Server Reference to two or more identically-named VIs, contained in separate LabVIEW libraries in a running executable, results in one successful VI reference and Error 1031 from all other Open VI Reference functions. Workaround: Rename the referenced VIs so there are no name duplicates across LabVIEW libraries
| |||||
| 442745 Return | RF-RIO Instr Default Personality 5646R.lvproj's FPGA VI will hang on save. Instrument driver\RFSA\5645R\Public\Apply Digital Correction.vi located in RF-RIO Instr Default Personality 5646R.lvproj will hang on save. This happens when removing the diagram disable structure. In addition, the VI cannot compile. Workaround: Currently, using the structure wrap included in the example code is recommended. If you only use one instance of the polymorphic VI, re-arrange the instances such that the instance you wish to use appears first in the list.
| |||||
| 462029 Return | LabVIEW crashes when typecasting a RIO handle to a VISA handle Workaround: Cast RIO handle to string and pass it into a VISA resource VI, or use the flatten to string/unflatten to string VIs.
| |||||
| 469070 Return | In some cases, Fract/Exp String To Number VI does not convert the string correctly Examples:"1E-9999" should return 0 but returns Inf"1E-12000" sould return 0 but returns 1E-1200"1E9999" should return Inf but return 0"1E12000" should return Inf but returns 1E1200 Workaround: N/A
| |||||
| 477352 Return | In the TDMS File Viewer VI, the menu becomes partially hidden after making the plot legend visible Workaround: Restart the VI containing the TDMS File Viewer and the menu should be fully visible
| |||||
| 467735 Return | "Format into File" produces Error 1 when appending to a file that has a size of 4 GB See this NI Community page for more information. Workaround: Use "Format Into String" and "Write to Binary File".
| |||||
| 468062 Return | Path to URL.vi does not handle network path Workaround: Use the attached Path to URL.vi and \vi.lib\Platform\browser.llb\Open URL in Default Browser core.vi in your code.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 408955 Return | Crash when deleting a newly created comment with Automatic Tool Selection turned off. N/A Workaround: This issue has been fixed in the LabVIEW 2013 f1 Patch
| |||||
| 415901 Return | When repairing LabVIEW 2013, the service locator dependency is uninstalled Workaround: This was fixed in the LabVIEW 2013 f1 Patch
| |||||
| 423385 Return | In LabVIEW 2013, once a Type Definition is made a Strict Type Def, it can not be made non-strict. N/A Workaround: This issue has been fixed in the LabVIEW 2013 f1 Patch
| |||||
| 442743 Return | Cutting text from one free label and pasting into another with the autotool disabled crashes LabVIEW N/A Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f1 Patch
| |||||
| 424541 Return | Upgrading code that contains an inplace element structure with auto grow disabled will turn auto grow back on N/A Workaround: N/A
| |||||
| 430758 Return | It is not possible to save a VI with the name of another VI in memory, even if they are in different libraries LabVIEW does not check the library namespace when determining if a VI is being saved with a name that is already in use. If a VI is in memory, it is not possible to save another VI with the same name in the same project even if they are in different libraries. Workaround: Close the other VIs with the same name so they are not in memory.
| |||||
| 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
| |||||
| 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
| |||||
| 420582 Return | Typing Obtain in Quick Drop populates with an unexpected selection Workaround: Disable 'relevancy-based search' in the Quick Drop configuration options
| |||||
| 435492 Return | Child class VI called using Dynamic Dispatch from TestStand passes out incorrect data. Calling a child class VI through Dynamic Dispatch from TestStand can initialize the child incorrectly and cause incorrect data to be passed. Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f4 Patch.
| |||||
| 472865 Return | Creating a subVI from a selected control that has been reordered may crash LabVIEW. Reordering diagram objects from front/back and then creating a subVI that includes selected controls may cause LabVIEW to crash. This is due to the VI becoming corrupt from front/back reordering of diagram objects. Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f4 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 441783 Return | LabVIEW Class VIs loaded from an unexpected path can sometimes load broken If a LabVIEW Class VI has a dependency that loads from an unexpected path, that VI can sometimes load with a broken run arrow. Workaround: This issue is fixed in the LabVIEW 2012 SP1 f8 Patch
| |||||
| 457434 Return | In LabVIEW 2013 SP1, removing a file from a class and then adding that file back to the same class can crash LabVIEW N/A Workaround: This issue is fixed in the LabVIEW 2013 SP1 f2 Patch
| |||||
| 461969 Return | When using a class containing a DAQmx Physical Channel control, it will not properly load that information from an XML file. The control can be changed and saved to the XML as expected and seen when opening the XML. However, when you try to load the channel from the XML it appears blank. Workaround: If you place the class cluster in an additional cluster the DAQmx Physical Channel control saves and loads as expected.
| |||||
| 470533 Return | When creating a property accessor method of an EndevoGOOP400 type for a Simple DVR Template Class in the LabVIEW GOOP suite, LabVIEW generates Error 7 Workaround: Manually create the property accessor.
| |||||
| 476362 Return | With an Actor Framework project in LabVIEW 2013 SP1 and the LabVIEW GOOP Development Suite, LabVIEW may crash when exiting if the Message Classes are Updated. Workaround: Right click and run LabVIEW as Administrator.
| |||||
| 481414 Return | In the LabVIEW GOOP design suite, you are unable rename a method of a GOOP class under an RT target from the project Workaround: Double click the method, open the VI, and navigate through top menu bar Tools >> GOOP >> Create VI Icon to rename the method
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 422680 Return | Deploying a Web service to the Application Web Server gives an error "NI Application Web Server service is still starting" When deploying a Web service to the Application Web Server from with a WiFi adapter enabled will give an error regarding the Application Web Server Workaround: This issue has been fixed in the LabVIEW 2013 f1 Patch
| |||||
| 413400 Return | When configuring a new project in LabVIEW, the Project Root directory cannot be set to a network drive If the project root path contains "\\" for a path such as a network drive, the following error is shown "The Project Root contains characters invalid for a file path." Workaround: Create the project in a local directory and then move it to a network drive
| |||||
| 430758 Return | It is not possible to save a VI with the name of another VI in memory, even if they are in different libraries LabVIEW does not check the library namespace when determining if a VI is being saved with a name that is already in use. If a VI is in memory, it is not possible to save another VI with the same name in the same project even if they are in different libraries. Workaround: Close the other VIs with the same name so they are not in memory.
| |||||
| 457434 Return | In LabVIEW 2013 SP1, removing a file from a class and then adding that file back to the same class can crash LabVIEW N/A Workaround: This issue is fixed in the LabVIEW 2013 SP1 f2 Patch
| |||||
| 468921 Return | Auto-populating folders may not update their contents correctly Saving a web page file (.htm) from certain programs can result in the auto-populating folder displaying the web page file as a ".ht_" file, which can cause errors in build specifications and other parts of the program that rely on the files. Workaround: Close and reopen the project to correctly update the files in the auto-populating folder. Or, press f5 to refresh the project window.
| |||||
| MathScript | ||||||
| 469268 Return | Formula Node and MathScript Node variable labels can shift to become misalligned After opening and closing its VI, the label will no longer look centered inside its owning box Workaround: This should not affect functionality. Recreate the variable on the node's border to recenter the label
| |||||
| Miscellaneous | ||||||
| 389041 Return | Error -314250 from Create Network Stream Writer Endpoint Error is returned when data type is set with a SGL value that has a unit label defined. Workaround: Change representation or DBL, or remove the unit label.
| |||||
| 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.
| |||||
| 436897 Return | VI Server connections to Localhost fail when wired and wireless adapters are both enabled Workaround: Add actual IP address to VI server access list instead of using 127.0.0.1 or "localhost"
| |||||
| 473389 Return | Unable to delete Waveform Chart or Graph plot entries Workaround: Change the number of plots visible. More information at: http://zone.ni.com/reference/en-XX/help/371361L-01/lvhowto/pl_number/
| |||||
| 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
| |||||
| 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 | ||||||
| 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
| |||||
| 431956 Return | Calling a LabVIEW web service repeatedly causes a memory leak Calling a LabVIEW web service or anything else that uses the NI Application Web Server repeatedly can cause a memory leak Workaround: This issue is fixed in the LabVIEW 2013 SP1 f2 Patch
| |||||
| 440114 Return | Executing a TestStand sequence with LabVIEW VIs in a user interface running in the LabVIEW 2013 Development System causes delays at the beginning of execution When running a TestStand user interface in the LabVIEW 2013 Development System, if a sequence containing LabVIEW VIs is executed multiple times, a delay will occur before the first LabVIEW VI step in the sequence is executed. Workaround: Build the user interface into an executable before testing sequences which call LabVIEW VIs.This issue is fixed in the LabVIEW 2013 SP1 f2 Patch.
| |||||
| 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.
| |||||
| Remote Target | ||||||
| 428872 Return | System State Publisher incorrectly reports cached memory as "used" memory on Linux Real-Time N/A Workaround: Use NI System Configuration API to obtain free memory metrics.
| |||||
| 447072 Return | Wait (ms) VI does not work on NI Linux RT Target if wait is longer than 30000 ms Wait (ms) VI does not work on NI Linux RT Target if wait is longer than 30000 ms. If the wait specified is longer than 30000 ms then the VI will hang. Workaround: N/A
| |||||
| 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.
| |||||
| 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.
| |||||
| 458973 Return | Writing a negative number to single point float Network Shared Variables through the OPC I/O Server fails. Workaround: Use Double precision shared variables instead.
| |||||
| 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.
| |||||
| Upgrade - Migration | ||||||
| 424541 Return | Upgrading code that contains an inplace element structure with auto grow disabled will turn auto grow back on N/A Workaround: N/A
| |||||
| 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
| |||||
| 407678 Return | LabVIEW will crash if closed while a local debug web service is running LabVIEW will crash if a Web Service is still running locally when LabVIEW is closed. Workaround: Stop all local debug Web Services before closing LabVIEW.
| |||||
| 431956 Return | Calling a LabVIEW web service repeatedly causes a memory leak Calling a LabVIEW web service or anything else that uses the NI Application Web Server repeatedly can cause a memory leak Workaround: This issue is fixed in the LabVIEW 2013 SP1 f2 Patch
| |||||
| 401078 Return | Opening any non-VI dialog, such browse for files or one button dialog, may block web service requests from executing. The most common form of this issue seen when Show Method URL Dialog Box blocks requests to a LabVIEW Web Service. This only affects LabVIEW web services deployed to the debug server or embedded in a LabVIEW executable. Workaround: Close the dialog box to allow requests to continue
| |||||
Document last updated on 12/3/2014