PStrCaseCmp fatal LabVIEW crash

[cdweiss]

We have an application running in LabVIEW 7.1.1. We are receiving a fatal LabVIEW.exe error:
From Windows Application Event Log: "Faulting application labview.exe, version 7.1.1.4000, faulting module labview.exe, version 7.1.1.4000, fault address 0x0009965e."
Separate Application Event log entry:
"The application, C:\Program Files\National Instruments\LabVIEW 7.1\LabVIEW.exe, generated an application error The error occurred on 09/10/2008 @ 14:25:53.435 The exception generated was c0000005 at address 004996DA (LabVIEW!PStrCaseCmp)"
We have this reoccurring and cannot see anything obvious in the code that may be causing this. Any ideas on what to look for???

[Justin_P]

Hi cdweiss,

I have a couple of questions that I would like to ask you about the error that you are receiving.  Do you always get this exact error (including the 9/10/2008 timestamp)?  Can you track this error down to a specific VI in your VI?  What other programs are running when you get this error?

What you are seeing is a Windows error.  Have you added any other programs recently?

[cdweiss]

The 2 error messages are identical every time with see them with the exception of the timestamp.  Faulting application error is always at address 0x0009965e and the application log exception is always c0000005 at address 004996DA (LabVIEW!PStrCaseCmp).  It seems to be the same functional area of our code but that could be any number of several VIs (>2000 nodes not including common subVIs they could be calling) Since we don't call PStrCaseCmp directly, we have not been able to identify the particular VI or any possible cause.  If we could get information to point us to what LabVIEW subVIs we could be calling that then call this PStrCaseCmp or pointers to where you might have seen this error in the past, that would help point us to areas to look into.  Our LabVIEW application is huge (>200,000 nodes) so it is like finding a needle in the haystack with no knowledge of what to look for to find this call.  This is a critical operational issue with the customer right now and if we don't get this resolved they may not allow us to use our LabVIEW application for the follow-on contract.  Any help would be appreciated.

[Justin_P]

Has this application been running previously, or is it a new application?  Do you get this same error when you run the application on other machines? 

If your application is large it will take some work to isolate the source of the error.  If it had been running before it may be easier to just undo what ever changes has been made (either in the code or on the machine).

The PStrCaseCmp could be used in any VI that is comparing strings, which hopefully narrows it down a little.

[cdweiss]

The application is not new and the problem is intermittent so we have not been able to isolate it.  String comparisons look good in code.  If NI can point to any knowledge underlying this error that could help us find string comparisons when used in certain structures or timing or ??? that would be greatly appreciated.

[Justin_P]

There are no known issues with the PStrCaseCmp.  To resolve this issue I would first try a repair install and if that does not fix the problem I would do an uninstall/reinstall of LabVIEW.  Hopefully the reinstall will reallocate the memory location that is causing the error.