LabVIEW 2012 f1 Patch crashes

I've just installed LabVIEW 2012 and unfortunately I've already run into some troubles.
I received a "Setup has stopped working" when I installed the device drivers. But the installation appeared to be fine. LabVIEW started and MAX would open. I did not try connecting to any hardware yet.
When attempting to install the f1 patch, LabVIEW crashed again. Subsequent retries net the same thing.
Has anyone else had this trouble with the patch?
This is on a Win7 machine with LV 8.6, and 2011 previously installed.
Patrick Allen
Solved!
Go to Solution.

Why do you have LabVIEW open when you are trying to install a patch? Are you running other versions of LabVIEW when performing the install? It is highly recommended you are not running anything NI when running installers from NI.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

Labview 2012 Runtime Application Crash: Access Violation Error

hi All,
my rather large app that I been develping over teh last few years has recently been crashing.
I do not know if it is since I began compiling it in LV2012 SP1 that the problem occurred or I have some programming error
that I cannot track down.
It use to run with uptimes over months, even with some memory leaks.
If I monitor using Task Manager there is no decernable increase in memory usage.
It crashes on two different systems - both running Windows XP.
The developer version running in LabVIEW 2012 f5 ( Windows XP ) does not crash. Only the runtime version crashes.
It also crashes either if the program sits idle for a few days - 5 or so ( memeory footprint stable ), or if it is used extensively to actively gather and control several instruements ( memory increase matches data size increase )
It does call several external API via ActiveX to spawn off processes, however from the lvlog.txt it seems the crashing is a simple open file that uses the NI supplied String to Config.vi.
I have double/triple check my code and I close any refernces open by the calling vi.
I am sure how to read teh mini-dump files so if someone can look at these it would be apreciated
thanks
Michael
Here are two crash logs:
Attachments:
fde86f7f-a024-417d-ac1c-d38b2e9a41e3.zip ‏61 KB
4f75c413-793d-46db-b66c-889a2f2daf69.zip ‏59 KB
00660fb7-749d-4af5-bcb1-ac5cad73a5cb.zip ‏56 KB

Hi Michael,
It's tough to tell what's going on, especially since it seems like you've really covered your bases! I'm curious about the fact that you don't see the crashes in LabVIEW (LV), just in the Run-Time Engine (RTE). Have you ever tried running it in LV for an extended period of time?
Also, do you have any loops in your program? Perhaps shrinking any waits that might be present and allowing your program to run faster would decrease the amount of time to see these errors from days to shorter.
In the future, when you get a dump file, submit it to our R&D department. It then pops up on a website that allows me to read them. I can also use win debug but that will take me a bit, so I'll have to get back to you on that.
Also, if you could take a picture of the error, that would help as well.
Julian R.
Applications Engineer
National Instruments

Force LabView 2012 SP1 f4 patch installation

Hi,
it was necessary to repair my LabView 2012 SP1 installation. When I start LV now
it has the version 12.0.1. I had installed also f4-Patch. When I try to install the f4 patch
now after my repair installation it doesn't work.
How can i force the installation of LV2012 SP1 f4 patch?
Regards

Hi Chris,
no, i don't get any error message. The installer told me only "nothing to update" as text message
inside of the installer window.
1. i have had installed LV 2012 SP1 f4
2. than LabView crashed sometimes
3. than i made a repair installation of LabView 2012 SP1 (from DVD)
4. tried to install the f4 Patch afterwards (as download and via update service, tried both)
I don't know where the patch setup gets it's information about
the installed LV 2012 version, but it seems that a repair installation
doesn't reset that information and let that info still on patch level f4.
However, i deinstalled all developer editions and removed everything from
NI and reinstalled my developer editions. That was, for me, the only way
to get my LabView back on patch level f4.
I didn't find any setup switch to force the installation (the info was shown with "/?" as parameter)
Stefan

After updating to 2012 f3 patch all built programs crash

I updated to the f3 patch yesterday and now all executables that I've built in 2012 crash without even opening. No error messages at all. Anyone else experiencing this issue on f3 and know of a solution? I've tried installing the 2012f3 runtime but it thinks it's already installed. Thanks.

Hello all,
Hopefully I can clarify this behavior a little bit -
Jeff·Þ·Bohrer wrote:
You built some executables in LabVIEW 2012 f1.
They do not execute with LabVIEW 2012f3 Run Time Engine
Correct?
(That might be expected behavior- NI?)
The runtime engine was broken by the missing files which is why your executables were not able to launch. To clarify how all the LabVIEW Runtime Engines work - each version of the runtime will execute executables built in that version of LabVIEW. For example the LabVIEW 2011 SP1 runtime can still run LabVIEW 2011, and the LabVIEW 2012 f3 runtime can still run LabVIEW 2012 f1 and LabVIEW 2012. However the runtime engine will not run code from other versions of LabVIEW, so the LabVIEW 2012 f3 RTE will not run LabVIEW 2011.
This is why you don't to have multiple runtimes within the same version of LabVIEW (you don't need a LabVIEW 2012 f3 RTE and a f2 RTE for example).
mattvx wrote:
I doubt it's anything to do with the builds themselves. All these exes worked before I patched to f3. Also I checked and I'm missing those files that the f2 patch supposedly removes.
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\tdtable.tdr
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\English\lvapps.rsc
But I think I went straight from f1 to f3 so I'm not sure how they got removed. Is it possible to just copy those files from another computer? Thanks.
This behavior can happen if the LabVIEW Run Time Engine is in use while the f1 patch is installed and then again when a later patch is installed. The reason this was a problem with the f2 patch was that LabVIEW 2012 ships with the "Variable Web Service" which uses the RTE even if all other applications have been closed. Thus in certain circumstances the f2 patch would remove those two files. We removed the f2 patch from circulation and issued the f3 patch which will restore the missing files (and adds some other fixes). The f3 patch also gets around the variable web service so that the RTE is not in use while the patch is being installed.
You went directly from the f1 patch to the f3 patch, which is entirely fine.
However, you can get into this state if you install a patch while the RTE is in use and then install a second patch to the same version of LabVIEW later while the RTE is again in use. The RTE must be in use during both installations for the files to be removed. This is not new to LabVIEW 2012 and can occur with any version of LabVIEW. Examples of things that use the RTE are the Example Finder, built executables, or certain web services (no web services ship with LabVIEW that are dependent on the RTE)
To prevent this - follow the installer instructions and close down programs that are using the RTE during the patch install process (close down all NI software and any built executables that are running).
If you do experience this - a repair installation of LabVIEW or an installation of a later patch will repopulate the missing files.
Hopefully that clears this up a little bit!
Regards,

Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW

Hi,
I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated.
Please see the attached images for more details.
Thanks
Attachments:
1.png ‏33 KB
2.png ‏71 KB
3.png ‏40 KB

Check out this thread. It looks like someone else ran into a similar issue and made changes that fixed their application.
http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
Jeff B.
Applications Engineer
National Instruments

Only have LabVIEW 2012. Why am I asked to download LabVIEW 2011 SP1 f2 RTE Patch?

Hello,
I recently got a new machine (clean install of Windows 8), and installed LabVIEW 2012, with no other previous versions. However, when I ran the NI Update Service, it listed "LabVIEW 2011 SP1 f2 R(32-bit) Run-Time Engine Patch" as a critical update.
I'm confused; did I accidentally install LV 2011 too?
Thanks
Solved!
Go to Solution.

Also, some addons use older RunTime Engines. It is not suprising that you need the 2011 RTE patch.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

XYGraph Cursor legend bug instantly crashes LabView 2012

Hi!
I am just facing a very annoying bug.
Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
It instantly crashes my LabView 2012 Full version: 12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
Anyhow, very strange and annoying behaviour...
Anyone could repeat the same bug?
Thanks for support!
Solved!
Go to Solution.
Attachments:
XYGraph_bug_test1.vi ‏149 KB

hello,
please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
thanks!
Attachments:
cursor_offset_label_via_propertynode.vi ‏12 KB

CRASH: Replacing enums in statecharts can bring LabVIEW 2012 down

Environment
Windows 8 64-bit, LabVIEW 2012 32-bit
Steps to reproduce
Open the attached project
Open Statechart.lsvc/Diagram.vi
Double-click on the blue Transition in the middle, navigate to Guard
Right-click on the enum constant -> Replace -> Select a VI...
Choose "Enum 2.ctl"
The "Select the VI to Open" dialog pops up again. Select "Enum 2.ctl" again
Observe first weird behaviour: The Guard block diagram is replaced by the enum's front panel
Click "Cancel"
Double-click on the blue Transition again. LabVIEW crashes here.
Error messages
I first encountered this in a large project with a complex statechart. This was the message shown before LabVIEW died:
With the small example I attached, there was no message at the time of crash -- LabVIEW just aborted silently. When I restarted, it showed (tested twice, same message):
Solved!
Go to Solution.
Attachments:
Statechart Crash.zip ‏138 KB

Hi JKSH,
Sorry for the incorrect post, I was talking with one of my colleagues on this issue. I was able to reproduce the issue on Windows 7 32-bit and LabVIEW 2013 (32-bit). I filled a bug report (called a Corrective Action Request or CAR) on the issue. The CAR number is 421985. You can use this to track when the CAR will be fixed as there will be a list of resolved CARs in the release notes. I also wanted to post that the workaround for this error is to just add the VI manually and then delete the original VI (as opposed to using the replace feature).
Thanks for helping find this bug.
Thanks,
Best Regards,
Bill
Notes for Branch AE:
Please reply to This Post within 24 hours
The US AE is expected to reply to all of your posts within 24 hours. Having this expectation will keep the escalation moving quickly and toward a fast resolution.
You can also use other communication channels: Phone, Sametime, Lync,etc. to discuss the issue with the US AE. This can help with troubleshooting and quick diagnosis of the issue.
Click here to provide kudos for a post on this page

LabVIEW 8.6.1 crashes

Good Day All,
   I've got an application where I'm getting intermittent crashes, sometime when in edit mode, sometimes when my program is actually running. I have gotten a couple of "MemoryManager.cpp line 437" crashes, but more often, but still intermittently, I just get the window that says something has happened to LabVIEW and it needs to be terminated. When you click on the more information link it pops up a window that says:
"AppName:labview.exe   AppVer: 8.6.0.4001 ModName: Unknown
ModVer.: 0.0.0.0        Offset 6f636974"
This happens when running the application or when editing. It may happen twice in an hour, or after several hours of running. I've watched the memory and thread usage in "Task Manager" and they seem to be stable.
The program has two main parts, a UI that at the beginning of the test run uses a .NET call to read back data over the network from the Unit Under Test, parse the returned XML string (using string functions, no "XML parsing" functions from LabVIEW or Windows) and a user interface to start the program. The UI sends a message over a queue to the "Test Engine" which then, depending on the "test recipe" installs and launches the appropriate test program using a "Call by Reference Node". The test program makes measurements of the UUT and saves the results to an Excel file using NI Report vi's from the NI Report Generation Toolkit. The measurements are visa calls to standard "rack and stack" instruments like spectrum analyzers and signal generators.
I've done a moderately deep search on the NI site, haven't found anything that looks like the issue, need ideas how to trap this beast and eliminate it.
I hope that many of the major players being at NIWeek won't impact the response time. It seems like those years I haven't been able to attend are the ones where I hit a snag like this one. I guess the moral is that I should always attend
Thanks in advance,
Putnam
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion
Solved!
Go to Solution.

Looking at this specific error, LabVIEW's memory manager has decided that a memory handle is invalid. One case in which this can happen is when different versions of LabVIEW are in use simultaneously and a data handle is passed from one version of LV to another. One such scenario would be:
LabVIEW 2009 calls the function 'myFunc' from 'foo.dll'
'foo.dll' was built using LabVIEW 8.6
'myFunc' expects an array of data, passed as a LabVIEW array handle
The problem arises in this case because the array handle allocated by the LabVIEW 2009 instance of the LV memory manager is sent to a VI running in the LabVIEW 8.6 Run-Time Engine, which has the LabVIEW 8.6 version of the memory manager. Because the data is an array handle, and LabVIEW may need to resize the handle, the code in the LV 8.6 Run-Time inspects the data handle to see if its memory manager considers it a 'good' memory handle (i.e. one that it allocated itself). It discovers that the LV 8.6 Run-Time didn't allocate the handle, and, being mistrustful of data from other memory managers ( ;-) ) it has no choice but to abort the application. It's either that or corrupt memory.
In such cases, a workaround is to pass array pointers (or strings) that cannot be resized -- an unsavory situation if the underlying implementation must resize the array (or string). The workaround in that case is more complex - e.g.. having two functions - a 'preflight' that tells you how big the output will be, and the 'actual' function that requires a properly sized output buffer.
For more complex data structures (e.g.. clusters) the workaround is to break apart the cluster into individual, simple types that can be passed as pointers to data or simple scalar values.
Whether this is at all similar to your case is unclear - it sounds like there are several component layers involved with different technologies. But the crash itself is still that LabVIEW 8.6 has gotten a memory handle from somewhere that's *not* been allocated by the LabVIEW 8.6 memory manager.
One thing you could do with Process Explorer and similar tools is determine if there are multiple versions of LabVIEW in the main process. For example, if both LabVIEW.exe and one or more lvrt.dll instances from different locations on disk are in memory, you've found a red flag. The quest then is to find out which components in your software stack are responsible for bringing in those different versions of LabVIEW, and how they're interacting via code.
Best regards,
intvsteve
LabVIEW R&D

Measurement Computing USB-DIO96H driver issue with Labview 2012 SP1 on Windows 7 x64

Is anyone else having issues with measuremetn Computing's USB-DIO96H driver in Labview 2012 SP1. It throws warnings in Labview when loaded that are unresolvable as you can't save to the DLL driver file. Also it regularily crashes Labview randomly. I am not impressed with their driver. Anyone have any suggestion other than replacing with NI-DAQ solution, which I am working on?

I've taken a look and I don't see any drivers available for that device on ni.com. There are two potential workarounds that would both involve building your own driver:
1. Write a LabVIEW application that calls functions on the DLL you downloaded from Measurements Group
2. Write a LabVIEW application that addresses the device using NI-VISA and serial communication.
Some resources if you choose to go down that path:
http://www.ni.com/devzone/idnet/development.htm
http://www.ni.com/white-paper/3271/en/
http://www.ni.com/white-paper/3009/en/
Hope this helps!
Rob B
FlexRIO Product Manager

Labview 2012

I am developing the application using labview 2012 with pci cards 6514,6221.
When I run it from design, it blinks (finished late occurs) whenever tries to output digital or analog signals with scan of 10ms. There is no blink happens at all try to save this project in lv2009 and runs.
So I would like to know whether lv2012 is creating a problem or is it needs any patch exe has to be downloaded to make it for stable run. I just thought and downloaded f5 patch too, but it says labview 2012 sp1 must be installed before installing this patch. I am not able to locate the lv 2012 sp1.
Any help is appreciated.
Thanks
Kousy

Kousy,
your information is indeed quite vague.
LV 2012 SP1 is a separate version and therefore not simply to download.
Regarding your observations:
Runtime performance is affected by many different things. As NI made some significant changes to the compiler between 2009 and 2010, i would expect your issue to come from those.
One little thing you can check for further testing: Disable debugging for your VI(s) before looking on "finished lates" of timed structure.
Also please make sure that priorities of timed structures are unique (no default 100!).
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

NI Update Service 2.1.0.103 recommends installing LV 2012 f1 patch over later version

Reporting this to NI support people as a possible bug: NI Update Service 2.1.0.103 (which came on the Aug'12 Dev Suite discs) still recommends the LV 2012 f1 patch as an urgent update, even after I installed the f3 patch.
Solved!
Go to Solution.

It's recommending the FPGA patch, not the LabVIEW core patch.
Chris M

LabVIEW 2012 and LegoNXT

Hi,
Will my EV3 Lego mindstorm brick work with LabVIEW 2012 and LabVIEW Lego MindstormNXT 2012? Because when I'm installing LabVIEW module for Lego 2012, it'sprompting me to install LV2012 SP1. I already have LV2012 but NOT SP1.
Regards.

NapDynamite wrote:
The system in my lab has no SP1, probably the guy over here never bothered to install that update. Now when I checked those updates to install SP1, the update service is locked for this patch and is asking for renewal of subscription.
My boss, who is not very cognizant of software stuff, is now asking me to use the EV3 software which comes along with LEGO pack becuase he's not ready to spend much to renew.
And my dream of teaching LabVIEW to school kids is now in vain.
Regards.
In vain?
A bit dramatic isn't it?
One license is $99.
Site license is $570.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/210666

Some fonts are not shown correctly in LabVIEW 2012

I found a bug related with fonts in LabVIEW2012 f3 KR.
- When I select NI7SEG in font selection dialog, right font is not shown in the example box.
- Draw text at point.vi shows same problem for some fonts while other fonts are working.
I reported it to Korean NI. As far as I know, this was not reported in previous versions and I couldn't find any related documents in Google.
So, here I would like to know whether it is related with only Korean version. Please let me know if English version is OK.
* OS: Windows 7 32bit KR

Just now, I installed LabVIEW 2012 f3 (32-bit, English) and checked for the issue. But the font(NI7SEG) was not shown properly in VI either.
- Both of Korea and English version of LabVIEW 2012 on Win 7 Korea OS shows wrong results. It is same on 64-bit OS.
- LabVIEW 2010 but on same PC shows correct fonts.
Is there a limit of number of fonts in LabVIEW? There are more than 100 fonts are shown in the "Selection Font" dialog and I can divide them into 3 groups by sequential order. I find that all fonts in the 3rd group are not applied correctly.
(1st group)
Arial Unicode MS...
Bookshelf Symbol 3....
Windings 3
(2nd group)
@Arial Unicode MS...
@Terminal
(3rd group)
Arial...
Consolas...
Courier...
Licida Console...
NI7SEG...
Verdana

Not able to find out the OCT 2012 CPU patch for 11.2.0.3

Hi
I am trying to download the OCT 2012 CPU patch for the 11.2.0.3 to install on Linux x86-64 which is having OS of RHEL 5.7. I am able to get the OCT 2012 PSU patch which include the CPU patch too.
Database 11.2.0.3.4 PSU Patch 14275605, or
GI 11.2.0.3.4 PSU Patch 14275572, or
But I just require only the CPU patch. Can anyone provide me the patch number or some link where I can download the Oracle CPU patch OCT 2012

The given link take to the window where CPU patch for all the quarter available.
The Critical Patch Updates released to date are listed in the following table.
Critical Patch Update Latest Version/Date
Critical Patch Update - October 2012 Rev 1, 16 October 2012
Critical Patch Update - July 2012 Rev 1, 17 July 2012
Critical Patch Update - April 2012 Rev 2, 19 July 2012
If I click on Critical Patch Update - October 2012 its takes to the window for selectin the database version (11.2.0.3). From there it goes to the Patch Set Update and Critical Patch Update October 2012 Availability Document [ID 1477727.1] which I had already checked.
There for the database products it shows the below option.
Table 9 Patch Availability for Oracle Database 11.2.0.3
+*<moderator edit - deleted MOS Doc content - pl do NOT post such content - it is a violation of your Support agreement>*+
It doesnt have the sepreate CPU patch. The below CPU patch is for the OC4J. I had a check.
Thanks
SHIYAS M

LabVIEW 2012 f1 Patch crashes

Similar Messages

Maybe you are looking for