LabView Crash

[canye23]

Hello,

I was successuflly running labview VIs on labview 2016. Now I unistalled labview 2016 and installed labview 2018 32bit. But when I run some VIs, labview crashes and displays the message attached below. Any help would be appreciated. 

Thank you

[Bob_Schor]

Are you working with VIs that formerly worked with LabVIEW 2016?  In LabVIEW 2011, I had numerous "We apologize for the inconvenience" crashes when I was editing some VIs that dealt with Network Streams.  Called NI Support, and subsequently learned there was a Fatal Flaw in the Network Streams code that got identified and fixed (in LabVIEW 2012).  

Try to identify what you are doing when the crash occurs.  Are you running a VI?  Are you "coding", i.e. using LabVIEW to drop functions, create and connect wires, etc.?  It might be related to the code, but also might be related to "what you are doing".  

There is, of course, the possibility that LabVIEW 2018 "mis-installed".  You might contact NI Support (support.ni.com).  You might also consider posting the Project that causes the crash and letting some of us see if we can open and "poke" it without crashing.

Bob Schor

[canye23]

Hello Bob Schor, 

The problem occurs while I am running the program, not when I am coding or when I am connecting something. I have installed labview 2018 three times now and I am concerned beacuse this problem occurs in different VIs with completely different coding and hardware.

[Bob_Schor]

---

@canye23 wrote:

The problem occurs while I am running the program, not when I am coding or when I am connecting something. I have installed labview 2018 three times now and I am concerned beacuse this problem occurs in different VIs with completely different coding and hardware.

---

This makes it sound like LabVIEW 2018 installation may be at fault.  Are there other LabVIEW 2018 installations at your site?  What happens when you run the program on those other machines?  Does your program use any "external" VI libraries (perhaps downloaded from VIPM) or code from other hardware manufacturers?

Bob Schor