LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application chrash always

Solved!
Go to solution

I have a test application who crash near test report generation.

 

can me helph the logfile to find the issue?

 

bottom information in the lvlog file :

 

<DEBUG_OUTPUT>
12.10.2021 13:52:39.371
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id:
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x73711632 - nierInterface <unknown> + 0
0x737163C5 - nierInterface <unknown> + 0
0x73715773 - nierInterface <unknown> + 0
0x772003CB - kernel32 <unknown> + 0
0x779E5B67 - ntdll <unknown> + 0
0x779A98D5 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

0 Kudos
Message 1 of 5
(1,766 Views)

It look like in combination with MS Office Report Express VI

 

 

0 Kudos
Message 2 of 5
(1,707 Views)

I think the report generation toolkit is somewhat sensitive to the version of Office you are using.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 3 of 5
(1,699 Views)

Hi Bill,

build executable on pc with LV2015 and office 365

run executable an pc with RT2015 and office 2007

 

0 Kudos
Message 4 of 5
(1,693 Views)
Solution
Accepted by topic author SeppR

@SeppR wrote:

Hi Bill,

build executable on pc with LV2015 and office 365

run executable an pc with RT2015 and office 2007

 


Yeah, that's probably going to cause problems. I abandoned the Report Generation toolkit and other ActiveX methods years ago. Due to subtle ActiveX and MS Office differences across target machines breaking things. 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 5 of 5
(1,690 Views)