From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
This document contains known issues for the various LabWindows/CVI modules and toolkits. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The known issues in this document are organized by the category of issue, and sorted by the date the issue was added to the document.
You can contact us through any of the normal support channels including phone, email, or the discussion forums. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative.
The following items are known issues in LabWindows/CVI modules and toolkits sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| CVI PID Toolkit | ||||||
| 103320 Return | Some PID example programs have clipped text on non-English operating systems. Workaround: N/A
| |||||
| 194550 Return | The Help»Online Function Help menu item does not work for PID Toolkit function panels. Workaround: N/A
| |||||
| CVI SQL Toolkit | ||||||
| 126143 Return | 64-bit integer parameters in SQL function panels use the wrong data type. Workaround: N/A
| |||||
| 130870 Return | The LabWindows/CVI SQL Toolkit can write incorrect date and time data to databases on a multibyte operating system. Workaround: N/A
| |||||
| 161601 Return | DBGetColLongLong code truncates values to INT_MAX. Workaround: N/A
| |||||
| 206582 Return | DBCreateTableFromMap can choose the wrong data types for float or double values. Workaround: N/A
| |||||
| 207683 Return | DBCreateTableFromMap can fail when the map contains a char entry. Workaround: N/A
| |||||
| 207817 Return | Date/time format strings do not properly handle format strings containing "AM/PM". 12 AM and 12 PM times are not being handled correctly. Workaround: N/A
| |||||
| 207895 Return | The GD, GDT, GL, GLT, and GT format strings return improperly formatted strings. These format strings are used to format date/time values. Appending [US] to these format strings also returns improperly formatted strings. Workaround: N/A
| |||||
| 207900 Return | Using the \<character> format string returns an error. Workaround: N/A
| |||||
| 308897 Return | DBCreateParamChar will not pass empty strings or NULL values.Workaround: To pass empty strings, use the RTRIM function on the parameters in your stored procedure to remove spaces.
| |||||
| 249898 Return | Formatting of LabWindows/CVI SQL Toolkit function panel help does not match style of standard LabWindows/CVI function panel help. Images are also missing from function panel help topics. Workaround: N/A
| |||||
| 279035 Return | DATE and TIME data types are truncated when read from a database. N/A Workaround: N/A
| |||||
| 333440 Return | The DBDeactivateSQL function hangs when called after the DBNumberOfRecords function when using an Oracle database. N/A Workaround: N/A
| |||||
| 34748 1P6DSRTL Return | Close and Discard functions can discard/release the connection handle even if an error occurs when closing the ADO object. N/A Workaround: N/A
| |||||
| 439730 Return | Building the browser2.prj shipping example fails with <command line>:28:9: error: macro names must be identifiers errors.The browser2.prj example has an incorrectly configured processor define that causes build errors.Workaround: In Options»Build Options»Compiler Defines, change /DUSE_LIST_TYPE 1 to /DUSE_LIST_TYPE=1.
| |||||
| 480852 Return | SQL Toolkit 64-bit applications always pass uninitialized data to the LabWindows/CVI ActiveX library which can result in an internal error or bad data being passed to server. Workaround: N/A
| |||||
| 480856 Return | Calling various Get Binary functions in SQL Toolkit 64-bit applications causes undefined behavior. Workaround: N/A
| |||||
| 517130 Return | DBSetParamBinary is not declared in cvi_db.h.DBSetParamBinary was changed to DBSetParamBinaryBuffer but the function panel was not updated to reflect the change.Workaround: Use DBSetParamBinaryBuffer in place of DBSetParamBinary.
| |||||
| Execution Profiler | ||||||
| 195781 Return | The PriorityInversion sample program does not generate a profile report during evaluation in 64-bit mode. Because of the 10 function limitation imposed by the Execution Profiler Toolkit in evaluation mode, none of the functions in the example are profiled. This is because there are more than 10 inline functions in Windows.h, which is included in the sample.Workaround: N/A
| |||||
| 210281 Return | The LabWindows/CVI Execution Profiler fails to load .cvip files containing profiling information for calls through function pointers defined in structures. When the file is loaded, the LabWindows/CVI Execution Profiler shows the error Could not load file: <file name>.Workaround: Open the .cvip file in a text editor. Locate a function tag containing a "name" attribute with a bogus value. Rename this value to struct_function_ptr or another similar name. This will allow you to open the file in the LabWindows/CVI Execution Profiler, but note that all calls through function pointers defined in structures will be collapsed into this one entry.
| |||||
| 330836 Return | The LabWindows/CVI Execution Profiler does not launch after an application completes execution if execution was terminated by the exit function instead of returning from main. N/A Workaround: N/A
| |||||
| 374282 Return | The Execution Profile Viewer is unable to load a CVIP file which contains an entry for a file with an ampersand (&) included in the name. This is a valid character for file names so it should load properly. Workaround: Remove ampersands from the file name entry.
| |||||
| 460558 Return | The LabWindows/CVI Execution Profiler Toolkit can be used only with the LabWindows/CVI compiler. When using an external compiler, no .cvip file is created at run time.Workaround: N/A
| |||||
| LabWindows/CVI Real-Time Module | ||||||
| 243305 Return | The LabWindows/CVI Real-Time Module cannot access RT targets that are locked Workaround: By default, RT targets are unlocked and have an empty administrator password. Avoid locking the target or setting an administrator password to access the RT target. Alternately, if you have already set an admin password by 1) Using the "Lock" operation in MAX 4.6 or earlier or 2) Using the "Set Permissions" operation in MAX 4.7 or later on a target *without* NI Web-Based Monitoring and Configuration then you can simply unlock the target from MAX using the "Lock" or "Set Permissions" action again. If you have installed NI Web-Based Configuration and Monitoring and set an administrator password from the web interface of the target, then you can undo this by first uninstalling the following two components from the RT target: NI Web-Based Configuration and Monitoring NI System configuration network support and then after the target reboots you can use the "Set Permissions" command in MAX 4.7 or later to unlock the RT target.
| |||||
| 121146 Return | Installing an application on an RT target from LabWindows/CVI or modifying the startup DLL from the RT File Copy Utility occasionally results in an internal error or a crash. Workaround: N/A
| |||||
| 144009 Return | CmtUninstallTSQCallback and CmtUninstallThreadPoolCallback functions return error -14908. In addition to the errors received when uninstalling the callbacks, the callbacks themselves are never actually called during the execution of your program. No error is reported by the callback installation functions CmtInstallTSQCallback and CmtInstallThreadPoolCallback.Workaround: N/A
| |||||
| 161478 Return | Unsubscribing and immediately subscribing to Network Variables hosted on an RT target might result in -6345 and -6382 errors. Workaround: Delay between calling CNVDispose and the CNVCreate functions.
| |||||
| 162738 Return | Using the Debug Project command to exit and restart an application from a breakpointed state in the debugger might cause the RT target to crash. Workaround: N/A
| |||||
| 167333 Return | Calling the exit function might not reboot the RT target. The program will cease executing, but the RT target will not reboot. Workaround: N/A
| |||||
| 174580 Return | System Replication functions in the Real-Time Utility Library fail when run from some host computers. Workaround: N/A
| |||||
| 180797 Return | Resource Tracking window continues to indicate a resource leak that has already been fixed until the RT target is rebooted. Workaround: N/A
| |||||
| 181147 Return | fopen does not truncate file to zero length when using w, wb, w+, or wb+ modes with Reliance File System. Workaround: If the file exists, delete it manually before writing new data.
| |||||
| 184021 Return | Abort and Reboot commands in the debugger might cause a target to hang. This issue seems to occur primarily when debugging multiple DLLs that have been deployed to the RT target. Workaround: N/A
| |||||
| 186783 Return | Breakpoints might be skipped in multithreaded applications if a watchpoint is set. This can also happen if there is an item in the Variables window that has an extended display, because most extended displays run watchpoints internally. Workaround: N/A
| |||||
| 218345 Return | Missing dependency DLL error messages can be reported when debugging or deploying an RT program. LabWindows/CVI does not always successfully locate DLL dependencies. Workaround: N/A
| |||||
| 219843 Return | RegisterTCPServerEx will return an error when called twice with the same port for two different network cards on a real-time target. Workaround: N/A
| |||||
| 221918 Return | Calling UDPWrite consecutively or in a tight loop can result in error -6822. Workaround: Sleep between calls to UDPWrite.
| |||||
| 233345 Return | The first asynchronous timer event is not called on the specified interval. The first asynchronous timer callback will always be called sooner than the specified interval. This is true only for LabWindows/CVI Real-Time applications. Workaround: N/A
| |||||
| 242498 Return | The LabWindows/CVI Real-Time Module cannot connect to a real-time target on Windows XP if the firewall is enabled. The error "The network connection was closed unexpectedly" will be reported.Workaround: Disable the Windows XP firewall.
| |||||
| 242585 Return | Selecting a LabWindows/CVI RT Target can fail if the Windows Firewall is enabled. The first time you try to connect to an RT target, you should be prompted to allow an exception in the firewall for the connection. Even if you allow the exception, connecting to the target will fail with the error "LabWindows/CVI has received an invalid reply to a debugging message".Workaround: Try connecting to the target a second time after enabling the exception.
| |||||
| 251687 Return | LabWindows/CVI crashes when browsing for a real-time target if an ethernet-to-GPIB controller is found. Workaround: N/A
| |||||
| 254504 Return | ServerTCPWrite can time out unexpectedly. This happens most often with packet sizes larger than 1KB. Workaround: N/A
| |||||
| 279032 Return | Non-void pointer types in function prototypes have an extra asterisk in the LabWindows/CVI help. All function prototypes in the LabWindows/CVI help contain an extra asterisk for non-void pointer type parameters. For example, the function GetNumListItems is written asint GetNumListItems (int panelHandle, int controlID, int **count);in the LabWindows/CVI help. However, it should be written as int GetNumListItems (int panelHandle, int controlID, int *count);This issue is only present in the compiled help accessed through the Help menu. The Function Panel help does not have this issue. Workaround: Do the following to resolve this issue:
| |||||
| 283485 Return | LabWindows/CVI threads are displayed as "StartAddr=0xZZZZZZZZ" in the Real-Time Execution Trace Tool. Workaround: N/A
| |||||
| 315278 Return | Deploying LabWindows/CVI Real-Time applications to a real-time target with particular drive configurations can cause a connection error. N/A Workaround: N/A
| |||||
| 428297 Return | Deploying LabWindows/CVI Real-Time applications to a real-time target with particular drive configurations can cause a connection error. N/A Workaround: N/A
| |||||
| 298363 Return | A custom control callback exception can occur when browsing real-time targets in the Select Real-Time Target dialog box. N/A Workaround: N/A
| |||||
| 247487 Return | Line break causes next RS-232 Library read function to return -4. The RS-232 Library read functions do not clear line break errors, causing the next read function to return a stale -4 error. Workaround: N/A
| |||||
| 305970 Return | The LabWindows/CVI Real-Time Module may crash when debugging code that uses network variables and DAQmx callbacks if Simulate RT Shutting Down is used. Workaround: Calling the DAQmxStopTask function or DAQmxClearTask function should reduce the likelihood that the crash will occur. The crash may still occur if a breakpoint is hit after selecting the Simulate RT Shutting Down option. In that case, disable Break on»Library Errors by unchecking the option in the Run»Break On menu. If the problem continues to persist, add a SleepUS function call after the call to the DAQmxClearTask function and before the end of RTMain.
| |||||
| 338815 Return | The RS-232 Library ComToFile function returns an "Unknown error" when passed a file handle opened as read-only.Workaround: N/A
| |||||
| 359921 Return | The UDP Support Library limits the maximum datagram size to 4096 bytes. Workaround: N/A
| |||||
| 360885 Return | On SMP targets, thread pool threads idle for up to 100 ms before running the next thread function. The thread is in a sleep state and is not using any processor resources during this time, but a new function cannot be scheduled on that thread until the 100 ms has elapsed. Workaround: N/A
| |||||
| 445580 Return | Adding a Break On Change watch expression when debugging causes a low priority thread to run even when a higher priority thread should be using all of the CPU resources. Workaround: N/A
| |||||
| 378400 Return | The printf console output is corrupted when called simultaneously from multiple threads.Workaround: N/A
| |||||
| 387902 Return | Asynchronous timers cannot be reset. After a timer is running, setting the Interval attribute does not change the interval at which the timer callback is triggered. Workaround:
| |||||
| 477720 Return | After installing LabVIEW Real-Time Module 2013 SP1 and LabWindows/CVI 2013 Real-Time Module on a real-time target, a fatal error occurs after installing an application. Workaround: N/A
| |||||
| 478223 Return | RT targets crash intermittently when LabWindows/CVI Real-Time DLL is set to run as startup DLL. Workaround: Add SleepUS call for approximately 10 seconds at the beginning of the RTmain function. You may need to increase the sleep period based on the RT target or the amount of software that is required to start. This SleepUS will ensure that other RT components are given time to start up before the DLL starts running.
| |||||
| 479143 Return | Resource Tracking displays leaked resources from previous runs of an application on real-time targets. The environment might display incorrect call stack values for those resources that were leaked in previous runs of a real-time application. Workaround: Rebooting the target will clear the list of previously leaked resources. You will have to do this each time you want to clear the previously leaked resources from the list.
| |||||
| 479320 Return | Resource tracking is not enabled by default in non-main threads for real-time DLLs built with Debugging level set to Extended.GetEnableResourceTracking returns FALSE.Workaround: Call SetEnableResourceTracking(1) from non-main threads.
| |||||
| 505780 Return | FormatRTSystem function will always fail on multicore real-time targets with an error message stating that the target could not be rebooted into safe mode.This issue is known to occur with SMP real-time targets. If the system is already in safe mode when the FormatRTSystem function is executed, the error will not occur.Workaround: Manually reboot the real time target into safe mode before calling the FormatRTSystem function.
| |||||
| 532473 Return | After modifying an RT application which was installed and set as a startup DLL, debugging the modified application results in the installed version running on the target. Earlier versions of LabWindows/CVI displayed an error dialog with the following text: Older versions of these DLLs are already loaded and may be in use.Workaround: Disable installed startup DLLs and restart the target before debugging.
| |||||
| 635316 Return | In rare situations, the CMTThreadPoolFunctions can cause Scheduler Assertion Error: C0000005. Workaround: N/A
| |||||
| Linux | ||||||
| 240526 Return | If two versions of the LabWindows/CVI Run-Time Module for Linux are installed, uninstalling one of them will break links to cvicc. The symbolic link to cvicc will be removed from from /usr/local/bin when uninstalling one of the two versions installed. To continue to use cvicc, either the symbolic link will need to be recreated to the version of cvicc still installed, or the full path to cvicc will need to be used.Workaround: Use the full path to cvicc, or recreate the symbolic link in /usr/local/bin
| |||||
| 243752 Return | Some fonts cannot be programmatically set by name. Workaround: N/A
| |||||
| 249722 Return | Some National Instruments libraries may fail to load on Red Hat and Red Hat derivative operating systems If SELinux is enabled on your Red Hat or Scientific Linux operating system, the following shared libraries will fail to load, causing early program termination:
chcon -t textrel_shlib_t '/usr/local/natinst/cvirte/lib/libLV100000_BLASLAPACK.so'
| |||||
| 90045 3VEB3S00 Return | TrueType fonts are not supported on Linux. Workaround: N/A
| |||||
| 90151 3W3EF800 Return | Custom mouse cursors display in the wrong location. Mouse cursors are displayed below and to the right of where they should be displayed. For example, when hovering over a splitter control, the custom cursor displays below and to the right of the mouse location. Workaround: N/A
| |||||
| 90664 3ZQG2MQ6 Return | Menu separators disappear after mousing over them. Workaround: N/A
| |||||
| 134617 Return | The trace attribute ATTR_TRACE_VISIBLE works inconsistently on Linux. The trace does not immediately disappear or reappear but instead disappears or reappears in chunks. Workaround: N/A
| |||||
| 162307 Return | Cannot set the active tab page after deleting a tab. Workaround: N/A
| |||||
| 193639 Return | The panel attribute ATTR_MOVABLE does not work when Aero is enabled. Workaround: N/A
| |||||
| 200558 Return | panels can behave erratically when their size is modified from within the panel callback as a result of a size event. Workaround: N/A
| |||||
| 230824 Return | Bitmaps do not draw properly when the color depth is 8 bits per pixel or less. Another symptom of this problem is that color maps are ignored when using the PlotIntensity and PlotScaledIntensity functions. Workaround: N/A
| |||||
| 235371 Return | cvicc returns an error code of 255 even on successful builds. Workaround: Create a wrapper script for cvicc that parses its output and tries to determine when an error occurred. Then return the appropriate error code.
| |||||
| 251009 Return | The panel attribute ATTR_MOVABLE does not work on Linux. Workaround: N/A
| |||||
| 90244 3WID0534 Return | Tabs positioned on the top right of a tab control do not display non-metafont text correctly. Workaround: Do not set the tab position to Top Right.
| |||||
| 90250 3WKAF700 Return | Dimming a tab panel does not dim the tab label. The tab panels themselves are dimmed, but the tab labels are not dimmed. Workaround: N/A
| |||||
| 250237 Return | cvicc cannot be invoked via sudo. Workaround: N/A
| |||||
| 251047 Return | Pressing Ctrl-right/left does not jump to the next/previous word boundary in the text box control. Workaround: N/A
| |||||
| 251079 Return | The down arrow on the scrollbar of a text box flickers on every keypress. Workaround: N/A
| |||||
| 247483 Return | Displaying a panel can take a long time when other threads are processing system events. While the panel is trying to display, the contents of the panel might be entirely black. Workaround: N/A
| |||||
| 248693 Return | On some Linux systems, FileSelectPopup doesn't show all the files in a directory. Workaround: N/A
| |||||
| 249669 Return | Pressing <Del> in a string control or text box results in a backspace instead of a delete. Workaround: N/A
| |||||
| 89690 3SEC9D34 Return | Rounded plot shapes and their outlines do not match up exactly. Workaround: N/A
| |||||
| 90141 3W4EGKIO Return | List box scroll bar does not redraw properly when using the mouse wheel. Workaround: N/A
| |||||
| 90143 3W3D97IQ Return | Large digital graphs do not display correctly. Workaround: Make the width of the graph smaller than 900 pixels.
| |||||
| 90224 3WKCSLZW Return | Pressing <Shift-Tab> to change the active control does not work reliably. Pressing <Shift-Tab> works on some Linux distributions, but not all. Workaround: N/A
| |||||
| 289943 Return | cvicc might crash after building binary. cvicc will crash with a segmentation fault after successfully and completely building the target binary. Workaround: A patch for the LabWindows/CVI Run-Time Module for Linux is available.
| |||||
| 290248 Return | cvicc only creates debug binaries. cvicc is supposed to create a release binary by default, or if you pass -config=release on the command line. cvicc should only create debug binaries when you pass either the -debug or -config=debug flag on the command line.Workaround: A patch for the LabWindows/CVI Run-Time Module for Linux is available.
| |||||
| 299113 Return | The help for the LabWindows/CVI Run-Time Module for Linux cannot be searched. Workaround: Use the index or the table of contents to find the topic that you're looking for.
| |||||
| 333915 Return | An application might hang if the graph or strip chart is on screen and axis labels are visible on Linux. For this problem to occur at least one axis label must be visible. When label strings get too close to the edge of the control, they will attempt to reposition themselves inward to avoid being cut off, but in some cases the repositioning algorithm will reposition to the same value and cycle endlessly. This can cause the application to stop responding on Linux. Workaround: There are two workarounds:
| |||||
| 385450 Return | The LoadPanel function may return error code 46 when loading a .tui file on a Linux system.The LoadPanel function will return an error stating that "The attribute passed is not valid".Workaround: N/A
| |||||
| 389986 Return | Loading a TUI file that contains a canvas control fails with a -12 error. Workaround: N/A
| |||||
| 425706 Return | Loading a panel containing ActiveX controls causes a segmentation fault. Workaround: N/A
| |||||
| 429443 Return | A specified font will not resize if the font does not exist in Linux. Workaround: Use a font that exists in Linux.
| |||||
| 438101 Return | Some fonts cannot be used on Linux. Workaround: N/A
| |||||
| 485486 Return | The ring select popup causes hangs in Linux. Workaround: N/A
| |||||
| 511718 Return | Asynchronous timers with a call to SetCtrlVal() within the timer callback may cause a memory leak on 64-bit Linux systems.The memory leak only occurs if SetCtrlVal is called in the callback for the asynchronous timer.Workaround: Replace the asynchronous timer with a timer control.
| |||||
Document last updated on5/22/2017
Return to the LabWindows/CVI Release Information document.