Application Builder are corrupted 4.1.1

Hi am having quite a few issues with users on Chrome AND IE has problem as well
I even had an issue.. this is an example
http://imgur.com/M3rjh6p
http://imgur.com/hTtZINd
Drop-downs seem to have text from other dropdowns?
Anyone have this issue?
maybe related to
APEX 4.1.1 patchset bug?
Not sure if its Chrome update.. or a recent patch to oracle database we did?
Dean
Edited by: Postie on Apr 26, 2013 12:35 PM
Edited by: Postie on Apr 26, 2013 4:22 PM

The NI ftp site contains a Application builder update for 4.0:
ftp://ftp.ni.com/support/labview/updates/windows/appbuild/lv4abud.zip with files dated 3-20-1996 (inside zip file).
From the README:
- File Descriptions -
lv4abud.zip:
LabVIEW Application Builder 4.0 update for LabVIEW 4.0
Windows 3.x/95/NT versions only
Disk 1 of 1
Copyright 1996 National Instruments Corporation
All rights reserved
Sorry, 4.0 is too old for me to remember much about such details, but I would just try to download and install this.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • Application files are corrupted. How do I reinstall application files?

    I own the macbook Pro. My application files are corrupted. How do I reinstall them?

    "Any more ideas?"
    The point of my reply was for you to apply the 10.3.9 Combo Update over your installation. Repairing Permissions is always a good idea before and after any update or upgrade. Did you try this and still having Java problems/errors?
    This will not harm anything to apply the Combo update over your OS.
    You did not post which version of 10.3 you are using but you may wish to check to see if this Apple Knowledge Base article applies to your situation:
    http://support.apple.com/kb/TS1537
    littleshoulders
    Message was edited by: littleshoulders

  • I am receiving a message that "your application files are corrupted!

    I am receiving the following message "Your application files are corrupted! For security reasons please reinstall the application"
    What application is it?  I cannot get further information.

    This message is coming from what source?

  • Your application files are corrupted!

    I recently purchased a new MacBook Pro.  I also have a three year old MacBook Pro that the new one is replacing.  When the new one was removed from the box, it was running fine.  It also asked me some questions concerning it being a replacement, so I said 'sure' and it wanted me to run the Migration Assistant.  So I ran the Migration Assistant for the next four hours.
    When it was completed, it said everything was copied successfully.  Now, whenever I log onto the new MacBook, I receive the following error message:
    "Your application files are corrupted!  For security reasons please reinstall the application."  Then there is an OK button.
    I have tried reinstalling the application files (I think).  Also, it only happens when I logon.  So, I made a new account thinking the account may be the problem, but the new account shows the same error message.  I tried holding down the Shift key until the progress bar appeared, but still no luck.
    The old MacBook ran, or still runs fine and error free.  What is my next step?
    Thank you.

    Recovery Mode and reinstall.
    Or erase and reinstall.
    You are not on a MacBook Pro forum.
    MacBook Series Forums
    https://discussions.apple.com/community/notebooks?view=discussions
    http://www.apple.com/support/macbookpro
    Mac OS X Forum
    https://discussions.apple.com/community/mac_os?view=discussions
    Install or Reinstall Mavericks or Mountain Lion from Scratch
    Be sure you backup your files to an external drive or second internal drive because
    the following procedure will remove everything from the hard drive.
    OS X Mavericks- Erase and reinstall OS X
    OS X Mountain Lion- Erase and reinstall OS X
    OS X Lion- Erase and reinstall Mac OS X
    About TimeMachine backups and Recovery Mode
    http://support.apple.com/kb/HT1427
    http://www.apple.com/osx/recovery/
    OS X Lion and later let you:
    Start from OS X Recovery using your Time Machine backup disk. With OS X v10.7.3 and later, Time Machine backs up the Recovery System on your Mac to your backup drive as well. This lets you use your Time Machine drive to start up your Mac if needed.
    OS X Recovery:
    http://support.apple.com/kb/ht4718
    OS X Internet Recovery
    Mac models introduced after public availability of OS X Lion include the ability to start up directly from an Internet-based version of the OS X Recovery system. OS X automatically uses this feature when the Recovery System on the hard disk isn't available (such as when your hard disk encounters an issue, or when your hard disk has been replaced or erased). OS X Internet Recovery lets you start your Mac directly from Apple's servers. Starting up from this system performs a quick test of your memory and hard drive to check for hardware issues.
    OS X Internet Recovery presents a limited interface at first, with only the ability to select your preferred Wi-Fi network and, if needed, entering a passphrase. Next, OS X Internet Recovery downloads and starts from a Recovery System image. From there, you are offered the same utilities and options as a local Recovery System.
    Requirements for reinstalling OS X using Recovery
    Reinstalling OS X using OS X Recovery requires broadband access to the Internet via Wi-Fi or an Ethernet connection. OS X is downloaded over the Internet from Apple when OS X Recovery is used for reinstallation
    If you use Internet Recovery to reinstall OS X, it installs the version of OS X that originally came with your computer. After installation is finished, use the Mac App Store to install related updates or later versions of OS X that you have previously purchased.

  • Application Builder and Corrupt VIs

    Howdy All,
    I'm developing a Medium-sized application in LabVIEW 7.0 used for instrument control. This application has grown over-time, and currently contains approximately 400 VIs. The basic structure of hte appliation is one main VI that has an instrument status display on the bottom, and a sub-panel on the top, into which all dialogs are loaded for user interaction. Each major task has it's own VI that is loaded into the subpanel as appropriate.
    I've read a few stories on the developer exchange about VIs becoming corrupt. I thought these were freak occurences, because by and large, it appears that LabVIEW is fairly stable. However last week I had a VERY scary experience.
    I was demonstrating to a collegue the properties of an XY graph control. We changed the colour of one of the plots, then hit cancel. LabVIEW complained of an internal error involving undo.cpp and proceeded to crash. I figured the crash was caused by some strange sequence of events, didn't think much of it, and reloaded my application. After making some changes, I went to the Application Builder to build the application. However the application Builder was complaining about a "missing board" in the DEFAULT build file. I knew immediately that something was VERY wrong. (When I say default build script, I'm referring the default script that is loaded when you press the "Build application or shared library..." button in the tools menu).
    (As a side note, does anyone know why the LabVIEW application builder gives such terrible error messages? I always get that "missing board" error when either: one of my support files cannot be found, or one of my dynamic VIs is not executable. Since the error doesn't pinpoint a file, I neeed to go through the files one by one - which is a pain because I have a lot. Another question, why does the application builder ALWAYs ask if you want to save changes to build script, even if you haven't made any changes?)
    After loading my build script for the application (which I've used HUNDREDS of times), I got the "missing board" error. I didn't think there was a problem with any of my paths or VIs, but I went throgh each included support file and dynamic VI in the build script to make sure it was there. Though there seemed to be no problems with any of the files, LabVIEW continued to complain.
    I figured the problem was specific to the computer I was working on, so I copied the source to another development machine to complete the build. I was VERY scared to find that I got the SAME error on the DEFAULT build script! Also, my actual build script refused to load properly.
    This was late at the end of a long day, so I decided to turn of my machines and go home. The next morning, everything worked fine - I was able to build the application, and I haven't had a problem since. (Maybe it was a bad dream, but I have clumps of hair on my desk from the night before...)
    I found this experience to be UTTERLY TERRIFYING. Once I had to revert to an archived copy of one of my main VIs, because the current version refused to open, claiming it was corrupt. Since I don't know what's going on behind the scenes in LabVIEW, I'm afraid that tiny internal LabVIEW errors might be adding up. I back-up the source very regularily, since it is such a large project, however I have *real* way of inspecting the integrity of the source.
    Does anyone know (A) why this might have happened - especially when the problem reproduced itself on multiple machines (B) has anyone had similar experience with internal LabVIEW errors or corrupt source (C) what sort of internal errors might be piling up that might cause a VI to claim it is "corrupt".
    All input is appreciated.
    WG

    Hi Robert,
    For the undo.cpp error, I got a couple different line numbers but didn't write them down. If I get them again, I'll be sure to get the specifics for you.
    As for the "missing board", I also got that description a little wrong - the error I'm talking about is:
    "Error 7 occured at Inovke Node in Dist read linkages.vi->Dist Cmp Settings to Disk Hier.vi->Build Application.vi
    Possible reason(s):
    LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for hte operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Unix.
    NI-488: Non-existent board."
    As you can see, I meant "non-existent board". This error is very easy to reproduce - m
    ake a build script and include some extra files. Save and close the build script. Move or rename some of the extra files included in the build. Reload the script. You should get that not very helpful error.
    Now that I think about it though, maybe that NI-488 error refers to GPIB control, which I think I have installed, but don't have a GPIB card installed... hmmm... no reason that error should be popping up *there* though...
    I could have *sworn* I would also get that error when one of the dynamic VIs in the build is not executable, but I can't seem to reproduce that right now.
    Tying back to the original thread - what makes a VI corrupt? I imagine if you cracked the binary file open yourself and messed around with some bits you would probably make the VI corrupt, but I'm assuming that editing a VI normally (ie through LabVIEW) should NOT cause the VIs to become corrupted. Any information on VIs becoming corrupt? Is it somehow related to the undo.cpp errors?(when trying t
    o undo some last change that wasn't recorded properly, the VI is modified improperly - after you save and close, it won't reopen?)
    Victrick

  • Can I include raw files into the installer folder with LV application builder?

    Hello,
    I have created a batch file that will run at the end of the installer, which will copy over some raw configuration files into the source destination so that the configuration files can be customized for each end user without rebuilding the installer with application builder. I also have an autorun.inf so the installer will automatically run when the user installs the CD.  
    However I would like to have some default configuration files and an autorun.inf file that will be automatically added to the installer "volume" folder using the application builder. 
    However I don't see a way to include raw files in the "volume" folder. It appears all source files in the application builder are embedded into the binary files.
    Please let me know if this is possible with the current application builder.
    Regards,
    Russell
    Engineering Team Leader
    G Systems, www.gsystems.com
    Certified LabVIEW Architect
    Certified Professional Instructor

    Russel,
    i think this link might give you some good hints....
    hope this helps,
    Norbert 
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Application builder subvi

    I'm just learning to use the application builder, my interest is in creating a stand alone application & installer. 
      Is it possible to generate a single executable file which contains the top level VI as well as all of its sub-Vis ??  If the answer is NO, then where (and as what) should all of the subvis be saved so as to maintain maximum simplicity and portability? 
    I haven't yet found a gold mine of resources/tutorials on using the Application builder, are they hidding from me?
    Thanks,  Kevin
    LV 8.2.1

    If you aren't using dynamic VIs (as opened by 'Open VI Ref') you will automatically include all subVIs into the executable.
    That's about all their is to be said.
    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!

  • DLL created with LV 7.1 Application Builder doesn,t work when analysis subVIs are present

    I'm looking for a solution of the following problem.
    The DLL created by the "sum1.vi" source works properly, while the DLL create by "sum2.vi" always gives a zero result.
    The "sum2.vi" source contains an additional "Hanning Window" VI (not wired), that seems to be the cause of the problem.
    If I delete the Hanning VI and re-build the DLL, the same works fine
    Is there a solution or is it not possible to make Labview DLLs when containing analysis VIs as filters, windows, FFTs, and so on?
    Thank you for your answers.
    N. Roberto
    Attachments:
    sum1.vi ‏12 KB
    sum2.vi ‏14 KB

    Roberto N. wrote:
    Thank you Jordan, I'm using Labview 7.1.
    Anyway I've resolved the problem by adding the "lvanlys.dll" file (present in "..\Labview 7.1\resource\lvanlys.dll" path) as support file in the building process. Now the DLL containing the analysis functions works correctly.
    Natalino Roberto
    Ok, you probably got lucky since the lvanlys.dll seems to implement that function directly. However most Advanced Analysis functions are just redirected by lvanlys.dll to the Intel Math Kerneal Library that gets installed with LabVIEW 7.1 and higher. The only way to get that properly installed with your LabVIEW executable or DLL is to create a LabVIEW installer in your Application Builder and make sure to select under "Installer Settings->Advanced" the "LabVIEW Run-Time Engine" and the "Analyze VIs Support". Then use that installer to install your DLL on another computer.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Are there any advanced user manual for Application Builder?

    Hi,
    I want to find Application Builder user manual that can teach me how to set the Install Settings. For example, I want to know what libraries will be included in the installer if I enable Serial Port Support and Port I/O Support. What's the function of Enable ActiveX server in Application Settings? The Application Builder user guide I found which is a 8 pages installation guide with release note. I hope some NI engineers can answer this question. Thanks.
    Best regards
    Bill

    For information about specific options in the Application Builder, click the Help button in the Build Application or Shared Library dialog box. In the Advanced Installer Settings dialog box, you also can click the Help button to display a topic with information about each option in the dialog box. Here are the descriptions of the two support options you mentioned:
    Serial Port Support -- Installs the serial portion of NI-VISA needed for applications that access serial instruments or serial port.
    Port I/O Support -- Installs the necessary support files for accessing parallel ports and for using the In Port and Out Port VIs.
    The description of the "Enable ActiveX server" checkbox is: "Enables the ActiveX server for the application so it c
    an respond to requests from ActiveX clients."
    These descriptions also have links to more information about the objects mentioned, such as the In Port and Out Port VIs and the ActiveX server.
    If this information is insufficient, please email [email protected] with your feedback so we can improve the help topics.
    Thank you,
    Kelly Holmes
    LabVIEW Documentation
    Kelly H
    LabVIEW Documentation
    National Instruments

  • What are the options in the application builder application.ini file

    What are the options that I can add in the application.ini file that is created by the application builder.

    They are about the same as LabVIEW.ini. Scott Hannahs has a list of ini settings for several versions of LabVIEW that can be found here.

  • Queues in application made with application builder don't work?

    (Labview 2011) I have a medium sized application that runs just fine within the Labview environment. It uses event trapping for most things and passes longer tasks off to a consumer loop using a queue. Having gotten it to run the way I want, I want to use the application builder to turn it into a stand alone exe that can be distributed. It compiles without any errors or warnings and starts up fine. However, anything that happens via a queue doesn't work. The very first thing that should happen within any of the queues is that it should disable and grey out certain buttons to prevent unwanted behaviour. They don't get disabled and greyed out. So it's pretty clear nothing gets started. The queues also all have error handlers and there's no peep from them. Everything that doesn't use a queue works OK. Is there some kind of option in the application builder I need to activate to get the queues to work properly? The consumer loop does use an enum to figure out what it should do. On the off chance that the queue was mistakenly running the default (blank) case, I stuck a message box in there to warn it was being accessed. No message comes up so there is no indication that it is running the queues at all. The program doesn't hang when it should be running a queue. It just doesn't do what it should. ANy help would be greatly appreciated.

    rossu wrote:
    Thanks for the replies. The answer is a bit bizarre, but might be useful to know. Apparently, in some of the cases in the event structure (producer loop), the Boolean value that gets wired to the stop control in the surrounding while loop was missing. In the Labview environment,this didn't cause a problem (default value?), but in the application it did. Making sure they were all fixed made the issue go away. Interestingly, which events were missing the Boolean and what didn't function were not correlated. The program never got hung in the event loop I.e. the interface didn't freeze.
    This does not make any sense either. There should be no difference between development and build. Most of my output tunnels of event structures are only wired in the non-default situations. I suspect there was maybe some corruption and changing the tunnels forced a recompile, clearing things up. No way to really tell.
    LabVIEW Champion . Do more with less code and in less time .

  • Problem with logging in to apex application builder listener

    I have problem with my settings and am posting this in hope that someone else out there had similar problem and solved it!
    I am trying to use reverseproxy to access to our db through apex listener.
    It's been all set-up and I can login to the application it self either through proxy or no proxy using the listener.
    But when I try to login to apex application builder I cannot do it through proxy(with no proxy, it works).
    It just refreshes the login page when I click login....
    I tried to upgrade the listener to the latest v1.1(using 1.0.2) but it causes my tomcat to crash...
    So solution i am looking for is how to make logging in work through proxy..
    In the firebug it is showing that below and few other request status as 302 moved temporariry
    http://myserver:8080/testsin/apex/wwv_flow.accept
    Where as with no proxy it is saying Found.....
    Any thoughts??
    Thanks
    Sin K

    Hello Sin K,
    so proxy and Tomcat are located on different machines as well? Is the proxy able to commuicate with the Tomcat on the configured internal ports and is the proxy able to lookup the hostname you configured for the Tomcat?
    For the connector, the proxyName and proxyPort should be the parameters the client uses to call APEX. So if your clients should call via http://proxyserver:8080/testsin/apex the settings would be
    proxyName=proxyserver
    proxyPort=8080Reason for this is that applications (e.g. the APEX Listener) generate there URL references with these parameters.
    But does your proxy actually serve on port 8080? And is that port accessible by clients? Do clients accept cookies from that server?
    In my case, there is only one 302 which redirects to http://host:port/apex/f?p=4500:1000:sessionid which is correct.
    If you look into your first post request in firebug, what's in the request header?
    -Udo

  • Report Generation for Excel does not work after using the Application Builder

    I have a VI that writes data to an Excel file using the Report Generation Toolkit. I recently compiled the VI into a single Application (EXE) using the Application Builder. My VI runs its tests properly, but no data is written to Excel. What could be the cause? I don't receive any error messages.

    Hi
    I usually build exe-files, which sometimes also have report functionality.
    Open the Application Builder and check the following things:
    1. Add the following vis: _Word Dynamic VIs.vi, _Excel Dynamic VIs.vi They should be located in the directory ..\LabVIEW X.X\vi.lib\addons\_office in the llbs _wordsub.llb and _exclsub.llb (report1.jpg)
    2. If you use an Installer, go to the Advanced Settings. There you can select some things to include in the Installer. Check if "NI Reports Support" is selected. (report2.jpg)
    These are the things I always do, if I need reports and I never had problems up to now. I made two screen-shots of these settings.
    Hope this helps.
    Thomas
    Using LV8.0
    Don't be afraid to rate a good answer...
    Attachments:
    report.zip ‏25 KB

  • The executible I build with the application builder does not function the same as my VI file.

    I am using a USB 6008 device with the newest DAQmx drivers and Labview
    8.2 to make analog voltage readings.  Within my main VI I first
    create a data folder in the same location as the VI using a property
    node and then use case statements to call two sub VIs that create a
    data file within the data folder and then collects data.  When I use the
    application builder to create an executible the resulting file does not
    operate the same as the origional VI.  The program appears to be
    reacting to button presses on the GUI, but there is no indication that
    the data folder is being created or that any measurements are buing
    made.  Are there any known issues that may account for this
    anomily?
    -Mike
    Message Edited by TMBurleson on 10-16-2006 03:09 PM

    Are you using the VI Path property, using a reference to the current VI?
    I could be wrong, but if you're attempting to use a path relative to the current VI, I think that does indeed change in a built application. If your VI used to be C:\somewhere\foo.VI, then after building its path would actually be C:\somewhere\foo.EXE\foo.vi . Thus, if foo.VI used to try to make a folder like C:\somewhere\datafolder, the built application would be trying to make C:\somewhere\foo.EXE\datafolder , which wouldn't work.
    This is sort of a shot in the dark, but does this sound like it might be the case?
    EDIT: Dennis beat me to it.Message Edited by kehander on 10-16-2006 03:26 PM

  • After installing an application that was created using the Application Builder

    After installing an application that I created using the Application Builder I get this error if I try to run " ANY " LabVIEW App's that I have built. "Executable Version 7.1.1 doesn't match Resource File 7.1. Check your configuration."
    The way that I tried to fix this is to reload LabVIEW 7.1 and DAQmx 8.0. I am using two NI-6528 switch cards.
    After I reload LabVIEW and DAQmx I can run my applications but as soon as I install one on this development machine the error begins again.
    The executable that I built works fine on the development machine and any other machine that I try it on but it appears that the Run-Time engine 7.1 becomes corrupt after I run setup.exe for the newly created application.
    I have built numerous Installers, setup.exe's in the past without this error. Just this latest one caused this problem to start.
    I can NOT upgrade to 7.1.1. I am doing work for many different sections of this factory and I can not force them to upgrade. I've asked. Others supply code for the same machines using LabVIEW 7.1.
    I am stuck creating executables and manualing moving the correct files to the target machines.
    What can be done?

    No. The KB article was talking about a machine with 7.1.1 installed. I have LabVIEW 7.1 installed.
    The machine that I am having trouble with is my development machine. LabVIEW 7.1, DAQmx 8.0.
    If I build the executable all is fine. I can still run old executables including the one I just built.
    If I create the installer all is fine. I can still run old executables including the one I just built.
    When I install the app on my development machine the corruption occurs. I can " NOT " run old executables including the one I just built. The subject error pops up.
    I have not moved any executables to the other machines yet. I don't want to corrupt others.

Maybe you are looking for