LabVIEW Run-Time Crash (2009) lvrt.dll

[GregAA]

Hello,

I am currently experiencing a problem with an application built with LabVIEW 2009.  At random periods (often not more than once or twice a week when using the application regularly) I get a Windows error referencing lvrt.dll as the culprit.  I am having a hard time troubleshooting because of the scarcity of the problem, as well as the random nature (appearing in completely separate parts of the application, does not seem to be associated with any particular module of the code).

A little background- I have inherited the application maintenance, which has gone through many different versions of LabVIEW.  I implemented the code into LabVIEW 2009 from 8.6, which is when the error began to appear.  At that time no change was made to the source code itself, just merely built using 2009 rather than 8.6.

I apologize for the somewhat vague information; unfortunately this is all I have after working on this issue for weeks.  If anyone has any suggestions or similar experience your advice would be greatly appreciated!

Thanks

[Sean_N]

Hello GregAA

I am probably going to need more information to help you try to solve this.  The main thing is to try to figure out what changed when the error started to occur.  As far as I can tell from your description, the program was written in an earlier version than 8.6, and the problem started to occur when it was upgraded to 8.6, correct?  This error is now occurring in 2009.  

Does this error occur in the developer environment or just as an executable?

Any other pertinent information you can think of might help us find a resolution.

Thank you,

Sean N

[Greg AA]

Hello Sean,

The problem appeared when moving from 8.6 to 2009.  Nothing was changed in the LabVIEW code itself, I just moved the project files to a computer with LV 2009 and did an application build.

The error only occurs when running as an executable.  I have not experienced the error when I run from the LabVIEW environment.

Thanks for your help, I know the information I have is somewhat limited- but I have exhausted as many avenues as I can think of to isolate the error further with no success.

[Sean_N]

Greg AA-

My initial thought was that you built and compiled it on a different OS than you are trying to run it on.  For instance, if you built it on computer A, that has LV 2009 and Windows XP, but are running it on computer B with LV 2009 and Windows Vista, there could be issues.  In theory, if it was compiled and is being run on Vista or 7, it should work because both are based off Windows NT 6.x (although it is not guaranteed to work unless it is compiled on the same OS that it is being run on.  This was just one thought.

If it was compiled on the same OS that it is being run on, then I am going to try some more digging...

-So we're clear, the error you are getting is a WINDOWS error, not a LabVIEW, correct?

-Have you run error wires through your code to see if LabVIEW reports any error?

-Have there been any changes to the development/deployment machines, such as software (non-LV) or OS upgrades?

-What OS are you using for both building and deploying?

-Is the deployment machine the same as the development machine?

Some of these questions might seem redundant, but I just want to make sure that I absolutely have every piece of information that might help.

Thanks,

Sean

[Sean_N]

A couple more things too...

-Is there a Windows error code associated with this?

-Have you looked at the Windows error log to track the error?

Thanks,

Sean

[Greg AA]

Hi Sean,

A few answers to your questions.

All systems have been running Windows XP exclusively.

The error is a Windows error (including an option to send the error report to Microsoft)

No changes to deployment machines in a few years.  Different development machine when moved to LV2009, previous computer running 8.6 is no longer available.  No obvious differences in development machines.

I have experienced the error across numerous deployment machines, never on the development machine

Thanks,

Greg

[Sean_N]

Greg AA-

-Are you running 2009 SP1?  SP1 with patches?

-Can you take a screen shot of the error so I can get a windows error number?

-Are you calling any other .dlls other than the LV runtime .dll?

-Are you accessing hardware?

-Try a debuggable .exe and use highlight execution to trace the error (could be time consuming, but might be worth a try).

-Try speeding up the code to reproduce the error more frequently (by decreasing wait times etc.).  If the error does indeed happen more frequently, this could help break down the location of the error.

I know it may seem like a lot of questions without any answers, but this will help us figure it out (been using my neighboring resources, so thats why the questions don't come all at once!)

Thanks,

Sean N

[GregAA]

Hello Again Sean, thanks for your help.

I am running 2009 SP1.

There are other DLLs called throughout the code, but not any specific calls seem to cause the crash.  Likewise, as the crash will occur randomly throughout all of the software I suspect it is not in the code itself (i.e. this application consists of nearly 1000 VIs.  The crash has occurred while running various parts of the software, so it can't be traced to any particular party of the code via debug mode, highlight execution, etc).

I have attached a screen shot of the error message I receive.  Any other thoughts would be greatly appreciated.

[Sean_N]

-Make sure that the development machine has all updated drivers

-Have all of the deployment machines had all proper driver updates?

-Are there any dependencies listed in the project when you build the application?

-If so, can you add these dependencies to the project, build the application, and then try running the executable?

-Do any other machines have LabVIEW installed so you can try building it on a different machine (and also try running it in LabVIEW)?

We'll keep eliminating all these options until the source is revealed!

Thanks,

Sean

[GregAA]

There are no dependencies listed in the project when I do the build.

Which drivers are you refering to for the development/deployment machines?  Hardware drivers?

Neither development nor test deployment have any DAQ hardware in them.  (Our code has a "offline" mode in which case structures are used to disable all DAQ portions of the code).

I can try to build the application using a different machine if you believe that may be helpful.

When running it in LabVIEW on the development machine this error has never occured.