LV2013 crashes when opening VI developed in LV2009

[MinerHokieRamp]

---

@Tortu wrote:

Greetings Jeff.

After reviewing the previous posts again, I noticed that nobody has asked this before: Has this project worked before?

The project was developed on another PC (Win 7) with LV2009. The project was published to LVRTE and works on the PC I'm using now (in other words, the LVRTE version of the code doesn't crash). The PC I'm using now doesn't have an installation of LV2009; an evaluation copy of LV2013 is installed.

Has your OS install any kind of upgrade that might be responsible of this error?

No updates to the OS. I don't know how we'll get OS updates for this PC; it's not connected to the web.

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? 

I drilled down and found the lowest level offending VI; i.e., this VI has no subVIs and makes no .dll calls. I sent screenshot images of this VI and the NIER logfiles to our area NI engineer who said he'd start a ticket on my behalf. I've included the images in this post.

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

Thanks,

---

[MinerHokieRamp]

Here's an email from NI support and my answer to the email:

Okay, here’s what happened.

1. 1.    Opened BlockStatusWordDecode.vi in LV2013, did File/Save, then closed it.
2. 2.    Opened the VI that calls BlockStatusWordDecode.vi (filename GetRTDataStore.vi)
3. 3.    Right-clicked the BlockStatusWordDecode.vi icon, then ‘replaced’ with the BlockStatusWordDecode.vi file I had just saved.
4. 4.    Saved GetRtDataStore.vi.
5. 5.    Closed GetRTDataStore.vi; saved changes when prompted.
6. 6.    Tried opening the top-level VI (filename ADIT_Menu01.vi); LV2013 crashed.

Is this what you wanted me to try? Was I prompted to save changes on exit (step 5) because something recompiled due to the subVI replacement?

Thanks,

Jeff

From:support@ni.com [mailto:support@ni.com]
Sent: Thursday, October 17, 2013 12:03 PM
To: Bledsoe, Jeff P
Subject: EXTERNAL: Re: (Reference#2074893) Phone Support E-Mail

Note: Your reference number is included in the subject field of this message. It is very important not to remove or modify this reference number, or your message may be returned to you.

Hi Jeff,

This is Mike in Applications Engineering at National Instruments. I'm emailing you about your LabVIEW crash issue.

Based on what I've read in the forum posts regarding your issue, I understand the following points to be correct:
A. You're able to open the 2009 project in LabVIEW 2013 with the VI "BlockStatusWordDecode" removed from the project.
B. You're able to open "BlockStatusWordDecode.vi" in LabVIEW 2013 as a stand-alone VI and run it successfully without crashing.

If the above statements are true, as a  work around, I suggest trying the following:
1. Please open "BlockStatusWordDecode.vi" in LabVIEW 2013 and save it.
2. Then, open the LabVIEW 2009 project in LabVIEW 2013 and add "BlockStatusWordDecode.vi" to the project.
3. Please try running the top-level VI at this point and observe if it executes successfully.

Please let me know if you have any other questions in regard to this issue.

Thank you,

Mike Pool
Applications Engineering
National Instruments
www.ni.com/support

[MinerHokieRamp]

In answer to NI support email (below):

Mike Pools said: "When you tried to open the top-level VI in step 6 [step 6 of my prior post] , had you previously opened the top-level in 2013 without the problem sub VI included?"

Answer: Yes, but I don't believe I saved the top-level VI without the problem subVI.

Here's what I just tried today:

1. Dragged BlockStatusWordDecode.vi out of the project folder onto the desktop.
2. Opened BlockStatusWordDecode.vi and saved it, then closed it; left it on the desktop.
3. Opened the top-level VI (while residing within the project folder) and saved it; then closed it, selecting "Save All" when prompted at closing.
4. Dragged BlockStatusWordDecode.vi from the desktop back to its prior subfolder within the project folder.
5. Opened top-level VI, LV crashed, same BEX error as before.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hi Jeff,

When you tried to open the top-level VI in step 6, had you previously opened the top-level in 2013 without the problem sub VI included?

The goal is to successfully open and save the top-level VI, and, therefore, all sub VIs besides BlockStatusWordDecode.vi, in 2013.
Then, open and save BlockStatusWordDecode.vi in 2013 and save it separately.
And, finally, include the 2013 BlockStatusWordDecode.vi in the 2013 project.

Upconverting the project and BlockStatusWordDecode.vi separately may avoid a crash.


Regards

Mike Pool
Applications Engineer
National Instruments
http://www.ni.com/support

[sekar15]

I am facing some error when I click Detailed help. Hence, my LabVIEW gets closed instantly. The following error is building

Problem signature:
Problem Event Name: APPCRASH
Application Name: LabVIEW.exe
Application Version: 13.0.0.4047
Application Timestamp: 51d23238
Fault Module Name: LabVIEW.exe
Fault Module Version: 13.0.0.4047
Fault Module Timestamp: 51d23238
Exception Code: c0000005
Exception Offset: 00a00005
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: cf25
Additional Information 2: cf2564169f90eb103215e8e62e4f5e03
Additional Information 3: d63f
Additional Information 4: d63fc2f2c190907402e1cc38abc24221

[billko]

And how does your problem relate to this one?  If it doesn't please start another thread.  You can do so by going to the LabVIEW forum page and click on the "New Message" button near the top right of the page.  For some reason or other, a lot of people (including myself, when I first found the forum) miss that button.

[MinerHokieRamp]

---

@JeffreyP wrote:

In answer to NI support email (below):

Mike Pools said: "When you tried to open the top-level VI in step 6 [step 6 of my prior post] , had you previously opened the top-level in 2013 without the problem sub VI included?"

Answer: Yes, but I don't believe I saved the top-level VI without the problem subVI.

Here's what I just tried today:

1. Dragged BlockStatusWordDecode.vi out of the project folder onto the desktop.
2. Opened BlockStatusWordDecode.vi and saved it, then closed it; left it on the desktop.
3. Opened the top-level VI (while residing within the project folder) and saved it; then closed it, selecting "Save All" when prompted at closing.
4. Dragged BlockStatusWordDecode.vi from the desktop back to its prior subfolder within the project folder.
5. Opened top-level VI, LV crashed, same BEX error as before.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hi Jeff,

When you tried to open the top-level VI in step 6, had you previously opened the top-level in 2013 without the problem sub VI included?

The goal is to successfully open and save the top-level VI, and, therefore, all sub VIs besides BlockStatusWordDecode.vi, in 2013.
Then, open and save BlockStatusWordDecode.vi in 2013 and save it separately.
And, finally, include the 2013 BlockStatusWordDecode.vi in the 2013 project.

Upconverting the project and BlockStatusWordDecode.vi separately may avoid a crash.


Regards

Mike Pool
Applications Engineer
National Instruments
http://www.ni.com/support

---

The resolution of these crashes can be found in the following thread. Thanks for the help.

http://forums.ni.com/t5/LabVIEW/Need-help-with-an-error-report/m-p/2800948/highlight/true#M821547

Jeff