Distribution problem in labview 2011(Error 11004)

Hi,everyone. I have a problem when i install my build "install". If i include "NI Labview Run-Time Engine 2011" in additional installers, the build files show the error message"
.\Distribution.cpp(2072): InstallerError 11004
Developer Error. Distribution contains invalid dependencies:
1. Product SN1Debug ({4CC67F54-9DD9-4DF2-B9C4-1158C9E9F412}) depends on
product with upgrade code {6AD6C111-233B-4924-A3BF-E4813FE23C7A},
version [11.0.416.0,), language in {}
which is not in the distribution.
Correct the distribution and try again.
<No Debug Message>
"  when i install it. and if i don't include it, the install is OK.
I want my distribution include lv2011 run-time engine, how can i do to deal with this problem?
Labview 7.0, 8.0, 8.6,8.6.1,2011
Attachments:
11.png ‏20 KB

Hi,
please try to download and install the NI Labview Run-Time Engine 2011 on your computer and run the builder again.
http://joule.ni.com/nidu/cds/view/p/id/2534/lang/en
In this folder are the installer saved:
C:\Programme\National Instruments\Shared\ProductCache
Regards,
Michael

Similar Messages

  • Labview 2011 Error code 3

    I am having the same Error code 3 using Labview 2011 student edition.  I tried adding connPaneRecoveryMode=True to the ini file and it did not solve the problem.  Can anyone help me to recover the vi?  It will set me back by days if I have to recreate it.  Your help will be much appreciated! 
    Attachments:
    Analyze_EMG_Data.vi ‏258 KB

    I'm glad it saved you so much work.  It is the first time I attempted to follow the procedures to fix this problem. I used LV2012 and saved it back to LV2011.  I know that when I didn't follow the procedures precisely, it crashed LabVIEW with an FPSane error.
    I mentioned the sequence structures because in general, the stacked sequence is being discouraged as a part of good LabVIEW style.  It hides code, and the sequence locals force you to have wires running in the wrong direction in one or more cases which confuses someone trying to follow the code.  If you have too much code that makes your block diagram too big, that is a time to consider consolidating code into logical functional groups that can be placed into subVI's.

  • Labview 2011 - Textbook

    Hi all,
    I am completely new to Labview and will be using it for one of my projects for university. I am a complete beginner to Labview and been having a look for a good text book and Labview for Everyone seems like a good choice.
    But, it seems like it was based on Labview 8. Given that I will be using Labview 2011, I was wondering if there will be drastic differences between the two? For example would it be as different as Ms Word 2010 is to Ms Word 2003. Basically would be the book still be worth purchasing?
    Would my project supervisor at university, who is farmiliar with Labview 8.5, be able to use Labview 2011 comfortably?

    Yes, a book for LabVIEW 8 is suitable to learn LabVIEW. The changes are small.
    Anyone comfortable with LabVIEW 8.5 will have no problem using LabVIEW 2011.
    LabVIEW Champion . Do more with less code and in less time .

  • Error in invoking the build rule editor, LabView 2011

    Hi all.  I'm having a problem in Project Explorer.  When I right-click on 'Build Specifications' and select New:Application (EXE), I get the following error dialog:
    "There was an error in invoking the build rule editor. Please check the corresponding provider directory to see if any VIs are broken."
    After this appears, no build specification is created.
    I built this application in LabView 2010 on WinXP and was able to compile and run it sucessfully many times over the last few weeks.
    The problem started yesterday when I had a problem with a Ring control. I right-clicked it and selected "Edit items" or "Properties" the cursor blinked for a moment but the dialog box did not appear.  I removed the Ring control and replaced it with a String control, then when I tried to build the application, I got this error message.  At that time, I also noticed that I could not get a Properties dialog box to appear for any controls or indicators.
    Yesterday, I installed NI Developer Suite 2011 Version DS2. This seems to have fixed the problem with the dialog boxes and I was able to use the Ring control. However, I still have the problem with the build rule editor.
    To determine if there was a problem in my program, I built a new 'Hello World' .vi with just a string control and string indicator. This program has the same problem when trying to build to an .exe.
    Currently, I am trying to remove all previous versions of LabView. When that is done, I will reboot and try to build again.  If that doesn't work, I will remove ALL National Instruments software and re-install NI Developer Suite 2011 DS2.
    I'm hoping someone can provide a solution before it comes to that.
    Two other facts which might be relevant:  I don't have Administrator on this machine, although I could probably get it if I could make a strong case. Also, I can't be sure, but I think the problem may have started when I undocked my laptop from the docking station to go to a meeting.
    I appreciate your help.  Thanks in advance.

    If you need additional assistance, I encourage you to create a new thread. It is more likely to be answered by other users as a fresh post.
    The most likely cause is a corrupted file (or files) in the builder directory. 
    I would  recommend renaming/moving the following folders and performing a repair install of LabVIEW: 
    \National Instruments\LabVIEW 2011\vi.lib\AppBuilder 
    \National Instruments\LabVIEW 2011\resource
    Regards,
    AnjelicaW.
    Regards,
    Anjelica W.
    National Instruments
    Applications Engineer

  • Labview 2011 NI Report and error 7

    I know this topic has been cover in this forum many times, but I just can’t get it working.
    Recently, we have updated our labview from 8.2 (Window XP) to 2011 sp1 (Window 7), and of course, NI report stops working.
    In our software, we have a project that eventually gets compile into a DLL (Not AN .EXE, THIS IS NOT AN EXECUTABLE). In this DLL, we modify an excel spread sheet. As a result, we need the NI report tool kit.
    Now I know that you would have to manually include the two folders (NIReport and LVclass)in your project in order for this to work in labview 2011, which I did by following the link below.
    http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument
    I made sure that the two folders were “Always Included”, and not using the labview 8.x file layout. After the compiling has been complete, one DLL was created (with 4 other files, which is good because I only want one DLL). I assumed that the NI report tool kit is included in the build since I selected “Always included”.
    After that I ran my main top level vi. The main top level vi tried to access the DLL, and I got error 7,
    Get LV Class Default Value.vi<APPEND>
    <b>Complete call chain:</b>
         Get LV Class Default Value.vi
         Test.vi
    <b>LabVIEW attempted to load the class at this path:</b>
    C:\BUILD PATH\DLL NAME.dll\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass
    Now I assume this might be caused by two reasons. The path is incorrect or the tool kit wasn’t included.
    I have been working on and off with this problem for weeks and still can’t get it working. I am guessing the path is incorrect, but I have manually changed the path to something different but got no luck. Any suggestions?
    Solved!
    Go to Solution.

    Hi,
    Thanks for the reply. 
    The reason I didn't select "use Labview 8.x file layout" is because it will also create 10 extra support folders (I think this is due to name conflicts in the DLL directory) after compiling the project. This is not an acceptable solution for my customer since no one would want a DLL that comes with so many extra files.
    And yes, I am aware of the file layout after Labview 2009. However, the path to NI_Excel.lvclass (C:\BUILD PATH\DLL NAME.dll\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass) was provided by “Excel class path.vi” (vi.lib\Utility\NIReport.llb\Excel class path.vi). In “excel class path.vi” it checks to see if the application is using the 8.x layout or not.
    I switched to “use Labview 8.x file layout” just for testing reasons but it still doesn’t work. The file path for NI_Excel.lvclass is now C:\BUILD PATH\DLL NAME.dll\Excel\NI_Excel.lvclass (provided by “Excel class path.vi”). I also hard coded the path to C:\BUILD PATH\DLL NAME.dll\NI_Excel.lvclass and that doesn’t work too.
    I have created a simple project to demonstrate my problem. Copy the attached folder to your desktop and you will see a folder named “Excel”. Open the “excel Test” project and build the DLL, check the build path and make sure it’s building to “Desktop\excel\Exceltest”. After that go to the DLL TEST folder (\Desktop\excel\DLL TEST) and run DLL test.vi. Make sure the path to the DLL (on the block diagram) is correct and run the vi. You should see the error I am talking about.
    Thanks,
    Attachments:
    excel.zip ‏19 KB

  • Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

    Hello,
    I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
    When I run my routine, I have this error message:
    Error -1074397038 occurred at IMAQ Start.vi
    Possible reason(s):
    NI-IMAQ:  The requested serial termination string was not found in the returned buffer.
    Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
    I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
    Could you help me to solve this issue please?
    Thanks
    Bests
    David Dulin

    This forum post is already handled --> SR 1154262.
    Kind regards,
    Corné Westeneng
    Applications Engineer
    NI-Netherlands

  • Labview 2011 FPGA Compile Error

    Hi,
    I'm new to FPGA. I want to use Labview 2011 SP1 with the Spartan 3E starter kit from Xilinx (Spartan 3E driver available from NI labview website).
    I'm trying to work my way through the examples that came with the driver. I've run into the same compiler error with a number of the examples. The error is attached.
    Error 7 occurred at Read from Text File in niFpgaCompileWorker_CheckForErrors.vi->niFpgaCompileWorker_JobComplete.vi->niFpgaCompile_Worker.vi:1
    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.
    C:\NIFPGA\compilation\Shift_FPGATarget_Shift_87E8371C\Spartan3EStarter.bld
    I've checked the registry to ensure that the path to the compiler is correct.
    Any assistance would be welcome.
    Regards,
    James.
    Attachments:
    Labview2011_FPGA_CompileError.JPG ‏96 KB

    Hi,
    I don't have any Xilinx tools installed - other than the ones that installed with the Labview FPGA module.
    I have attached the compilation logs and output results from my attempt.
    I have renamed the extension on the following files from .lvtxt to .txt
    BuildResults.txt
    CodeGenerationResults.txt
    Regards,
    James
    Attachments:
    BuildResults.txt ‏5 KB
    XilinxLog.txt ‏42 KB

  • LabVIEW 2011 starts with an error every time on OS X

    I get this error dialog every time I start LabVIEW 2011 on my Mac.
    OS X 10.6.8
    LabVIEW 11.0 Student edition
    +Control system toolbox
    +MathScript RT
    Attachments:
    Screen shot 2012-06-22 at 12.22.02 AM.png ‏37 KB

    It has given this error every time LabVIEW has started up. This is a fresh install and it has done this every time.
    Here is the log file:
    #Date: Fri, Jun 22, 2012 1:01:30 AM
    #OSName: Mac OS X
    10.6.8
    #OSVers: 10.6.8
    #OSBuild: 10K549
    #AppName: LabVIEW.app
    #Version: 11.0
    #AppKind: FDS
    6/22/12 1:01:31.544 AM
    DWarn 0xAFBF5C57: LabVIEW not initializing for Pro, Full or Student Edition. Undefined behavior may result.
    LVLicenses.cpp(485) : DWarn: LabVIEW not initializing for Pro, Full or Student Edition. Undefined behavior may result.
    $Id: //labview/branches/2011/dev/source/licensing/LVLicenses.cpp#9 $
    0x0014D8D3 - __Z13CallErrorInfoPKclS0_17_DebugOutputLevelmS0_ + 49
    0x021DAADB - _DebugOutputCallHandler + 45
    0x021DA958 - __ZNK11DebugStream7ProcessEv + 3E
    0x00B669CF - __ZN11CLVLicenses25CheckNonNILMFunctionalityEv + 3B5
    0x00B66F43 - __ZN11CLVLicensesC1Ev + 41
    0x00B66FB2 - __ZN11CLVLicenses26InitializeLVLicensesGlobalEv + 42
    0x00B6723E - __ZN16LVLicenseService4InitEv + C
    0x00710834 - __Z7InitAppv + BE
    0x0071D2AC - __Z13AppInitializev + 85E
    0x00723C09 - __Z15LVMainEventProcP6WEventl + 1B41
    0x01638D90 - __Z17InternalEventProcP6WEvent + 20
    0x0163FEB6 - _WSendEvent + 27E
    0x00007844 - __Z13InitializeAppl + 54
    0x00007136 - __Z6MGMainlPKPKc + 17E
    0x000074E2 - _CommonMacMain + 1B8
    0x00002C02 - <unknown> + 2B11
    0x00002B29 - <unknown> + 2A38
    0x00000002 - <unknown> + FFFFFF11

  • Error installing LabVIEW 2011 on Win 7

    I'm getting an error installing LabVIEW 2011 Professional:
    I found a thread concerning missing MSIs, which suggested that one run setup.exe with the /log function, so I did, but I don't think it actually says anything useful.
    I also found a Microsoft download page for WindowsInstaller-KB893803-v2-x86.exe, which is the thing that's supposed to be missing. This seems to be an old version of the installer (most recent compatible OS = WinXP SP2), so I don't really feel like installing this on my Windows 7 system.
    Help!! Thanks in advance.
    -- Philip

    Hi Keller,
    I'm Jamie an Applications Engineer at NI UK.
    It does seem that you are missing some of the necessary support files required for the installer to run correctly, the details of which are available in the KnowledgeBase article here. Did you download the install files or are you installing from disk?
    In addition to the setup.exe file, ensure that you have copied the following folders to the target PC or destination folder when creating an installer with LabVIEW.
    bin
    license
    supportfiles
    Hope this helps get you up and running with LabVIEW 2011, let me know if you experience any further issues.
    Thanks
    Jamie
    Jamie S.
    Applications Engineer
    National Instruments

  • Labview 2011 64-bit install problem

    I'm trying to install the 64 bit version of LabView onto a win7 64 laptop. The install seems to go ok. When I try to run it, it crashes with this exception 0xC06D007E$r. I've tried uninstall/reinstall and I still get the same error. I have the 32 bit version of LabView 2011 installed on this machine and it runs fine. What else should I be looking at?
    Thanks
    dp 
    Attachments:
    lvlog.txt ‏2 KB

    To address the point made by smercurio_fc, the Program Files (x86) folder is generally reserved for 32 bit applications. As I understand, Windows uses the distinction purely for organization. Having done more reseach, I will concede that we should look for a different workaround.
    By your responses, it seems you may not need LabVIEW 32 bit. This article discusses the pros and cons of each version. This Q&A may be particularly useful in deciding whether or not you can continue on 64 bit alone.
    Q. Which LabVIEW modules and toolkits are available for LabVIEW 64-bit?
    A. Currently, the NI Vision Module, Application Builder, and Measurement Suite for Fixed WiMAX are available for use in LabVIEW 64-bit. Any other modules and toolkits must be run using LabVIEW 32-bit. See this Developer Zone Tutorial for more information.
    Depending on your applicaion, this could be our solution If you are able to install LabVIEW 64 bit after uninstalling the 32 bit version.
    KyleP
    Applications Engineer
    National Instruments

  • Problem on LabVIEW + Debian 64bits

    Hello,
    I'm trying to install LabVIEW 7.1 on my Debian SID x64, I have all de requirement writen in the Readme.txt and I tryed to install it by INSTALL-norpm . The problem is that I always get :
    #sh INSTALL.norpm labview70-appbuild /usr/local/share/labVIEW/
    Installing labview70-appbuild-7.0-1.i386.rpm into /usr/local/share/labVIEW/...
    /home/esox/labview/rpm2cpio: error while loading shared libraries: libdb.so.2: cannot open shared object file: No such file or directory
    even if :
    #locate libdb.so.2
    /lib/libdb.so.2
    Could you help me?
    Thanks a lot

    it seems to be very very hard to install Oracle 9i on Debian Etch, I found this on the net :
    > Is it possible to install Oracle 9i on Debian etch?
    So far I have had no luck due libraries requirement.
    I appreciate any suggestions.Officially no.
    Unofficially, you should be able to with a loooot of tweaking. The
    secret is in the "compat" libraries. Basically Oracle is a binary
    distribution and relies on gcc296 - not gcc3. You should also get your
    own jdk install. Get 1.1.8 (yep - good old one) and use it to run the
    installer. With Oracle9i there's no gurantee that the jdk in the
    installer will run on your distro. Luckily you can override the jdk with
    your own.
    If anyone knows a simple way to do it, I'd like to know, but I'd rather give up about this idea
    It seems to be to tricky for my poor Linux knowledge

  • How do I troubleshoot installation/distribution of a LabVIEW .exe which processes data using Matlab when it works on some computers but not others?

    I've been given the unenviable task of troubleshooting and installing/distributing software written by a former co-worker. I've modified the LabVIEW code and built an .exe file. I've successfully installed the Labview .exe file on several computers, but it won't work on some others. What's more baffling is that I installed it successfully on one computer, uninstalled it, and tried reinstalling it with no success. In fact, it's a new error (Dr. Watson for Windows NT application error). It doesn't help that I have different versions of LabVIEW and Matlab on the target computers. Some have LabVIEW 5.1, some
    have 5.0, and some don't have it at all. Some have Matlab 5.2, some have 5.3 (R11) and some have 6.0 (R12). It's also not clear to me where the Matlab m files should be located. I'm not sure if it's a LabVIEW Runtime Engine problem, or if it's a Matlab problem. I've also wondered how LabVIEW and Matlab talk to each other. When LabVIEW calls Matlab, it seems that Matlab is running in the background. In other words, clicking on the Matlab Command Window and typing "whos" or any other command/variable doesn't work.

    Jay del Rosario wrote:
    >
    > How do I troubleshoot installation/distribution of a LabVIEW .exe
    > which processes data using Matlab when it works on some computers but
    > not others?
    Poke around zone.ni.com and
    http://digital.natinst.com/public.nsf/$$Search/ .
    Good luck, Mark

  • How to start an 8.2 app in LabVIEW 2011

    This has been a problem that I've been trying to deal with for the past week to no avail. 
    In short:
    The 8.2s which worked on an XP machine were openned on a Windows 8 with LabVIEW 2011, made into an executable, put back on to the Windows XP to see if it will still all worked, and it does not. 
    In detail:
    I had a ready made, working application made in LabVIEW 8.2. The goal is to update all old software to the new LabVIEW 2011, but to still make it work. The problem is, after making it run in edit mode for at least a little bit (after debugging common errors with openning in a newer version), after making an executable and putting it on the machine it used to run on, it won't run. The program will not communicate with the machine and will give the following errors which are, my eyes, things that should not be happening after working in edit mode.
    Two error codes received:
    1)  One or more Configuration File(s) are not available. Please Check the Hardware configuration!
    2) {
        Error 7 occured at Openfile+.vi: Open file
        Possible reason(s):
        LabVIEW: File not found. The file might have been mover 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 Linus. Verify tht the path is correct using the command prompt or file       explorer.
        =========================================
        NI-488: Non-existent board.
    Please, if anyone has had the same or a similar issue and can give any sort of feedback or thoughts, I would greatly appreciate it. Thank you!
    -Hub25

    Bob_Schor wrote:
    There are a number of issues here.  First, LabVIEW 8.2 cannot be installed on Windows 7 (to say nothing of Windows 8), and LabVIEW 2011 cannot be installed on Windows XP.  I'm not sure whether executables can be built across Windows 7/XP boundaries, but I'm pretty sure that, at a minimum, you'd need to install the LabVIEW 2011 Run Time Engine on the Windows XP system (and I don't know if this is possible).
    After next April, Windows XP "turns into a pumpkin" as Microsoft drops support for it.  A good time to migrate to Windows 7!
    You can install LabVIEW 8.2 on a Windows 7 computer.  I have that right now specifically for converting old code.  And I am sure LabVIEW 2011 can go on XP as well.
    I'm guessing the main issue is the lack of the 2011 Run-Time Engine on the XP machine.  But I would also advise moving away from the OpenFile+.vi since that is a really old VI and the newer LabVIEW file I/O primitives are so much better anyways.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Labview 2011 save for previous version crashes

    Hello,
    I am trying to save an existing Labview 2011 project to any previous version. I have tried 2010 all the way down to 8.0. I have a clean project, all files are LV 2011, it builds and runs correctly. I have mass compiled.  It did call 2 dynamic vi's but I have removed those. The project did contain conditional compilation, but that is removed. It did contain disabled diagrams, but they are removed. I did a save hierarchy to a seperate folder, just to make sure the standard save works. It does.  There are 1196 vi's and controls in the project.
    If I save to LV 2010, quite a number of sub vi's are saved (909 including controls), but none of the top level ones. The crash is manifested by Labview leaving memory (task manager doesn't see it any more) and the Labview window dissapearing.
    Attached is the save dialog at the instance before crashing.
    I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
    Has anyone experienced similar problems? If so, any clues on how to fix this?
    Thanks,
    Bart Schroder
    Attachments:
    LV2011 save crash.jpg ‏17 KB

    BartSchroder wrote:
    I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
    In the advanced build configuration, check "generate build log file". See if you get more information. Good luck.
    Quote from the help:
    Generate build log file—Specifies whether to create a log file for the build. The build log file lists all files contained in the build, including subVIs you do not specify as Startup VIs or Always Included. The log file also contains general build information such as build start and end time, the build specification and project name, and any errors that occurred during the build.
    LabVIEW Champion . Do more with less code and in less time .

  • LabVIEW 2011 and the USB-845x

    Hello there,
    I was curious to see if anyone else had the same problem and a resolution to my issue. I have Windows 7 x64 and recently did a clean install of LabVIEW 2011 x64. I have a USB-8451 SPI/I2C card that I am trying to make available to use in LabVIEW. The newest drivers (2.0) say in the readme file that Windows 7 x64 is supported and that LabVIEW 2011 x86 is supported but not x64. I installed and tried it out to no avail. However upon copying and pasting from the Program Files x86 to the Program Files (64-bit) LabVIEW folder, I now have the 845x palette available under the Instrument I/O main palette but everytime I choose one for the block diagram it asks for the location for the ni845x.dll shared library file. The only one I found on the whole system was in C:/Windows/SysWOW64 and I link to that file and now the VI's error out saying the library wasn't found/loaded and am just stuck now. Any help would be greatly appreciated.
    Thanks

    The issue has to do with being able to (or rather not being able to) load 32-bit DLLs into a 64-bit process. While the driver readme says that it's compatible for both Windows 7 32-bit and 64-bit, that's not the same thing as saying the DLL is 64-bit. And in order to be able to use it from LabVIEW 64-bit you need a 64-bit DLL. This is an operating system limitation, not a LabVIEW one. Thus, you have to use LabVIEW 32-bit. Your license allows you to install both 32-bit and 64-bit, so unless you have a specific reason to use 64-bit LabVIEW (like you're trying to manage gobs of memory), stick with 32-bit LabVIEW for now.

Maybe you are looking for