adlibelf.dll?

[rmp]

I'm getting a pop up window when I double-click a vi from Win7: "Labview.exe - System Error The program can't start because ADLIBELF.dll is missing from your computer. Try reinstalling the program to fix this problem". If I just click the OK button in the pop up window the message goes away for a second while Labview appears to begin loading the selected vi. But the window pops up again while (I think) it's searching for a dll that our folks wrote. 

Anyone know what this ADLIBELF.dll is, and why I might not have it (a google search turns up NOTHING!!!!)?

A little more info:

 - I have LV 2010 SP1 (and have been using it for 2+ years)

 - other VIs seem to load/open OK

 - the vi that I'm trying to load/open is part of a large package of LV + DLLs for our company's application

 - I just downloaded our source code (the VIs) on to my laptop so that I can study it. I think our folks developed the application in LV 2010

Hmmmm, a little more info:

 - because of our license manager for Labview, my computer takes about 20 minutes to boot if I'm not connected to the internet

 - I think this is a Labview license manager issue

 - Over the past 3-4 months I've been trying to solve this problem by following suggestions found online (reconfigurations of Labview start up or license manager configs... it's been a while so I'd have to find my notes)

 - I wonder if this is related?????

[apriltalksrobots]

rmp, 

It appears that adlibelf.dll is a custom .dll created by your company because, as you stated, it does not come up in any searches of NI's .dlls. As to why you might not have it, it's possible that it's located in a file that's not searched by LabVIEW's routine search path. I would try searching your computer to find this file, and see if it has been moved to another location. You could also search the source code you mentioned to see if it's in there. 

You could also try doing a force reinstall of LabVIEW to see if that fixes the issue, but I'm not sure if it will. Let us know if you're able to find that .dll! 

Thanks, 

aprillest

[rmp]

Thanks Aprillest,

That would make sense. Maybe it's a library that goes along with an A/D that we're using... if it's an obscure product, or a library that we created for the A/D, that might explain why a Google search comes up empty.

I might not have gotten the full distribution of our code. I'll go back to our engineers to try to find out what and where this dll is.

Thanks again,

Richard

[rolfk]

Also if you find that the DLL is actually present somewhere and in a place that LabVIEW can find it, you still might get this error if a secondary dependency of that DLL is not present on your computer. For instance if your company uses Visual Studio to create that DLL and selected to make it link to the DLL C Runtime library, the according Microsoft Visual C Runtime library must be explicitedly installed on your computer. And not just any C Runtime library but the one that matches the Visual Studio version used to compile that DLL. And if they use some other compiler it can happen just as much if the compiler settings are set to link to the dynamic C runtime version for that compiler.

So it's probably important to identify to which package the DLL belongs, then read the whole installation documentation for that package, which hopefully documents what needs to be installed and how for all the components to work. What there is no such documentation? Go and find the product developer and whack him a few times with a stick!

[rmp]

Thanks Rolfk,

I think I followed most of what you're saying.... the DLL might call other C routines or libraries, and Labview would probably not catch those in its load/compile errors.

I'm begging for source code and support in rounding it all up, so I have to walk softly and bribe with candy bars... whacking would leave me in library lookup hell, I'm afraid. I'm sure there's documentation somewhere, but developers come and go so quickly that keeping up with it is a challenge. Thanks for the insights

[rmp · Accepted solution]

Thanks folks, yup, I had not installed a "toolkit" for a DSP that we use... once installed, everything loads and compiles. Hopefully there are no runtime issues...