LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV2013 crashes when opening VI developed in LV2009

Greetings Jeff.

 

I see in the Microsoft forum that you went through some troubleshooting steps. These steps makes the "BEX error" dialog disappear. What does this mean? What other error does it throw? (If any)

What were the results of creating a fresh LabVIEW project and adding all the VIs? If you are concerned about your original code, make a backup of all the VIs beforehand.

 

Do you have access to another computer with LabVIEW? What happens if you try to convert the version of the code in this other computer?

 

Please let us know what are the results.

 

Have a good day.

Luis J.
Applications Engineer
National Instruments
0 Kudos
Message 11 of 26
(814 Views)

@Tortu wrote:

Greetings Jeff.

 

I see in the Microsoft forum that you went through some troubleshooting steps. These steps makes the "BEX error" dialog disappear. What does this mean? After removing all 'services' and 'startup' items, LV2013 crashed without the appearance of the dialog box that announces the BEX error. So, nothing changed as far as the LabVIEW crash: it crashed before and it crashed after removing services and startup items.

 

 

What other error does it throw? (If any)  No error dialog box; therefore, no errors thrown that I know of.

What were the results of creating a fresh LabVIEW project and adding all the VIs? I haven't done that. You're suggesting I throw all ~100 subVIs into a project (without connecting them)? If that new project didn't crash LV2013, what would I do next?

 

 

If you are concerned about your original code, make a backup of all the VIs beforehand. The code was copied from an image on another computer.

 

 

Do you have access to another computer with LabVIEW? I don't have access to another computer with LV.  

 

What happens if you try to convert the version of the code in this other computer?  A colleague tried using LV2010 a couple of months ago and had a problem with this code; however, not sure if it was the same issue I'm having. I'll check with him again.

 

Please let us know what are the results.

 

Have a good day.

 

Thanks,

 

 


 

Jeffrey Bledsoe
Electrical Engineer
0 Kudos
Message 12 of 26
(801 Views)

Luis,

 

Can NIER log errors for a PC that is not connected to the web? If not, are there other ways to log errors?

 

Thanks,

Jeffrey Bledsoe
Electrical Engineer
0 Kudos
Message 13 of 26
(782 Views)

Hi Jeffrey,

 

NIER is a process that catches LabVIEW errors and crashes. It does not require network access to catch errors and generate dump files. It only requires network access to submit those crash reports to NI R&D, however it will still catch errors and generate dumps. There is more info here - NI Error Reporting FAQ

 

Regards,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

0 Kudos
Message 14 of 26
(773 Views)

Finally made a little progress.

 

While the main VI was opening subVIs, I clicked "STOP" to look at the list of VIs that hadn't been opened. Wrote down the list, closed LV, removed each VI from the list, one at a time, and attempted to open the main VI.

 

Using this method, I found the subVI that, when removed from the subVI folder, allowed the main VI to open.

 

Now I have to figure out what's wrong with the code in the offending VI.

Jeffrey Bledsoe
Electrical Engineer
0 Kudos
Message 15 of 26
(752 Views)

That is good news. If you open the subVI by itself directly from disk does it crash LabVIEW 2013? Did you try turning on NIER to see what it catches about the crash?

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

0 Kudos
Message 16 of 26
(745 Views)

Opening the offending subVI by itself doesn't crash LV.

 

Haven't figured out how to activate NIER. Maybe it runs automatically. Either way, don't know where to find the NIER log files.

Jeffrey Bledsoe
Electrical Engineer
0 Kudos
Message 17 of 26
(742 Views)

Greetings Jeffrey.

 

I'm glad you had a breakthrough on this issue.

 

I found a document here that explains how to find the Error Log Files that the NIER generates.

http://digital.ni.com/public.nsf/allkb/7E9EBE4CA3B6DCE786257633005E7121?OpenDocument

 

What kind of things are inside the offending VI? Does it make dll calls, interact with any LabVIEW toolkit or driver?

 

Please let us know. Have a good day.

Luis J.
Applications Engineer
National Instruments
0 Kudos
Message 18 of 26
(730 Views)

The offending VI's subVIs make DLL calls.

 

Got three (3) logfiles now; the logfiles were created when LV crashed.

 

Here's the contents of the text file:

 

####
#Date: Tue, Oct 15, 2013 1:18:17 PM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 13.0 32-bit
#AppKind: FDS
#AppModDate: 07/02/2013 01:54 GMT
#LabVIEW Base Address: 0x00400000


starting LabVIEW Execution System x00000002 Thread 0 , capacity: 24 at [3464705900.58200220, (13:18:20.582002163 2013:10:15)]
starting LabVIEW Execution System x00000002 Thread 1 , capacity: 24 at [3464705900.58200220, (13:18:20.582002163 2013:10:15)]
starting LabVIEW Execution System x00000002 Thread 2 , capacity: 24 at [3464705900.58200220, (13:18:20.582002163 2013:10:15)]
starting LabVIEW Execution System x00000002 Thread 3 , capacity: 24 at [3464705900.58200220, (13:18:20.582002163 2013:10:15)]

 

 

Who could analyze these logfiles?

 

Thanks,

 

Jeffrey Bledsoe
Electrical Engineer
0 Kudos
Message 19 of 26
(720 Views)

Greetings Jeff.

 

After reviewing the previous posts again, I noticed that nobody has asked this before: Has this project worked before? Has your OS install any kind of upgrade that might be responsible of this error?

 

Other than that, what kind of things does the offending subVI does. You mentioned it does .dll calls. Which ones? Does it do them with the Call Library Function Nodes? You mention this subVI have several subVIs, is it possible to further specify an offending subVI within this offending subVI? 

 

Please let us know of any breakthroughs you have with this problem.

 

Luis J.
Applications Engineer
National Instruments
0 Kudos
Message 20 of 26
(700 Views)