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

Similar Messages

  • Error -214722148​0 occured at building dll stub

    I am trying to create a LabView Dll, however i keep getting this error whan i attempt to build it. I have created Dll's before but all of a sudden it just stopped working. Has anyone else seen this and can shed some light? I'm using LV 7.0

    Hello,
    I am sorry that the previous solution didn't fix the problem. I found another knowledge base entry that may be the correct solution. Please follow the instructions on the following link:
    http://digital.ni.com/public.nsf/websearch/51A4147​B66E59BA286256C690077109B?OpenDocument
    I honestly feel that this will cure your problem. However, if you still experience the same error after trying this second fix, please let me know so that I can properly escalate the situation within our support team.
    I hope this helps. Please keep me updated.
    Kind Regards,
    Joe Des Rosier
    National Instruments

  • Getting "Error 10 occurred" when building exe

    I am getting the following error when trying to build an executable: "Error 10 occurred at C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\Daq\lvdaq.dll"
    Listed under possible reasons were:
    LabVIEW: Duplicate path.
    NI-488: New I/O attempted with old I/O in progress.
    I made some changes and added a .vi to my program, but get no errors if I run the program from the top level .vi.
    Any ideas?

    Hi Rob,
    For some reason there's an issue with the link to the lvdaq.dll in your
    application. The lvdaq.dll is used by the DAQ VIs from the palette -
    are you by any reason calling the DLL directly from a Call Library
    Function Node?
    Can you please explain what changes you made to the VI that caused the
    issue. It would also be a help if you submit the VIs that you are
    trying to build into an executable, thanks.
    - Philip Courtois, Thinkbot Solutions

  • Error 7 occurred when building Exe in LabVIEW2010 SP1

    Hi All,
    I wanted to build an Exe for my Application. When I created an Exe and give Generate Preview, I got the following warning.
    Further, I tried to delete most of the code and give generate preview
    I didnt get any warning but I dont know, What is that empty file under data folder? Please explain if any one know the reason
    Then I build the Exe, the following error is popped up.
    Error copying files.
    Source: D:\Test Exe\SC\SubVIs\
    Destination: D:\Test Exe\Exe\data\
    source does not exist
    Details:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 7 occurred at AB_Destination.lvclass:Copy_File.vi -> AB_Source.lvclass:Copy_SourceItem.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
    =========================
    NI-488: Nonexistent GPIB interface."
    Herewith I have attached the LabVIEW code (LV 2010 SP1) which I extracted from my Project.
    I browsed our ni forum and the answers posted couldnt sort my problem.
    Thanks for your reply in advance
    Thanks,
    Charu Praba
    Attachments:
    Test Exe.zip ‏9 KB

    Hi Rob,
    For some reason there's an issue with the link to the lvdaq.dll in your
    application. The lvdaq.dll is used by the DAQ VIs from the palette -
    are you by any reason calling the DLL directly from a Call Library
    Function Node?
    Can you please explain what changes you made to the VI that caused the
    issue. It would also be a help if you submit the VIs that you are
    trying to build into an executable, thanks.
    - Philip Courtois, Thinkbot Solutions

  • Error 7 occurred while building source distribution in labview 8

    I can build exe file and  installer for my project. But while trying to build source distribution i got an error. Error description is as follows:
    Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine.vi -> SDBUIP_Build_Invoke.vi -> SDBUIP_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux.

    Hi Andy,
    FYI, initially part of this project was developed in LabVIEW 7.1 and now I have
    converted all the project files to LabVIEW 8.0. This was done by mass compiling and
    saving all the VIs.
    It is possible for me to build source distribution for some other programs. But I got the error while building source distribution for my current project. Same error was generated even while previewing the source distribution. This project contains some dynamic VIs. I had included them under the dynamic VIs and support files while creating EXE file. While building source distribution, i got an error message saying that :
    "Unable to generate preview. An included VI or one of its dependencies does not exist. Open all Startup/Exported/Dynamically called VIs, recompile them  (Ctrl-Shift Click the run arrow), and save them to update their dependencies.
    \\Source code\Controls\Tests\Battery Current Calibration\Battery Current Calibration1.ctl
    <Call Chain>Error 7 occurred at ABAPI Dist Report Read Link Info Error.vi -> ABAPI Dist Cmp Settings to Disk Hier.vi -> ABAPI Get Settings From File.vi -> SDBEP_Invoke_Build_Engine_Preview.vi -> SDBUIP_Build_Rule_Editor.vi -> SDBUIP_Item_OnDoProperties.vi -> SDBUIP_Item_OnDoProperties.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux."
    For this error I rename the control, relink it in the code, and save the VI. Now I got an error message indicating different control. I was totally confused by this behaviour. What is the problem? Why the problem occured? What procedure to follow to avoid these kind of errors in future? I would be thankful, if I can get answers for my questions.
    Thanks in advance.
    Ramasamy.

  • Error 1 occurred while building source distribution in labview 8.2.1

    I can build exe file and  installer for my project. But while trying to build source distribution on RT i got an error. Error description is as follows:
    Error -1 occurred at Invoke Node in SDBUIP_Build_Invoke.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_CreateNewWizard_Invoke.vi->SDBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
    When i click generate preview, i got an error.
    Unable to generate preview. Invoke Node in ABAPI Dist read linkages.vi->ABAPI Dist Cmp Settings to Disk Hier.vi->ABAPI Get Settings From File2.vi->SDBEP_Invoke_Build_Engine_Preview.vi->SDBUIP_Build_Rule_Editor.vi->SDBUIP_Item_OnDoProperties.vi->SDBUIP_Item_OnDoProperties.vi.ProxyCaller
    Thanks in advance.
    Poolsak T.
    Attachments:
    rt_deploy2.zip ‏34 KB

    Hi,
    I would first try mass compiling the vi's within your project to ensure there aren't any unresolved conflicts. Moreover, it's intersting that you can create an application without problems but upon building a distribution, things go awry.
    Do the vi's run on the RT target without error? Does the application run on the target without error? Or do they run on your host just fine and its when you attempt to deploy on to your RT target that this error occurs?
    Let's see where this gets us.
    Cheers,
    Emilie K | National Instruments

  • Error 8 occurred when building an executable due to file permission error?

    I received this error on executable builds from two different .vis.  Other .vis in the project build without incident and the message below doesn't seem to indicate the file that is causing the problem, unless it is the SPT-errors.txt file listed at the end of the error message.
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  File permission error. You do not have the correct permissions for the file.
    =========================
    NI-488:  DMA hardware error detected.
    C:\Program Files\National Instruments\LabVIEW 8.5\project\errors\Japanese\SPT-errors.txt

    Hi DanielAllis,
    Like mentioned earlier, there is most likely an application on the internet that you can find and use where you can see what processes are calling specific files or folders to see if that specific file is being used by anything else.  It doesn't sound like this is the root of your problem, but it couldn't hurt to check.  Also, I have seen a similar problem to this with someone who was using the software Subversion and Tortoise with their application.  I am not familiar with this software in particular, but I have attached a link below that goes through the steps that this other person took to try and fix the same error when having this software on their computer.  Let me know if any of this helps!
    http://forums.ni.com/ni/board/message?board.id=170&message.id=172537&query.id=115461#M172537
    Regards
    Noah R
    Applications Engineering
    National Instruments

  • Error 6 occurred during build of compact FieldPoint executable

    I am building my executable for the compact FieldPoint and I received the following build error:
    [ERROR]
    Code:6
    An error occurred while saving the following file:
    C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\Utility\SMTP\smtpeml.llb\SMTP Email Get Case Insensitive Search Pattern.vi
    Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_RTEXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_RTEXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
    <APPEND>
    Method Name: <b>Save:Target Instrument</b>
    <Call Chain>Error 6 occurred at AB_Source_VI.lvclass:Close_Reference.vi -> AB_Build.lvclass:Copy_Files.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_RTEXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_RTEXE.lvclass:Build.vi -> AB_Build.lvclass:Build_from_Wizard.vi -> AB_UI_Frmwk_Build.lvclass:Build.vi -> AB_UI_FRAMEWORK.vi -> AB_Item_OnDoProperties.vi -> AB_Item_OnDoProperties.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  Generic file I/O error.
    =========================
    NI-488:  I/O operation aborted.
    Any ideas what caused this or how to fix it?

    Hi Carol
    I encountered an error similar to this when i was working with CD and SIM, I solved the problem by building the executable from the C: drive concluding that the file reference was too long.
    http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx
    Be sure to also disconnect all type definitions in Application Builder.
    Message Edited by Eric_R on 10-12-2009 03:22 PM
    Thank You
    Eric Reid
    National Instruments
    Motion R&D

  • Error 7 occured at Advapi32.dll-source does not exist.

    I'm using LV 6.02 and W2k Sp2. I'm trying to build an application that worked fine with Sp1. Any idea?
    Andras Ferencz

    Are you trying with the correct path? If your vi is included in a llb, you must know that current path function gives the name of the llb too, and if an executable, current path gives the exe name in the path, so you must handle this.
    Hope this helps

  • 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

  • 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

  • Build Question: error 7 occurred at source does not exist

    I have VIs built in LabVIEW 6.1. It works and built well. In LabVIEW
    7, It works well. But when I try to build it. I got error.
    I first use the mass conpile to compile VIs and then build the exe
    with default settings. I got:
    Error 7 occurred at source does not exist
    Possible reason(s):
    LabVIEW: File not found. The file might have been moved or deleted,
    or the file path might be incorrectly formatted for the operating
    system. For example, use \ as path separators on Windows, : on Mac OS,
    and / on UNIX.
    NI-488: Non-existent board.
    But It does not point out which file does not exist.
    Anyone can help me out?

    Hello yqin,
    Here are some more KnowledgeBases that may pertain to your issue.
    Error 7 When Building Applications and DLLs That Use the LabVIEW Report Generation Toolkit
    Why Do I Get Error 7 When Building an Executable from a Build Script?
    Error 7 at Invoke Node When Building a LabVIEW Executable
    If the above KnowledgeBases do not work, we will want to try the following procedure.
    1. Open your Main VI.
    2. Hold + a
    nd click the run arrow (forces recompile).
    3. Close the VI and mass compile it.
    4. Keep the VI closed and build the application from scratch (do not use a script).
    5. Ensure that all VIs called dynamically are included as support files before building.
    Please let me know if you have any questions,
    Matt
    Keep up to date on the latest PXI news at twitter.com/pxi

  • Error of heads when build the .dll by visual studio 2003

    I am trying to call the dll function in labVIEW which build by visual studio 2003.
    while I compile the basic program in visual studio 2003,the dll will be built successfully,but if I include heads like or in my program, etc.Compiling has the error of ,so the dll can not be built.
    I have trued to look for the solution in NI Discussion Forums,but havent seen the related article about the error of including .
    If someone can answer this for me,that will be a great help,and I'll be so appreciate if anyone get me out
    of the trouble.
    Sean

    I'm a little unclear about your question. What is the exact error that you are receiving and at what point are you receiving it? Is the error occurring when calling the DLL in LabVIEW or is it occurring when building the DLL in Visual Studio? Further clarification about exactly what the problem is and where it is occurring would be a big help!
    Regards,
    E. Sulzer
    Applications Engineer
    National Instruments

  • Error 7 occurred at Open VI Reference with Application Builder

    Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
    "Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

    Dear Sir;
    There are two things that are good to try:
    First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
    Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
    .llb file to compile.
    Regards

  • Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi- Dist Build LLB Image.vi- Dist Build App Image.vi- Build Application.vi

    When trying to build  an application using labview 7.1 and windows XP,  I get the error
    Error 1003 occurred at Open VI Reference in Dist Copy Non-VI Files.vi->Dist Build LLB Image.vi->Dist Build App Image.vi->Build Application.vi
    I've tried the crtl-shift-run as well as  a mass compile and I still get the error.
    Any ideas?
    Thanks,
    Mike

    Hopefully this thread, or this KB article might help.
    It seems like this could come from a lot of things, but there's suggestions in those which might lead you in the right direction
    Message Edited by Day on 09-22-2006 02:07 PM

Maybe you are looking for

  • PI 7.11 - Where can I get the NEW java API's

    Hi, We use PI 7.0 in productive environment, but we plan a release update to PI 7.11. We have several Java Mappings for PI 7.0 with Java 1.4. So we have to upgrade this also to Java 1.5. We are using following SAP Java libs: - aii_map_api.jar - aii_m

  • Issues With iTunes Library On An External Drive

    I'm attempting to use my external iTunes library across both Mac and Windows. My music library has been living on my Mac for awhile, and that's where I'm trying to move everything from. I started off by redirecting my music folder to the external dri

  • Trackpad not working correctly.

    My mac seems to have been taken over. The trackpad is not working properly and is opening up everything on the desktop. I've connected a wireless mouse via bluetooth and it does the same thing. It's almost as if it's possessed. Please help!

  • Failure to recognise internet account

    I have suddenly stopped receiving e-mails on one of my accounts I checked Preferences, but the System fails to recognise that account.  I have checked that the account details and password are corect.  When I tried to reload my account details the sy

  • Google map

    Hello, We are on Oracle Forms 10g. We have a requirement of calling a Custom Map application (Like Google Maps) from Oracle Forms 10g. We want to show the Employee's Hose location in the form when city,street and state is entered. We are using the fo