Exception: Access violation (0xC0000005) at EIP=0x010111F5 when opening VI

[jOBrien]

Hello. 

I am currently updating a bunch of VIs from LabVIEW 7.1 to LabVIEW 2013. Whenever I try to open one of the VIs it gives me an Exception: Access violation (0xC0000005) at EIP=0x010111F5 error. 

The report for this error is pasted below:

####
#Date: Thu, Oct 17, 2013 11:07:52 AM
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 13.0f1 32-bit
#AppKind: FDS
#AppModDate: 09/06/2013 16:56 GMT
#LabVIEW Base Address: 0x00400000

starting LabVIEW Execution System x00000002 Thread 0 , capacity: 24 at [3464867274.30055670, (11:07:54.300556660 2013:10:17)]
starting LabVIEW Execution System x00000002 Thread 1 , capacity: 24 at [3464867274.30055670, (11:07:54.300556660 2013:10:17)]
starting LabVIEW Execution System x00000002 Thread 2 , capacity: 24 at [3464867274.30055670, (11:07:54.300556660 2013:10:17)]
starting LabVIEW Execution System x00000002 Thread 3 , capacity: 24 at [3464867274.30055670, (11:07:54.300556660 2013:10:17)]

<DEBUG_OUTPUT>
10/17/2013 11:08:00.291 AM
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 83712b62-7819-4d24-94f5-765ce4128351
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x01BA653B - LabVIEW <unknown> + 0
0x01BA6A9C - LabVIEW <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77CF74FF - ntdll <unknown> + 0
0x77CB9F45 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
#** Loading: "F:\Work_stuff\Motion Station\In Development\big screen panel.vi"
*** End Dump ***

Any help in this matter is greatly appreciated.

Thank you. 

[JÞB]

7.1 to 2013 is a large jump!

Worse, 7.1 doesn't support modern OS's  So, What OS are you using?

Have you tried to wash it through a few intermediate versions?

Can you isolate it to a specific section of code that fails?

[jOBrien]

We were using Windows XP with LabVIEW 7.1 but are upgrading to Windows 7 wich is why we are going from 7.1 to 2013. We do not have licenes for any intermediate versions and I was told by an NI representitive in my area that going from 7.1 to 2013 was a fairly straight forward conversion which documentation on the NI website supports. 

I cannot isolate it as I cannot even open the VI with LabVIEW 2013, as soon as I try to open it the error pops up.  

[JÞB]

If you have a licensed version of LabVIEW 2013 installed you can co-install any previous version.  I'm going out on a limb here but I'd bet dollars to doughnuts that the code wasn't originally written in 7.1 and has several depreciated funtions in it where the mutation code fails.  I'd send the example source to an AE with a SSR Ticket

[jOBrien]

After looking into the problem more, I found that the VI in question uses references to its controls. I was also able to install and open the VI on LabVIEW 7.1 on Windows 7 as an intermediate step, however I still cannot open it in LabVIEW 2013. 

Do you have more information on co-installing older versions? I have not been able to find any information on this online, and it looks like that is the way I will have to go. 

Thank you. 

[Jason-H]

LabVIEW 7.1 isn't compatible with Windows 7, you'll have to convert it to at least LabVIEW 2009 SP1, http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB.

[jOBrien]

I understand that it is incompatible, I just tried it to make sure the copy I had was not corrupted (I wasn't going to spend much time on it but the install worked enough that I was able to open the VI that I have been having problems with). 

[jOBrien]

One thing that I just found out is that any of the VIs that I have been trying to bring to LabVIEW2013, all of them that have this error are dealing with arrays. Does LabVIEW 2013 handle arrays differently then how the older version of LabVIEW does? 

Again, thanks for any help anyone can provide. 

[JÞB]

---

@jOBrien wrote:

One thing that I just found out is that any of the VIs that I have been trying to bring to LabVIEW2013, all of them that have this error are dealing with arrays. Does LabVIEW 2013 handle arrays differently then how the older version of LabVIEW does? 

Again, thanks for any help anyone can provide. 

---

Not really,

Can you post a vi that exhibits the behavior?  I'd like to take a peek at it

[jOBrien]

Hello, 

Here is one of the VI's I am having problems with. 

Thank you again.