LabVIEW 2011 and 2011 SP1 Known Issues

Publish Date: Dec 05, 2014 | 7 Ratings | 2.71 out of 5 | Print

Overview

This document contains the LabVIEW 2011 known issues that were discovered before and since the release of the LabVIEW 2011 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 2011 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 Category

The following items are known issues in LabVIEW 2011 sorted by Category.

ActiveX and .NET
245359 Selecting a newer version of a .NET assembly does not reload assembly
355840 "Get Image" method is unreliable on .NET controls in LabVIEW (64-bit)
473514 TestStand ActiveX invoke nodes may not return the expected error 97 ("LabVIEW: A null or previously deleted refnum was passed in as an input.") when a null reference is used.
Analysis and Math
174929 Repeated Loading & Unloading of the Analysis Library Generates Exception
169840 Large matrix operations that utilize the Intel MKL on Linux may crash LabVIEW
332247 To Long Integer produces incorrect result for a SGL input of 2^31
361311 "Natural log of 1 + x" primitive incorrectly returns NaN for small positive values
Building and Distributing LabVIEW Applications
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
208364 LabVIEW built installers created on a 32-bit machine will not install most drivers when run on a 64-bit machine
212136 "The VI is not executable. The full development version of LabVIEW is required to fix the errors" dialog on a built app
199969 Search dialog box can hang a LabVIEW built .NET Interop Assembly when called.
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
300592 LabVIEW built executable with network streams won't exit process
255617 Error 1502 can occur if dependencies are placed in non executing case structures
282737 Applications with Chinese characters in the executable name will throw fatal error on English Windows 7
308464 LabVIEW cannot build some large applications because it fills the image table.
320485 User Events Created from Objects Cause Broken Packed Library VIs
316099 Project load time can be affected by large lvlps file
187412 Custom RTM will incorrectly link to the source location when built into an executable
323425 Build failures cased by inlined VIs in a PPL
340266 Custom I/O Servers are not included in LabVIEW Build Application
325201 Front Panel Indicators to Fail to Update Correctly When EXE is Loaded in Bad State
186525 'visarc' file included in source distribution even when excluding vi.lib
351741 Panes 'Top' pixel coordinates will vary when Windows 'Aero' is enabled/disabled
346295 You can't create a negative user-defined error codes in the Edit Error Code Assistant.
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.
367445 Source distribution of a class which uses dynamic dispatch can become broken looking for a missing subVI
334314 Creaing an Override VI for a child class that has a parent in a Packed Project Library gives error 1035
423616 If a LabVIEW executable containing .NET is included in an installer, it will fail to run when installed
445175 Two or more Static VI References between the same VIs with different strictness can result in broken executables from Application Builder
Compatibility
333463 LabVIEW 2011 will fail to launch on computers equipped with AMD FX "Bulldozer" CPU's
Controls and Indicators
219819 Center justified tables display improperly when overlapping with the front panel origin
51311 477DKPBQ LabVIEW does not maintain child-only item setting when dragging an item within a tree
52297 4AIFC0R0 Internal error related to locked tab control at fpsane.cpp line 369 and line 367.
91672 477M7K00 Large amounts of data in combo box can appear to hang LabVIEW.
45133 4I0976O4 The coercion of an enum through its digital display behaves differently in the development environment than in a LabVIEW executable.
45360 4I0EE2BQ Localization Codes do not Function for Timestamp Controls
167056 Wiring cluster of fixed point values to waveform chart causes a broken arrow
208088 Updating the Labels of a Cluster Written to a Chart Does Not Update the Cluster Used for Chart History
185890 Text on a VI can be mutated to appear as Unicode
176848 Picture Control Stops Updating After Setting Properties to Default.
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
250588 Warning Generated in a Method or Property of an XControl Appears as an Error in the Top Level VI
275961 Silver style Thermometer frame doesn't resize correctly when control is resized.
290105 Text Labels in Silver Control are not in silver style
252270 Stacked chart will not update all points if Digital Display is visible and on top of the chart
306025 Changing Front Panel object's font properties affects all objects that were created after it
314062 Silver Listbox Control Does not Grey Disabled Item
314082 Listbox Control With Transparent Cell Background Does not Grey Disabled Item
319990 Default active plot on silver Waveform Graph is incorrect
338840 Shortcut Menu Activation Interferes with Independent Autoscale Y Settings in Waveform Chart or Graph with Multiple Plots
342148 Boolean reference as first item in cluster can causes LabVIEW crash
239719 Property page doesn't update when Adapt to Source is coerced to off
365679 LabVIEW 3D Picture control does not work with certain AMD video card drivers
377021 Primitives are not correctly overloaded for Silver Matrix controls
184689 UI Performance degredation when displaying NaN values on 3D Surface Graph in LabVIEW
367463 References returned by Property: Controls[] of a pane containing type definitions do not match VI Server References to the control
364607 Invalid Network VISA reference causes DAQmx calls to slow in different loop
376714 Using the Merge VIs utility with VIs that contain a tab control causes LabVIEW to hang
DataSocket
206944 Version in DataSocket Server About Box is incorrect
External Code
153731 Unhandled Exception can occur if absolute path for system DLL used in CLFN
429726 LabVIEW crashes when .NET event callback calls a VI that has already been deregistered in LabVIEW.
File I/O
47819 3N68LE00 2GB file size limit of datalog files
243468 Default Namespaces not supported in XML Parsing VIs
285210 Read from Measurement File Express VI can read incorrect data
236193 Crash with invalid input (o or negative values) of "samples per channel" when misusing TDMS Set Channel Information
112702 Cannot read file that shows up as zero bytes.
239631 Memory Growth with TDMS Write
315798 TCP Write Stream generates add extra characters to TDMS files during FTP transfer
303503 When a LVM file is read by the Read from Measurement File Express VI, the Y Unit attribute is ignored.
257506 Write Binary on array of extended / complex extended with no array size information writes invalid data when set to write native byte ordering.
464572 Reading a datalog file truncated from more than 128 records returns error 4 "End of file encountered"
372668 The channel order is incorrect for the first TDMS group after using NI_MinimumBufferSize property.
Functions, VIs, and Express VIs
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
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
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
124783 Sound Input Read VI does not return samples requested
213279 Some nodes may crash or yield incorrect/inconsistent results when Inlined
227030 Wait on Notification from Multiple function has unexpected behavior when ignoring previous input.
235019 OpenSSL fatal error when LabVIEW exits
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
322914 Formula VI does not execute pow(x,y) function
248421 Bitshift does not work correctly in Expression Nodes and Formula Nodes with a data type smaller than I32
255466 Shared variable moved from a project directly to a tab control is not added to the active page.
192804 Error 91 occurred at the Variant To Data node
289842 Get Variant Attribute VI returns wrong value if attribute not found
306205 Error 1003 when building an executable with OpenTrace.vi within a LabVIEW Class
279373 SMTP has been updated to use port 587; LabVIEW makes use of legacy port 25
295415 Error message for External Data Value Reference is incorrect
310513 LabVIEW can crash when aborting a VI using Asynchronous Call by Reference
311293 Not A Reference does not work with FTP References
311294 FTP Close Session.vi will not unregister a session if server is unresponsive
329925 Continuous Sound Input.vi example unresponsive after pause execution
359662 Some dotted scripting property calls can crash LabVIEW if earlier properties error
202192 LabVIEW UDP broadcast is inconsistent across different OS's.
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
381656 Adding or subtracting timestamps causes a conversion to double and precision loss
465817 LabVIEW converts a Double Precision numeric "NaN" value to integer data types differently since LabVIEW 2010
384591 A password protected VI accessing a password protected community scoped VI is broken if the VIs are set to separate compiled code from source code
I/O Servers
340266 Custom I/O Servers are not included in LabVIEW Build Application
Installation and Activation
166253 LabVIEW.app does not show up after LabVIEW 2009 Installation
333463 LabVIEW 2011 will fail to launch on computers equipped with AMD FX "Bulldozer" CPU's
LabVIEW Environment
36543 4039KEG8 Edit-time crashes when many modules, drivers, and toolkits are installed
105509 The "do not save automatic changes" setting does not affect libraries
148149 Event Structure Cases can Incorrectly Remap to Other Dynamic Events
95055 Save for previous fails if file path is too long
185226 FXP configuration diffs don't show up when comparing VIs
256141 Windows 7 often shows "(Not Responding)" and will bring other windows to the front during expensive operations
258758 Setting digits of precision in Distributed System Manager has no effect.
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
238713 3D Picture Controls can display transparently or crash LabVIEW on certain graphics cards
257194 Connector pane of a VI can change from LabVIEW 2009 to LabVIEW 2011
303342 Choose Environment dialog exit behavior is bad
305928 Saving a VI that has separated compiled code will leak memory
311617 Undoing block diagram cleanup in VI with CD∼ Loop and subsystem crashes LV
312130 Show Buffer Allocation tool shows that all inlined VIs are inplace
304858 NIER is not supported on Windows Server 2003 and 2008.
317005 Several Express VIs become broken when placed on Block Diagram after Spectral Measurement VI.
250532 ConnectorPane.cpp can cause a VI to be unable to load
317952 Most RT Probes report "Not Executed" from customer's RT Main VI
321876 VI Password Protection can be defeated
322188 VI Revision History "prompt for comment when a VI is closed" doesn't save comment
333463 LabVIEW 2011 will fail to launch on computers equipped with AMD FX "Bulldozer" CPU's
331216 Rare Crash on VI Compile
341200 Continuously showing front panel control tipstrip causes slow memory leak.
244551 Editing large strict type definitions can take a long time to update
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
316641 LabVIEW does not limit DWarn prints (to the log file) in LV 2011
357219 Pasting into the Icon Editor stretches the clipboard image in the x and y direction.
334801 LabVIEW may continue to save VI after internal error, resulting in a corrupt file
369142 Front Panels may stop updating with 3+ monitors with Windows Aero enabled
375002 Old library icon template persists on lower layer of VI icon after making library icon changes
315663 Files inside a NIER Report have the incorrect date
376714 Using the Merge VIs utility with VIs that contain a tab control causes LabVIEW to hang
305978 Save As Duplicate with Include All Dependencies makes a Copy of the instr.lib Folder.
408790 Palette Editor Cannot Add LabVIEW Classes
453896 Error message encountered during TestStand Deployment Utility build process may show incorrect list of VIs
LabVIEW Object Oriented Programming
52027 4A4GRP00 Cannot use the 'New>>VI for Override...' dialog to create override of password-protected VI unless you have the password
185059 Member VIs of a class that is a member of a project library have a red X on them in the palettes
103315 Creating a circular link between an Xcontrol and a LVClass can crash LabVIEW.
245148 Class Properties dialog sometimes throws timeout error 123 when opening and must be restarted
284936 Breaking one Override VI in LVOOP shows all siblings as broken but does not explain why
293342 Preallocated reentrant LabVIEW Class Property accessors cause LabVIEW to crash
294981 Creating a copy of a class and adding it to the current project from the Save As dialog may crash LabVIEW
300225 Overriding class property accessor in a grandchild class may sometimes report an error
313044 Long Delays when editing VIs with LVOOP property nodes
233061 4AQA5L00 LabVIEW crashes after working with Simulation Subsystem using a LabVIEW Class
356656 Crash when compiling VIs that call into a certain class based VI hierarchies
334314 Creaing an Override VI for a child class that has a parent in a Packed Project Library gives error 1035
360229 Class VI ,with source only turned on, loaded before a property accessor for a dynamic property it uses is broken on load
LabVIEW Project
163371 "Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner library
232348 Changes to a library item's access scope sometimes do not update broken callers.
361793 I/O tags with names that are the same apart from case behave different in a built application
257735 Class VIs that call shared variables in a library in an auto-populating folder will not be loaded
334314 Creaing an Override VI for a child class that has a parent in a Packed Project Library gives error 1035
Logging
318415 Error reading LVM file "Incorrect file type"
Miscellaneous
296966 Selecting Cancel in the LabVIEW Report Sender dialog box will not actually cancel the sending of the report
392232 Autopreallocate Arrays and Strings VI Property Can Crash LabVIEW when not in FPGA Context
403727 Repeated Dynamic Calls to VI in Packed Project Library Can Cause Error in VI Call
Operating System Specific
157246 The Property Node "Bring to Front" doesn't work in Windows Vista
283709 Logos Sockets should broadcast on all available NICs
306797 Cannot create indicator/control/constant for refnum datatypes from XML property and invoke nodes
326123 TCP Open Connection can mishandle service locator behavior
333279 Calling the System Exec VI after calling the Pipe VI in LabVIEW for Linux will Hang LabVIEW.
351506 [Mac] Test Device option on Play Waveform Express VI Configuration page doesn't output test tone
Performance
256238 Last iteration of parallel for loop may not execute in parallel when it has non-indexing output tunnels
389991 Memory leak when calling LabVIEW DLLs from C with new threads.
429726 LabVIEW crashes when .NET event callback calls a VI that has already been deregistered in LabVIEW.
Remote Panels
97181 On a Mac, a VI that writes waveform data to a chart on the Web Server crashes the Web browser when accessed from a PC
181687 Web publishing tool fails without error
136677 Remote panels do not work if Internet Explorer is embedded in an ActiveX or .NET Container
251105 S&V XControls built as Remote Panel crashes LabVIEW.
258226 Remote Panels cannot be viewed by Safari for Mac OS X 10.6 or later
Shared Variables
141699 NI Distributed System Manager does not show deployed libraries if they contain non-Latin characters.
128059 Shared variable bindings in the same library are not updated properly when copying/renaming the library
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
168005 Dynamic Variable API Does Not Support I/O Servers that Use Ranges
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.
284802 Programmatically enabling shared variable alarm leads to deployment error and mismatch between shared variable properties and the multivariable editor.
294285 Type Defined Shared Variable not found in Executable
310077 Variable Browse Dialog doesn't show any deployed IOVs
288455 Shared Variable Not Updated When Changing Representation
257735 Class VIs that call shared variables in a library in an auto-populating folder will not be loaded
Source Code Control
229641 Hang can occur when deploying RT project that has not been check out of VSS
Toolkit - Report Generation
188911 Control image alignment incorrect when "new report page" VI is used
313610 Excel ActiveX methods lead to an error in Report Generation Toolkit 2011.
Upgrade - Behavior Change
51185 47FGSQCS Cannot save VI as the same name as missing library member VI
52263 4AJA41TQ Some operations on integer waveforms lose dt value
119444 Multi-column listbox format lost on upgrade
119204 Plot Legend Does Not Update When Using Property Nodes
198717 Unflatten From XML fails for cluster and arrays that consist of variants
218083 VIs with errors may show additional errors for code in disabled frames of Conditional Disable Structure
221113 CLFN with the wrong calling convention may silently crash LabVIEW
Upgrade - Migration
138552 Load VRML File.vi missing "error in" terminal
Web Server/Web Services
236817 NI-Auth does not work with Firefox
278730 Web Services ignore No App switch on RT targets
374195 Report Gen VIs fail with Office 2010 when built into Web Service
311279 Deploying a web service will fail
327431 Import WebService Tool doesn't work for HTTPS protocol



ID Known Issue
ActiveX and .NET
245359

Return
Selecting a newer version of a .NET assembly does not reload assembly
Changing a constructor from an old version of a .NET assembly to a newer version at edit time does not cause the new assembly to be loaded and consequently none of the new functionality is available.

Workaround: 1. Remove the old assembly so the .NET Runtime is not able to find it. It will then return the updated version to LabVIEW.2. Load the new assembly in a blank VI before opening your existing VI. This will load the new version into memory prior to you requesting the older version.

Reported Version: 2010 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
473514

Return
TestStand ActiveX invoke nodes may not return the expected error 97 ("LabVIEW: A null or previously deleted refnum was passed in as an input.") when a null reference is used.
If a null reference is wired into an Active X node and the error wire is not wired , the node may not correctly return error 97 ("LabVIEW: A null or previously deleted refnum was passed in as an input.").

Workaround: This issue has been fixed in the LabVIEW 2013 SP1 f4 Patch.

Reported Version: 2011 SP1    Resolved Version: 2014    Added: 12/03/2014
Analysis and Math
174929

Return
Repeated Loading & Unloading of the Analysis Library Generates Exception
This problem has only been reproduced on Linux using the latest versions of MKL v10.x, and has been reported to Intel as 545399. Some analysis VIs in LabVIEW use Intel's Math Kernel Library (MKL) internally to compute results. Opening these VIs or using them on another VI's diagram loads the MKL library. When all references to these analysis VIs are closed, the MKL library is unloaded from memory.When working with a VI that use these analysis VIs, the following development patterns can lead to this problem:1. Dynamically opening and closing references to the VI while no references to the analysis VIs are in memory.2. Iteratively opening and closing the VI while no other analysis VIs are loaded in memory.3. Using the File >> Close All operation in between editing one or more VIs that use the analysis VIs.

Workaround: To avoid the exception, the MKL library must remain in memory during the entire LabVIEW session. You can achieve this in many ways:1. Open the front panel of an analysis VI that loads MKL and keep it open until exiting LabVIEW.2. Open a reference to an analysis function that loads MKL and close the reference before closing LabVIEW.The A x B.vi from the Mathematics >> Linear Algebra palette is an example of analysis function that serves this purpose.

Reported Version: 2009 32-bit    Resolved Version: 2014    Added: 09/30/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
332247

Return
To Long Integer produces incorrect result for a SGL input of 2^31
For a SGL input value of 2^31 (2147483648), To Long Integer returns -2147483648 instead of saturating to 2147483647.

Workaround: Convert SGL inputs to DBL before converting to I32.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 04/27/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
Building and Distributing LabVIEW Applications
51179
47B12U5U


Return
Error 6 occurred at Create Folder in Create Directory Recursive.vi when building an application (EXE), shared library (DLL), source distribution or web service
When building a Build Specification, the build process fails with Error 6 at Create Folder in Create Directory Recursive.vi. This usually happens if the path one of the files generated by the build (temporarily during the build process or as part of the output) is too long. The operating system requires paths for files to be less than 255 characters.

Workaround: 1. Use a shorter path for your build destination (i.e. c:\build\) and if necessary copy the output to the final location you need.2. A. For application (EXE) and shared library (DLL) build specifications, place a checkmark in the Use LabVIEW 8.x file layout checkbox on the Advanced page of the Properties dialog box.2. B. For source distribution or web service build specifications, uncheck the Preserve disk hierarchy checkbox on the problem Destination on the Destinations page of the Properties dialog box.

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

Return
Search dialog box can hang a LabVIEW built .NET Interop Assembly when called.
When calling a method from a LabVIEW built assembly, it pops up the dialog showing it is searching for a dependency. This is the first problem, as users will not expect a runtime engine popping up a dialog.The second problem is that if called in a single threaded application, this dialog causes a hang.

Workaround: Place an ini file (described below) with a token telling the LabVIEW Run Time to not load this dialog. - .ini file next to .exe- INI file section name [LVRT]- INI token: "ShowLoadProgressDialog = False"

Reported Version: 2010 SP1 32-bit    Resolved Version: 2012 32-bit    Added: 04/28/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
300592

Return
LabVIEW built executable with network streams won't exit process
LabVIEW built executables that load the the network streams dll will not dispose of it properly when finished. The executable's process will remain in the task manager

Workaround: Manually kill the process after completion.

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 10/29/2010
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: 2014    Added: 04/20/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
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
316099

Return
Project load time can be affected by large lvlps file
The .lvlps file contains information about the local machine. Information about build spec outputs are stored in this file. If you have some large build specifications with many build output directories this can cause the lvlps file to grow. When you load the project with an lvlps file with this information it can cause the load time to increase significantly.

Workaround: Delete the lvlps file. This file doesn't contain information necessary for the project to load. The lvlps file will be generated when a save occurs or a build occurs.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 09/29/2011
187412

Return
Custom RTM will incorrectly link to the source location when built into an executable
If you have a custom Run-Time Menu you can include it in an executable. When we build the executable we incorrectly link to the original location of the RTM file instead of the one being brought into the build.

Workaround: Save the original RTM files in a location that you can distribute. For example if you save them in the "Data" directory that is next to where the executable will be saved this will work and create a package that isn't terrible to distribute.

Reported Version: 2009    Resolved Version: 2012 32-bit    Added: 11/02/2011
323425

Return
Build failures cased by inlined VIs in a PPL
If you have a packed project library that has inlined exported VIs, is built into another PPL and then built into another application can cause error 1003 stating that the calling VIs is not executable.

Workaround: If you get a build error 1003 stating that the top level VI is not executable, then try unlining all VIs in your packed library, or build your packed library with debug enabled option set.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 11/16/2011
340266

Return
Custom I/O Servers are not included in LabVIEW Build Application
Custom I/O Servers created with LabVIEW DSC 2011 SP1 are not included in the EXE when an application is built with Application Builder.

Workaround: This issue has been fixed in the LabVIEW 2011 SP1 f1 Patch.

Reported Version: 2011 SP1    Resolved Version: 2012    Added: 04/06/2012
325201

Return
Front Panel Indicators to Fail to Update Correctly When EXE is Loaded in Bad State
In a specific case, VIs inside the application were getting saved as 'bad', even though the application build process completed successfully. Upon load, the bad VI becomes loadable, so we are able to go ahead with the operation and run the VI. However, since the VI was bad when initially loaded, we were skipping some steps during load, one of which was initializing the front panel. Since the front panel wasn't initialized, the UI thread was ignoring the update flag and not refreshing the UI when indicators changed.

Workaround: This issue has been fixed in the LabVIEW 2011 SP1 f1 Patch.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 04/13/2012
186525

Return
'visarc' file included in source distribution even when excluding vi.lib
If you are using VISA and build a source distribution you get a copy of the visarc file with your source distribution and your VIs link to that copy.

Workaround: 1. Delete the visarc file made by the build2. Add visarc to the project under My Computer. In the build spec, add the file as Always Excluded.

Reported Version: 8.6.1    Resolved Version: 2012 32-bit    Added: 04/26/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
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
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
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
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
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
445175

Return
Two or more Static VI References between the same VIs with different strictness can result in broken executables from Application Builder
The broken executable displays the error message: "This VI is not executable. The full development version of LabVIEW is required to fix the errors."

Workaround: There are multiple potential workarounds:1. In the exectuable's build spec, uncheck the "Remove unused polymorphic VI instances" option under Additional Exclusions2. Use the old method of calling a VI using the Run VI method3. Use a Strict type specifier VI refnum instead of a Static VI reference connected to the Open VI Reference

Reported Version: 8.0.1    Resolved Version: 2014    Added: 07/30/2014
Compatibility
333463

Return
LabVIEW 2011 will fail to launch on computers equipped with AMD FX "Bulldozer" CPU's
Early in the LabVIEW load process, LabVIEW calls a DLL (niCPUlib.dll) that queries the CPU for low level information (e.g. # of cores and cache size). This DLL call causes an infinite loop when executed on a computer that contains these processors. For more information, please see KB 5U2H8PYJ.

Workaround: Please see KB 5U2H8PYJ.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 03/02/2012
Controls and Indicators
219819

Return
Center justified tables display improperly when overlapping with the front panel origin
When you add a table control to the front panel so that it overlaps with the vertical origin of the front panel, LabVIEW displays center justified columns off center when you type text. The cells appear to float or move horizontally until aligned with the vertical origin. Formerly tracked as 50061 and 42NAR8SA

Workaround: Move the table away from the front panel's vertical origin.

Reported Version: 8.0.1    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
52297
4AIFC0R0


Return
Internal error related to locked tab control at fpsane.cpp line 369 and line 367.
If you lock a tab control that is already locked using Group»Lock, you might see two internal errors and LabVIEW may crash.

Workaround: Do not lock a control that is already locked.After the fact: copy the Tab Control from the block diagram into a new VI. It will show up unlocked in the new VI.

Reported Version: 8.5    Resolved Version: 2012 32-bit    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
45133
4I0976O4


Return
The coercion of an enum through its digital display behaves differently in the development environment than in a LabVIEW executable.
The coercion of an enum through its digital display behaves differently in the development environment than in a LabVIEW executable. Neither produce an out of range value, but one coerces to the last entry in the enum, the other leaves the enum unchanged.

Workaround: Use an event structure to capture value change filter events and restore the enum to the value you choose. You can also disable the digital display for the enum.

Reported Version: 7.1    Resolved Version: 2012 32-bit    Added: 02/22/2008
45360
4I0EE2BQ


Return
Localization Codes do not Function for Timestamp Controls
According to the help, localization codes are available for format strings. They allow to specify the decimal separator and override the system decimal separator. However, this doesn't work for the Timestamp "advanced format" option.

Workaround: If you would like to discuss this issue and possible workarounds, please visit the NI Discussion Forums

Reported Version: 8.5    Resolved Version: 2012 32-bit    Added: 12/09/2008
167056

Return
Wiring cluster of fixed point values to waveform chart causes a broken arrow

Workaround: Change the representation of the number wired into the cluster to something like I64, then back to FXP

Reported Version: 8.6.1    Resolved Version: 2012 32-bit    Added: 11/17/2009
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
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
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
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
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
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
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
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
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
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
319990

Return
Default active plot on silver Waveform Graph is incorrect
Default active plot on silver Waveform Graph is set to 11. It should be 0.

Workaround: Change the control after placing.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 11/09/2011
338840

Return
Shortcut Menu Activation Interferes with Independent Autoscale Y Settings in Waveform Chart or Graph with Multiple Plots
The Autoscale Y setting is not remembered for each plot when a waveform chart that contains multiple plots also contains a Shortcut Menu Activation as a Dynamic Event Registration. By changing the setting of one axis, it becomes altered on another.

Workaround: None

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 02/17/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
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
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
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
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
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
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
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
DataSocket
206944

Return
Version in DataSocket Server About Box is incorrect
The About Box of the DataSocket Server always displays version 4.5, regardless of the installed DataSocket Version (4.5/4.6/4.7).

Workaround: N/A

Reported Version: 2009 32-bit    Resolved Version: 2014    Added: 03/09/2010
External Code
153731

Return
Unhandled Exception can occur if absolute path for system DLL used in CLFN
If you use a specific path to a system DLL (C:\windows\system\user32.dll) and build your VI into an application it will create a copy of the DLL inside the application. This can cause an unhandled exception when running

Workaround: LabVIEW searches in the system directory when looking for DLLs. If you are using a system DLL simply put the name in the in DLL Path box in the CLFN properties. In the example above you would simply put "user32.dll"

Reported Version: 8.6    Resolved Version: N/A    Added: 07/23/2010
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
File I/O
47819
3N68LE00


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

Workaround: N/A

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

Return
Read from Measurement File Express VI can read incorrect data
If you use a Write to Measurement File Express VI to write an LVM file, the data can be misinterpreted from the Read from Measurement File Express VI if the LVM file has headers. The file is correctly written; however, it is just read incorrectly.

Workaround: Don't write headers in the LVM file

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

Return
TCP Write Stream generates add extra characters to TDMS files during FTP transfer
TCP Write Stream VI checks and replaces EOL characters in text files. It also incorrectly replaced EOL character in some binary files. The Write to Binary File VI appears in the True case when it should have been placed in the False so that the EOL characters are not replaced.

Workaround: Switching the case with the Write to Binary File VI from True to False fixes the problem.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    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
257506

Return
Write Binary on array of extended / complex extended with no array size information writes invalid data when set to write native byte ordering.
If you write an extended array with no dimension size in native byte ordering (not big or little endian, but only native ordering) using Write to Binary File, the data is output as 10 byte values instead of 16 byte values.

Workaround: n/a

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 08/03/2012
464572

Return
Reading a datalog file truncated from more than 128 records returns error 4 "End of file encountered"

Workaround: N/A

Reported Version: 2011 SP1    Resolved Version: N/A    Added: 05/09/2014
372668

Return
The channel order is incorrect for the first TDMS group after using NI_MinimumBufferSize property.

Workaround: Do not wire group and channel information to the TDMS Set properties function when setting NI_MinimumBufferSize.

Reported Version: 2009    Resolved Version: 2014    Added: 05/12/2014
Functions, VIs, and Express VIs
37575
3PD8N0M8


Return
LabVIEW uses large amounts of memory when reading an entire wave file at once
The Sound File Read VI uses large amounts of memory to read an entire .wav file.

Workaround: Read the data from the .wav file in sections rather than in one large file.

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
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
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: 2014    Added: 08/20/2008
124783

Return
Sound Input Read VI does not return samples requested
If the user inputs a value of "number of samples/ch" into the Sound Input Read VI and the waveform that this returned is only 75% of the samples.

Workaround: N/A

Reported Version: 8.5.1    Resolved Version: 2012 32-bit    Added: 04/28/2009
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
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
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
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
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
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
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
192804

Return
Error 91 occurred at the Variant To Data node
Variant To Data sometimes throws an error 91 when running in a built executable in LV 2009"Error 91 occurred at ...Possible reason(s):LabVIEW: The data type of the variant is not compatible with the data type wired to the type input."

Workaround: 1) Update the variant type by generating a new one. (In an empty VI wire the typedef into the "data to variant" prim and run the VI. Then create a constant from the indicator and use this constant as the new type for the variant.)OR2) Use a Flatten Variant to String and then an Unflatten from String (not the variant version). If you wire in the control you're trying to extract from the variant, it will work like a charm.

Reported Version: 2009 32-bit    Resolved Version: 2012 32-bit    Added: 02/18/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
306205

Return
Error 1003 when building an executable with OpenTrace.vi within a LabVIEW Class
If you are building a stand alone LabVIEW executable that has the polymorphic OpenTrace.vi within a LabVIEW class error 1003 will occur during the build.

Workaround: Call the individual instance of the OpenTrace VI (Open Trace (Numeric), Open Trace (Logical), etc) instead of the polymorphic VI. These VIs can be found at C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\lvdsc\historical.

Reported Version: 2010    Resolved Version: 2012 32-bit    Added: 07/20/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
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
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
311293

Return
Not A Reference does not work with FTP References
Using the Not a Reference function from the comparison palette on a FTP refnum always returns true, even when the reference is valid.

Workaround: Extract the TCP reference using the FTP register or type cast the FTP reference to TCP and put that through the function.

Reported Version: 2011    Resolved Version: 2012 32-bit    Added: 11/09/2011
311294

Return
FTP Close Session.vi will not unregister a session if server is unresponsive

Workaround: N/A

Reported Version: 2011    Resolved Version: 2012 32-bit    Added: 11/09/2011
329925

Return
Continuous Sound Input.vi example unresponsive after pause execution
The Continuous Sound Input.vi shipping example becomes unresponsive when the VI execution is paused from the block diagram and then continued.

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 04/27/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
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
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
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
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: 2014    Added: 04/15/2014
384591

Return
A password protected VI accessing a password protected community scoped VI is broken if the VIs are set to separate compiled code from source code
This only happens if the VI source-only option set to true: Tools -> Options -> Environment Settings -> Separate Compiled Code from New Files set to true, or via the VI Properties window

Workaround: Do not separate the compiled code from the source code or remove the password

Reported Version: 2011 SP1    Resolved Version: N/A    Added: 05/09/2014
I/O Servers
340266

Return
Custom I/O Servers are not included in LabVIEW Build Application
Custom I/O Servers created with LabVIEW DSC 2011 SP1 are not included in the EXE when an application is built with Application Builder.

Workaround: This issue has been fixed in the LabVIEW 2011 SP1 f1 Patch.

Reported Version: 2011 SP1    Resolved Version: 2012    Added: 04/06/2012
Installation and Activation
166253

Return
LabVIEW.app does not show up after LabVIEW 2009 Installation

Workaround: This is only an issue for customers who installed the LabVIEW 2009 Beta for Mac. Delete /Library/Receipts/LabVIEW*9.0.pkg before running the LabVIEW 2009 installer for Mac OS.

Reported Version: 2009 32-bit    Resolved Version: Unknown    Added: 07/31/2009
333463

Return
LabVIEW 2011 will fail to launch on computers equipped with AMD FX "Bulldozer" CPU's
Early in the LabVIEW load process, LabVIEW calls a DLL (niCPUlib.dll) that queries the CPU for low level information (e.g. # of cores and cache size). This DLL call causes an infinite loop when executed on a computer that contains these processors. For more information, please see KB 5U2H8PYJ.

Workaround: Please see KB 5U2H8PYJ.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 03/02/2012
LabVIEW Environment
36543
4039KEG8


Return
Edit-time crashes when many modules, drivers, and toolkits are installed
Edit-time crashes during various operations (right-click menu selection, VI save, moving a VI from one block diagram to another, building an application [executable], shared library, or source distribution, etc.) can result from LabVIEW's image table overflowing from large amounts of palette icons being loaded in memory due to many installed modules, drivers, and toolkits. In this scenario, may receive LabVIEW error log files reporting "You filled the image table" in image.cpp.

Workaround: In Tools->Options->Controls/Functions Palettes, change the Palette Loading from "Load palettes in background" (default behavior) to "Load palettes when needed" and restart LabVIEW. This workaround does not work if you:

1. Perform a palette search.
2. Click "place me on diagram/front panel" from the LabVIEW Help.

Reported Version: 8.0.1    Resolved Version: 2012 32-bit    Added: 10/08/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
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
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
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
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
258758

Return
Setting digits of precision in Distributed System Manager has no effect.

Workaround: N/A

Reported Version: 2010    Resolved Version: 2012 32-bit    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: 2014    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
238713

Return
3D Picture Controls can display transparently or crash LabVIEW on certain graphics cards
The 3D Picture Control is built on a OpenSceneGraph which uses OpenGL. Several reports of the 3D picture control crashing LabVIEW have been reported. In almost all cases it was an Intel integrated graphics card involved. This crash is caused by an incompatibility of the graphics hardware.Note: Many of the 3D Graphs use the 3D Picture Control

Workaround: There have been several things that have worked for users:
  • 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
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
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
311617

Return
Undoing block diagram cleanup in VI with CD∼ Loop and subsystem crashes LV
If you do a block diagram clean up in a VI with a CD∼ Loop and then undo the change, LabVIEW will crash.

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: 2012 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 not having any buffer allocations. Just because a VI is inlined does not mean the inputs are inplace with the outputs.

Workaround: See if the subVI is inplace if it isn't inlined.

Reported Version: 2011 32-bit    Resolved Version: 2014    Added: 08/30/2011
304858

Return
NIER is not supported on Windows Server 2003 and 2008.
NI Error Reporting does not work on Windows Server 2003 and 2008. It also does not work if you use the "switch user" feature on Windows 7/Vista (instead of logging off the old user and logging into the new user).

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 09/12/2011
317005

Return
Several Express VIs become broken when placed on Block Diagram after Spectral Measurement VI.
1. Blank VI, all other VIs closed2. Add Spectral Measurements VI, accept default settings.3. Add Other Express VI, accept default settings ----> the VI is now broken internally (library/ownership problem).Express VIs that have shown the problem include: Signal Analysis Tone Measurement, Filter, Statistics.

Workaround: 1. Blank VI, all other VIs closed2. Add Express VI, accept default settings3. Add Spectral Measurements VI, accept default settings. ---> all as expected

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 09/29/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
317952

Return
Most RT Probes report "Not Executed" from customer's RT Main VI
An issue with some Real-Time VI's that run correctly, but most probes placed on the block diagram report "Not Executed" for their value. This occurs even as the corresponding indicators change, and as highlight execution shows the wire value.

Workaround: Place main VI code into subVI's or use front panel indicators.

Reported Version: 2011    Resolved Version: 2012 32-bit    Added: 11/09/2011
321876

Return
VI Password Protection can be defeated
It is possible for an attacker to defeat a VI’s password protection. Refer to KB: Security of LabVIEW VI Password Protection vs. Removing VI Block Diagrams. This issue will be marked as fixed when the information is in the LabVIEW Help.

Workaround: Use Remove Block Diagram for maximum protection.

Reported Version: 8.5.1    Resolved Version: 2012 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
333463

Return
LabVIEW 2011 will fail to launch on computers equipped with AMD FX "Bulldozer" CPU's
Early in the LabVIEW load process, LabVIEW calls a DLL (niCPUlib.dll) that queries the CPU for low level information (e.g. # of cores and cache size). This DLL call causes an infinite loop when executed on a computer that contains these processors. For more information, please see KB 5U2H8PYJ.

Workaround: Please see KB 5U2H8PYJ.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 03/02/2012
331216

Return
Rare Crash on VI Compile
When the VI is compiled, an intermediary representation gets into a bad state and causes the crash.

Workaround: This issue has been fixed in the LabVIEW 2011 SP1 f1 Patch.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 04/13/2012
341200

Return
Continuously showing front panel control tipstrip causes slow memory leak.
Leaving the mouse idling over a control with a tipstrip for an extended period of time with the "operate" tool selected will cause a memory leak, which can cause LV to crash (stack overflow) when the front panel of the VI is later closed.

Workaround: This issue has been fixed in the LabVIEW 2011 SP1 f1 Patch.

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

Return
LabVIEW may continue to save VI after internal error, resulting in a corrupt file
N/A

Workaround: This issue was fixed in the LabVIEW 2011 SP1 f1 patch.

Reported Version: 2011 32-bit    Resolved Version: 2012    Added: 08/30/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
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
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
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
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
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
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: 2014    Added: 03/31/2014
LabVIEW Object Oriented Programming
52027
4A4GRP00


Return
Cannot use the 'New>>VI for Override...' dialog to create override of password-protected VI unless you have the password
You use the 'New>>VI for Override...' dialog to override an ancestor VI in a LabVIEW class if the VI you want to override is password-protected.

Workaround: Make a public VI which wraps the functionality of the private VI, and instruct others to override the public VI.

Reported Version: 8.5    Resolved Version: N/A    Added: 09/01/2007
185059

Return
Member VIs of a class that is a member of a project library have a red X on them in the palettes
Normally this red X only appears when you put private or unlicensed VIs into the palettes. VIs marked with this red X still drop on block diagrams successfully.

Workaround: You can create a set of Merge VIs that are not part of the class that have just a single subVI on their block diagram that is the class VI you wanted to drop.

Reported Version: 2009    Resolved Version: 2012 32-bit    Added: 09/08/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
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
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
293342

Return
Preallocated reentrant LabVIEW Class Property accessors cause LabVIEW to crash
When you change a LabVIEW Class Property accessor to preallocated reentrant, LabVIEW may crash. The crash will be soon after making the change. The crash only occurs when there is an open VI which uses that property more than once.

Workaround: N/A

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 08/02/2011
294981

Return
Creating a copy of a class and adding it to the current project from the Save As dialog may crash LabVIEW
A bug exists in LabVIEW which may cause it to crash when using "Save As" to create a copy of a class and add it to the current project at the same time. If you have a class that has LabVIEW class properties and that class contains a VI which uses those properties, LabVIEW may crash when adding that class to the project. This only occurs when you use the check box in the Save As Dialog that says "Add copy to XYZ.lvproj"

Workaround: Don't add the class to the project from the Save As dialog. Once you've saved a copy, add it to the project separately.

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 08/02/2011
300225

Return
Overriding class property accessor in a grandchild class may sometimes report an error
If you have a grandparent (or more elder) class with a property that is both readable and writable, a parent class that overrides only the read or only the write, and a child class that overrides the opposite direction of the parent, you will get an error message stating "The property defintion adds readability or writability to an overridden property" and that "The property definition folder named "XYZ" overrides a property in a parent class and gives the child property read or write access that is not available in the parent property. Overriding properties cannot add read or write access that does not exist in the parent property"This is incorrect because you are not adding readability or the writability to the property. Instead, the check for this is incorrectly only checking the parent, instead of the eldest property.

Workaround: Add an override to the parent class (the one that overrides the read or the write) in the other direction (i.e. add a write if there's a read or vice versa) and make it directly call the parent using a call parent node.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 08/02/2011
313044

Return
Long Delays when editing VIs with LVOOP property nodes
Some VIs that contain LVOOP property nodes may show delays when editing block diagram objects that use the class. This deleting and adding terminals and wires of the specified data type.

Workaround: Use the accessor VIs instead of the property node interface.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 09/12/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
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
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
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
LabVIEW Project
163371

Return
"Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner library
Old Description :"Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner libraryIf you have a nested library, a library that is owned by another library, and you use Save As:Copy, there is an option to add the duplicate library to the original owner library. If you use this option, the member VIs of the duplicate library are all broken because they are not correctly named as members of the owning library.This bug affects all types of libraries, .lvlib, .lvclass, .xctl and .lvsc.

Workaround: Option 1: Do not use the "add to owning library" option and instead add the duplicate library to the owner manually after the copy.
Option 2: After the copy operation, open and close one of the new VIs and then move the duplicate library out of the owner library. Browse to any missing VIs that pop up a browse dialog. Move the duplicate library back into the owner library.

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

Return
Error reading LVM file "Incorrect file type"
If you save data to a LVM file using the "Overwrite once, then append to file" mode, you can potentially get an error when reading this file back. The error will show up as "incorrect file type". The problem is that the step reads back the file in 65K chuncks and if this chunk happens to end in the middle of a header section, the step will give this error.

Workaround: A potential workaround is to add a few extra lines in the beginning of the file and thus shifting where the next 65k chunk starts. Also, in general, the LVM file type is not the best file format for overwriting the file with multiple sections, thus it's better not to use this mode

Reported Version: 2010    Resolved Version: 2012 32-bit    Added: 07/30/2010
Miscellaneous
296966

Return
Selecting Cancel in the LabVIEW Report Sender dialog box will not actually cancel the sending of the report
Selecting the Cancel button in the LabVIEW Report Sender dialog box will only dismiss the dialog as NIER will continue to send the report in the background. The timeout for each session is 5 minutes, so if the send process takes more than 5 minutes - when there's a large report + slow connection - it will be terminated.

Workaround: N/A

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 08/02/2011
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
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
Operating System Specific
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
283709

Return
Logos Sockets should broadcast on all available NICs
The behavior of a UDP broadcast on a machine with multiple network adapters has changed between Windows XP and Windows 7. It's not clear at the moment whether this change was introduced in Windows 7 or Windows Vista. In Windows XP, if a UDP socket is not bound to a specific NIC, a broadcast packet would be sent on all available adapters. In Windows 7, only one adapter is used (the one with the lowest numeric IP address, which is essentially random). This link gives further details:http://serverfault.com/questions/72112/how-to-fix-the-global-broadcast-address-255-255-255-255-behavior-on-windows

Workaround: Setting the "ServiceBindTo" INI token to the MAC of the primary NIC will guarantee that broadcasts happen on that NIC. See this KB:http://digital.ni.com/public.nsf/allkb/D358BABAE2F61F1A862571570056867DHowever, this will not allow broadcasting on multiple subnets, and it will make the chosen NIC the only NIC which can perform Logos Sockets communication. New Logos XT communication will be unaffected, but this could be important for legacy apps. Note, however, that Logos Sockets can only ever use a single NIC, so any legacy app running on a mult-NIC machine has likely already bound all Logos communication to the appropriate NIC.

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

Return
TCP Open Connection can mishandle service locator behavior
Usage of TCP Open Connection primitive with a named port input (which uses the service locator) can cause unexpected behavior including crashing. Other behavior observed: infinite Reset; works when probing/single stepping but crashes when not.This issue has only been observed on Mac systems but the problem can occur across all platforms.

Workaround: A good workaround for this is to avoid using the built-in service location feature of the TCP Open prim (string name wired to port input) and instead use the utility VI "SL_Get Port.vi". This vi is located in vi.lib/utility/ServLocInterface.llb".

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 12/07/2011
333279

Return
Calling the System Exec VI after calling the Pipe VI in LabVIEW for Linux will Hang LabVIEW.

Workaround: Do not call the System Exec VI after calling the Pipe VI.

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 04/26/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
Performance
256238

Return
Last iteration of parallel for loop may not execute in parallel when it has non-indexing output tunnels
The last iteration of a parallel for loop may execute serially after all of the other iterations are finished when the loop has at least one non-indexing output tunnel. This can be particularly noticeable when the loop executes a small number of iterations and each iteration performs a large amount of work.

Workaround: Remove all non-indexing output tunnels from the loop.

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 03/21/2011
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
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
Remote Panels
97181

Return
On a Mac, a VI that writes waveform data to a chart on the Web Server crashes the Web browser when accessed from a PC
When posting a VI that writes waveform data to a chart inside a loop on the Web Server for remote front panels on a Mac, accessing the remote front panel from a PC may crash the Web browser.

Workaround: Use graphs instead of charts. If chart functionality is necessary, you can programmatically create a history of data that gets plotted to the graph on each plot.

Reported Version: 8.2    Resolved Version: 2012 32-bit    Added: 07/08/2008
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
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
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
258226

Return
Remote Panels cannot be viewed by Safari for Mac OS X 10.6 or later
Versions of Safari that shipped with Mac OS X 10.6 or later do not allow plugins that make use of older graphics API's. This means that the Remote Panels plugin needs to be rewritten to work in current versions of Safari.

Workaround: Use Firefox, or connect directly to the Remote Panel from within LabVIEW via the Operate » Connect to Remote Panel… menu.

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 08/03/2012
Shared Variables
141699

Return
NI Distributed System Manager does not show deployed libraries if they contain non-Latin characters.
If a library with non-Latin characters (such as Japanese, Chinese, or Korean) is deployed, it will not show up in the NI Distributed System Manager tree view.

Workaround: Rename the library using only the Latin alphabet and re-deploy the library.

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

Return
Programmatically enabling shared variable alarm leads to deployment error and mismatch between shared variable properties and the multivariable editor.
When programmatically generating shared variables and enabling specific alarms (HiHi, LoLo, etc.), the shared variable properties do not match the multivariable editor

Workaround: Programmatically generate the shared variables and manually enable the specific alarms using the multivariable editor.

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    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
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
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
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
Source Code Control
229641

Return
Hang can occur when deploying RT project that has not been check out of VSS
When using VSS source code control for a real time project and trying to deploy code that has not been checked off the deployment window blocks a pop up from VSS saying that the code has not been checked out. The deployment status window is modal so it does not allow you to select to proceed in the VSS window.

Workaround: In the LabVIEW project properties disable the prompts from source code control. Or you could make sure that the VIs are saved prior to deploying.

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 07/23/2010
Toolkit - Report Generation
188911

Return
Control image alignment incorrect when "new report page" VI is used
When using Append Control Image to Report.vi, the alignment of some images are ignored when New Report Page.vi is used between appended images. This problem only exists with Office 2007. Other versions - Office 2003 and Office 2010 do not exhibit this behavior.

Workaround: Use a New Report Line.vi between appending the image and the New Page.vi

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 06/16/2010
313610

Return
Excel ActiveX methods lead to an error in Report Generation Toolkit 2011.
When the examples are opened the VI has a broken run arrow and the error list says the SubVI's are not executable. SubVI's contain invoke nodes that are calling Active X methods that are not linked properly.

Workaround: Right click on reference wire into broken invoke node and select Create » Create method for 'broken invoke node' to recreate the invoke node. Then rewire and VI is fixed.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 04/27/2012
Upgrade - Behavior Change
51185
47FGSQCS


Return
Cannot save VI as the same name as missing library member VI
If a library contains a VI and the VI is missing, you should be able to save a VI as the same name as the missing VI in order to rebuild the missing VI. Currently, LabVIEW does not allow this.

Workaround: Delete the item from the library, save the new VI as the same name as the missing VI and then move the VI into the library.

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
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
119204

Return
Plot Legend Does Not Update When Using Property Nodes
When the properties of a plot legend are changed by property node or by a reference and a property node, the legend does not redraw.

Workaround: A redraw can be forced by changing the property node Plot.Name, changing the property node Legend.Visible, or a mouse movement over the plot legend.

Reported Version: 8.5    Resolved Version: 2012 32-bit    Added: 01/27/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
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
221113

Return
CLFN with the wrong calling convention may silently crash LabVIEW
LabVIEW 8.5 through 2009 could adjust the calling convention at run time if the user selected the wrong option. In 2010 this no longer happens. More information is found in KnowledgeBase 59KB14WI

Workaround: Use the correct calling convention

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 07/23/2010
Upgrade - Migration
138552

Return
Load VRML File.vi missing "error in" terminal
In LabVIEW 8.6, the "error in" terminal was removed from the Load VRML File.vi. LabVIEW 8.2/8.5 has this terminal. Thus, if a VI that has the Load VRML File VI is upgraded to 8.6, the previously working VI will be broken.

Workaround: Place a case structure around the Load VRML File VI to handle the error manually.

Reported Version: 8.6    Resolved Version: 2013    Added: 01/14/2009
Web Server/Web Services
236817

Return
NI-Auth does not work with Firefox
Web Services using NI-Auth work incorrectly in Firefox. A user's log in credentials will never be accepted.

Workaround: Use Internet Explorer

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

Return
Import WebService Tool doesn't work for HTTPS protocol
Web Services cannot be imported if they are on an HTTPS server. The same web service can be imported if it is on an HTTP server

Workaround: Use an HTTP server

Reported Version: 2010 32-bit    Resolved Version: 2012 32-bit    Added: 12/02/2011

Document last updated on 12/3/2014

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit