Labview 2010 dll crash issue

Hello All,
I am using LV 2010 full development system, NI vision tools 2010 and Windows XP to create a .dll to control a FLIR SC305 IR camera using the GenICam interface. The source code runs without an issue in the LV environment and the dll compiles without an issue. The code is very simple, only using a few string controls and indicators and the configuration vi's to load attribute names used to control the camera.
When I test the dll in labview it runs but LV either locks up or disappears completely. I have attached the source and dll calling convention I am using.
Best Regards,
Karl
Attachments:
ini dll proto.vi ‏42 KB
test ini.vi ‏9 KB

Hello,
I have tried the "Run In Any Thread" with the same results. I have attached the build log file if that is useful.
Regards,
Karl
Attachments:
FLIR A325 Controller_RATT SC305 INI_log.txt ‏9 KB

Similar Messages

LabVIEW 2010 F2 - Crash - Localization issue ?

Hi fellows !
I am using LabVIEW 2010 F2 (French localized version) and I am facing this strange behavior. Can you confirm that this is a bug and / or this is because I am using a localized version of LabVIEW ?
When using the Modifications:VI property node (CTRL+SHIFT+B) and connecting its output to a case structure everything works fine (it looks like that).
But now if I change the Modifications:VI property to Modifications:Front Panel and let the output of the property node connected to the case structure, LabVIEW crashes or the broken arrow appears.
If I click on the broken arrow or try to save the VI (CTRL+S), I get the following error message :
Fpsane.cpp line 442
Thanks for your help.
Regards,
Da Helmut
Attachments:
err.PNG ‏11 KB
test.png ‏14 KB
test.vi ‏7 KB

Hi,
Thanks for the answer.
There is another bug with LabVIEW 2010 (F4 this time).
To reproduce it you have to create a (strict) type definition that consists of a cluster and put a constant which is linked to this typedef on the BD (just select the .ctl file in the BD) and then delete the type definition from the hard drive.
Close the VI that has the constant in the BD.
Re-open the VI, and in the BD, right click on the cluster constant and select "View as Icon". Now you get LabVIEW crashed. (ok it is useless doing that on a non existing typedef but this is crashing LabVIEW, so I thought this should be reported).
Keep me informed if you have any further informations about that.
Regards,
Da Helmut

Error 404 causes Labview 2010 to crash but only occasionally

Hello,
I am requesting help to solve a problem with LabVIEW 2010 crashing. I am new to this company and the last Labview developer left without providing
background on this problem. Labview crashes after running project VIs. Labview closes without warning or error messages. The project acquires data from pressure transducers, dP transducers, thermocouples, IEPE, load cells, and voltages through NI real-time system and has digital I/O. NI hardware includes PXI-1050 with modules 6221, 6280, 6224, 6220 and NI PXI-1052, SCXI-1306, SCXI-1112, SCXI-1520, and SCXI-1102. I've reviewed the labview program and the software relies heavily on shared variables, references, and local variables but I cannot find anything that stands out as a problem in the software .
The program crashed again today after running for only 1/2 hour and was not recording data. No error message occurred before the crash and the only error after restarting LabVIEW was the standard message that LabVIEW did not close properly. I went to the Event Viewer and at the time of the crash I received the following information:
Event ID = 3299
Source = LabVIEW
Log = Application
Level = Error
LabVIEW Information: Error 404 "Not found" for "/national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport", file "Crogram files (x86)/ national instruments /shared/ ni webserver/ www/ national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport": Can't access URL
According to Event Viewer, this error 3299 occurred 15 times in the last 3 days. LabVIEW crashed today at 10:19 am at the same time this error 3299 occurred but LabVIEW did not crash the other times this error occurred in the last 3 days. I believe this error is related to the crash but does not usually cause the crash. It appears to me from reading the error message that the error is the result of occasional lose of communication with the real-time system (Can't find URL). Any suggestions how to resolve this would be greatly appreciated.
Bill

1. Have you had this code working before on this or another machine?
2. Which operating system and version of LabVIEW are you running? (This can be found in Control Panel >> All Control Panel Items >> System)
3. Which National Instruments Drivers are you using? (This can be found in the measurement an automation explorer under the software tab [a screenshot would be good])
I would look into removing afsetup.exe which is a data collection tool provided by Microsoft which could a) not be installed correctly and/or b) trying to pull data from LabVIEW. I think this may help you out, as even though your programs aren't explicitly calling it, the service is running in the background.
Secondly, I would look into stopping the NI Web Server application that could be polling a web page that's not needed.

LabVIEW 2010 crashes when changing representation of TypeDef

Hello NI,
I have to report a bug
which causes LV 2010 to crash with error in "datamgr.cpp", line 2720.
This crash is reproduceable.I use LabVIEw 2010, 32 bit on Windows 7.
To cause this crash you have to perform the
following steps (I attached a sample VI to reproduce these steps.):
Place a ring control on the FP, change
representation to I32
On the BD, create a property node “Strings
And Values[]”
The datatype of this property is Array of
Cluster with 2 Elems, “String” & “Value”, where “Value” is of type I32
Create a control of this property,
surprisingly the type of Value is “extended”
On the FP, select the cluster inside the
array, click “Customize Control…” from Edit- menu
In the Control- Editor change the DataType
of Value to I32, then exit the Control Editor without saving the control,
but replacing the original cluster
LabVIEW 2010 will crash with the error
message stated above
The problem is to change the
representation of the cluster element, where the cluster is part of a typedef. A
solution is to forbid to call the “Customize”- editor directly from the FP (not
nice) or to forbid to replace the orginal control, instead force the user to
save the altered control to a .ctl (nicer).
This shows a general problem with TypeDefs,
where the array of a not-typedefed cluster is typedefed. This was discussed
earlier with the cursor list of waveform graphs (couldn’t find it anymore, but
read it in this forum) where this problem also can occur. So this is an appeal
to National Instruments to change the TypeDef to the clusters and make arrays
of them.
And, after all, for me it is
unexpected behaviour that a constant / control / indicator, created from a
property (or any terminal / node I can find on the BD) has another datatype
than the original terminal or node.
Greets, Dave
Picture 1: Type of property node
Picture 2: Type of created control
Picture 3: Error message
Greets, Dave
Attachments:
Ring TypeDef Problem.vi ‏66 KB

Hi All,
I am also facing the same bug from the long time which causes loss of data unexpected.Please solve this bug and tell me any way to solve this.I am using Control Type Def in my project.
Thanks
Yogeshwar
Attachments:
error.jpg ‏19 KB

LabVIEW 2010 Crash

All,
LabVIEW 2010 now crashes every time I try and open it. It seems to crash at the "loading plugins" phase. I don't recall what I did to cause this. How can I solve this?
Also there's no error log in the LabVIEW data folder under my documents.
Regards,
Ken

Has anything changed about the system? Has the system ever been in a working state? Has the computer received recent updates from IT or the OS? Did you face any installation problems?
Has any third party software been recently installed on the computer?
Thank you very much for your time and follow up. Perhaps an installation repair for LabVIEW would assist in ensuring all the correct files are still on disk, in case anything may have been deleted.
Cheers,
Patrick Corcoran
Application Engineering Specialist | Control
National Instruments

Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

I build an application exe and then its installer along with run time environment.
The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: AGMS.exe
Application Version: 1.3.0.0
Application Timestamp: 4c24e8f5
Fault Module Name: lvrt.dll
Fault Module Version: 10.0.0.4033
Fault Module Timestamp: 4c9273f4
Exception Code: c0000005
Exception Offset: 00005310
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell System XPS L502X
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 8106MB RAM
Page File: 3457MB used, 12753MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: HuronRiver Platform
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
Memory: 4096MB RAM
Available OS Memory: 4010MB RAM
Page File: 1359MB used, 6658MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
Now as I see it, it could be a Run-time environment mis-match error.
For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
I checked DEP, for all 3 PCs and it was set to the following
Turn on DEP for essential Windows programs and services only (first option).
I am confused. I can not find a solution for this and it is really frustrating.

But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
Since from the picture you can see its including the support installers from '\Program Files (x86)\'
The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
Yes I did reboot every time after I ran the installation.
Still getting the same error.

LabVIEW 2010 crash when calling user32.dll

Interesting LabVIEW 2010 "feature" I discovered this morning.
Attached are two identical VIs, one saved in 2010 and one saved in 2009. These VIs were specifically written to demonstrate the bug I stumbled upon this afternoon. Each VI when run should allow you to find a specific program (window) open in Microsoft Windows and bring it to the foreground. It relies on "user32.dll" to perform this operation. It also allows you to specify the calling convention for the function call.
In LV 2009, either calling convention works, without error. However, in LV 2010 the calling convention for the function must be "stdcall (WINAPI)" and not the default "C". If the calling convention is "C" then LabVIEW crashes and closes without warning.
If you happen to have both LV 2009 and LV 2010 on your computer, I would love to hear if this phenomenon is duplicated so that I can pinpoint whether the bug is LV 2010 related or is more specific to my personal setup.
Thanks,
~David
Solved!
Go to Solution.
Attachments:
LV2010 test.vi ‏13 KB
LV2009 test.vi ‏14 KB

221113
Return
CLFN with the wrong calling convention may siliently 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: N/A
Added: 07/23/2010
From 2010 release notes.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Labview 2010 crash at startup windows 7

Hi,
Labview crashes on startup. I get this message: "Labview 10.0 Development System has stopped working." I don't get any further than this.
I have 95 computers running Windows 7 64-bit Enterprise. To install Labview on these I use the automated installer with these options: "/q /acceptlicenses yes /r:n /applyspecfile k:\zfdmsi\Labview2010\yellow1\".
This was working on Windows XP. I have tried to install Labview manually on one of the windows 7 computers and it works fine.. But I cant do that on 95 computers...
Any ideas why it's crashing?
Thanks in advance.
Solved!
Go to Solution.

Yes, m: is a network drive. We have a local policy on all workstations redirecting My Documents to the M: drive.
I got the issue resolved by installing Labview 2010 SP1

LabVIEW 2010 in-placeness crash bug

[cross-posted to LAVA]
I found an odd LabVIEW 2010 bug that will cause a hard crash. The bug appears to be related to how LabVIEW operates on data in-place and some interaction between clusters, arrays, and the Aum Array Elements node. It's hard to describe verbally, so I'll just draw you a picture
LabVIEW 2010 CRASH.vi (16.56K)

No crash on my system: LV2010, W7 64-bit, Pentium E5200
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

LabVIEW 2010 App Builder: Registry editor has issue with keys of the same name at the same level in registry tree

This is a bug report for an NI application engineer. Please file a CAR.
In a LabVIEW 2010 project, create a new installer build and go to the Registry editor.
Enter some keys like the following
Click OK to close the installer wizard.
Now reopen the build specification and go to the Registry editor. The registry editor comes up blank and non functional.
I believe the registry entries are still written when the installer executes, but you cannot edit the registry any further in LabVIEW 2010. This was not an issue in LV 2009. The issue seems to stem from having two keys with the same name at the same level in the registry tree (in this case, the two "Test" keys).

Hi sensor_daniel,
This was reported to R&D (#305026) for further investigation.
Thanks for the feedback!
Have a great day,
Chris V
Applications Engineer
National Instruments

Labview 2010 crashes XP while looking for webserver

Hi,
I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable. I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
I've gone into the Windows Event Viewer and there is an event that says "Labview information: Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL ."
I'm attaching a jpg of the Event in case I typed it incorrectly. There is another post that mentions this error but there is no resolution and the discussion went in a different direction: http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true
Neither my Win 7 development laptop or my target Win XP system have this www folder.
Has anyone seen this before or know the cause? Thanks.
Steve
Attachments:
Event Viewer small.jpg ‏69 KB

Altenbach,
Thanks for the quick reply.
Yes, the time stamp of this error coincides with the crash. I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer. Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
This only happened on time and I have not been able to reproduce it again.
I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again. Do you have any suggestions? Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.
Thanks.
Steve

Wdapi900.dll error on windows 7 while running labview 2010 executible

Hello All,
I am trying to run a "1.exe" on a windows 7 PC created from a Labview 2010 version.
It gives me a following error
"The Program cant start because WDAPI900.DLL is missing from your computer"
However the previous version of labview 2009 "2.exe" file works absolutely fine on the same Windows 7.
I tried running the Labview 2010 "1.exe" file on Windows Vista and it runs absolutely fine.
Any ideas?

I created another .exe file from LV 2010 and ran it on win7 PC.
It ran perfectly fine.
The difference between this file was, i was just using a serial port for communication.
On the other program i was using a winI2c interface along with options to choose from NI 8451 and serial interface.
The error messages i am getting are as attched.
Error 1 is the 1st message i get as soon as u open the program.
After pressing OK, i get a bunch of other error messages as shown in Error2.
I have already installed latest Win-I2CUSB on win 7 machine.
Attachments:
error.jpg ‏30 KB
error2.jpg ‏14 KB

Deleting broken wires crashes Labview 2010

Hi
I am down to earth after
enjoying all the nice features of LV 2010.
I randomly encounter
hour-glass hang-up when I try to delete broken wires. This is really
unpredictable as far as I have watched. I t happens if click on a broken with
the mouse or when I select a couple of those. It does not happen, if I use
ctrl-b.
When you try to delete it,
the hour glass comes up and the window is no longer refreshed.
I use the task-manger to
kill LV after
that a wild hard disk action starts, whoever initiates that ??
After LV-restart I usually
can recover a lot, but this make RAEL work almost impossible.
I a running an English LV
2010f2 on a German WinXP professional.
And Please, please patch
this as soon as possible.
Gabi
7.1 -- 2013
CLA

Hi Gabi,
I'm glad to hear that you are enjoying LabVIEW 2010! Can i ask what is the specifiation of the computer you are using it on?
This is because it might be that your computer doesn't have enough memory for this program.
Also there is a patch for LabVIEW 2010, in this link.
Hope this helps!
John McLaughlin
Insides Sales Engineer Team Leader
National Instruments UK & Ireland

Lvrt.dll crash LV2010SP1

Problem Event Name:   APPCRASH
Application Name:   Test.exe
Application Version:   1.0.0.0
Application Timestamp:   4d2fa0d5
Fault Module Name:   lvrt.dll
Fault Module Version:   10.0.1.4002
Fault Module Timestamp:   4d2fb3a1
Exception Code:   c0000005
Exception Offset:   007487b7
OS Version:   6.1.7600.2.0.0.256.48
Locale ID:   1033
This is LabVIEW 2010 SP1 on Windows 7.
Maybe it has something to do with "Call By Reference" , but not sure.

Strange, I would also appreciate any updates on a solution. I can run my application for several days as well and then the system gives me the error. I have not checked my DEP settings, but will do so. I was leaning towards a problem with resources since I am running for several days - I thought maybe the memory or cpu usage was a problem.
I am using Windows 7, LabVIEW2013, SP1 64 bit application.
Is there any reasonable way to recover from this crash programmatically since it is a Windows error?
Problem signature:
Problem Event Name:                        APPCRASH
Application Name:                             Avionic_Communication.exe
Application Version:                           5.0.0.2
Application Timestamp:                     52d9885e
Fault Module Name:                          lvrt.dll
Fault Module Version:                        13.0.1.4018
Fault Module Timestamp:                  52d99503
Exception Code:                                  c0000005
Exception Offset:                                0000000000bb7e80
OS Version:                                          6.1.7601.2.1.0.256.48
Locale ID:                                             1033
Additional Information 1:                  56fb
Additional Information 2:                  56fb6f9c2aae0ddbb77d8c94b1041558
Additional Information 3:                  848b
Additional Information 4:                  848b2abc34bf08ac556f274cd9d77734
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

LabVIEW 2010 unstable on Windows 7

I am finding that LabVIEW 2010 is fairly unstable on Windows 7 Ultimate system.
LV stopped working several times, LV tells me that it stopped working, looks for a solution and then shuts down. Like just a few minutes ago, shortly after system power up.
Several times it just closes all of the Windows and terminates without any message or error displayed. Didn't even say goodbye.
I have even had one BSOD (which is hard to do on Win 7) almost immediately after an application was built and run. Didn't happen again when app was run again and built again.
I have only observed these problems with LV. All other applications have been running fine over the last month without unusual errors or misbehaver.
The system is only 1 month old. It is fairly clean with minimal software installed.
I don't know how much data on these problems that NI is capturing automatically. I haven't seen my system request permission to send problem reports to NI.
Has anyone else seen similar behavior with LV and Win 7 Ultimate?

I too am extremely (that's a total understatement) displeased with the behavior of Labview 2010 under Windows 7.
I get frequent crashes, some with recovery/log/.error message, some where Labview just exits. One minute I'm editing my code with 7 windows up; the next I'm staring at an empty desktop.
I too have started saving my work every few seconds. It's a royal pain in the ass.
I have turned in NUMEROUS bug reports, including samples of code that cause Labview to crash. MANY of them are related to typedefs. I just found another one and will be turning in that bug report within minutes. In this case I have a typedef (NOT strict) that contains only a combo listbox. If I right-click on the combo listbox, Labview silently exits and does no recovery or logging when started back up.
I have lost SOOOOOO much time trying to create code while fighting numerous Labview 2010 issues. The most egregious (to me) is that I have a control (I *want* it to be a strict typdef) that when I drop it on the Labview block diagram, Labview crashes. Yes this has been reported. I had to change the control from 'strict typedef' to 'control' to use it. The result is that every time I have to modify it (it's a work in progress) I heve to go thru my code and change over 60 occurrences of that control. By hand. If it was a typedef, I would change it ONCE.
I have a customer I'm developing Labview code for; I find it both personally and professionally embarassing to be missing deadlines for delivery, and blaming Labview instead of myself. But I have 3 pages of bug reports online with NI; each one cost me between an hour and 3-4 days of time. Many of them required me to redesign code I'd alrady written to avoid using constructs in Labview that simply don't work.
I'm glad to know I'm not alone - but absolutely dismayed that the code base for Labview 2010 is so buggy under Windows 7; it may be buggy on every platform, but that's all I'm using.
NI tech support has been helpful; but only to a point. They routinely generate correction requests based on my bug reports; not one has resulted in a patch from engineering to date.
I've been a software engineer for over 35 years. This is probably the 2nd worst experience with an IDE that I've had. The first was with a Sun product that was supposed to generate user interfaces; it simply was crap. Labview is dismayingly similar. If I'd elected to write this application in C I'd not only be finished, but it would have taken 6 months less on the calendar. Some of that is due simply to the way you have to construct and enter code in Labview; but in my case, most is due to failures of Labview to work as documentd, or to failures in the Labview documentation to explain what Labview is really doing (yes, I've turned those in too).
Here's an example of a Labview crash: open this VI and right-click on the listbox on the front panel. Make sure you do NOT have any other Labview code open at the time...!
Gary Sloane
SB/US Engineering Inc.
Attachments:
HL2_CAL_DISPLAY.ctl ‏5 KB

Labview 2010 dll crash issue

Similar Messages

Maybe you are looking for