LabVIEW executable with .NET controls crash, if operating system's regional format is Turkish

[Wirer2]

Tested with Windows 7 and LabVIEW 2009 and 2010:

Crash is very easy to reproduce:

1. Go to Windows Control panel -> Region and Language -> In the first tab, set format: Turkish (Turkey) -> Apply change (doesn't need system restart)

2. Start LabVIEW (2009 or 2010) and create a blank VI.

3. From the .NET palette, drag the MonthCalendar to your front panel. In many cases it crashes at this point.

4. Save the VI and build an application exe about it.

5. Run the built application: it doesn't start, just crashes. From the Windows event viewer you can get some information:

Faulting application name: TurkishCrash.exe, version: 1.0.0.0, time stamp: 0x4b47dc79

Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86

Exception code: 0xe0434f4d

Fault offset: 0x0000c42d

Faulting process id: 0x%9

Faulting application start time: 0x%10

Faulting application path: %11

Faulting module path: %12

Report Id: %13

By searcing with KERNELBASE.dll and 0xe0434f4d you can get some information from web and it seems to be .NET related issue.

I'm wondering how the LabVIEW application developers survive in Turkey because of this problem..

Anyone noticed this, NI engineers?

BR,

Jani

[nyc_(is_out_of_here)]

---

@Wirer2 wrote:

Tested with Windows 7 and LabVIEW 2009 and 2010:

Crash is very easy to reproduce:

1. Go to Windows Control panel -> Region and Language -> In the first tab, set format: Turkish (Turkey) -> Apply change (doesn't need system restart)

2. Start LabVIEW (2009 or 2010) and create a blank VI.

3. From the .NET palette, drag the MonthCalendar to your front panel. In many cases it crashes at this point.

4. Save the VI and build an application exe about it.

5. Run the built application: it doesn't start, just crashes. From the Windows event viewer you can get some information:

Faulting application name: TurkishCrash.exe, version: 1.0.0.0, time stamp: 0x4b47dc79

Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86

Exception code: 0xe0434f4d

Fault offset: 0x0000c42d

Faulting process id: 0x%9

Faulting application start time: 0x%10

Faulting application path: %11

Faulting module path: %12

Report Id: %13

By searcing with KERNELBASE.dll and 0xe0434f4d you can get some information from web and it seems to be .NET related issue.

I'm wondering how the LabVIEW application developers survive in Turkey because of this problem..

Anyone noticed this, NI engineers?

BR,

Jani

---

Have you tried to use the .NET control in a simple Windows Form application in VB.NET or C# ?

Does it behave the same way?

[Wirer2]

Well, at least other c# applications build with VC seem to work when Turkish format enabled.

But LabVIEW-built applications with any .NET controls seem to cause crash, not only MonthCalender.

[JÞB]

Which version of .NET? and did you create the LabVIEW.exe.config file?

[Wirer2]

With LabVIEW 2009 .NET 2.0

With LabVIEW 2010 .NET 4.0 (which I have enabled through LabVIEW.exe.config)

[JÞB]

You did create the TurkishCrash.exe.config and included it in the build too right?

[Wirer2]

Yes I did. Crashes with and without it.

[Wirer2]

Tested with LabVIEW 2014 and seems to work perfectly, no crash.

Maybe it's time start using the latest LabVIEW version..