12-15-2014 11:08 AM
Hello,
I have a problem with .net application that uses LabView shared dll (c mode). The thing is applicatin as exe works only on my PC where I have my VS2013 and LV 2013 (32.0-bits) installed - on the other PCs after running exe following error occurs: (computers have labView 2013 or LV runtime 2013 )
####
#Date: 15 Dec 2014 11:57:18
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: BLABLABLA
#Version: 13.0 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
starting LabVIEW Execution System x00000002 Thread 0 , capacity: 24 at [3501489438.75507830, (11:57:18.755078316 2014:12:15)]
starting LabVIEW Execution System x00000002 Thread 1 , capacity: 24 at [3501489438.75507830, (11:57:18.755078316 2014:12:15)]
starting LabVIEW Execution System x00000002 Thread 2 , capacity: 24 at [3501489438.75507830, (11:57:18.755078316 2014:12:15)]
starting LabVIEW Execution System x00000002 Thread 3 , capacity: 24 at [3501489438.75507830, (11:57:18.755078316 2014:12:15)]
<DEBUG_OUTPUT>
15/12/2014 11:57:19.112
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 6310d4c9-a5e1-463b-8ff6-1c2c218e45f0
ExceptionCode: 0xE0434352
</DEBUG_OUTPUT>
0x307614F6 - lvrt <unknown> + 0
0x3076187C - lvrt <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77D774FF - ntdll <unknown> + 0
0x77D39F45 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
I don't get it because Frameworks are the same and well, all the files in the same folder, the same windows and others.
Does anyone know maybe what am I missing?
kind regards,
Kasia
12-16-2014 08:20 AM
12-16-2014 08:23 AM
Hello Daniel,
my Visual Studio 2013 is configured for x86 debug targetting Framework 4.0. It is working on my PC but...not on any other.
While creating even interopAssembly I include library that my labView project uses (Include if referenced) but still it doesn't work anywhere else...
Kasia
12-18-2014 08:29 AM
Hi Kasia,
Can you please post a screenshot of the error so we can take a look?
Regards,
Gavin
12-18-2014 08:44 AM
Hi Gavin,
sure here it goes.
PS
#Date: 18 Dec 2014 14:37:35
#OSName: Windows 7 Professional Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: ShowComputerID
#Version: 13.0 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
starting LabVIEW Execution System x00000002 Thread 0 , capacity: 24 at [3501758255.25306420, (14:37:35.253064156 2014:12:18)]
starting LabVIEW Execution System x00000002 Thread 1 , capacity: 24 at [3501758255.25306420, (14:37:35.253064156 2014:12:18)]
starting LabVIEW Execution System x00000002 Thread 2 , capacity: 24 at [3501758255.25306420, (14:37:35.253064156 2014:12:18)]
starting LabVIEW Execution System x00000002 Thread 3 , capacity: 24 at [3501758255.25306420, (14:37:35.253064156 2014:12:18)]
<DEBUG_OUTPUT>
18/12/2014 14:37:36.492
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: 385cb53c-e479-4778-a424-f51432089cd1
ExceptionCode: 0xE0434352
</DEBUG_OUTPUT>
0x307614F6 - lvrt <unknown> + 0
0x3076187C - lvrt <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77EE74FF - ntdll <unknown> + 0
0x77EA9F45 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
12-19-2014 06:37 AM
Hi Kasia,
Thanks for the screenshot. I was hoping it might have a little more information on it but let's look at some other options. I think going back to Daniels approach may help. Deos the target machine have the appropriate version of the .NET framework installed as your development machine?
Regards,
Gavin
12-19-2014 06:41 AM
Hi Gavin,
yes unfortunately the .net Framework is exactly the same on both PCs. I was wondering about labView dependencies from the project but after creating a testing project similar to original there are no problems with compatybility. I just don't want to have random unexplainatory issues with my cross platform applications...
thank youu though for your interest!
Kasia
12-19-2014 08:45 AM
Hi Kasia,
I am glad you have found a work around but No Fault Found (NFF) style behavior is far from ideal. I will not be able to reply for a few weeks but if this ocurs again in a similar system please post again and we can look to analyse in a more in depth manner.
Happy Holidays,
Gavin