Error Building DLL, LabView 8.2

Hello everybody,
I'm building a
CVI application. I need some functions of LabView (related to time
series analysis), so I'm trying to build DLLs with the .VIs I need. I
followed all the steps necesary and visited all the related topics at
ni.com. I always get the following error:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. +¡
Use the following information as a reference:
Error -2147221480 occurred at Building DLL stub.
This can be caused by illegal function or parameter
names. Please verify your names are legal C identifiers and do not
conflict with LabVIEW headers
This error code is undefined. No one has provided a
description for this code, or you might have wired a number that is not
an error code to the error code input.
Once, I got a correct DLL with no errors, so it should be possible for others.
This is an example of what I'm trying to compile:
And this is what appears, only for a moment, at the end of the
compiling (it didn't appear when I manage to build with no errors):
I'm using: LabView 8.2, LabWindows CVI 8.5, NI-DAQ 8.5, Windows XP (SP2)
Any suggestion is really appreciated.
Maybe another way to use this functions in CVI (I need functions related to spectral estimation, ARMA; MUSIC,...)
thank you!
Eduardo Tamargo
Spain

Hi Tamargo,
The following KnowledgeBases may help you find out what is happening:
Creating and Calling LabVIEW DLLs with Various Data Types from Microsoft Visual C++
What are the Differences Between "Array Data Pointer", "Array Handle", and "Array Handle Pointer"?
Calling a LabVIEW DLL from C with an Array in a Cluster as a Parameter
Have you tried developing a very simple VI with an array as an input parameter and checking if the same problem takes place when you build the DLL?
Regards,
David Oña

Similar Messages

Error building dll

I am getting the following error when I try to build the dll in VC++.
"Linking...
Creating library Debug/winport.lib and object Debug/winport.exp
LINK : warning LNK4098: defaultlib "MSVCRT" conflicts with use of other libs;
use /NODEFAULTLIB:library
MSVCRTD.lib(crtexe.obj) : error LNK2001: unresolved external symbol _main
Debug/winport.exe : fatal error LNK1120: 1 unresolved externals
Error executing link.exe."
Can anyone help me to get rid of this problem?
Thanx & Regards,
Srini.

srini,
Are you trying to use the dll in LabVIEW and getting the error from LabVIEW? If you are using Measurement Studio there is a seperate discussion forum for those issues. The MSVCRT is a Microsoft Visual C Run Time library. This thread explains it a little better: MSVCRT.dll
If you are trying to create C++ dlls to be used in LabVIEW you may need to create wrappers if you are using certain classes. Here is some more information on calling dlls in LabVIEW An Overview of Accessing DLLs or Shared Libraries from LabVIEW
Sam R.
Applications Engineer
National Instruments
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

LabVIEW 2011SP1 Error building installer: LabVIEW Run-Time Engine 2013 is missing 3 dependencies???

I'm having a problem building an installer in LabVIEW 2011SP1.
It's been a while since I've tried to build an installer but it used to work fine and building executables is still working fine.
Now when I try to build the installer I get "The build was unsuccessful."
Possible reasons: Error generating preview for My Application 3.1.7.
Details:
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> IB_MSI.lvclass:Build.vi >> IB_MSI.lvclass:Engine_InitializeDistribution.vi >> IB_MSI.lvclass:Report_Preview_Error.vi >> IB_Source_Container.lvclass:Report_Preview_Error.vi
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
*** Error: An internal error occurred for which the cause is unknown. (Error code -41)
*** Error Details:
Error in MDF API function: _MDFCommon_GetNextLogMessage
Error in MDF::GetInstance - MDF static instance is not initialized!
*** End Error Report
Loading product deployment information
*** WARNING ***
NI LabVIEW Run-Time Engine 2013 is missing 3 dependencies. This product, or other products that depend upon NI LabVIEW Run-Time Engine 2013, may not function properly while the dependencies are missing. Visit ni.com/info and enter the Info Code "" for more information.
The really strange thing about this is that I'm using LabVIEW 2011SP1, I don't even have LabVIEW 2013 installed, not even the runtime.
Where is the problem? Why is it even complaining about LabVIEW 2013? Has anyone seen this before?
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.

I do have the LabVIEW 2013 discs but didn't install it.
I checked in Control Panel > Programs and Features > National Instruments Software and the LabVIEW 2013 Run-Time is not listed there.
I also checked in MAX > Software and I must have missed it the first time I looked. LabVIEW Run-Time 2013 is listed there after all.
Now I remember installing VISA 5.4 to get rid of a nasty bug. It must have installed the 2013 Run-Time when I did that.
So now I need to distribute 2 runtimes with my application?!?!
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle

Building Dll for labVIEW RT gives errors

Hi All
Does building dll for labVIEW RT using CVI require labview runtime engine to be installed?
becuase i get some errors of unsatisfied referances to some library while building the dll with target selceted to "labVIEW real time only".
Regards
Arun

Hello Arun,
You don't need to have LabVIEW Run Time installed on your machine. Please check the link below to see the function that are supported by exporting the LabWindows/CVI LabVIEW RT Engine
http://digital.ni.com/public.nsf/websearch/D3EFE7C6F073384886256FDD005FBCDA?OpenDocument
Ame G.
National Instruments

Build dll error in application builder 8.6.1

Hello,
I get always an error in the LV 8.6 application builder, when I build a dll. There is only one function in it, that has a string and an error input, and nothing else. I attach a screenshot of the VI prototype, and hier is the error description:
Error 1 occurred at Building DLL.
A component needed for Application Builder does not support the required functionality. This might have been caused by installing an older version of LabVIEW after this version was installed. Reinstall the current LabVIEW version to correct this issue.
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
After that I reinstalled LV8.6, I tried to reinstall only the 8.6 app builder, but no success.

Hello,
thank you for the reply.
I have solved the problem. I uninstalled the last installed LV version, this was 8.0. Then ran appbuilder again in 8.6, then I have got an instruction to run applibs\lvdllbuilder\lvdb.exe. Since then works.
regards
Mitulatbati

Error building a DLL

I am getting this error while I attempt to build a DLL. I have reinstalled LabVIEW and the drivers twice with no help. Any thoughts would be apprieciated. Thanks.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error -2147221164 occurred at Building DLL stub.
The LabVIEW DLL Builder is not registered with the system. Reinstalling the Application Builder or Professional version should correct this problem
This error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input.

To whoever gave my response one star: If you have a better answer, why don't you post it instead of hiding behind an anonymous rating? That article directly addresses the user's post. Whether or not it solves the user's problem depends on whether or not it's tried in the first place. Did you take issue with my comment regarding searching? If the user had entered 2147221164 in the search box at the top of any of the pages on this web site, that link would have been the second hit. Point? Most users don't even bother doing a simple search before posting their question.

Error -2147221480 occurred at Building DLL stub

When I build a Shared Library, I get following error message
Error -2147221480 occurred at Building DLL stub.
This can be caused by illegal function or parameter names. Please verify your names are legal C identifiers and do not conflict with LabVIEW headers
This error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input.
Can anyone help me out regarding this error...

To begin with, do didn't say whether you have checked the two possible errors listed in the error message:
1) the function and parameter names are legal C identifiers
2) the function and parameter names do not conflict with LabVIEW headers
How many functions does your DLL have? What are their names?
What parameters do the function(s) have? What are their names?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

User events from labview build dll

Reference to pattern
Previous discussion
I had this pattern in place in a LV 7.1 application using a LabVIEW
build DLL, but when migrating to LV 8.5 I found that User Events
created in one application instance can not be fired by another
application instance. It seems that since LV 8.x a LabVIEW build DLL
are a different application instance. The generate user event function generates an error inside the DLL stating that it is not working because it is a reference from another application instance.
Is the behaviour of a LV build DLL different than a C build DLL? Is the C build DLL part of the same application instance as the LV executable?
Is there a way the get the LV build DLL to be a part of the same application instance as the LV build executable or development environment?
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Forgot to tell that I rebuild the DLL in LV 8.5, before making that conclusion.
Message Edited by andre.buurman@carya on 09-04-2008 01:12 PM
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Application Builder Error "Browse to LabVIEW.exe"

LabVIEW gurus...
I am currently building a standalone app from my project. When I run the application (which builds successfully), LabVIEW prompts me to browse to the LabVIEW.exe file. However, I want this app to run on a computer that will not have LabVIEW installed, and so browsing to this file isn't an option.
I know that the reason for this problem is that I'm using 2 call library functions named StrLen and MoveBlock within the LabVIEW.exe library (to access data from a pointer to a pointer).
LabVIEW.exe shows up as one of the dependencies in my project, but I can't figure out how to add it to my build specifications. I tried to build an installer and include the LabVIEW runtime environment, but this doesn't seem to work either.
Any suggestions would be greatly appreciated!
I'm using LabVIEW 8.6.
Thanks,
Jason
Solved!
Go to Solution.

In the dll call simply type LabVIEW without any path. This should work (I used it on 7.1)to automagicallylink it.
The functions are also located in the lvrt.dll which is the main part of the runtime engine.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Error when building DLL using Keithley library

I'm trying to build a Labview Shared DLL of my VI's, however I'm using Keithley's KPCI-PIO24 Labview driver. When I include any of their library calls into my DLL, I will get a "LABVIEW.LIB was not called from a Labview process". I have mass compiled all the Keithley libs but this hasn't helped. Any ideas??
Bob Wirth

I am not 100% sure but I beleive that the KPCI line of drivers are DOS based. I know that Keithley's GPIB driver is DOS based. I am not sure about the labview drivers. This may have some effect on building a DLL. You may have to settle for building a llb instead of a DLL.
- tbob
Inventor of the WORM Global

Error when building dll

I tried to run the example HelloWorld given in JNI tutorial. http://java.sun.com/docs/books/tutorial/native1.1/stepbystep/index.html
But when I try to build dll
I typed under dos
C:\Program Files\Microsoft Visual Studio\VC98\Bin>cl -Ic:\jdk1.3.1\include -Ic:\jdk1.3.1\include\win32 -LD HelloWorldImp.c -Fehello.dll
There was this error message:
/dll
/implib:hello.lib
/out:hello.dll
HelloWorldImp.obj
LINK: fatal error LNK1104: cannot open file "LIBCMT.lib"
Does anyone know what is wrong? Thank you very much for your help.

That looks like one of your libraries from Microsoft visual studios is missing or the folder it belongs in is not on your path. do a search on your computer to see if the file exists...if it does, make sure your path has that folder in it.
if the file is there, and on your path...try getting a fresh copy from your visual studios install cd. if you cant find the file on your hard drive, you can either add the file to the visual studio folder or try reinstalling visual.
good luck

When I try to migrate vision builder to labview I get an error message

when I try to migrate vision builder to labview I get an error message "Error at Labview code creation step #6"

Does the error seem to be occurring at the same step in your Vision Builder AI script? See if you can determine if a certain step introduces the error by trying different modifications of your script and/or generating LabVIEW code from a Vision Builder AI example inspection. Also, are you using IMAQ Vision 7.0 for LabVIEW or a previous version of the Vision software?
Best regards,
Dawna P.
Applications Engineer
National Instruments

Application crash with error ntdll.dll 00018fea

Hi,
I have a problem with my app.exe build.
I attach a simple code; the Vi open and close a TDM file.
If I run this Vi in Labview works fine.
If I build the application.exe on a notebook and I run it I got "Application crash with error ntdll.dll 00018fea".
I've tried to build the Vi on another Pc Desktop with Labview and here if I run the exe it works fine.
On the two PC I have LV8.5; the build options are the same.
On the notebook I've try also to reinstall LV8.5 but I got the same error.
Can you help me?
Thanks a lot
Attachments:
open tdm.vi ‏33 KB

MicheleS wrote:
This morning I've try to put the ntdll.dll of the other PC in the notebook but the problem remain.
Never ever do that! You were very lucky that both ntdll.dll files were probably the same version so the exchange didn't do much but ntdll.dll is one of the core Windows DLLs were everything goes through that normal applications may access in Windows. A mixup in such a part because of incompatitible ntdll.dll with other system API DLLs might prevent your computer entirely from starting up even in safe mode.
You should not attempt to ever switch system DLLs between different computers. In such behaviour lays insanity. If you expect a system DLL to be corrupt attempt to do a repair installation instead. Also Windows nowadays has techniques to detect if a system DLL got corrupt and will attempt to repair it, though I guess if ntdll.dll would go belly up it's likely your computer won't even start up.
Rolf Kalbermatter
Message Edited by rolfk on 01-14-2008 08:05 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LoadLibrary error from dll

I have created a dll in Labwindows CVI. In this dll I dynamically call another dll using LoadLibrary function. This dll works fine when I call in labwindows cvi but using labview I can't load dll using LoadLibrary function. Any idea why?
for example;
I have created mydll.dll in cvi.
In mydll.dll I have code like this
    dll_handle = LoadLibrary ("LIB2.dll");
    if(dll_handle == NULL)
     MessagePopup ("ERROR", "LIB2.DLL Load Error");
     return -49;
using labwindows I can call mydll.dll and it successfully loads LIB2.dll.
When I call mydll.dll in labview dll_handle is null. another words it couldn't load LIB2.dll using SDK LoadLibrary function.
Message Edited by test_man on 08-06-2008 01:41 PM
Thanks.
CVI 2010
LabVIEW 2011 SP1
Vision Builder AI 2011 SP1

yes, all dlls, cvi project and labview project are in same dir.
Message Edited by test_man on 08-06-2008 02:18 PM
Message Edited by test_man on 08-06-2008 02:19 PM
Thanks.
CVI 2010
LabVIEW 2011 SP1
Vision Builder AI 2011 SP1

Error building stand alone application, with LV.7.01

Hi to all....
I always get this pop up error (see picture attached) when trying to build a Stand alone application. I got the full version of Labview 7.01 and the Application builder also. the runtime engine is also 7.01.
Regards
HFZ.
HFZ
Solved!
Go to Solution.
Attachments:
Error Building App.JPG ‏51 KB

Hi GardW
All comm. problem are handeled.
The problem was based on the destinations for the .VI's.
Labview 7.1 isn't so got to manage these. It's something the user got to be carefully about.
Allmost solved. But now can't get the default 'labview Icon' to my finnished Application. You know... when you make a stand alone application..
then somewhere under the building process... you can choose if you want your own Icon added as the application starter icon! If you don't choose any.. Labview makes the Labview Icon as your application starter Icon.
And that is my problem now. Any ideas???
Thanks for trying to help , i appriceate it !!
Regards HFZ
HFZ

Error Building DLL, LabView 8.2

Similar Messages

Maybe you are looking for