Executable built with CVI 8.1 error -5093, The analysis library was not found

[tommyH]

Upgraded development machines to Labwindows/CVI 8.1 from Labwindows/CVI 7.0. A previous application was built using the CVI 7.0 and installed onto a test machine. The same code built with CVI 8.1 is erroring when performing the stdev function, Error code -5093 was generated. (  From analysis.h: LibraryNotFoundAnlysErr = -5093,    // The analysis library was not found. ) Tried building an installation with 8.1 and installing that onto the test machine, and the application still errors when performing the stdev function. Switching back to the same application, but built with CVI 7.0, it works fine. Am i missing something with the build options in 8.1? Or is it something in the workspace or project? Please advise. Thanks in advance

[LuisG · Accepted solution]

Hi Tommy,

In CVI 8.0, the implementation of the analysis library changed from a static library that was linked to your .exe to a DLL that needs to be loaded at runtime. If you rebuild your source code and want to to deploy it to a different machine where the CVI environment is not installed, then you need to re-create an installer distribution in CVI 8.1, so that it can package the analysis library along with your program.

You can confirm whether or not the analysis library is installed by looking for C:\Program Files\National Instruments\Shared\Analysis\nianlys.dll in your target machine (although it is not sufficient to simply copy this file manually).

When you create an installer in CVI, make sure that, in the Drivers & Components tab of the Edit Installer dialog, the Analysis Support item under the LabWindows/CVI Run-Time Engine group is checked.

Luis

[tommyH]

Luis, Thank you.

This solved the missing analysis library problem, but now I am getting one of those application errors from Windows that says this application needs to close, click to send report or do not send report. Is there a problem with having multiple runtime engines on the PC? Whereas when running the application built with 7.0 used to run fine, but also now getting the same needs to close error from Windows.

[LuisG]

Hi Tommy,

That dialog means that the application is crashing somewhere. We don't know where in the software stack the crash is occurring, but if the Windows dialog reports an instruction address, that might help narrow things down.

This crash might or might not be related to the change in the analysis library. It's too early to tell.

You mention that you have multiple runtime engines in the same PC. Normally, it's only possible to have one runtime engine installed (there are some advanced scenarios in which it's possible to deploy multiple "private" versions of the runtime to be used by individual applications, but unless you explicitly chose this option, this is probably not what's happening). When you reinstalled your application in the target PC, the new version of the runtime engine should have replaced any earlier version that might have been there. You can find out which version you have by running NI-MAX (Measurement and Automation eXplorer) and browse to the CVI Run-Time Engine entry in the Software section.

Have you tried debugging the application yet. to see if you can narrow down when exactly the crash occurs?

Luis