NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
All of the following fixes have been implemented in LabVIEW 2009 SP1. If you have upgraded to LabVIEW 2009 SP1, you do not need to install this patch. If you have not installed LabVIEW 2009 SP1 then it is strongly recommended that you install this patch.
The LabVIEW 2009 f3 patch includes all of the fixes of the LabVIEW 2009 f2 patch. Additionally it resolves the following issues:
| ID | Description |
|---|---|
| 184077 and 199423 | In rare cases a front panel object can become corrupt. After the corruption occurs, LabVIEW is unable to load the VI and will display LabVIEW load error code 3 as described in KnowledgeBase 520GHNKU: LabVIEW Load Error Code 3: Could Not Load Front Panel in the Development Environment. This patch resolves two distinct causes of this error. |
| 175141 and 197530 | After building applications, DLLs, or source distributions out of VIs containing MathScript Nodes, the VIs might become broken. The VIs error list will display MathScript Node failed to compile. This patch resolves two distinct causes of this error. |
ID 175141 and 197530 require additional steps after installing this update if your system has been affected. With LabVIEW closed, navigate to ..Documents\LabVIEW Data\InstCache\9.0 and delete the contents of the folder. These files are generated when LabVIEW compiles MathScript Nodes. To check if you have corrupt instantiation VIs in your InstCache folder, please see KnowledgeBase 553C13WI: Detecting Corrupt Instantiation VIs and MatchScript Node Failure To Compare Errors in LabVIEW 2009
Issues resolved by the f2 patch:
| ID | Description |
|---|---|
| 151665 | Memory leak when using .NET callback in LabVIEW (Windows Only) |
| 178614 | Type defined constant can lose value when updating to edited typedef if feedback node also on diagram |
| 182053 | Custom About screen not displayed with a LabVIEW built application |
| 183560 | Graph does not display timestamps on X-axis as expected when using timestamp data type |
| 185219 | Error 1502 while building a LabVIEW application |
| 185348 | VIs with very large type descriptors (like the Enum with 2000 items) will crash on load after being saved in LabVIEW 2009 |
| 185362 | Timed loops using a timing source terminal upgraded from LabVIEW 8.6 to 2009 will function correctly, but incorrectly indicate the built-in timing source is used (Windows Only) |
| 185980 | Editing An Event Structure With A String Event Might Crash Localized Versions Of LabVIEW 2009 (Windows Only) |
| 186276 | Certain references (SoftMotion, WSN...) may incorrectly refer to data associated with a different reference |
| 186418 | Image Display control does not update using Value property node in a LabVIEW built application (Windows Only) |
| 186602 | Application Builder uses too much memory, which may result in build failures |
| 187759 | Cannot launch LabVIEW 2009 when using Microsoft Mandatory User Profiles (Windows Only) |
ID 185362 and 186276 require additional steps after installing this update if you have saved your VIs in LabVIEW 2009 before installing this update. These steps are enumerated in the individual documents linked in the table above.
Related Links:
LabVIEW Support: LabVIEW 2009 Service Pack 1 Bug Fixes