Labview 8.0 and lvanlys.dll

I had an application developed on Labview 8.0 and has the main file of it as llb and included it as project as well.
I have 2 questions
1.How to create an installer using Labview 8.0 project window.?(i was able to creat exe,but when i create installer and install it in another pc which doesn't have any NI software,i'm not able to get the exe of the software.i'm not sure what im doing wrong?,Its able to show runtime engine 8.0.1 i guess)
2.My second is,My application requires lvanlys.dll.I had put the exe of the software in new pc and copied the lvanlys.dll file manually to that PC and when i try to run the executable,it shows "Generic Error:lvanlys.dll is not a valid labview file".Is this file dependant on labview version also?because i found in that PC,i have runtime engine of 7.1.1.But i had copied this dll (from resource folder)from a pc which has Labview 8.0 installed.
Is this a mismatch?
Kindly provide help on the above 2 queries.
Thanks
-Murali

1) To create installer in LabVIEW You have to right click Build Specification Select New and then Installer. A new window pops up ,select the way you you want installer to be made .Include the main VI in Source Files and in Additional Installers select LabVIEW RunTime Engine 8.0 (or the same LabVIEW Version in which you are creating the installer). After this click on Build and the installer will be made.
2) Better provide lvanlys.dll of the same version. Or insatall DAQ drivers(or device drivers) corresponding to the LabVIEW in which the installer was made. For 8.0 you can install any drivers after NI DAQ 8.0 on the system you are running the exe.Or youcan include NI DAQ in Additional Installers whilecreating the installer.
Gaurav Ahuja

Similar Messages

LABVIEW 2009 and lvanlys.dll

Hi,
I'm relatively new to LABVIEW and I'm building an application with LABVIEW 2009. The application works well on my PC. However, the application is
intended to be ran on another machine. I then tried two approaches. First, I copied the executable file onto the second machine and second, I created
an installer file. Both methods resulted in an error when the executable was ran on the second machine. Here is the error:
"Missing external function lvanlys.dll Mean_Head.C in VI NI_AALBase.lvlib:Mean.vi". I'm hoping anyone out there knows the solution to this.
Thanks!
Bobby C

I'm not sure that link is appropriate since it talks about LabVIEW 7.1 installer and windows NT.
For LabVIEW 8 or higher, make sure that the data folder is part of the install. Done correctly, there will be your application, the data folder, and in the data folder, lvanlys.dll.

Creating a DLL in Labview 8.6 and calling it from Visual Basic 6.0

Dear friends,
I need to create a DLL in Labview 8.6 and call it from Visual Basic 6.0. The system works as follows:
I made an application using Labview 8.6 + Vision Assistant 8.6 where I can obtain the x,y coordinates of a template in an certain image being captured by an USB camera. The template coordinates change every time it moves and Visual Basic 6.0 must read these x,y values in real time. I found some information in the link http://zone.ni.com/devzone/cda/tut/p/id/3925, but it works for version 6.x of Labview and 8.6 version is different. Am I in the right path? If you have an updated tutorial like the one in the link above but for Labview 8.6 It would be very nice. Please help me.
Kind regards.
João Júnior

Hello Osvaldo,
I analysed the updated tutorial you sent me, but the thing is that it doen't show how to create the DLL in LV 8.6 but only show how to accessing the DLL from VB6. My problem is really HOW TO CREATE THE DLL IN LV8.6. In the link http://zone.ni.com/devzone/cda/tut/p/id/3063 there is detailed information about how to do this in LV6.x, the problem is that I don't find the path Tools»Build Application or Shared Library (DLL) in LV8.6, I think the procedure in LV8.6 is a little bit different. Don´t you have an updated tutorial on how to build a dll in LV8.6?How could you help me?
Kind regards.
João Júnior

Why do Analysis VIs need the full path to lvanlys.dll?

I've noticed that all Analysis VIs contain the full pathname of the lvanlys.dll that is being called. This means that the .lvproj file lists this fully qualified DLL filename as a dependency of the project. This turns out to be an issue if the same project is opened in both 32-bit and 64-bit LabVIEW - the pathname changes from "Program Files (x86)/..." to "Program Files/...", and the project has a "dirty dot". Some other VI libraries which also call DLLs located in the resource directory do not use the full path name (for example, the Vision VIs and the Wavelet Analysis VIs are two I noticed) and their dependencies are stored in the .lvproj file with the property "NI.PreserveRelativePath" set to "true".
Is there a reason why the full path is necessary, and if not, can it be removed? I've also notice that VIs calling lvinput.dll and lvsound2.dll have a full pathname, but haven't tracked through to see which others also do, or do not.

Hi,
Licensing and toolkit development are reasons for whether the full pathname is being used or the property "NI.PreserveRelativePath" is set to "true". There isn't a way to change it. Also, most toolkits will only work in 32-bit LabVIEW. According to this KB, as of 2009, NI Vision is the only toolkit that can be used in LabVIEW 64-bit. You maybe able to solve your dirty dot issue by mass compiling.
Rohama K.

"Missing external function lvanlys.dll" when running EXE

Windows 7 x32, LV2009SP1 / LVRuntime 2009
I am trying to build an EXE from a customer's code. They use the analysis library (NI_AALBase.lvlib).
It runs fine on my dev machine. When I build the EXE and pass it to a target machine with LVRuntime on it, I get the error:
Missing external function lvanlys.dll: Mean_head:C NI_AALBase.lvlib:Mean.vi.
I explicitly added the lvanlys library to the project. I added the library as a source file in the build. Finally I added the DLL itself to the project and as a source for the build.
Always the same error. The DLL is located in the data folder after the build. I tried to move it into the same folder as the EXE, and into the system32 folder. Nope.
I just changed the DLL's extension to dllx and tried again, and I get the same error, so it looks like it can't find it.
Do I need to register this DLL or something? Does it need a support file?
Solved!
Go to Solution.

Runawaycode wrote:
As the application was launched, a pop up window suggested to download the Labview run time engine, and an internet address was suggested.
I am not aware that there is a download link suggestion. Can you show us a picture of the popup window? Does the link really point to the minimum run time engine? That would be hard to believe.....
Runawaycode wrote:
National Instruments should warn the users that there are more download versions or possibly suggest the complete version if something goes wrong.
The download page for the run time engine is very specific about the various versions. It is a matter of actually reading it.
It is even more clear in the newer versions, where the minimum run time version has been renamed into web browser plugin. The description is:
This is the download page for the LabVIEW 2012 (32-bit) Remote Front Panel Web Browser Plug-in (formerly known as the Minimum Run-Time Engine). The Web Browser Plug-in is a smaller download intended for viewing VIs embedded in a web page. It does not contain the full run-time engine and is not recommended for running executables.
Compare with the standard run time engine where the description is:
"This Run-Time Engine must be installed on any 32-bit or 64-bit Windows system where you plan to run executables that you build with the Application Builder in LabVIEW 2012 or 2012 SP1 (32-bit). Executables built with LabVIEW 2012 or 2012 SP1 (64-bit) require the LabVIEW 2012 (64-bit) Run-Time Engine.
Additionally, the Run-Time Engine allows your browser to display VIs embedded in Web pages."
I am not sure how much clearer it could be made. Do you have a suggestion?
LabVIEW Champion . Do more with less code and in less time .

Lvanlys.dll

请教各位大侠，我安装了ｌａｂｖｉｅｗ８．２０中文试用版，本人刚学这个软件，从开始打开模板准备打开模板是出现lvanlys.dll初始化例程失败，不知道为何。请各位大侠指教
Attachments:
Image00005.GIF ‏46 KB

Hi, thank you for your reply!
I have just fixed the problem! I have replaced all the content in "D:\Program Files\National Instruments\Shared\MKL" with another copy from my classmate who has successfully installed labVIEW2012. And it worked!
The problem was that when I tried to add an "simulation signal" component in the Block Diagram, an error message kept popping up indicating an error in loading "D:\Program Files\National Instruments\LabVIEW 2012\resource\lvanlys.dll" and DLL initialization examples failed. These messages kept popping up for dozens of times and finally a blank "simulation signal" component with no available attribute came up.
I guess the reason of this problem is that I have uninstalled labVIEW2013 on this computer before. When I searched the Internet I found that there is something wrong with the NI uninstallation and after you reinstall it there will be all kinds of problems.
Anyway it is so great that my labVIEW finally works, after I have spent this whole week trying all kinds of methods I can find on the Internet to fix it !

Lvanlys.dll file issues

The lvanlys.dll is listed in my project files in three separate entries in three separate folders, one of which was not found. Why is this dll not pulled from the labVIEW vi library and how can I reconcile all of these separate files? I am using labVIEW 2010

I apologize, I have been out of the office for the past two weeks and have been unable to work on this. I have just a few clarifying questions. You are unable to fully build the executable correct? Because LabVIEW keeps trying to locate the lvanlys.dll file? Or can you build the executable, but the lvanyls.dll file is missing?
From what I've looked into, this lvanlys.dll file has caused some issues before. Sometimes there is an issue with LabVIEW trying to link to a previous version of the dll file. Here are a few links here for you to look through that may help.
http://forums.ni.com/t5/LabVIEW/lvanlys-dll-problem-with-linking-and-math-functions/td-p/214758
http://forums.ni.com/t5/LabVIEW/DLL-build-by-Labview-App-Builder-doesn-t-work-if-Built-IN/m-p/206695...
http://digital.ni.com/public.nsf/allkb/FA6D52BA5D44232D86256FAB006FF038
Daniel K | NI Applications Engineer | Certified LabVIEW Developer

I just installed LV2011 and one dll from my vi won't load with the error "application configuration is incorrect"

I just installed LV2011 and one dll from my vi won't load with the error "application configuration is incorrect", which is Windows lingo for "missing package dependencies". All the computers at my company with 2010 loaded seem to do OK. When I do a Dependencies Walk I get missing Visual C debug dll's missing plus IEshims and wer which both have a whole tree of dependencies missing on my machine. The Windows install is the same "Windows XP version 2002 Service Pack 3" on my PC and the working PC's. So I'm thinking I have to uninstall 2011 and go back to 2010. Is this correct? Those VC debug dll's were installed on the machines with 2010 in them but were not installed in mine.
I've heard the advice to recompile the dll with debug turned off but I don't have access to the source code.
Thanks in advance.

u87 wrote:
Thanks for the reply. This at least tells me that going back to LV2010 is not likely to solve the problem. The missing dll's are:
MFC90D.dll
MSVCR90D.dll
IESHMS.dll
WER.dll
And, once again, IESHMS and WER have other dependencies. So perhaps i need to install the Visual C++ development environment.
IESHIMS.dll is an Internet Explorer DLL that gets usually delay loaded by shdocvw.dll. As delay load it can not cause DLL load errors but only runtime errors. Maybe your DLL has it as direct dependency but that is unlikely since it does not have a documented interface.
WER.dll is Windows error reporting for Vista/Win7.
MFC90D.dll is the Microsoft Foundation classes and MSVCR90D.dll is the MS C runtime library, both as debug variant.
So all the DLLs you mention are actually MS DLLs! You haven't identified the DLL that you try to access in LabVIEW that causes these error messages. IESHIMS and WER are usually delay loaded by any component that needs it and should not likely be used by non MS code.
What is the DLL you try to load into LabVIEW and by whom? Get the provider of that DLL to provide you a non Debug build of the DLL. Installing Visual C on all the machines just to make the DLL load is not a solution, besides that it is likely not legal since I doubt you have that many licenses.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

I am trying to integrate simulink model (.mdl) file with SIT of Labview for RCP and HIL purpose. I am using Labview 8.6, Simulink 6.6 with RTW 6.6 and RTW embedded coder 4.6 ,Visual C Express 2008 and Visual C++ Express 2008.

I am trying to integrate simulink model (.mdl) file with SIT of Labview for RCP and HIL purpose. I am using Labview 8.6, Simulink 6.6 with RTW 6.6 and RTW embedded coder 4.6 ,Visual C Express 2008 and Visual C++ Express 2008. I have selected system target file as nidll.tlc,make command as make_rtw and template nidll_vs.tmf. When I try to generate .dll file I get the following error.
Attachments:
SITProblem.JPG ‏101 KB

Hi,
No . I could not solve the issue. Presently we are using microautobox (from Dspace)for doing the RCP.
Himadri

I keep getting an error trying to open labview 7.1, and I am really confused. screen shot and log included

Hello,
For some reason, recently I have been getting problems trying to run labview. It all started when I upgraded from labview 6 to labview 7.1. I even went as far as to re-image a brand new machine with XP and start over again. I'm still getting issues. What do you think? Can a virus cause problems like this?
Thanks for your help, I really appreciate it
Attachments:
error_labview_7_1.JPG ‏13 KB
4f9d_appcompat.txt ‏27 KB

Hello!
Sorry to hear you are experiencing problems with
LabVIEW. This error dialogue is a result
of some error causing Windows to shut LabVIEW down. This is a little different than an internal
LabVIEW error which usually results in an error message with a .cpp file/line
number. I don’t really know how to
decode the MS error log file, but what I see it looks like you are doing quite
a bit of complicated programming. I see references
to quite a lot of the more advanced LabVIEW programming items (such as dlls, mathscript,
images, and storage). I highly suspect
that the crashes are occurring somewhere in external code, but without more
info on your program it could be hard for me to diagnose. Could you provide us with a little more
information about your application? Also,
it would be great for troubleshooting if you could reduce the crashing VI as
much as possible so that we can see exactly _where_ the crash is occurring. This could shed a lot of light on the
problem.
Also, if you are doing some mathscript stuff, don’t forget
to check out: http://digital.ni.com/public.nsf/websearch/4475BC3CEB062C9586256D750058F14B?OpenDocument
in case any of this pertains to your system.
Thanks for posting to the NI Discussion Forums! Please let me know how it all goes-
Travis M
LabVIEW R&D
National Instruments

LabVIEW Mac prompting me for dll's in conditional disable structure

I'm using LabVIEW 2014 Mac and I have several conditional disable structures which call user32.dll but only in the Default case whereas they do nothing in the TARGET_TYPE=Mac case. When loading my source code in LV Mac I get prompted to find "user32" and I have to Ignore All. Afterwords the code is open with no errors.
It seems to be a bug that this prompt is occuring? Is there a way to supress it?
Solved!
Go to Solution.

Hello Thomas,
It sounds like the user32.dll is being loaded along with your LabVIEW code on launch instead of being loaded when called. What you can do is encapsulate the function that is making the user32.dll call in a subVI (if you haven't already done this), right-click the subVI and go to Call Setup. From this window, choose Load and Retain on First Call. This should make sure the user32.dll is only loaded when you reach the Default case in your Conditional Disable structure, and not search for it every time the code is loaded into LabVIEW.
Hope this helps,
Siana A.
Application Engineering
National Instruments

Is it possible through labview to set and read window¿s based file properties?

Any file in XP operating system has file properties associated with it, such as, size, location, when the file was created, modified and last accessed. I know that Labview has the ability to access the size and modified property. Other file types such as image format types jpg, bmp and tif have additional associated properties such as: title, subject, author, and comments. Is it possible through labview to read and set these properties programmatically?

Hpopenoe wrote:
> Any file in XP operating system has file properties associated with
> it, such as, size, location, when the file was created, modified and
> last accessed. I know that Labview has the ability to access the size
> and modified property. Other file types such as image format types
> jpg, bmp and tif have additional associated properties such as: title,
> subject, author, and comments. Is it possible through labview to read
> and set these properties programmatically?
Well, you can most probably do that by calling Windows API functions.
Note however that the properties you mention are not generic Windows
file properties but file specific internal attributes. Explorer does at
least in XP handle some of those properties and shows them to the user
but does so with internal file type handlers to extract the properties
from the file.
I'm not sure those file type handlers are actually available for other
applications than Explorer without quite some work. If they are
available they are certainly not part of the standard Win32 API but most
probably part of the Windows shell component and I would guess not just
through normal API function calls, but through the shell namespace
enumeration, which is built on COM interfaces, something you only can
call from standard programming languages, most of them are done in C++
(and if you are a little more persistant in standard C).
So you are likely to need to either write your own DLL doing the nitty
gritty work of calling the shell interface and using that DLL in LabVIEW
or find an Active X component which does the work for you. No doubt
there is such an Active X component somewhere but how good and expensive
is always a big question.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Using both, LabVIEW 32-bit and 64-bit

Hi Guys,
I have a requirement where I have to interface with a camera using LabVIEW 64-bit (because the dll provided is for 64-bit system). At the same time, I have to communicate with several variables via OPC Server using LabVIEW DSC, which is only available in 32-bit. I was told that I cannot run one same program but utilizing LabVIEW 32 and 64 bit simultaneously. Hence, I would like some advice, especially on the architecture, on how should I approach this.
Advices are much appreciated.
Shazlan

Are you sure that you can't have a 32-bit compatible dll for your camera? It would really make your life easier.
Also if you only use the DSC module for the OPC function, maybe you could look for a different set of OPC functions that support 64-bit.
In the end if you really have not choice but to use DSC module and use the 64-bit dll for the camera, you will need to apps, one in LV32 and one in LV64 and you will have to decide which one is the main one and find a way to communicate between them, TCP comes to mind, also VIServer, I have never tried VIServer between a LV32 app and a LV64 app but my bet is that it should work seamlessly.
Good luck!
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

What are analogous shared libraries that can be called using a call library function to user32.dll and lvtoolbox.dll when using Linux and Mac?

I am wondering if anyone is familiar with how to get similar information with a LV program using a Linux shared library as well as the corrolate Mac library to the Windows user32.dll and lvtoolbox.dll. I specifically am trying to get system metrics such as screen resolution information and cursor information as well as being able to set mouse position. I am trying to convert a LV Windows program to these other operating systems and I am unfamiliar with these platforms.
Thanks for your time - I really appreciate it.

There is no simple answer to that. On Linux you will likely have to call into X Server, which would be a pain to do, due to various versions and implementations of that. On the Mac there would be the difficulty that you can't call into the native ObjectiveC API but would need to find a Carbon API or something like that to do what you want.
If you seriously want to do something like this for multiplatform, you should bite the bullet and start coding an intermediate shared library in C. This library would export a LabVIEW friendly C API and access whatever system API you need to have for the particular functions. But multiplatform programming on this level is a pain in the ass, no matter what.
Message Edited by rolfk on 04-21-2010 08:26 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LabVIEW 8.5 and building executable (using fxs from Advanced Signal Processing Toolkit)

Hello out there to NI and Gavin:
For for building an executable using LabVIEW 8.5 and functions from the
Advanced Signal Processing toolkit, do we still need to manually copy the
special set of DLLs related to the toolkit use to the target installation, or are these now included
within a build file for automatic installation to the target
installation?
Thanks,
Don

Hi Don,
I imagine that any improvements made to steps required to build an executable using toolkit-specific vi's would be inherent of the toolkit itself. Meaning, I imagine the inconvenience you experienced would be eliminated with the next release of the Advanced Signal Processing Toolkit.
Cheers,
Emilie K. | Applications Engineer

Labview 8.0 and lvanlys.dll

Similar Messages

Maybe you are looking for