LabView 12 AppCrash

[maximint]

Hello together,

we're using since years a LabView application (exe without dev. environment), which is running in the meanwhile under LabView 12. It's a huge application with many RS232 communications, an I/O board, printer, etc. OS is Windows 7.

Now, we have two new test machines and I have an app crash which I cannot localize.

The application is running successfully on older machines, also equipped with W7.

Many Thanks for a tip.

Thomas.

Here the crash report:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    ASELCA.exe
  Application Version:    1.0.0.0
  Application Timestamp:    50d22f24
  Fault Module Name:    lvrt.dll
  Fault Module Version:    12.0.1.4014
  Fault Module Timestamp:    522f374c
  Exception Code:    c00002b4
  Exception Offset:    0093f2c5
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    4103
  Additional Information 1:    0a9e
  Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:    0a9e
  Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

[maximint]

nobody any idea? I cannot find the reason and customer is getting a little bit nervous.

I attach the NIR report

####
#Date: Fr, 21. Apr 2017 14:47:22
#OSName: Windows 7 Ultimate Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: ASELCA
#Version: 12.0.1f9 32-bit
#AppKind: AppLib
#AppModDate: 04/20/2017 12:55 GMT
#LabVIEW Base Address: 0x30000000



<DEBUG_OUTPUT>
21.04.2017 14:53:00.676
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash 0x0: Crash caught by NIER
minidump id: c9c9686f-6b82-480b-8b05-dd4fa1fe50c6
ExceptionCode: 0xC00002B4 N

</DEBUG_OUTPUT>
0x30729214 - lvrt <unknown> + 0
0x30729598 - lvrt <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77CB82CA - ntdll <unknown> + 0
0x77CA3B26 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

<Version>2.0</Version>
<Autosend>False</Autosend>
<Email>

[Bob_Schor]

This is my understanding:

• You have a LabVIEW application built as an Executable with LabVIEW 2012, 32-bit..
• It is running successfully on a Windows 7 PC, of unknown bittedness (Win-32 or Win-64, you didn't say, or I didn't see it).
• You want to run it on a second Windows 7 PC, also of unknown bittedness, but it doesn't run.

Here are my questions:

• Is the first Windows PC (on which the App works) the PC on which the software was developed, and still has LabVIEW 2012 installed?
• If not, how did you install the software on the first Windows PC?
• Are the two Windows PCs both running the same bit-version of Windows?
• If you didn't specifically install it, you may be missing the LabVIEW 2012 Run Time Engine on PC #2.  If PC #1 was the Development PC, it would already have the RTE.

Bob Schor

[nclark]

I have to agree with Bob. Those issues all seem very likely. Less likely is this: If you're machine's RAM is already filled up with other stuff and LabVIEW cannot block off large blocks of consecutive memory, then the program may throw memory errors and crash. I know this happens for image acquisition which requires large chunks of memory, but I'm unsure if it'll happen with anything else. The way to fix this is to minimize your startup programs and restart the computer. This will clear the RAM and help keep your startup programs from taking up memory space.

[maximint]

Here are my questions:

• Q: Is the first Windows PC (on which the App works) the PC on which the software was developed, and still has LabVIEW 2012 installed?
• A:no. The first PC is a PC running with LV2012 runtime.

• Q: If not, how did you install the software on the first Windows PC?
• A: LV2012 runtime plus executable

• Q: Are the two Windows PCs both running the same bit-version of Windows?
• A: Yes, but W7 ult., 32bit
• Q:If you didn't specifically install it, you may be missing the LabVIEW 2012 Run Time Engine on PC #2.  If PC #1 was the Development PC, it would already have the RTE.
• A: no, RT latest version installed.

Thanks for your answers so far. I'm now ready for weekend and continue on Monday.

Thx.

[maximint]

it's not an image acquire app.

It uses

- WASCO digital IO card

- a lot of RS 232 units like Keithley measurement equipment and scanners

- a lot of ODBC database traffic

Thx. Thomas.

[JÞB]

Well, if you did not build an installer for the app you probably missed a bunch of drivers.  VISA Run-time and configuration support comes to mind.  

How did you configure the hardware?  Like assigning aliases to the COM Ports?  Did you import a *.nce file into NI MAX?  is MAX installed? If so- does the system configuration look similar between the two machines?  Are you missing any other third party drivers? (Virtual COM Ports, Wasco HW Driver, etc....)

[Minions]

BTW, if it has a lot of ODBC calls, are both systems setup the same?  Are the files located in the same directories on both machines?  Check under REGEDIT to ensure that both ODBC sections are the same for the files and applications being used.

[maximint]

Hello together,

the ODBC settings and HW settings are identical.

The main difference is the hardware. The old running system uses other main board, other CPU and other memory than the new not working system.

Question:

1. is it possible that the memory could be the reason? We use one memory module 2GB.

2. is it possible that the main board could be the reason?

The crash comes from time to time after different events, for example closing a window, popping up a user message window, directly after start up the app.

3. Is there a possibility to isolate the problem ?

[RavensFan]

2 GB on any modern PC and OS sounds like a low amount of memory.