Application builder closes labview

For whatever reason my application builder quit working. I had built several applications since I installed 8.0 and all work fine but now when I try to build an application it closes out LabVIEW and never builds anything. There are no error messages and it is not resident in the task manager (windows XP) anymore. It seems to be a clean close, but why can't I build an app anymore? I've tried it with both a VI and a project file seeing if that made a difference and neither work.
Also after talking with tech support I uninstalled and reinstalled 8.0 with no luck. I also checked my license manager and app builder has the green box next to it.
Furthermore I have the "NI-PAL Service Manager has encountered an error and needs to close" error on boot-up. Could this be linked?
Any help would be greatly appreciated.
thanks,
Dave

Hi Dave,
The NI-PAL Service error messages are being caused by your NI-Motion driver, possibly in connection with your NI-DAQmx driver. I would highly recommend downloading and upgrading to the latest versions of these drivers to try to get rid of that error, in the case that it is causing other things to fail. Because you are seeing errors, it would probably be a good idea to uninstall NI-DAQmx and NI-Motion before installing the new versions. They can be downloaded here:
Drivers and Updates: NI-DAQmx 8.3
Drivers and Updates: NI-Motion 7.4
I don't think the 1 year anniversary of your install would have anything to do with Application Builder stop working or getting error messages. Usually if a product is not activated there is a 30-day trial period, but in your case it seems that the products are activated.
The problem when you try to open a .lvproj file and seeing the error: "There was a problem sending the command to the program." definitely suggests some sort of corruption or installation problem. If after trying to get rid of your NI-PAL errors you are still having these problems, you may have no choice but to start clean. In this case it would be easiest to start with a fresh Windows XP image, but there are ways to just remove all National Instruments software. If you choose that route, please open a service request via phone/email with National Instruments.
I would also encourage you to upgrade to LabVIEW 8.2 if you are on our Standard Service Plan. Creating a duplicate hierarch can be done by creating a source distribution or a zip file from the Build Specifications. The source distribution tool is much improved in LabVIEW 8.2 from LabVIEW 8.0.1.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Similar Messages

Application builder for labview 4.1

I have a legacy application that compiles with 4.1 but does not with 6.1. We had application builder for 4.1 but only have access to Applications builder 6.1 at this time. Where can I get a copy of Application Builder 4.1?

I would contact NI's Sales group. I highly doubt that it is still available, but it's worth a try. You can reach them at 512.683.0100.
J.R. Allen

LabView, Application Builder, FieldPoint - Programmabsturz beim Aufstarten einer erzeugten EXE-Datei

Hallo, habe folgendes Problem:
Für einen Kunden wurde ein Programm zur Datenerfassung entwickelt (2005).
Die Daten werden über die Fieldpoint-Schnittstelle erfasst und in einer CSV-Datei abgespeichert.
Für ein Folgeprojekt möchte der Kunde eine angepasste Version dieses Programms.
Darum wurde zusätzlich der Application Builder erworben um eine Exe-Datei zu erzeugen.
Da ich sonst nichts mit LabView mache ist meine LabView-Version nicht mehr die neuste
LabView Version 7.1
Application Builder für LabView 7.1
Fieldpoint Version 4.1
Das Erstellen einer EXE-Datei war auch erfolgreich, nur beim Ausführen der EXE auf dem neuen Zielrechner, bricht das Programm beim Aufstarten die Anwendung öfters mit einer Fehlermeldung ab (Fehlerbericht an Microsoft senden...) und beendet diese.
In der Ereignisanzeige des Rechners erscheint in diesem Falle immer die Meldung ".NET Runtime 2.0 Error Reporting"
Typ: Fehler
Ereignisskennung: 1000
Warum das Programm manchmal abstürzt ist leider nicht auszumachen, ich schätze aber dass es mit der Schnittstelle zu FieldPoint (Version 4.1) zu tun hat.
Wenn ich das Programm aus meiner Entwicklungsumgebung aus Starte funktioniert es einwandfrei.
Testweise habe ich auch schon die Entwickungsumgebung auf dem neuen Zielrechner installiert, auch dann läuft mein Programm wenn ich es manuell von dort aus starte. Kann ich beim Erzeugen der Exe-Datei noch was falsch gemacht haben?Aber warum funktioniert die EXE-Datei dann ab und zu?
Solved!
Go to Solution.

Translation
Hi, following problem:
For a client, a program was developed for data collection (2005).
The data are recorded on the FieldPoint interface and stored in a CSV file.
For a follow-up project, the customer would like a customized version of this program.
Therefore, in addition, the Application Builder has been acquired to produce an executable file.
Since I do nothing else with my LabView LabView is no longer the latest version
LabView version 7.1
Application Builder for LabVIEW 7.1
FieldPoint Version 4.1
Creating an EXE file was successful, only when you run the EXE on the new target machine breaks
Program at startup, the application several times with an error (send error report to Microsoft ...) and ended it.
In the event viewer of the computer appears in this case always the message ". NET Runtime 2.0 Error Reporting"
Type: Error
Event ID: 1000
Why does the program crashes sometimes unfortunately not identify, but I guess that with the interface
to do on Field Point (version 4.1) has.
When I run the program from my development environment from Start it works fine.
Test,
I've already installed the development environment on the new target
machine, even running my program when I start it manually from there. Can I have when creating the exe file does do something wrong? But why the EXE files work now and then?

I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

srinivas wrote:
Sorry for confusion ,
My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
Br,
/Roger

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

How to build a Labview driver for a USB device?

I have purchased a USB Hall probe (a device that measures magnetic fields) and now I need to build a LabVIEW driver for it (the company that sells this device did not build drivers for it, to keep the price down I suppose). The USB device does come with an operating software, but what I need is to control the device using LabVIEW. I have some experience with LabVIEW, but none with building drivers. I don´t really know where to start, so any advice would be helpful.

To do USB in LabVIEW you'll want to get the NI-VISA driver. After you've got VISA, check out a few examples:
USB Instrument Control Tutorial
Six Things You Need to Know about USB Instrument Control
There are also examples built in to LabVIEW (under Help>>Find Examples to open the NI Example Finder, then under Hardware Input and Output>>VISA)
Tim W.
Applications Engineering
National Instruments
http://www.ni.com/support

Compiling a form with Dblink makes Builder close unexpectedly

I got Windows XP, Patch 18 installed and anytime I try to compile a form that uses a DBLINK, as soon as I try compiling the form, my form builder closes to desktop (no error, message, nor anything).
I tried FORMS COMPILER --> Compile ALL and nothing =(
If I put in Comment the dblink instruction the thing works as it should.
Any Idea?
gracias

Patch 18 sounds like Forms 6i.
Patch 18 is only certified against E-Business-Suite. Are you working in that environment? Else I think you must go to Patch 17, the last version for nomal development.

When I try to migrate vision builder to labview I get an error message

when I try to migrate vision builder to labview I get an error message "Error at Labview code creation step #6"

Does the error seem to be occurring at the same step in your Vision Builder AI script? See if you can determine if a certain step introduces the error by trying different modifications of your script and/or generating LabVIEW code from a Vision Builder AI example inspection. Also, are you using IMAQ Vision 7.0 for LabVIEW or a previous version of the Vision software?
Best regards,
Dawna P.
Applications Engineer
National Instruments

Report builder closes on its own saying it has encountered an error

hi
i am using reports 6i ,i changed an existing query in data model with a query consiting of union statements
eg earlier the column names(just giving eg of one column) were DT_TRANSACTION_DATE
now
after giving the modified query consisting of union clause the column name comes as DT_TRANSACTION_DATE1
why is this happening ? in the modified query i havent changed th existing column names ,just included a new column
why do the existing columns get a 1 as suffix
now when i try to run the report ,report builder closes on its own saying it has encountered an error
kindly guide
thanking in advance

This "changing" of field-names, in general, happens when the column-names in the SQL-query are not written with proper aliases, so that reports creates aliases on its own.

Application build

I have a problem for application build.
Ask:
Where I download free application build for labview 5.1 ????, please

Hi,
The Application Builder was included in the Professional Development system. If you had the Standard Edition of Labview 5.1 you had to buy Application builder as a separate add-on. Cost was $995.
Sorry,
Jim
"Michele" wrote in message news:000f01c09919$b7f51be0$[email protected]..
I have a problem for application build.
Ask:
Where I download free application build for labview 5.1 ????, please

Vision SNAP.vi closes labview

Hi all,
I have 2 systems that run different applications but they both use NI snap VI to acquire images from a NI-PCI capture card (single channel). About 10 times each day windows reports that Labview.exe has generated errors and closes labview. Does anyone know how to fix this issue? Should I update IMAQ or LabVIEW (or both)? Or maybe stop using snap and initialise the card only once. Any other ideas?
Im using IMAQ 3.5.0 with LabVIEW 8.0.1 on XP
TIA
-Martin
Certified LabVIEW Architect

Hi Martin,
Hope you are doing alright! What sort of errors do you get? Can you attach screenshots? Also, if you can attach a VI or a screenshot of it, that would be great! Do these errors appear on both machines?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Command-line build using Labview 8.0

My company is trying to automate builds from a single machine (nightly builds). This requires an unassisted (read scripted/command-line) build for LabVIEW executables (currently we are building manually). LabVIEW 7.1.1 and prior didn't really offer this and i was needing to know if LabVIEW 8.0 has added this functionality.

PLEXSYS wrote:
My company is trying to automate
builds from a single machine (nightly builds). This requires an
unassisted (read scripted/command-line) build for LabVIEW executables
(currently we are building manually). LabVIEW 7.1.1 and prior didn't
really offer this and i was needing to know if LabVIEW 8.0 has added
this functionality.
For pre-LabVIEW 8 you could take a look at the OpenG Builder.
It is basically yet a different application builder around the LabVIEW
core functionality that does the actual building. Since the OpenG
Builder is distributed in source code it is not a very difficult
(although possibly laberous) exercise to call the specific functions
necessary in your own scripted or otherwise controlled LabVIEW
application that would allow you to do some sort of batch processing.
The folks at OpenG are looking into possibilities to extend the OpenG Builder for LabVIEW 8 but it is a quite involved change.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Receive an error when closing my program built using LabVIEW application builder

When I close my program built using LabVIEW application builder I receive an application error,"The instruction at "0x77fcb1ad" referenced memory at "0x023a0010". The memory could not be "read". Click OK to terminate the program"
I have no idea why this is happening.

This is most likely due to a reference or similar left open. You will experience this if you leave an image undisposed in IMAQ as well.
Check all of your references and be sure you are cleaning everything up.

How to distribute the serial core only with my exe and DLL application using the Labview application builder 8.21. I'm not interested having MAX and other components installed on the customer PC and in the program menu

Since Labview ver 8.0 and later, I am not very happy with the new way the project installer is managing the additional drivers such as Serial.
With LV 7.11 the serial components was included in the cab file and was installed on the target computer in a specific directory. The size of the distribution was pretty small and well suited for compact distribution.
My LV application use only the serial object and with LV 8.21, if I include the serial 3.2 component, I get an enormus file including max, visa ... and a lot of fucky component I do not need.
To distribute my application, I just need, the runtime engine and the serial driver as it was with the version 7.XX
Looking for clever advises from you gentlemen!

Thanks Dennis for you input
My problem is in fact very simple. 3 years ago, I developped a software suite for X ray generator; My company is selling such generator all over the world and our control panel software and DLL (for OEM integrator) is based on Labview professionnal development plateform.
To drive our generator, we just need to transfer ascii data using the strandard RS232 port still present on most of equipments used in the industrial area.
Until LV version 7.11, there was no problem to include serial component in my distribution with a very reasonable size and transparency for the end user.
with LV 8.xx (preparing a new release), I'm very disapointed to see, my distribution is increased of about for 10 Mo to 180 Mo just because I increase the serial component.
May I mix a previous version of the serial component with LV 8.21?
Should I change my source to Visa instruction only and merge visa runtime only to my distribution?
is there any simple serial example based on visa and distributed with th application builder?
I will appreciate your help in order to optimize my distribution
Pascal

LabView 2010 Application Builder for EXE Always Included files are not Included

In LabVIEW 2010 F2, When I am using the Application Builder to build an EXE file, I have listed 10 or so files to Be "Always Included". But when I Explore the directory where the EXE was built, those "Always Included" files are not there or in any subdirectory under the EXE file.
This frequently makes my EXE file not work properly because important files are missing. I have to spend extra debugging time to find out the the cause of my problem is missing files that the Application Builder should have transferred "Always".
Why did the Application Builder, when building an EXE target, not include the files that should be "Always Included"?
Why does the Application Builder ignore these files specifications?

Dennis Knutson wrote:
The build does include files you select. Post an example project with a small VI and some separate files where this does not happen.
No, it does not appear that all of the files that I listed in the "Always Include" list are copied during the Build process to the Build directory or any subdirectory under that.
The Build Source Files.jpg file shows most of the list of the files that should be "Always Included". Notice the .VI and .ctl files that are listed
The Build Directory.jpg file shows the file in the Build directory that were built.
The Data Directory.jpg file shows the data directory under the Build directory and may include some of the files listed in the "Always Include", but not all of them.
The other subdirectories under the Build directory were created by me and do not include any files that were copied during the Build process.
So not ALL of the files that were included in the "Always Include" list were copied into the Build directory area as expected. ALL of the files that are listed as "Always Include" should be copied, if they exist. Those files existed when then were selected for the List and they existed at the time of the Build.
I can not include an example project that demonstrates this. I am prevented from doing so by the terms of an NDA. You are going to have to take my word that this event is real and happens the same way every time. This information should be sufficient for someone to investigate why do not ALL of the files listed in the "Always Include" list are copied into the Build directory area regardless of the file type or contents.
Attachments:
Build Source Files.jpg ‏151 KB
Build Directory.jpg ‏125 KB
Data Directory.jpg ‏131 KB

Applicatio​n builder closes labview

Similar Messages

Maybe you are looking for

Application builder closes labview