Labview Installer - WD-Monitor 3.5

Hi,
I have a problem when I'm trying to generate an installer for my labview (2011) application. When I'm trying to include the NI-Visa Rutime 4.3 I'm asked for the WD-Monitor 3.5 and should add the "media" for it ? Where can I find this "tool" in order to include the NI-Visa-Runtime into my installer ?

WD-Monitor is not NI software. It seems to be software made by Weller (http://www.weller.eu/new/content/downloads.php?pgid=2). I have no idea how it got involved with the NI installer. Sounds like a corruption in your MSI database. I'd suggest uninstalling WD-Monitor and then running a repair on your NI software.

Similar Messages

  • How can I create more than one program shortcuts in LabView Installer?

    I have builded 3 executable files in LabView Application Builder. I want to create an installer (using the same application builder) that can copy the 3 files to the same destiny directory, install the Runtime Engine and create (in the same program group) 3 shortcuts for the executables. Is it possible with LabView Installer?

    The Application Builder does not offer this option. It is really intended as a basic installer builder. However, you can use other software packages to enhance your isntaller. There are many third party installer builders that you can use to modify the msi file which the application builder create for you. You might want to check one of those out and use it for your application.
    J.R. Allen

  • I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

    I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
    Solved!
    Go to Solution.

     Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
     Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
     You can find more details about this issue in this KB:
    KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
    And for keeping a copy here is more info:
     How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
    Best Regards
    Benjamin C
    Senior Systems Engineer // CLA // CLED // CTD

  • Launching unrelated app, launches LabVIEW installer.

    I'm having a the same problem that this guy is having. The application we're trying to launch is ietm52.exe  the LabVIEW installer starts and attempts to install 7.0 files when the installation is 7.1.1.
    What is causing an entirely different unrelated program to launch LabVIEW's installer? How do we make that stop? is there a patch or something?
    [quote]Okay, so I'm a desktop tech, know little about LabView, but can at least install it.  We also use pdfcreator on our desktops.  For some reason, however, whenever pdfcreator is used (for ANYTHING, not just LabView stuff), a windows installer fire
    s up, "please wait while windows configures NI LabVIEW Run-Time Engine 7.0."  The installer proceeds, then gets stuck while trying to find the msi.  Well I don't HAVE the proper MSI apparently, because my version is 7.1.1!  When I put in th
    e 7.1.1 Run-Time CD (the only one I have) and point it to the msi it seems to be looking for, it still fails (apparently due to different versions).
    So first, why is pdfcreator invoking this installer in the first place (they seem to have nothing to do with each other!)
    Second, why is the installer looking for the Run-Time for 7.0, instead of 7.1.1?[/quote]

    We did some research on this issue and found that VB6.0 common dialog box is what is causing LabVIEW to launch it's installer.
    If a blank form was created with a common dialog box on it and run on the effected box, LabVIEW would would immediately launch it's runtime engine installer. The application we were trying to launch utilizes the common dialog box several times (as do many programs).
    We then replaced version 7.1.1 with version 8 (which shows itself as version 7.0 in it's installer) and it resolved the issue.
    I hope this is helpful to others who may have the same problem.

  • Labview installer input commands

    I am building a labview applaiction that is part of an entire tool suite which has a master installer.  The master installer installs all the programs one at a time from a main interface that takes things like target directory inputs and passes tehm down to the individual tool installers. 
    Is there a way to pass dir information to a labview installer setup.exe file when called from another top level installer?

    http://digital.ni.com/public.nsf/allkb/DE2BAD19D4A9124C862573B400808EC6
    Especially look at the png attached at the bottom of the page
    Or here
    Jeff

  • LabVIEW Installer is not writing to the registry

    I have a LabVIEW installer with the following Registry page in it and it does not write the values I have requested to the registry on Windows Server 2008 R2.  Any clues that anyone can give me to assist.
    Note:  The [INSTALLDIR] variable is a valid command.

    Hi Cbauer,
    You didn't mention which bitness of LabVIEW 2009 you were using, but I'd guess 32-bit?  If so, just a sanity check that you are looking at the 32-bit registry location on Server 2008 R2? 
    Assuming you're using 32-bit LabVIEW, then it is going to create a 32-bit installer. The 32-bit installer can only write to the 32-bit registry. So though you are writing to HKLM\Software\Summitek (which is a 64-bit registry location), Windows redirects the key creation to HKLM\Software\Wow6432Node\Summitek (which is the 32-bit location). Look at that location to see if your key is there.
    This isn't actually a problem, as if your 32-bit LabVIEW application tries to open HKLM\Software\Summitek - it too will be automatically redirected to the "Wow6432Node" location. So in short, because of Window's automatic redirection, it's something you don't usually need to worry about.
    Regards,
    - Wes

  • Tiger Installation Problems, Monitor Doesn't Have Picture

    *Originally Posted in Tiger Support Discussions but no response.*
    Hi every1,
    I'm having problems as well trying to install Tiger on my power mac G3. I did the software exchange thing where I got CD's in place of the DVD. During installation,I restart the computer w/ the CD in drive, the computer starts but my monitor doesn't come on.
    I've been looking through the discussions and no 1 is having the same problem i'm having. I downloaded the firmware but when I go 2 install it, A message says the firmware is the latest and doesn't need 2 be upgraded. Could it be a problem w/my Viewsonic LCD VE701b Monitor. Do I need 2 upgrade the video card or is there some other problem?
    Power Mac G3 350mhz
    1gb Ram (PNY Technologies)
    Tempo ATA 133 PCI Card
    Western Digital80gb hard drive, 4 partitions
    currently using Mac OS 9.2.2 on main HD (8gb, 6.40gbs remaining)
    Partition I want 2 install Tiger is 23.30gb
    Any info will be helpful.
    Thanks every1,
    Andrea
    Pt. 2
    Hey every1,
    I see U are stumped as well but anyway, I've been doing research and here's what I did.
    1. I reset the PRAM, Nothing.
    2. I reset the PMU, Still Nothing.
    3. Emailed Tech Support at ViewSonic, (Awaiting a response).
    Anybody have any other suggestions? Could it be corrupt CD?
    Thanks,
    Andrea

    Take a look at this thread for useful stuff about the Oxford chipset:
    http://forums.macosxhints.com/archive/index.php/t-55470.html
    Your computer cannot give you USB2, and USB1 is very very slow, useless for tasks like backing up that involve transfers of large chunks of data. With what is built in on a B&W, your only choice is FW.
    The Oxford chipset is not the only one that works, but we know it does and those enclosures give you both stability and the ability to boot from the external drive.
    p.s. I responded to this earlier this morning. Are posts getting lost?

  • LabView installer problem : undetected CRIO in MAX

    Hello,
    I'm working on a data acquisition project in LabView 2010 SP1 composed by a LabView Host program (XP SP3 PC) and a CRIO acquisition module. They communicate together through Shared Variables and Network Streaming.
    I made an installer of my Host project composed by: runtime 2010 SP1, MAX, NI-RIO 3.6.0 driver and Microsoft Silverlight .
    I created this installer on my Dev PC and installed it to a Client PC (see the joint image). The whole program works on the Client PC and the data exchange (Shared Variables and Network Streaming) is OK.
    The problem is that the CRIO is not detected by MAX in Remote Devices. On the other hand, when I use the NI Network Browser, it works well (it detects the CRIO).
    The other problem is that, even if I have installed the NI-RIO 3.6.0 driver, the RIO Device Setup is not present on the Client PC.
    If I install all the standard drivers from the NI device Drivers DVD, it installs everything and then the CRIO is well detected and the RIO Device Setup is also installed.
    My conclusion is that I haven't included all the necessary packages in my installer.
    What are the necessary components to install in order to have:
    the CRIO fully detected
    the RIO device setup installed
    Must I also install some DAQmx components ?
    Thanks in advance for your help.
    Attachments:
    Ni-programs.jpg ‏87 KB

    There is a difference between a network and subnet. I have a similiar problem where I can see the device but can not configure it. You can tell if you are on the same subnet by retireving the ip address for the client and get the subnet mask of the client machine. The example is the following:
    client machine ip address 192.168.20.37 subnet mask 255.255.255.0
    CRIO machine 192.168.22.15
    They are not on the same subnet. If subnet is 255.255.0.0 it is on the same subnet.

  • How to install an entire directory structure and files with the LabVIEW installer

    I think I may be missing something on how to do this - preserve a file directory structure in the LabVIEW build process.
    Is there an easy way to distribute an entire directory structure (multiple directory levels/text files) and have the LabVIEW build process properly preserve and install them?   I included a directory in my build specification but it completely flattened the file structure and then so when the installer builds it, the resulting structure in the /data directory is flattened as well.    I'd prefer not to go through each file (~100) and setup a specific target location.   Is there an easy way to preserve the file structure in the build process/installer process that I am missing (maybe a check box that I didn't see or an option setting somewhere)?
    -DC

    Hi DC
    Sorry for the delay in responding to your question.
    You should be able to do this using a 'Source Distribution' as described below:
     - Right click on 'Build Specifications' and select 'New' - 'Source Distribution'
     - Provide a name
     - Add your files to 'Always included' under 'Source Files'
     - Under 'Destinations' select 'Preserve disk hierarchy' and ensure that 'Directory' is selected as the 'Destination type'
    When building an installer your can then choose to include your source distribution and it will be installed to a location of your choosing.
    Hope this helps.
    Kind Regards
    Chris | Applications Engineer NIUK

  • Running a labview installer without installing drivers

    Ouch. I have to install multiple LabView programs onto the same machine and they were all compiled with different versions. I don't have the luxury of rebuilding them. When I try installing some of them, the program won't let me install because newer drivers are already installed on the machine. Is there a way of running an installer to install the program without installing the drivers?
    Solved!
    Go to Solution.

    The folder where the installer was placed into should have a bunch of folder in the "bin" folder all starting with "p". These contain the various installers that are run. The actual installer for your executable should be in there somewhere, so you could try running it directly.

  • Labview installation - not compatible directory

    I have problem with installing LabVIEW 2014 64bit on my Windows 8.1 Proffesional 64 bit machine.
    Story:
    I downloaded LabVIEW 2014 and installed it only to find out its 32bit version. I wandted 64bit version so when i found it i downloaded it. Then i used windows control panel and add and remove features to uninstall LabView 2014 32bit (when i clicked LabView in add/remove features a window opened where i could select, fix/remove and something else, i picked remove and then selected all parts of LabView). After that i was asked to reboot my computer. I did it.
    Then i wanted to install LabVIEW 2014 64bit in same directory where i had previous version installed (which is now completley empty). But when i chose it during instalation it tells me:
    "An incompatible product is already installed in that directory, please select other directory"
    How is there supposed to be anything installed there if i removed everything? The folder is empty.
    I understand something like that happend IF I would remove files manually but NO. I used OFFICIAL uninstaller, i didnt do anything on my own. Yet it "remembers" old installation and wont let me install other version.

    Under Windows 64 bit 64 bit applications get installed into C:/Program Files/<Company>/etc but 32 bit applications get installed into  C:/Program Files (x86)/<Company>/etc.
    Windows will prevent you to install a 64 bit application into C:/Program Files (x86) so that is probably where your problem comes from.
    As to the other problem the most easy solution might be to install some virtualization software like VirtualBox and install Windows in there and then LabVIEW. That gives you a system where you can run LabVIEW until your current system is fixed.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Labview Installer Problems

    Hi,
    I have been using Labview 8.2.1 Professional for years developing customer user interfaces. I have started to receive several field incidents of installer failures. Some of the error encountered include:
    - "Fatal Error!! Required MSI property PersonalFolder is an invalid location "R:\"
    - Error 1335.  The cabinet file 'MDFSupport1.cab'
    required for this installation is corrupt and cannot be used. I can use the exact same installer on a local machine here.
    - The NI-ORB 1.6.0f0 installation has failed with the following error.  The
    installation package could not be opened.
    - The NI MDF Support installation has failed with the following error.  Internal
    Error 2350.
    Up until today, I have not had any issues with installations. I was able to recreate the first error with a test machine. The test machine had a mapped but disconnected R: drive. If I boot the machine up without any mapped drives it installed.
    I guess what I'm really asking is is there a more reliable installer builder available in the newer releases? Am I getting these errors because of my older version of Labview? I have stuck with this version because it works with all of my application and I'm a little tentative to upgrade to a newer version that may introduce other issues (my last upgrade from 7.1 to 8.2 killed a lot of my applications). I really need a reliable installer that takes zero input from the users as they are typically not computer literate.
    Thanks in advance for your help,
    John.

    Thanks for your help muks. I will send your suggestions out to my guys in the field. If I upgrade from 8.2.1 to the latest labview release, will either of these issues be addressed?

  • Labview Installer won't run on target PC

    Hi,
    I just created a Labview app and made an installer build, but once I try to install it on the target PC, I get an error saying that I must install Labview on the PC first.  The instructions for Labview (and the book I have) are very vague about saving, creating builds, and installers.  I thought that the installer includes the run-time engine with the installer, so a full version of Labview isn't needed on the target PC.  I even tried installing the run-time engine by itself beforehand, but it still won't work.  Can someone clear this up for me, please?  I'm very new to Labview, and programming in general.  Thanks!
    Todd Munsell
    Turbine Engine Test Technician/IT Tech
    Wood Group Pratt & Whitney Industrial Turbine Services, LLC
    Plattsburgh, NY

    You shouldn't have to include the VI for an exe distribution in the installer.
    In the Installer creation, there's a option to have the Development Environment needed to install, perhaps you have (accidently) activated that setting?
    Good Luck,
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • Error 1722 in Windows 7 LabVIEW Installation Application Deployment

    Hi,
    I am using Application Builder in version 8.5 of LabVIEW to deploy my stand-alone executable. I've never had an issue on Windows XP, and have had many successful installation on Windows 7. However now I have a customer who gets the following error in Windows 7 (but the same installation package works fine for him on XP machines):
    Currently Installing NI-DIM 1.7.0f0, Part 10 of 19 with Error 1722.
    Error 1722.  There is a problem with this windows installer package.  A program run as part of the setup did not finish as expected.  Contact your support personnel or package vendor.  Contiunue Y or N.
    Anyone (NI application engineers in particular) have any ideas? (My support contract has expired. I think there is a way to report bugs, but is there a way to contact NI support directly in addition to this forum?)
    Thanks for any help.
    Ed
    Solved!
    Go to Solution.

    UPDATE:
    Good news! My customer got back to me and told me it was his anti-virus software (Trend Micro) that caused the error. When he disabled it as I suggested (which I got from a NI knowledge base article on "Error 1722"), the installation was successful.
    Thanks all 'till next time...
    Ed

  • LabVIEW installer issue

    Hi all
    I have created a installer in labview(). When I tested in labview installed PC. It is working fine. But when I try it in a fresh PC. I have created installer by adding runtime, max and ni visa toolkit.
    when i try to run that exe, it showing error "the program can't start because cvirte.dll is missing from your computer. Try reinstalling the program to fix this problem."
    when I searched it in ni website, it is showing labwindow/CVI. Which I didn't used in this application.
    Please suggest to resolve this problem
    phani srikanth
    Solved!
    Go to Solution.

    Are you absolutely sure the CVI runtime engine is not used by any components of your program? That may be some libraries you use, while I would say such situation is more typical for TestStand, not for LabVIEW. Try to include cvi runtime in your installer and see what will happen.
    Sergey Kolbunov
    CLA, CTD

Maybe you are looking for