Labview crashes with Excel ActiveX

Dear all,
I have written a program to read and write the data in the
excel using ActiveX sheet but crashes the Labview drastically when
executed.
Please go through the attached files.
Actually the program has to sort the data in ascending order in a
column in a
Specified worksheet and it should write the sorted data in another
worksheet in the same excel file itself. But while writing it should
neglect the repeating data and should write the corresponding data in
the other column with respect to sorted one.
For example , In datafile.xls in sheet1 cells are like below. Let a,
b & g are columns
a1=0.02, b1=2.1 , g1=0.1
a2=0.04, b2=4.2 , g2=0.3
a3=0.05, b3=4.2 , g3=0.35
a4=0.06, b4=4.3 , g4=0.43
a5=0.0
7, b5=7.1 , g5=0.43
a6=0.08, b6=7.2 , g6=0.43
a7=0.09, b7=7.2 , g7=0.75
a8=0.11, b8=7.4 , g8=0.75

I am not sure what is causing the crash. Can you give us more information? For example what does the crash say, when you relaunch LabVIEW does it comment on an error log file?
The code you mentioned was not attached, so I was not able to try and reproduce it. I would be happy to try it here, if you can attach it.

Similar Messages

LabVIEW crashes with ntdll.dll!7C911e58 as the error in debugger.

I am running a streaming video application (VLC) in LabVIEW as an activeX control. There are 6 separate containers with different streams in each.
Labview Crashes citing ntdll.dll!7C911e58 as the error in debugger when I try to run the VI.
As well, every 4th attempt to run the VI results in the BSOD.
Does anyone know what I can do to try and fix this serious error?
Regards,
Sean

Which version of LabVIEW do you have? There wasn't a LabVIEW 7.2. Did you mean 7.1.1?
Did you get an error log generated? That would be useful in diagnosing the problem. This KB reviews its location:
http://digital.ni.com/public.nsf/allkb/54E361E3FF477EC186256C320068184F?OpenDocument
Trey B
Applications Engineering
National Instruments

Labview crashes with access violation(0xc00000050at EIP=0x7c8219a6

when i poen my project in labview ,it crashes with "access violation(0xc00000050at EIP=0x7c8219a6.why is this happening?how can i open my project?

Probably nothing to do with it but I had some dodgy memory, and windows would complain that there was an error to do with that exact memory location: c0000005

Link labview data with excel sheets

I would like to save the output of a cluster(containing strings and numeric data) in a specific format(each data in respective columns)
in an excel sheet.
how do I do it in labview??
I tried mathscript, is there any other way? If there isnt can u suggest how can I use it to solve the above mentioned issue.
similarly, can I recieve data in real time from excel sheets??
pls suggest.
Solved!
Go to Solution.

I think you should use the ActiveX to fullfill your requirements.
You can refer to this example
<LabVIEW Folder>\examples\comm\ExcelExamples.llb\Excel Macro Example.vi
Use activeX to write and read data.
Best Regards
Hu Yu

Big issues with the new MAC OSx RDP client; crashes with Excel formattings or open Libre Office

We found out, that the new version of the MAC OSx RDP client (Version 8.0.24255) has some big problems: example: formatting an Excel column: text
blue: the RDP crashes (re-producible); opening libre office calc (with 3 RDP-sessions open): RDP crashes and is not able to be opened, until libre office is closed in another windows-rdp-session.

Crashreporter:
Process:         Microsoft Remote Desktop [56434]
Path:            /Applications/Microsoft Remote Desktop.app/Contents/MacOS/Microsoft Remote Desktop
Identifier:      com.microsoft.rdc.mac
Version:         8.0.24308 (8.0.24308)
App Item ID:     715768417
App External ID: 224042646
Code Type:       X86-64 (Native)
Parent Process: launchd [331]
Date/Time:       2014-04-10 16:21:58.896 +1000
OS Version:      Mac OS X Server 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report:          11 sec
Crashes Since Last Report:           1
Per-App Interval Since Last Report: 7 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      1FCED11E-54A0-400D-8433-DE8DDFD05728
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffffffffffc
Crashed Thread: 8
Thread 8 Crashed:
0   com.microsoft.rdc.mac            0x0000000172f937dd void HLW::bltImpl::bltWordImplDR<unsigned int>(unsigned char, unsigned char const*, int, HLW::Point const&, unsigned char*, int,
HLW::Rectangle const&, unsigned char const*, int, unsigned int, unsigned int, int, int, unsigned int) + 6365
1   com.microsoft.rdc.mac            0x0000000172f99827 void HLW::bltImpl::bltWordImpl<unsigned int>(unsigned char, unsigned char const*, int, HLW::Point const&, unsigned char*, int,
HLW::Rectangle const&, unsigned char const*, int, unsigned int, unsigned int, int, int, unsigned int) + 167
2   com.microsoft.rdc.mac            0x0000000172f7a305 HLW::Blt::blt(unsigned char, unsigned char const*, int, HLW::Point const&, unsigned char*, int, HLW::Rectangle const&, unsigned
char const*, unsigned int, unsigned int, unsigned int, int, int, unsigned int) + 2101
3   com.microsoft.rdc.mac            0x0000000172f9c021 HLW::SoftwareRenderer::drawBlit(unsigned char, HLW::IBuffer*, HLW::Point const&, HLW::Rectangle const&, HLW::IBuffer*, HLW::Point
const&) + 1345
4   com.microsoft.rdc.mac            0x0000000172fc8cee HLW::Rdp::RenderManager::PatBltOrderImpl::threadedHandle() + 2060
5   com.microsoft.rdc.mac            0x0000000172fc8f0d non-virtual thunk to HLW::Rdp::RenderManager::PatBltOrderImpl::threadedHandle() + 29
6   com.microsoft.rdc.mac            0x0000000172fcd504 HLW::Rdp::RenderManager::OrderHandlingThread::run() + 114
7   com.microsoft.rdc.mac            0x0000000172be6ead Gryps::Thread::threadFunc(void*) + 103
8   libSystem.B.dylib                0x00007fff876edfd6 _pthread_start + 331
9   libSystem.B.dylib                0x00007fff876ede89 thread_start + 13

External clock LabView crash with Measurment Computing board.

Hi,
I'm using a Measurment Computing PCI-DAS6402-16 board with Labview (using Universal librarys VIs) in a 4-stroke engine DAQ application and amognst the signals obtain Internaly clocked, there is In-Cylinders Pressure signal which is timed with a Crank-angle deocoder sending analog pulse signal.
Although there seems to be no problem while the motor is running, it appears that when to external clocked signal is not getting any pulses (while the motor is not running) then Labview stops to respond and awaits for the external clock to start, and that doesnt happen within 10s then it crashes.
I dont know whether it is Software problem (because external and internal clocked signals are both in the same WHILE LOOP) or if it is a Hardware problem (because With a NI card there seem to be no problems).
THNX in Advance

Well it couldnt be a more typcal windows crash:
If a channel is externally timed with an analog pusle signal, If the VI starts running but the external clock isn't then:
-Labview stops to respond to any clicks (there is no .exe at this point) but it keeps working though (That i know cause if i start the ext. clock at this point it "un-stucks' and starts working)
-But, if for some secs no ext. pulse signal is generated then labnview app stops respondin and i get the typical 'send error report' window.
Could it be that the Universal library for Measurment Computing boards haw a bug? Cause the same thing happens with the "Analog input External Clock.vi" example given with the Library..so it can't be my mistake..or can it?!

Labview crashes with database searches

I have been searching a DB file for various amounts of data, but as the amount of data increases, I find myself dealing with crashes. At times the data array size doesn't seem to matter, because LV crashes regardless of the array size. I have tried using various methods to deal with this issue, such as changing the date range(getting various array sizes), setting various cache sizes, choosing various cursor types, and even using the disable diagram structure to pinpoint where my crashes are occuring. The files attached are part of a project with over 30 VI's and I have spent a considerable amount of time to determine the attached code is the specific location where crashes occur. I do not know if there are limitations to the DB operation VI's, but any assistance from others about its limitations, if they exist, would be appreciated. Please look at the attached code and use the attached DB to perform the SQL queries included or perform your own if desired. I hope there is an explanation for LV crashing.
Thanks,
Fernando

the DB had to be reduced in size due to upload file size limitations, but if the data is copied and made to mimic a dataset larger than 3 weeks, the crash occurs.
Attachments:
SQL VARIANT DATA TO CLUSTER.vi ‏41 KB
String to TimeStamp.vi ‏15 KB
Reactor Database.zip ‏51 KB

Labview VI with Excel toolkit report

In SignalExpress, I have to analyze data and save this analysis in Excel Workbook, to do this, i reuse VI for the analysis, and use Report Generation 1.1.1 toolkit for Office. But an error appear : Error (97): Unknown System Error in Excel_Get_Properties.vi->Excel Workbook Properties.vi->BDT FIL Create or not worksheet.vi->Data to Excel.vi->BDT ANL Process and Save.vi->Data Processing Main.vi->Data Processing Main.vi.ProxyCaller
So, What is it ?
John Doe

Hi Julien,
What version of signal exepress are you using ? and what version of OFFIce is installed on your computer ?
Regards,
ClémentG

Labview crashes with intensity chart

Twice this morning, LV2010 has hung ("program is not repsonding") when I have tried to reposition an intesity chart on my front panel. In one case I copied the chart from a NI example program into my VI. When I tried to reposition the chart on my front panael, LV stopped responding. Same thing happened when I tried again; the second time, I got the intensity chart from the charts and graphs palette. I have LV 2010, version 10.0f2, and windows XP. Thanks.
Solved!
Go to Solution.

Hi there!
The following KnowledgeBase explains why this might be happening.
http://digital.ni.com/public.nsf/allkb/9A8FB888BFCED9658625721500434A31
Basically, that chart might be holding a lot of data, and when you move it, LabVIEW has to rearrange all that information in RAM as you move the chart. You can either write smaller data, or save all that data in an array separate from the chart at the end of execution so you can save it. If you want to view it in a chart later, just input it back into a chart.
Ravi A.
National Instruments | Applications Engineer

Error -2147221080 (0x800401A8) with Excel ActiveX on sheet access

Hi all !
I get this error while accessing an excel sheet.
Could it be linked to file permissions or something?
Thanks!
Attachments:
error -2147221080.JPG ‏91 KB
sondes.JPG ‏17 KB

Well... it kind of resolved itself.
I just added a 'Worksheet' property node before the 'Range' method and it then worked. I then removed the property node and it was still working!
I don't understand exactly what happened here...
Anyone got an idea?

Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
Can you tell me why this occurs and what the solution is?

Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

Labview crash when saving

Hi Forum
When trying to save the attached file in 8.6 (the file is created in 7.1) LabVIEW crashes with a Windows error telling me that the system has encountered a problem and needs to close.
All the SubVIs save without problems and I don't see what should cause this specific VI to cause trouble.
I have searched the forum and tried the different tricks mentioned in other threads about this issue, but none of them seems to help on my VI.
I hope that somebody has a good suggestion as to what I can do.
B.R.
Martin
Solved!
Go to Solution.
Attachments:
Crash when save.vi ‏87 KB

The problem appears to be with the typedefs. Specifically, it looks like it's the text ring. Disconnecting the typedefs in 7.1 and resaving it allows it to be opened in newer version. Attached is in 8.2
Attachments:
Crash when save 8.2.vi ‏27 KB

LabVIEW crashed while loading Sensor Mapping Express VI

Dear all,
I've just installed LV8.6 evaluation with all the toolkits available in the DVD. I have two problems now, one major and one minor:
1. Whenever I tried to use the Sensor Mapping Express VI, LabVIEW crashed with the pop-up window saying that "LabVIEW 8.6 Development System has stopped working". When I expanded Window's error pop-up, the message as can be found below. The same error occurs whenever I tried to load the sensor mapping demo I downloaded from the Developer Zone. I'm using Dell Inspiron 640m, by the way. When I tried with another Dell laptop (Dell Vostro), everything was alright.What I've done so far is to uninstall all NI's softwares inside this laptop, defrag, clean the registry and then reinstall LV 8.6 again but to no avail.
Error message:
Problem signature:
Problem Event Name:    APPCRASH
Application Name:    LabVIEW.exe
Application Version:    8.6.0.4001
Application Timestamp:    4862fd60
Fault Module Name:    ig4dev32.dll
Fault Module Version:    7.14.10.1147
Fault Module Timestamp:    457ef11c
Exception Code:    c0000005
Exception Offset:    000063b2
OS Version:    6.0.6001.2.1.0.768.2
Locale ID:    17417
Additional Information 1:    da97
Additional Information 2:    7a880e72b9f1636f81b04947e06e5c6a
Additional Information 3:    09b4
Additional Information 4:    56e138085db0c350e7bf46ba31a7691f
My computer specs are:
OS: Windows Vista Home Basic
RAM: 1.5 Gb
Harddisk: 10Gb free (after LV is installed)
Processor speed: 1.6 GHz Dual Core
Anti Virus: Kaspersky Internet Security
2. This is minor but still an annoyance. Whenever I tried to load my newly installed LabVIEW 8.6, it takes about 10-15 minutes before I got the Getting Started window. This includes the 5 minutes waiting period before I got the window stating how many days left for evaluation. This wasn't the case when I used LabVIEW 8.5.1 (even when every toolkits and modules are installed). Why so long?
I've asked the local NI engineers but they are also clueless.

Hi Lan,
Thanks for your post and I hope your well today.
1) You specs seem okay.
Minimum
Recommended
Processor
Pentium III/Celeron 866 MHz or equivalent
Pentium 4/M or equivalent
RAM
256 MB
1 GB
Screen Resolution
1024 x 768 pixels
1024 x 768 pixels
Operating System
Windows Vista/XP/2000
Windows Vista/XP
Disk Space
1.6 GB
1.6 GB (Note -- Includes default drivers from NI Device Drivers CD)
There has been some record of issues with the Sensor Mapping Express VI.
Does it crash when you place it down on the block diagram? Or when you click to move it? Or when you run it? Does this happen when you load a model into it?
However, as it seems to be an instance of your Dell Inspiron 640m, Im not sure what we can suggest - except to ask how the specs compare between the two machines?
Some advice for Dells,
#) So that LabVIEW can function properly with the video hardware, it is
occasionally necessary to reduce the video acceleration. You can do
this on Windows 2000 by right clicking on your desktop » Properties » Settings » Advanced » Troubleshooting.
Start with the second setting from the right, "Disable bitmap and
cursor acceleration.", and work your way left if the problem persists.
#) Number of other issues with versions of Dell video drivers.. upgrade?
2) If this is a new installation that is slow then you may be having issues with specs, however there are a few things to try:
a) Defrag Drive
b) VLM licensing? If so, there is a timeout of a view minutes... is your version licensed currently?
c) Clean your registry
d) Check LabVIEW ini file to make sure the tasks are all necessary and the paths are local.
e) Repair LabVIEW finally
Hope this helps make some progress,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Report Generation Toolkit, Print Excel Report, LabVIEW Crash

Hello,
when printing a report generated with the report generation toolkit for excel my build application crashes on our customers PC.
When I run this application on my PC it works fine.
The problem is the active X invoke node that trys to print the report but i cant get any error messages to find out where to locate the problem.
Maybe that there is a problem with the active X node or the Excel Version on the customers PC?
I use LabVIEW 2010 and Excel 2007 the customer has Excel 2003 SP 3.
I changed the report to generate it in Word where the Print_Report.vi fine on both PCs. But in Word Report there is called another active X invoke node to print the Report. So it seems for me that there really is a problem with the Print in Excel active X invoke node.
Mybe someon can help me in finding out whats the problem.
Greetings Daniel.
Solved!
Go to Solution.

Hi Daniel,
your behavior has been reported by others. For example:
Application Build Failure on Excel.Print Report call
http://forums.ni.com/t5/LabVIEW/Application-Build-Failure-on-Excel-Print-Report-call/m-p/1563242
Problem posted: 05-17-2011 02:19 PM
Workaround posted: 06-01-2011 and later
So their workaround was to use Excel 2007 or 2010 instead of 2003. Is this working for your customer?
Best Regards,
Jan

LabVIEW - Excel - ActiveX

We have an application that may need to work with Excel. However, we may have to develop on a Sun machine. If this is the case, I assume I won't have ActiveX available to me. Can I use LabVIEW and Excel. If so, how do I go about it without using ActiveX?

I think your only option will be to save the Excel files as comma or tab separated text files. Then you can use Read From/Write to Spreadsheet File. Imho, even if you were to develop under windows, this would still be a better option if all that you have to do is populate a spreadsheet with data.

Labview crashes with Excel ActiveX

Similar Messages

Maybe you are looking for