Bug (LabVIEW 2011 sp1 crash)

Bug (LabVIEW 2011 sp1 crash)
1) Open LabVIEW
2) Blank VI
3) Front Panel / View / Class Browser
follow exactly this :
Class Browser / Object library ---> select "LabVIEW Classes" ---> and then clic "Search"
result : The window "Class Browser Search" opens ----> do nothing ... just "Cancel"
back to the window Class Browser ...
Class Browser / Object library ----> now select "DAQmx"
result : in the window Class Browser : Objet library = DAQmx
Class = DAQmx buffer
don't touch anything else (!)
and now clic "Search" ... LV CRASH

When you meet your colleagues, could you ask them, of course when they have time, to create this number.
This will make me happy, and this would be a small reward for this bug report.
Thank you very much in advance ThiCop

Similar Messages

Bug report: on LabVIEW 2011 SP1 and Windows 8 'Open URL in default browser.vi'

Dear colleagues,
Here is a bug report.
Culprit: 'Open URL in default browser.vi'.
System: Windows 8, Professional. LabVIEW 2011 SP1.
Abnormal behaviour and steps to reproduce:
Above mentioned VI doesn't work when LabVIEW was started with administrator privilegies. And it works as expected when LabVIEW running in normal (non-administrator) mode.
Looking forward to see this fixed.
Best regards,
Igor Titov.
CLD.
=========================
Igor Titov, CLA
WebPager - put LabVIEW front panels into the web page
Labicom.net

Hi Igor,
Unfortunately LabVIEW 2011 SP1 does not support Windows 8. I tested this behavior with LabVIEW 2012 SP1 on Windows 8 and everything worked correctly.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

Hello,
I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
When I run my routine, I have this error message:
Error -1074397038 occurred at IMAQ Start.vi
Possible reason(s):
NI-IMAQ: The requested serial termination string was not found in the returned buffer.
Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
Could you help me to solve this issue please?
Thanks
Bests
David Dulin

This forum post is already handled --> SR 1154262.
Kind regards,
Corné Westeneng
Applications Engineer
NI-Netherlands

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

Need link to LabVIEW 2011 SP1 Windows 32-bit download

I have been looking for the link to LabVIEW 2011 SP1 Windows 32-bit download for an hour. I thought it might be incorporated into the SP1f2 version. Nope. SP1f1 version. Nope. The ni.com search can't find it, Google can't find it, I am stuck.
Certified LabVIEW Developer
NI-VLM Administrator
Solved!
Go to Solution.

That I did not know. I guess the other question is even if you do have a right to the older version, would they not show up if you are not logged into NI.com at the time?
I would've figured that if you didn't have rights to a version, then you wouldn't be able to activate that version once you installed it. That you'd be left in evaluation mode. I didn't think that the website would block an attempt to download it.
EDIT:
I see that if you are not logged in, it says:
"Need previous versions? Access your SSP benefits by logging in."

Labview 2011 SP1

Just wondering if anyone knows if\when Labview 2011 service pack will be available? Have just got the cds for 2011 from it department, but realising that they often release a service pack in feb so don't want to waste a day installing the original on machines only to have to remove it again.
Solved!
Go to Solution.

Service Packs do generally get released, but NI don't pre-announce them. Installing LV2011 before the Service Pack isn't a big deal, you certainly don't need to "uninstall anything" before putting the Service Pack onto your computer. If you are including any addons or toolkits, these are generally not updated in the service pack so there are a number of good reasons to go ahead and put 2011 on your machine now.
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Does LabVIEW 2011 SP1 make such a big difference?

These are my working build specification in LabVIEW 2011
Any idea?
Solved!
Go to Solution.

First I spend time to upgrade to 2011SP and after update, when I find out about broken build specification. I started to question myself is it really worth spending time to upgrade?
BTW, the issue is resolved. How I have no idea. For the first 2 times I opened the project, the build specification was broken and third time I was correct. Luckily I did not save the project first 2 times.

Bug Légende Graph Labview 2011 Sp1

Bonjour à Tous,
Je ne sais pas bien ou l'on peut faire un bug report alors je post ici.
Ci joint le VI qui pose problème. La propriété Graph -> Légende -> Nombre de lignes ne fonctionne pas correctement lorsque le tableau est horizontal.
Pièces jointes :
Bug légende Graph.vi ‏20 KB

Kriss,
Merci pour ces précisions. Lorque le tableau est horizontal il n'est composé que d'une seule ligne, c'est pourquoi on récupère la valeur 1. Le noeud de propriété définit bien le nombre de lignes dans la légendes des tracés et non le nombres d'éléments.
Constates-tu bien le même comportement que moi? (A savoir nb de ligne=1)
Cordialement
Jean-Baptiste C.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Téléchargez dès maintenant toutes les présentations techniques !

Labview 2011 application crashes from time to time

Hi together,
from time to time my LV application crashes. This happens in different stages of the program.
I use some ext. DLLs written in C, some simple IO hardware and some serial communications with ext. hardware.
My feeling is that it has s.th. to do with the upgrade from LV 851 to LV 2011, but I'm not sure.
On target PC and on develpment PC we're using WXP Pro. SP3.
Many Thanks.

The crash dialog from LV indicates (most common reason) an unhandled exception thrown by a component used in your application. Therefore, the OS shuts down the process of this exception, in your case LV.
From experience, external code is a prominent source for such exceptions. You should try removing all DLL calls as a first step for pin-pointing the source of the crash. If the crash is not occuring anymore, it is most likely that a call has invalid parameters (e.g. empty array instead of a predefined buffer).
Try to boil down the issue as much as possible. To be honest, this could be a very time consuming issue, but you have little to no choice i assume.
Sidenote: Do you have the Desktop Execution Trace Toolkit? If yes, run it and observe memroy allocations, reference leaks and unhandled errors as primary parameters.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Labview 2009 SP1 crashes when moving large selection with arrow key

If I select a lot (10 or 15) of Block Diagram components and try to move them some distance with the arrow key, I will frequently get a program crash. Since a smaller number of components seems to crash after a longer travel distance, it looks like some kind of buffer overflow error. I do not see this problem when using the mouse to move selections.
I have checked to be sure I have the latest video driver for my NVIDIA Quatro FX570. I have also tried working with no hardware acceleration and no combined writes. This is happening on Windows XP SP3 with all the current updates.
It has become so bad that I have to do a Save As every fifteen minutes to keep from losing data.
Why don't I use my mouse for all movements? Because it is not as accurate and not so easy to restrict to one dimension of movement. My hand is not as steady as it once was.
I hoping someone will have a suggestion that will clear up this problem.
Solved!
Go to Solution.

As I indicated, I had the same problem with 8.5 and just DID a new installation of Labview 2009.
Since it is possible my three-monitor setup, which obviously requires more video memory, may be at the root of the problem, I am satisfied with the workaround of dragging the objects near their final destination and then using the arrow keys.
Three monitors are ideal for front panel, block diagram and Help/Internet/Probe Window. When I had to work in the field with only one monitor, I felt severely handicapped.
You may consider the matter closed.
Thanks for attempting to duplicate the failure.

BUG: LabVIEW 8.6 crashes when you save a class vi with the same name

I am running into an annoying crash. If you try to add a VI with the same name to an existing class, LabVIEW will notify you that you made an error. Once you hit OK, LabVIEW crashes. Obviously, the workaround is not to save any VI with the same name as an existing VI to your class.

I have attached a ZIP file with an example project. Open the project and open one of the VIs in Test Class. Choose File->Save As. Choose Copy->Open additional copy. Make sure the box for Add copy to Test Class.lvclass is checked.
Do NOT try to save the VI over top of the existing VI. Go to a new folder and save the VI without changing the name. LabVIEW will save the VI, then inidcate it cannot add the file due to a naming conflict. Once you hit OK, LabVIEW may or may not hang for a few seconds, then crash.
When LabVIEW restarts, it does not indicate anything happened. It just comes up with the standard startup screen.
I stumbled across this attempting to create a copy of an existing VI, but forgetting to change the name.
I confirmed this does not happen in LabVIEW 8.5.1, so the behavior is new to 8.6.
Message Edited by Matthew Kelton on 12-19-2008 07:52 AM
Attachments:
Class Test.zip ‏19 KB

FPGA LabVIEW 2011 Compilation Crash - I/O Node

When I try to compile this FPGA LabVIEW code then LabVIEW crash every during" Generating Intermediate Files"
It don't like these "FPGA I/O in" variables in FPGA I/O Node.
Constants "POT_net_1_x" are same standard DIOs.
Hardware: PXI-7841R
Solved!
Go to Solution.

Hi JCC,
Glad you got it to compile, it may have been that LabVIEW got a corrupted file somewhere in the project that was causing an issue and by rewriting the code you bypassed this problem.
If the further problems relate to a problem with FPGA compilation then you could post them here, otherwise it is probably best to create a new thread with a title that relates to that problem, that way other people will know what the thread is about and it they know the answers or have suggestions they will help.
Kind regards,
James W
Controls Systems Engineer
STFC

BUG: LabView 2009 WebServer crash

Here is a simple VI containing no controls, functions or libraries in LabView 2009 f3.
WebServer
settings are default. After Tools->Web Publishing Tool operation
from other PC we are connecting to this panel (IE6 for example) and
putting a finger to F5-button not raising it.
Web page with the VI is refreshing continiously.
There are 3 results.
1. In DevEnv: LabView die.
2. In DevEnv: Need to restart LabView so WebServer reloads and connection restores.
3. In App.exe: die
4. In App.exe: LabView interpreter loose some while-cycles in case they exist but connection stored.
5. In App.exe: connection lost but the application working good.

Link to original post
Justin Parker
National Instruments
Product Support Engineer

LabVIEW 2011 compiled application icon missing

Previously when I built an application the VI Icon would appear in the top right corner exactly the same in the compiled executable as it did in the VI.
Since upgrading to LabVIEW 2011SP1 all I get is a blank/question mark, icon missing indicator.
This happens for all of my compiled applications regardless of what icon I specify, even if I leave it as the default.
VI icon looks like this Application icon looks like this.
Just to be extra clear, there is no problem with how the exe icon appears in windows explorer and shortcuts.
I am ONLY talking about how the front panel icon in the top right corner appears.
The application works, it just looks ugly/unprofessional.
Is this a bug? Do I have something configured incorrectly? Is there a workaround? Has anyone else noticed this?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I tried building on another computer. It works properly.
My usual development machine is running Windows XP SP3.
The other computer I just tried a build on is running Windows 7 and that works fine.
I'm trying a repair of the XP installation now (I'll get back to you in a couple of hours!).
One other possible difference is that on the XP machine I installed the LabVIEW 2011 SP1 f1 patch.
Now I can't remember if I uninstalled it again afterwards. How can you tell if the patch has been applied or not?
I can't remember if I did it on the Windows 7 machine too???
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

LabVIEW Access Violation Crashes

We've been seeing numerous LabVIEW crashes when calling VIs through the LabVIEW adapter in TestStand. I've searched the knowledge base and discussion forums without success and figured I would post here before opening a help request.
The actual error we see is:
Exception: Access violation (0xC0000005) at EIP=0x012B60E6 Version: 11.0.1f1
We see these crashes several times a day, but while calling no specific VI. They happen mostly on 2 PCs that are running Windows 7 - 64 bit, but I think we've seen them in the past on PCs running the 32 bit version of Windows 7. Here is the data related to those 2 problematic PCs.
OS: Windows 7 Professional SP1 64 bit
LabVIEW: 2011 SP1 (11.0.1f1) 32 bit
TestStand: 2010 SP1 (4.5.1.134) 32 bit
PC: Dell Optiplex 790 with Intel Core i5
Other significant information.
We see these crashes when we're running the batch model in TestStand with multiple threads open. Some VIs are reentrant, and some are not.
The 2 PCs that run the batch model (with multiple threads) have the 64 bit version of Win 7 Pro, and crash most often.
The 3 PCs that run the sequential model or the batch model with a single thread have the 32 bit version of Win 7 Pro and rarely if ever have crashed.
Not sure if it's related to the OS version or the multi-thread usage and switching the PCs/OS versions to isolate that isn't easy.
Has anyone else seen similar issues? Does Windows 7 Pro 64 bit work reliably with LabVIEW 2011 32 bit?
Any information would be appreciated.
John Morrissey

Hi Amezam, thanks for your reply.
We appear to be having different access violations each time (or they are one of a large group of them, we cannot tell).
The crashes appear to be at random, we cannot connect the crashes to any specific sequences of events and we cannot reprocude the crash consistently on the same piece of code! One pattern I have noticed, however, is that the violations appear to coincide with a peak in program activity - very frequent indicator updates for instance*.
I am unable to disable antivirus protection at will, but I will raise it with our IT Support to see if we can try that.
I believe that we are intearacting with external code - 3rd party device drivers which include packed libraries. I have no control over these and, furthermore, if I were to remove them the code would not be able to function at all. However, if you think it is a good idea I can attempt to create a separate piece of code which calls the same driver function very rapidly to see if that is the problem.
As for error handling - those nodes which use them only return error codes from the base 3rd party libraries, which according to the documentation only return custom error codes (these are not related to the error/crash that we are seeing). If you think it's still possible that they will return an Access Violaton error and crash, I will link them up.**
* - sidenote: I implemented a method of reducing the number of updates to a graph indicator (from several times a second to several times a minute) - this has reduced the problem significantly.
** sidenote 2: Some of the nodes which return custom errors are linked properly, and they are not returning errors; these ones are the most likely to return errors since they are called extremely frequently. I am not seeing anything except the documented custom error codes from them.

Bug (LabVIEW 2011 sp1 crash)

Similar Messages

Maybe you are looking for