Build Specifications gone with LabVIEW 2009

I'm using LabVIEW 2009 and I still have the same problem as described in the following post (where all the answers were for older LabVIEW versions):
http://forums.ni.com/t5/LabVIEW/build-specifications-gone/m-p/625815
When I move a LabVIEW project from one PC to another, parts of the build specifications are gone. In the specification for the executable I have to redefine the start-up VI, the included files and the icon.
Is this a known issue and is there a fix for it?

Hello,
this might be a corrupt project file. Does this only happen with this project?
If so, then I'd suggest recreating the project and the build specifications on the original PC and trying to migrate it again to the other PC.
Regards,
Joseph Tagg

Similar Messages

  • Can i build an application with Labview 2009 for Windows 7?

    Hello
    i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
    Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
    Solved!
    Go to Solution.

    Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
    I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application.  After installation I had to move the files from 1 location to the other to make it work.

  • Is it possible to build a project with Labview 2010 on a Windows XP system, that is useful for a system with windows 7 on it?

    Hi there,
    I am planning to use Labview 2010 in a short time.
    But before I'm going to use it I have some questions.
    I know it is possible to run Labview 2010 in an XP environment. But is it also possible to, when running Labview 2010 on a XP system, to build a project to a version that is useful in a Windows 7 environment?
    Or do I have to run Labview 2010, when I want to build a project that is useful on a Windows 7 system, on a system with Windows 7?
    Please give me some information.
    I hope to hear from one of you soon.
    Regards,
    Kenny
    Solved!
    Go to Solution.

    Is it possible to build a project with Labview 2009 on a Windows XP system, that is useful for a system with windows 7 on it?
    Thanks.
    Philippe B.
    Certified Associate Developer / Dépt Moyens d'essais
    www.ingenia-system.com

  • IS APPLICATION BUILDER 6 COMBATIBILE WITH LABVIEW 7 ?

    IS APPLICATION BUILDER 6 COMBATIBILE WITH LABVIEW 7 ?

    No it's not but it is a free upgrade last time I checked. Go here and click on the Upgrade Advisor link. You will need the serial number of your current app builder.
    p.s. LabVIEW 7.1 was released today so you might want to skip 7 and go straight to the latest.

  • Error when trying to set up OPC I/O server with LabView 2009

    Hi.I get an error when I try to set up OPC I/O server with LabView 2009 and the DSC module. If I open an empty project, right click ”My Computer”. Select new / I/O Server… and then OPC Client, the following error appears: Unable to browse OPC Server from the selected machine.Error -2147467262 occurred at GetOPCServerList.viPossible reason(s):LabVIEW: (Hex 0x80004002) No such interface supported.  I have tried to repair LabView, but with no luck. Any idea what it could be?

    The problems are not related to each otherOk then. Lets try getting this solved. Lemme dig......

  • Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

    We have discovered an issue with the above listed software.  Specifically this pertains to Print Report.vi in the Report Gen palette.  Basically, we have discovered that with Office 2003 installed the VI will error out.  We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft).  With Office 2007 we don't have a problem.  We've tried building the examples into executables, and those work because they are printing HTML reports.
    Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly.  Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

    yeah, we had seen that, and been told about it by another user.  we tried, to no avail.  we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

  • Error: "not enough memory to complete this operation" when building EXE + LLB in LabVIEW 2009

    Just upgraded to LabVIEW 2009 last week and can't build anymore.
    I am building and EXE with support files in LLB.
    PC Specs:
    -P4 3GHz
      -4GB RAM
    -Windows XP PRO SP2 
    - Windows is already enabled to use up to 3GB of virtual memory for applications. 
    - Performed a mass compile on all vi's.
    Not sure what else to try and will appreciate any suggestions.
    Thanks,
    Tavi. 

    This issue as well as a few others have been fixed in the LabVIEW 2009 f2 patch that was released today.  For more information, check out the following Knowledgebase for the list of resolved issues as well as download instructions.
    David_L | Certified LabVIEW Architect
    LabVIEW Tools Network | LabVIEW Tools Network Developer Center

  • Building a dll with labview for CVI

    Hi,
    I am making some abstract hardware layers for some instruments and i use to work with Labwindows CVI. But i have found ONE instrument, the Instek pst3201 alimentation which is ONLY created with Labview.
    So i downloaded the 8.6 LV demo and builded the llb projet in order to obtain some .dll, .h and .lib files and included it to a CVI project in order to construct an intermediate Dll level.
    Everything builds fine, like usually when i use an IVI driver but my problem is that when i try to call this intermediate Dll level with my abstact hardware layer using LoadLibrary, nothing is returned like if the DLL doesn't exist.
    So my question is : Do you think that this is a problem from CVI (and i repeat that i have made a lot of others abstract hardware layers using IVi drivers except that this time i haven't got any .fp or .c but  a .h and i include the .lib to the project), or a problem from Labview and i should use the LV Application builder if it's different ?

    Hi,
    It's seems that you have no exported function. What function do you have in your header file? did you tryed to create a really simple dll (doing an addition for example ) in LabVIEW only to verify that you are correctly creating the dll?
    Manuel R
    AE dans une autre vie

  • Build specifications gone

    LV 8.5 on XP Pro
    I have a project with the build specifications for an executable.  The problem is that the startup VI's that are designated in the properties keep coming up missing.  The ICON is still in the project, but when I go into the "source files" they do not seem to save.  The problem is intermittent.  I have tried entering the properties, saving and then closing and reopening LV and had no problems but then the next time I go to do a build I receive error "You did not specify any Startup VI's." 
    Also the installer properties continually are corrupted and I have to re-create the installer.
    Any suggestions?
    ~gold 

    Hey Gold,
    Thank you for contacting National Instruments.  I'm not exactly sure if I understand your problem, so I do want to clarify what you have going on.
    If I understand you correctly, you have a project with VI, documentation, etc, to create an exe as well as an installer.  All files appear in the project explorer, and there does not appear to be any problems with the files there.  When you go to build an exe, you select your startup VIs, and move them into the Startup VI's section of the build page.  When you go to click build, you get an error that you have not selected any startup VI's.  Is this correct? Are there any details you would like to add to that?
    Also, can you please explain what you mean when you say the installer seems to be corrupted?  Can you give any error messages, or a better description of what is going on?
    Thanks,
    Kevin H
    National Instruments
    WSN/Wireless DAQ Product Support Engineer

  • How to build demo versions with Labview ?

    Hello,
    is it possible to design Labview applications in a kind,
    that it is possible to generate "demo versions" of it ? Demo version in the means of feature-limited crippled versions of a full instrumentation software, where SOME hardware access is denied, but you can load and view and analyse data.
    Of course it might be useful to compile this demo version with the Labview Application Builder,
    What might be the business modell for demo versions:
    A hardware manufacturer creates a Labview application which controls the manufacturer's components, and allows instrumentation and data recording. The application is not free but sold for extra money.
    As pre-sales benifit, the manufacturer would like to send the (compiled) Labview application to future customers.
    Now the problem is, that the customer has not (all) the external devices or PCI/USB devices,
    on the other hand the hardware manufacturer does not want to give the "full application" as gilft to the customers.
    Now with traditional software development with C++, Java, C#,
    either a demo version is gained from the full version by replacing some module with hardware access by modules wth "empty" function body or with function body which return constant values instead of accessing the hardware.
    In the world of process industry, usual process control systems may supply "alternative" values if the original device is not available.
    What kind of software structure must I build with Labview, to do the same ?
    Now the problem with Labview applications is
    Labview applications depend on drivers. Drivers depend on hardware.
    So if the FULL commercial version of the Labview program accesses a DAQmx driver, GPIB driver or any other hardware driver by a VI,
    and often this means that a special manufacturer VI is used in the Labview program which does the actual hardware access,
    how to modify the software to make a demo version
    a) so that IF the customer buys the hardware and gets the hardware driver, he still does not have the full version
    b) so if the customer neither has the hardware nor the driver, he still can run the Labview software and load an view data, push buttons, can execute menu items even can manipulate data ect, can use the manufacturer's VI
    Unfortunately, it is no solution just to delete "some" of the VIs with hardware access from the distribution of the demo version, as this just causes error messages during the loading of the (compiled) Labview demo application.
    Message Edited by hemmerling on 01-11-2007 12:35 AM
    Message Edited by hemmerling on 01-11-2007 12:37 AM

    Thanks alot.
    Conditional Disable and Diagram Disable Structures
    http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/cond_diagram_disable/
    are indeed at least a part of what I wanted.
    Anyhow, as such "suspended" VIs are often the *source* of signals,
    so there must be an addtional method how to provide "alternative" signals for the demo version,
    which does not make the administration / further development the full version  too complicated...
    For example: The VI for an external signal generator device is disabled, but alternatively it would be nice if the users of the demo version can get a fixed sinus signal instead...
    How to do that with Labview and the "Conditional Disable and Diagram Disable Struktures",
    and can I test this all even without Labview Application Builder, in the full development system ( so that I don´t need the compiler for frequent checking ) ?
    Btw, with what version was this "Conditional Disable and Diagramm Disable" feature introduced ? Is ist already available with Labview 7.0, /.1 ?
    Sincerely
    Rolf

  • Font size on Windows 7 with LabVIEW 2009

    Hello,
    after installing labview 2009 on windows7, I have a problem with the font size of my old application written in 8.6.
    the Application Font has seemed to default to another style under windows7 so I searched the forum for the default font under XP when I used lv 8.6. Tahoma 13pt seemed to the correct choice, however when i changed all default fonts to Tahoma 13pt it helped and they look very similar, but the Tahoma under windows7 is slightly longer that the original and it looks like there is some sort of font smoothing going on... perhaps windows is doing its "cleartype" thing by default and influencing its length (thou i thought this shouldnt be the case).
    This small difference is causing havoc in my GUI as objects are being resized in a bad way.
    Please see the screenshot for an example of my concerns
    Another question on the side... is there a Font I can use that will keep the appearance and size over all OSs?
    Any help would be appreciated...
    Best Regards
    Alex.
    :. LV2010 SP1 ... W7 .:
    Attachments:
    Font Difference.png ‏3 KB

    Actually this problem affect LabVIEW itself even while editing!
    Many of NI's screens suffer from the same problem. Configuring events is one of the most obvious cases. Since teh edit events screen does not allow for resizing, there are some events that you can only guess what they are.
    I tried reporting this but the AE wanted me to spoon feed screen shots and ....
    I think what really irks me over this problem is that I purchased a laptop with the biggest screen available just to let me do LV and in the end LV can't handle the laptop.
    Double -  
    Ben
    Message Edited by Ben on 05-06-2010 10:13 AM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • NI Goop Wizard not working with LabVIEW 2009

    I have added the NI Goop Wizard using VIPM (VI Package Manager) into my LabVIEW 2009 SP1 installation however it is not working. Whenever I select Create New Class from the drop down (same applies to menu selection) nothing happens and the drop down returns to it's default selection. I have tried this on 2 PC's both with 2009 SP1 installed, both exhibit the same unwanted behaviour. One of the PC's also has LabVIEW 8.2.1 installed also with NI GOOP Wizard and this installation works fine.
    Anybody using GOOP Wizard with 2009 ?
    Cheers
    Chris
    Don't forget to give Kudo's for a good answer !
    LabVIEW Champion
    Certified LabVIEW Architect
    Certified TestStand Architect

    Hi there Chris,
    Off the top of my head it's my understanding that NI GOOP wizard is legacy software that was made redundant by the native GOOP tools in LabVIEW 8.2.0 and later.
    In light of this it's a bit confusing that everything is working fine with 8.2.1 for you. Is there a version to the NI GOOP Wizard that you are using?
    I had a search across the website but I'm afraid I haven't found any other examples or poeple using the GOOP Wizard in LabVIEW 2009 or 2010.
    Kind Regards.
    Rhys
    Applications Engineer
    National Instruments

  • Interfacin​g Siemens Desigo PXC Building Automation controller with LabVIEW

    Hello everyone,
    I am currently trying to interface Siemens building Automation controller Desigo PXC100-E.D http://www.buildingtechnologies.siemens.com/bt/glo​bal/en/buildingautomation-hvac/building-automation​...
    with LabVIEW using OPC servers. I had once interfaced the S7-300 PLC of Siemens with simatic step-7 software with LabVIEW but in this case I don't which driver should I select and don't know is it possible or not. If any one of you have similar sort of expierence please I need advice..
    Thanks
    Naqqash.
    Naqqash

    Hi,
    As you have described I've done the whole configuration. I am using MatrikonOPC for BACnet and as I've checked my device and the software are working properly. Now what I am trying to is that I am connecting the BACnet OPC server with LabVIEW so that the MatrikonOPC act as a connection layer between my device and LabVIEW. So that I will be able to change values directly from my LV vi. Now when I connect that Bacnet OPC with LabVIEW using the same procedure for PLC it gets connected because it is showing all the tags from the device. But after doing the whole procedure which is the same according to the tutorial 'connecting LV to any PLC using OPC' when I deploy the variables I am getting some error. I am attaching the screenshot of the error. Please let me know if I am doing any thing wrong.
    PS: I am using a virtual machine and I've tried the whole thing with the NI OPC servers as well according to the tutorial but still when i deploy variables I am getting this error.
    Naqqash
    Attachments:
    OPC_error.JPG ‏22 KB

  • SourceGear Vault with LabVIEW 2009 gives error

    Hi,
    I try to evaluate SourceGear Vault for version control in LabVIEW 2009.
    At their website they say that Vault is compatible with Microsoft SCC interface, but as soon as I select  "SourceGear Vault Classic Client" as provider in LabVIEW I get the error "Error -2924 occurred at prefPage_Source Control.vi".
    Does anyone successfully use Vault with LabVIEW?
    Any ideas of things I might need to do to get i to work?

    The text of the error is "An error occurred while opening a source control project or accessing a file.
    The specified path is invalid." Some providers are expecting certain values in parameter calls based on assumptions on how they will be used by various IDEs (mainly Visual Studio). It is possible that valid information passed by LabVIEW to SourceGear's provider does not match what they expect. This would require testing on both LabVIEW's and SourceGear's side to determine what is going on. It would probably be a good idea to start with SourceGear's support to see if they can identify what is invalid.
    George M
    National Instruments

  • Build applicatio​n with LabView 8.2 Prof

    Hello,
    in the past (V 6.1) it was possible to build LabView application with a complete setup routine, not only *.exe. In Version 8.2 I dont find these option. Anybody knows where to find it?
    Best regards
    Robert

    I think that what you want it's to create an installer. See the steps on the attach picture.
    Software developer
    www.mcm-electronics.com
    PS: Don't forget to rate a good anwser ; )
    Currently using Labview 2011
    PORTUGAL
    Attachments:
    teste.png ‏333 KB

Maybe you are looking for