LabVIEW 2012 and 2012 SP1 Known Issues by Date

Publish Date: Apr 16, 2014 | 1 Ratings | 1.00 out of 5 |  PDF

Overview

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.

Document Organization

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.


Contacting NI

You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you have feedback on this document, please contact NI on this NI Developer Zone post.

Known Issues by Date

The following items are known issues in LabVIEW 2012 SP1 sorted by Date.

219819 Center justified tables display improperly when overlapping with the front panel origin
37575 3PD8N0M8 LabVIEW uses large amounts of memory when reading an entire wave file at once
39161 401FEQTL The device ID input of the Play Sound File VI does not work on Windows
39604 49UBP4LE Write to Clipboard Method consumes 100% of CPU for several minutes
47819 3N68LE00 2GB file size limit of datalog files
48016 3P7CBB4Q Unsigned int32 loses value in formula node when you write to the most significant bit
50420 44CG88SN Update the Pulse Transition Measurement Express VI
51185 47FGSQCS Cannot save VI as the same name as missing library member VI
51311 477DKPBQ LabVIEW does not maintain child-only item setting when dragging an item within a tree
52027 4A4GRP00 Cannot use the 'New>>VI for Override...' dialog to create override of password-protected VI unless you have the password
52263 4AJA41TQ Some operations on integer waveforms lose dt value
91672 477M7K00 Large amounts of data in combo box can appear to hang LabVIEW.
105509 The "do not save automatic changes" setting does not affect libraries
119444 Multi-column listbox format lost on upgrade
120686 Write to LabVIEW Measurement Files (LVM) using Express VIs takes up a lot of memory
122057 Joining Numbers of Different Widths Produce Unexpected Values
51179 47B12U5U Error 6 occurred at Create Folder in Create Directory Recursive.vi when building an application (EXE), shared library (DLL), source distribution or web service
138552 Load VRML File.vi missing "error in" terminal
141699 NI Distributed System Manager does not show deployed libraries if they contain non-Latin characters.
148149 Event Structure Cases can Incorrectly Remap to Other Dynamic Events
157246 The Property Node "Bring to Front" doesn't work in Windows Vista
128059 Shared variable bindings in the same library are not updated properly when copying/renaming the library
166253 LabVIEW.app does not show up after LabVIEW 2009 Installation
181687 Web publishing tool fails without error
173080 When a project that contains variables with binding is created in one language and opened in a different language, variables may fail to deploy
163371 "Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner library
174929 Repeated Loading & Unloading of the Analysis Library Generates Exception
168005 Dynamic Variable API Does Not Support I/O Servers that Use Ranges
169840 Large matrix operations that utilize the Intel MKL on Linux may crash LabVIEW
103315 Creating a circular link between an Xcontrol and a LVClass can crash LabVIEW.
95055 Save for previous fails if file path is too long
198717 Unflatten From XML fails for cluster and arrays that consist of variants
208364 LabVIEW built installers created on a 32-bit machine will not install most drivers when run on a 64-bit machine
213279 Some nodes may crash or yield incorrect/inconsistent results when Inlined
212136 "The VI is not executable. The full development version of LabVIEW is required to fix the errors" dialog on a built app
206944 Version in DataSocket Server About Box is incorrect
208088 Updating the Labels of a Cluster Written to a Chart Does Not Update the Cluster Used for Chart History
188911 Control image alignment incorrect when "new report page" VI is used
227609 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
153731 Unhandled Exception can occur if absolute path for system DLL used in CLFN
185890 Text on a VI can be mutated to appear as Unicode
218083 VIs with errors may show additional errors for code in disabled frames of Conditional Disable Structure
227030 Wait on Notification from Multiple function has unexpected behavior when ignoring previous input.
229641 Hang can occur when deploying RT project that has not been check out of VSS
232348 Changes to a library item's access scope sometimes do not update broken callers.
235019 OpenSSL fatal error when LabVIEW exits
236817 NI-Auth does not work with Firefox
243468 Default Namespaces not supported in XML Parsing VIs
185226 FXP configuration diffs don't show up when comparing VIs
176848 Picture Control Stops Updating After Setting Properties to Default.
136677 Remote panels do not work if Internet Explorer is embedded in an ActiveX or .NET Container
196607 DTbl Replace Subset VI behavior change between LabVIEW 8.6.1 and 2009
196742 Load STL Geometry VI cannot load binary STL files
226840 Formula VI does not execute pow(x,y) function
236377 Dropping XControl from public library breaks XControl
248914 Changing the order of controls or deleting controls in a type def cluster can change references
322914 Formula VI does not execute pow(x,y) function
256141 Windows 7 often shows "(Not Responding)" and will bring other windows to the front during expensive operations
248421 Bitshift does not work correctly in Expression Nodes and Formula Nodes with a data type smaller than I32
250588 Warning Generated in a Method or Property of an XControl Appears as an Error in the Top Level VI
255466 Shared variable moved from a project directly to a tab control is not added to the active page.
277283 When creating a VI Snippet with code that contains a tab control, the snippet does not properly save the contents of each tab.
257275 Format Into String does not work with the %d format for numbers larger than I32
278730 Web Services ignore No App switch on RT targets
236193 Crash with invalid input (o or negative values) of "samples per channel" when misusing TDMS Set Channel Information
245148 Class Properties dialog sometimes throws timeout error 123 when opening and must be restarted
251105 S&V XControls built as Remote Panel crashes LabVIEW.
275961 Silver style Thermometer frame doesn't resize correctly when control is resized.
289842 Get Variant Attribute VI returns wrong value if attribute not found
290105 Text Labels in Silver Control are not in silver style
238713 3D Picture Controls can display transparently or crash LabVIEW on certain graphics cards
255617 Error 1502 can occur if dependencies are placed in non executing case structures
284936 Breaking one Override VI in LVOOP shows all siblings as broken but does not explain why
306189 Deploying a Variable Library with an IO Alias to a RT Target Programmatically Returns Error 1
186808 Shared Variable library on PC is undeployed if the a V in the same project is programmatically deployed to a Real-Time target
284289 Source distributions with block diagrams removed prevents the use of static Shared Variable nodes.
252270 Stacked chart will not update all points if Digital Display is visible and on top of the chart
257194 Connector pane of a VI can change from LabVIEW 2009 to LabVIEW 2011
279373 SMTP has been updated to use port 587; LabVIEW makes use of legacy port 25
282737 Applications with Chinese characters in the executable name will throw fatal error on English Windows 7
294285 Type Defined Shared Variable not found in Executable
303342 Choose Environment dialog exit behavior is bad
305928 Saving a VI that has separated compiled code will leak memory
306025 Changing Front Panel object's font properties affects all objects that were created after it
308464 LabVIEW cannot build some large applications because it fills the image table.
320485 User Events Created from Objects Cause Broken Packed Library VIs
374195 Report Gen VIs fail with Office 2010 when built into Web Service
295415 Error message for External Data Value Reference is incorrect
306797 Cannot create indicator/control/constant for refnum datatypes from XML property and invoke nodes
310077 Variable Browse Dialog doesn't show any deployed IOVs
311279 Deploying a web service will fail
312130 Show Buffer Allocation tool shows that all inlined VIs are inplace
314062 Silver Listbox Control Does not Grey Disabled Item
314082 Listbox Control With Transparent Cell Background Does not Grey Disabled Item
310513 LabVIEW can crash when aborting a VI using Asynchronous Call by Reference
112702 Cannot read file that shows up as zero bytes.
250532 ConnectorPane.cpp can cause a VI to be unable to load
322188 VI Revision History "prompt for comment when a VI is closed" doesn't save comment
233061 4AQA5L00 LabVIEW crashes after working with Simulation Subsystem using a LabVIEW Class
239631 Memory Growth with TDMS Write
303503 When a LVM file is read by the Read from Measurement File Express VI, the Y Unit attribute is ignored.
352146 In Actor Framework based projects, interacting with the front panel of an aborted actor may cause the VI to become nonresponsive.
351506 [Mac] Test Device option on Play Waveform Express VI Configuration page doesn't output test tone
351741 Panes 'Top' pixel coordinates will vary when Windows 'Aero' is enabled/disabled
359662 Some dotted scripting property calls can crash LabVIEW if earlier properties error
356420 Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name
244551 Editing large strict type definitions can take a long time to update
288455 Shared Variable Not Updated When Changing Representation
342148 Boolean reference as first item in cluster can causes LabVIEW crash
362018 Crash when loading some VIs, saved in a previous version of LabVIEW, into LabVIEW 2012.
362925 Crash when dragging instance of Polymorphic VI from dialog to block diagram.
363464 Plots with reversed X axis display extraneous horizontal line
202192 LabVIEW UDP broadcast is inconsistent across different OS's.
358049 When a specific VI is opened, and then closed, LabVIEW remains in the task bar, with no windows open.
359369 Application Font change not applied correctly when pasting text
239719 Property page doesn't update when Adapt to Source is coerced to off
245359 Selecting a newer version of a .NET assembly does not reload assembly
316641 LabVIEW does not limit DWarn prints (to the log file) in LV 2011
321293 Event structure: OldVal Event Data Node incorrect with combobox control events
335576 Play Waveform Express VI gives error 4803 with Sample Rate 3125, 6250, 12.5K, 25K, 50K, 100K, 200K Hz
346295 You can't create a negative user-defined error codes in the Edit Error Code Assistant.
346762 [Mac] Sound VI's Device ID doesn't correctly route audio to non-default output devices.
347272 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.
353261 Conditional Indexing Terminal on Parallel For Loop with Shift Registers Runs with "Memory is Full Error"
355840 "Get Image" method is unreliable on .NET controls in LabVIEW (64-bit)
356466 Stopping VIs and immediately closing project may crash LabVIEW
356656 Crash when compiling VIs that call into a certain class based VI hierarchies
357219 Pasting into the Icon Editor stretches the clipboard image in the x and y direction.
361311 "Natural log of 1 + x" primitive incorrectly returns NaN for small positive values
361666 Tools >> Actor Framework Message Maker... is missing in Linux
361839 Boolean constant & string constants grow to length of label when cluster is type defined
362742 Updating multiple shared variables' Networking Published: Binding Project Path crashes LabVIEW
364338 "Error while retrieving database: Forbidden" connecting to a RT target via the web configuration.
364462 Crash when changing value of numeric within a typedef constant that was moved out of an array constant
369142 Front Panels may stop updating with 3+ monitors with Windows Aero enabled
368375 Compound Arithmetic node will produce incorrect results when operating on units in LabVIEW 2012
368396 Certain applications built with Application Builder fail to launch
365679 LabVIEW 3D Picture control does not work with certain AMD video card drivers
368115 HTTP POST VI will always timeout when POSTing to a Web Service using NIAuth
366331 Dynamic event registration of an array of controls fails with Error 1
374828 Updating a Library Icon and applying to existing VIs, removes custom icons from VIs
370957 Specific type of cluster sent over the network may produce incorrect results
371733 Passing array data to a Formula Node may produce incorrect results or cause LabVIEW to crash.
375002 Old library icon template persists on lower layer of VI icon after making library icon changes
381905 LabVIEW Projects will not open from disk after a crash with autosaved VIs
377021 Primitives are not correctly overloaded for Silver Matrix controls
379023 Items with colons in their localized names do not drop with Quick Drop in LabVIEW German
315663 Files inside a NIER Report have the incorrect date
361793 I/O tags with names that are the same apart from case behave different in a built application
367468 Wiring multiple inputs to Split Signals.vi causes LabVIEW to crash
371714 Slow load time when adding a VI to the Exported VIs List for a DLL
377385 Error 1390 on Dynamic VI Call to Friend Library
378888 The Mixed Signal Graph does not correctly label plots in LabVIEW 2012
378947 MD5Checksum File.vi returns the wrong value for files larger than 4GB
379444 Register Event Callback does not function in LabVIEW 2012 Base Edition
382333 The Match Regular Expression VI in LabVIEW 2012 on Linux crashes when the screen's color depth is set to 16-bit
385212 Adding and removing a registry key from a build specification can cause the build specification to become corrupt
385324 The Max&Min VI incorrectly compares NaN values in arrays of 16 or more
184689 UI Performance degredation when displaying NaN values on 3D Surface Graph in LabVIEW
362366 Packed Project Library deployment fails on Real-Time targets
364281 Specifying a file path with HTTP GET.vi using an upper case C:\ returns error 363510
364845 Streaming data to a Digital Display Chart data occasionally incorrectly displays zero even when the data is non-zero
366921 Community scoped VIs within classes in a LabVIEW library will break a packed project library and cause Error 3
367249 It is not possible to customize the Run-Time Shortcut menu of a 3D Graph
367463 References returned by Property: Controls[] of a pane containing type definitions do not match VI Server References to the control
368466 Plot visibility check box can not be toggled for plot 0 on an XY Graph
368973 Editing the scale on a numeric control or indicator within an array causes LabVIEW 2012 to crash
372644 Saving a VI that contains conditional tunnels for Previous Version in LabVIEW 2012 creates an uninitialized shift register
373150 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
376574 Launching the Getting Started Window repeatedly can launch a blank VI instead of the Getting Started Window
377164 The Unlock file and folder attribute in an installer specification has no effect in LabVIEW 2012
381656 Adding or subtracting timestamps causes a conversion to double and precision loss
384576 NI SSL Libraries not installed for LabVIEW Runtime Engine on Mac OS X
257735 Class VIs that call shared variables in a library in an auto-populating folder will not be loaded
381128 The MonthCalendar .NET control automatically resizes to the incorrect size when the VI is run
387557 LabVIEW 2012 uses 100% of one core after being open for over a day
367445 Source distribution of a class which uses dynamic dispatch can become broken looking for a missing subVI
376379 Graphs and charts have slow performance with thick line style and large data range in LabVIEW 2012
380475 Data returned from a LabVIEW built .NET Assembly that unbundles a cluster is incorrect
381707 The Render to Image method for 3D picture controls demonstrates slow performance
389295 LabVIEW 2012 SP1 breaks custom prototypes in DLLs that contain LabVIEW classes
334314 Creaing an Override VI for a child class that has a parent in a Packed Project Library gives error 1035
364607 Invalid Network VISA reference causes DAQmx calls to slow in different loop
375872 Setting a floating point numeric control to Inf, -Inf, or NaN when it is configured for relative time display format crashes LabVIEW
376714 Using the Merge VIs utility with VIs that contain a tab control causes LabVIEW to hang
369833 LabVIEW Draw VIs will sometimes create corrupt PNG images when used with the LV Image to PNG Data VI
374196 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.
389991 Memory leak when calling LabVIEW DLLs from C with new threads.
390386 LabVIEW HTTP Client does not implement Curl Rewind causing authentication errors for auth-basic.
396984 Sequential For Loops structures will sometimes execute incorrectly when VI property "Allow Debugging" is unchecked.
408844 Memory growth observed when using Asynchronous Call By Reference node in long running loop.
408845 Measurement speed can degrade when using Asynchronous Call By Reference node in long running loop.
305978 Save As Duplicate with Include All Dependencies makes a Copy of the instr.lib Folder.
388446 Eval Parsed Formula Node.vi returns incorrect results
391455 Applying an icon to LabVIEW class overwrites the icons of its methods
391784 Memory Lead when Sound VIs are Called Dynamically
392232 Autopreallocate Arrays and Strings VI Property Can Crash LabVIEW when not in FPGA Context
392446 Installing LabVIEW on a Windows Laptop Decreases Battery Life
392545 Timed Loop crashes LabVIEW after exiting
394454 Data Binding: Path property can change bindings in other VI clones
398998 3D Surface Axis Labes not Visible when Dialog Font Changed
399068 Double Numeric Slide can not be Set to 0 when it has Defined Limits with Mouse
401421 Updates to Global Variables Not Visible when Remote Debugging a LabVIEW Built Stand-Alone Application
401689 Constrained Non-Linear Optimization VI has Potential for Infinite Loop
403182 Sound Output.vi Does Not Support more than 2 Audio Channels on Windows 7
403727 Repeated Dynamic Calls to VI in Packed Project Library Can Cause Error in VI Call
404038 Unevenly Sampled Signal Spectrum VI Uses Incorrect Sample Weighting
405271 Boolean Mechanical Actions Don't Work as Expected on Windows 8 Touch Screen
406311 VI.Control Value.Set will Crash LabVIEW When Value Non-Variant Data is Used for Value Parameter
406658 LabVIEW Crash when VI for Override is Created from a Class that is Open in Two Projects.
406710 LabVIEW Crash when Inlined SubVI with Feedback Node inside of Parallel For Loop is called.
407614 Control.Delete Method Crashes LabVIEW When Used on Grouped Pictures and Free Labels
407633 Set Cell Value Method Returns Error 1604
408391 Non-printable Characters in the Description of Will Corrupt LabVIEW Classes and Libraries
408790 Palette Editor Cannot Add LabVIEW Classes
409768 Array Subset Can Cause LabVIEW 64bit to Crash
410360 LabVIEW Classes Become Corrupt When Multiple Files With Same File Name are Added to the Class
410479 Grouping ActiveX containers removes inserted ActiveX objects
410733 Ramp Pattern VI does not produce expected results
410904 Print.VI to Printer Method Always Prints Header in LabVIEW Built Applications
412912 LabVIEW Crash when VI has String Control Wired to Generate User-Defined Trace Events is Traced.
415924 Double precision numeric constants set to "bar" units sometimes use Pa units
420965 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
423373 Under certain conditions, a compiler optimization will cause array shift registers to share memory space.
429724 Under certain circumstances an internal race condition can cause the LabVIEW UI thread to stop updating front panel objects
408891 Getting an Entire Column of Data from a 2D Array in the MATLAB® Script Node Returns Only 1 Element
414839 Complex to Re/Im VI outputs incorrect value if the input is a complex waveform unless both terminals are wired
425562 Scan from String requires a space between modifiers when using SI notation
429726 LabVIEW crashes when .NET event callback calls a VI that has already been deregistered in LabVIEW.
412979 Flatten to XML String does not properly escape single and double apostrophes in a string input (' and ")
423616 If a LabVIEW executable containing .NET is included in an installer, it will fail to run when installed
416470 Using the Get Waveform Attribute in a subVI can cause incorrect data to be returned to the main VI
390021 An inlined VI can not be placed on the block diagram of a VI with subroutine priority unless it also has subroutine priority
445636 Postscript printing of graphical elements on the front panel fails
433622 LabVIEW can crash if a VI is unloaded from memory before closing its VI references
437390 File Path control does not display "Browse" dialog if Start Path is an invalid network path.
453896 Error message encountered during TestStand Deployment Utility build process may show incorrect list of VIs
360229 Class VI ,with source only turned on, loaded before a property accessor for a dynamic property it uses is broken on load
465817 LabVIEW converts a Double Precision numeric "NaN" value to integer data types differently since LabVIEW 2010



ID Known Issue
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.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 09/01/2007
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.

Reported Version: 8.0    Resolved Version: N/A    Added: 09/01/2007
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.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 09/01/2007
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

Reported Version: 8.2.1    Resolved Version: 2013    Added: 09/01/2007
47819
3N68LE00


Return
2GB file size limit of datalog files
The maximum size of datalog files is 2 GB.

Workaround: N/A

Reported Version: 8.0    Resolved Version: N/A    Added: 09/01/2007
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.

Reported Version: 8.0    Resolved Version: N/A    Added: 09/01/2007
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).

Reported Version: 8.5    Resolved Version: N/A    Added: 09/01/2007
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.

Reported Version: 8.5    Resolved Version: N/A    Added: 09/01/2007
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.

Reported Version: 8.2.1    Resolved Version: N/A    Added: 09/01/2007
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.

Reported Version: 8.5    Resolved Version: N/A    Added: 09/01/2007
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.

Reported Version: 8.0.1    Resolved Version: 2013 SP1    Added: 09/01/2007
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

Reported Version: 8.2    Resolved Version: 2013    Added: 09/01/2007
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

Reported Version: 8.0    Resolved Version: N/A    Added: 06/20/2008
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

Reported Version: 8.5    Resolved Version: N/A    Added: 07/12/2008
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.

Reported Version: 7.1    Resolved Version: N/A    Added: 08/11/2008
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.

Reported Version: 8.0    Resolved Version: N/A    Added: 08/20/2008
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.

Reported Version: 8.2.1    Resolved Version: N/A    Added: 10/06/2008
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.

Reported Version: 8.6    Resolved Version: 2013    Added: 01/14/2009
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 02/10/2009
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.

Reported Version: 7.1    Resolved Version: 2013    Added: 03/13/2009
157246

Return
The Property Node "Bring to Front" doesn't work in Windows Vista

Workaround: N/A

Reported Version: 8.6.1    Resolved Version: N/A    Added: 04/20/2009
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.

Reported Version: 8.0    Resolved Version: N/A    Added: 04/28/2009
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.

Reported Version: 2009 32-bit    Resolved Version: Unknown    Added: 07/31/2009
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.

Reported Version: 8.6    Resolved Version: N/A    Added: 08/03/2009
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.

Reported Version: 8.6    Resolved Version: N/A    Added: 09/08/2009
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.

Reported Version: 8.5    Resolved Version: N/A    Added: 09/30/2009
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 09/30/2009
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 11/10/2009
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 11/10/2009
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.

Reported Version: 8.5.1    Resolved Version: N/A    Added: 11/17/2009
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.

Reported Version: 8.5    Resolved Version: N/A    Added: 11/17/2009
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

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 02/01/2010
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 pageKnowledgeBase 5A8KPKZL: Why Isn't the NI-DAQmx Runtime Installed on a 64-bit System By My Installer?

Reported Version: 8.5    Resolved Version: N/A    Added: 02/16/2010
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 02/19/2010
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.

Reported Version: 2010 32-bit    Resolved Version: 2012 SP1    Added: 03/08/2010
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

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 03/09/2010
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 03/09/2010
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

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 06/16/2010
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.

Reported Version: 7.1.1    Resolved Version: N/A    Added: 06/16/2010
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"

Reported Version: 8.6    Resolved Version: N/A    Added: 07/23/2010
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. More details are in this KnowledgeBase

Reported Version: 8.6.1    Resolved Version: N/A    Added: 07/23/2010
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.

Reported Version: 2010    Resolved Version: N/A    Added: 07/23/2010
227030

Return
Wait on Notification from Multiple function has unexpected behavior when ignoring previous input.
This issue is described more in KnowledgeBase 5ADB14PJ

Workaround: See KB

Reported Version: 8.0    Resolved Version: N/A    Added: 07/23/2010
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 07/23/2010
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 07/23/2010
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.

Reported Version: 2010 32-bit    Resolved Version: Unknown    Added: 08/03/2010
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

Reported Version: 2010 32-bit    Resolved Version: Unknown    Added: 08/03/2010
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"),

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 08/17/2010
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

Reported Version: 2009    Resolved Version: 2013 SP1    Added: 08/30/2010
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. See KnowledgeBase 5DNA97W5 Picture Control Stopped Updating After Setting Properties to Default.

Reported Version: 8.6.1    Resolved Version: N/A    Added: 09/24/2010
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

Reported Version: 8.6    Resolved Version: N/A    Added: 10/01/2010
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

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 10/01/2010
196742

Return
Load STL Geometry VI cannot load binary STL files

Workaround: Use a different type of STL file.

Reported Version: 2009 32-bit    Resolved Version: 2013    Added: 10/01/2010
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 10/01/2010
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

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 10/01/2010
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

Reported Version: 7.1.1    Resolved Version: N/A    Added: 10/01/2010
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 10/01/2010
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 10/28/2010
248421

Return
Bitshift does not work correctly in Expression Nodes and Formula Nodes with a data type smaller than I32

Workaround: N/A

Reported Version: 8.5.1    Resolved Version: N/A    Added: 10/29/2010
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

Reported Version: 8.5.1    Resolved Version: N/A    Added: 11/02/2010
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 12/15/2010
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

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 12/15/2010
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 12/31/2010
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

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 02/10/2011
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".

Reported Version: 2010    Resolved Version: 2010 CVI    Added: 02/18/2011
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 02/18/2011
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 02/18/2011
275961

Return
Silver style Thermometer frame doesn't resize correctly when control is resized.

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 03/08/2011
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

Reported Version: 8.6.1    Resolved Version: N/A    Added: 03/21/2011
290105

Return
Text Labels in Silver Control are not in silver style

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 04/05/2011
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 Controlyada

Workaround: There have been several things that have worked for users:
  • Update the video driver
  • Turn on/off hardware acceleration
  • Turn on Aero in Windows 7
  • Turn off Aero in Windows 7


Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 04/20/2011
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

Reported Version: 8.6.1    Resolved Version: N/A    Added: 04/20/2011
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

Reported Version: 8.6.1    Resolved Version: N/A    Added: 04/20/2011
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.

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 07/06/2011
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.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 07/20/2011
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 07/20/2011
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

Reported Version: 2010 32-bit    Resolved Version: 2013    Added: 08/02/2011
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

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 08/02/2011
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 08/02/2011
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 08/02/2011
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 08/02/2011
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

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 08/02/2011
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

Reported Version: 2010 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 08/02/2011
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.

Reported Version: 2010 SP1 32-bit    Resolved Version: 2013    Added: 08/02/2011
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. Please see this KnowledgeBase for more information.

Reported Version: 8.0.1    Resolved Version: 2011 SP1 32-bit    Added: 08/02/2011
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

Reported Version: 2010 SP1 32-bit    Resolved Version: N/A    Added: 08/02/2011
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

Reported Version: 2010 SP1 32-bit    Resolved Version: 2013    Added: 08/02/2011
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.

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 08/19/2011
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

Reported Version: 8.6.1    Resolved Version: 2011 SP1 32-bit    Added: 08/30/2011
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.

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 08/30/2011
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

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 08/30/2011
312130

Return
Show Buffer Allocation tool shows that all inlined VIs are inplace
The Show Buffer Allocations tool will always show inlined VIs as inplace. 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.

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 08/30/2011
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.

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 09/07/2011
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.

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 09/07/2011
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.

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 09/12/2011
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.

Reported Version: 8.6    Resolved Version: N/A    Added: 10/20/2011
250532

Return
ConnectorPane.cpp can cause a VI to be unable to load
This internal warning can cause a VI to have a corrupt connector pane. If this occurs you will get Error Code 3: Cannot load front panel, when you attempt to open the VI.

Workaround: For more information, see KnowledgeBase 520GHNKU: LabVIEW Load Error Code 3: Could Not Load the Front Panel in the Development Environment.

Reported Version: 2010 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 11/09/2011
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

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 11/09/2011
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 11/10/2011
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.

Reported Version: 2009    Resolved Version: N/A    Added: 04/27/2012
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

Reported Version: 2010 32-bit    Resolved Version: 2013    Added: 05/01/2012
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.

Reported Version: 2012 32-bit    Resolved Version: 2013    Added: 05/04/2012
351506

Return
[Mac] Test Device option on Play Waveform Express VI Configuration page doesn't output test tone
N/A

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 05/07/2012
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.

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 05/07/2012
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.

Reported Version: 2010 SP1 32-bit    Resolved Version: N/A    Added: 07/11/2012
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

Reported Version: 2012    Resolved Version: N/A    Added: 07/13/2012
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.

Reported Version: 7.1.1    Resolved Version: N/A    Added: 07/23/2012
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)

Reported Version: 8.6.1    Resolved Version: 2011 SP1 32-bit    Added: 07/23/2012
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.

Reported Version: 8.5.1    Resolved Version: 2013    Added: 07/23/2012
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.

Reported Version: 2012 32-bit    Resolved Version: 2012 SP1    Added: 07/23/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 07/23/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 07/23/2012
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

Reported Version: 8.6.1    Resolved Version: N/A    Added: 07/24/2012
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.

Reported Version: 2010 32-bit    Resolved Version: 2013    Added: 08/02/2012
359369

Return
Application Font change not applied correctly when pasting text
n/a

Workaround: Set the font manually before pasting text.

Reported Version: 2010 32-bit    Resolved Version: 2013    Added: 08/02/2012
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.

Reported Version: 2010    Resolved Version: N/A    Added: 08/03/2012
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.

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 08/03/2012
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

Reported Version: 2011    Resolved Version: 2011 SP1 32-bit    Added: 08/03/2012
321293

Return
Event structure: OldVal Event Data Node incorrect with combobox control events
n/a

Workaround: n/a

Reported Version: 2011 32-bit    Resolved Version: 2011 SP1 32-bit    Added: 08/03/2012
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.

Reported Version: 2010 SP1 32-bit    Resolved Version: N/A    Added: 08/03/2012
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

Reported Version: 2011 32-bit    Resolved Version: 2013    Added: 08/03/2012
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

Reported Version: 2012 32-bit    Resolved Version: N/A    Added: 08/03/2012
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.

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 08/03/2012
353261

Return
Conditional Indexing Terminal on Parallel For Loop with Shift Registers Runs with "Memory is Full Error"
See KnowledgeBase 5YIEE7GW: Conditionally Indexed For Loop Terminal Uses More Memory than Expected for more information.

Workaround: Use the Build Array in a Case structure

Reported Version: 2012 32-bit    Resolved Version: N/A    Added: 08/03/2012
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

Reported Version: 2011 64-bit    Resolved Version: N/A    Added: 08/03/2012
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. For more information please see KB 63CATUYS: Closing project window may crash LabVIEW if asynchronously called VIs are stopping.

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.

Reported Version: 2012 32-bit    Resolved Version: 2013    Added: 08/03/2012
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.

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 08/03/2012
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.

Reported Version: 2011 32-bit    Resolved Version: 2013    Added: 08/03/2012
361311

Return
"Natural log of 1 + x" primitive incorrectly returns NaN for small positive values
n/a

Workaround: n/a

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 08/03/2012
361666

Return
Tools >> Actor Framework Message Maker... is missing in Linux
N/A

Workaround: This issue is fixed in the LabVIEW 2012 f1 patch.

Reported Version: 2012 32-bit    Resolved Version: 2012 SP1    Added: 08/03/2012
361839

Return
Boolean constant & string constants grow to length of label when cluster is type defined
n/a

Workaround: n/a

Reported Version: 2012 32-bit    Resolved Version: 2012 SP1    Added: 08/03/2012
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.

Reported Version: 2012    Resolved Version: 2013    Added: 08/03/2012
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/03/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 08/03/2012
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.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 09/01/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 09/13/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 09/13/2012
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.

Reported Version: 8.6.1    Resolved Version: 2012 SP1    Added: 09/14/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 09/14/2012
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

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 10/16/2012
374828

Return
Updating a Library Icon and applying to existing VIs, removes custom icons from VIs
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 10/17/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 10/18/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 10/18/2012
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

Reported Version: 2011    Resolved Version: 2013    Added: 10/18/2012
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.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 12/05/2012
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.

Reported Version: 2011    Resolved Version: 2013    Added: 01/24/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 01/25/2013
315663

Return
Files inside a NIER Report have the incorrect date
N/A

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: 2013    Added: 01/28/2013
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

Reported Version: 2011    Resolved Version: 2013    Added: 01/28/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 01/28/2013
371714

Return
Slow load time when adding a VI to the Exported VIs List for a DLL
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/28/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 01/28/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 01/28/2013
378947

Return
MD5Checksum File.vi returns the wrong value for files larger than 4GB
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: 2013    Added: 01/28/2013
379444

Return
Register Event Callback does not function in LabVIEW 2012 Base Edition
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: 2013    Added: 01/28/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 01/28/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 01/28/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 01/28/2013
184689

Return
UI Performance degredation when displaying NaN values on 3D Surface Graph in LabVIEW
N/A

Workaround: N/A

Reported Version: 2009 32-bit    Resolved Version: 2012 SP1    Added: 01/29/2013
362366

Return
Packed Project Library deployment fails on Real-Time targets

Workaround: This issue has been fixed in the LabVIEW 2012 f1 patch.

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/29/2013
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:\

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/29/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 01/29/2013
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

Reported Version: 2012    Resolved Version: 2013 SP1    Added: 01/29/2013
367249

Return
It is not possible to customize the Run-Time Shortcut menu of a 3D Graph
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 01/29/2013
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

Reported Version: 2011 32-bit    Resolved Version: 2012 SP1    Added: 01/29/2013
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

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/29/2013
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

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/29/2013
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

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/29/2013
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

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/29/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 01/29/2013
377164

Return
The Unlock file and folder attribute in an installer specification has no effect in LabVIEW 2012
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 01/29/2013
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

Reported Version: 2011    Resolved Version: N/A    Added: 01/29/2013
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"

Reported Version: 2012    Resolved Version: 2013    Added: 01/29/2013
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

Reported Version: 8.6.1    Resolved Version: N/A    Added: 02/01/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 02/01/2013
387557

Return
LabVIEW 2012 uses 100% of one core after being open for over a day
N/A

Workaround: Relaunch LabVIEW

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 02/01/2013
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

Reported Version: 8.6.1    Resolved Version: 2013    Added: 02/04/2013
376379

Return
Graphs and charts have slow performance with thick line style and large data range in LabVIEW 2012
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: 2012 SP1    Added: 02/04/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 02/04/2013
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.

Reported Version: 2012    Resolved Version: 2013    Added: 02/04/2013
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

Reported Version: 2012 SP1    Resolved Version: 2013    Added: 02/18/2013
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

Reported Version: 2011 32-bit    Resolved Version: 2013    Added: 04/29/2013
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

Reported Version: 2011 SP1    Resolved Version: 2013    Added: 04/30/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 04/30/2013
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.

Reported Version: 2011 SP1    Resolved Version: 2013    Added: 04/30/2013
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.

Reported Version: 2012    Resolved Version: 2013    Added: 05/01/2013
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.

Reported Version: 2012    Resolved Version: 2013    Added: 05/01/2013
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

Reported Version: 2009    Resolved Version: 2013    Added: 06/19/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 06/19/2013
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

Reported Version: 2012    Resolved Version: 2013    Added: 06/19/2013
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.

Reported Version: 2012 SP1    Resolved Version: 2013    Added: 07/17/2013
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.

Reported Version: 2012 SP1    Resolved Version: 2013    Added: 07/17/2013
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

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 08/02/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2010    Resolved Version: N/A    Added: 08/02/2013
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

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2011 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: 2013    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2009    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: 2013 SP1    Added: 08/02/2013
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

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 08/02/2013
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.

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 10/14/2013
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

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 10/14/2013
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

Reported Version: 2012    Resolved Version: 2013 SP1    Added: 10/14/2013
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.

Reported Version: 2012 SP1    Resolved Version: 2013 SP1    Added: 10/14/2013
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.

Reported Version: 2012    Resolved Version: N/A    Added: 10/16/2013
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 (more details available at http://digital.ni.com/public.nsf/allkb/BD88F2CE35A2691986257BE10051D214?OpenDocument )

Reported Version: 2012 SP1    Resolved Version: 2013 SP1    Added: 10/16/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 10/16/2013
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

Reported Version: 2011    Resolved Version: 2013 SP1    Added: 10/16/2013
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

Reported Version: 2012 SP1    Resolved Version: N/A    Added: 10/17/2013
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.

Reported Version: 2011    Resolved Version: 2013 SP1    Added: 10/23/2013
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.

Reported Version: 2012 SP1    Resolved Version: 2013 SP1    Added: 11/18/2013
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

Reported Version: 2012    Resolved Version: N/A    Added: 03/11/2014
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

Reported Version: 2012    Resolved Version: 2013 SP1    Added: 03/14/2014
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

Reported Version: 2012 SP1    Resolved Version: 2013    Added: 03/21/2014
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.

Reported Version: 2012    Resolved Version: N/A    Added: 03/24/2014
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

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 03/31/2014
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

Reported Version: 2011 32-bit    Resolved Version: 2013    Added: 04/15/2014
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.See KnowledgeBase 6KDJGMF0: Why Does the To Unsigned Integer Function Show Different Behavior in LabVIEW 2010 and Later Versions? for more information.

Workaround: Check if the numeric is NaN with the "Not a Number/Path/Refnum?" Function.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 04/15/2014

Document last updated on 4/16/2014

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit