Application builder 7.1 sous Xp ne marche pas avec vista

Bonjours,
J'ai créé un VI simple avec Labview7.1 pour communiquer avec une carte electronique via RS232 (avec NI-VISA 4.2). Aucun pb pour faire fonctionner le VI sur l'ordi source (sous XP). J'ai créé sans pb une application déployée qui fonctionne sur un autre PC sous XP. En revanche, ce programme ne fonctionne pas avec un autre PC sous Vista. L'application s'est installée sans pb, mais le VI déployé met 10min pour s'ouvrir et la communication RS232 ne fonctionne pas.
Merci d'avance pour votre aide

Bonjour,
Quel carte ultilisez-vous?
Avez-vous tentez d'effectuer une mise à jour de VISA pour Vista?
(http://joule.ni.com/nidu/cds/view/p/id/831/lang/fr)
Cela pourrait etre suffisant pour régler votre problème.
Bonne journée
Flo
Open Diagram First

Similar Messages

APPLICATION BUILDER Related :creaate txtfile based on input argument.

(s1) In database package (PL/SQL), i witten the package P1 to pass the aggument as a binary file alongwith complete path and DLL argument file and generate the txt file and finally it create table dynamic table "table1" wirh dynamic columns and data inserted in to table "table1"
step S1 is completed
Q : in APEX : i want to use this package P1 (from S1) and pass the argument file alongwith complete path using file browser (already availble in apex application builder). Please help me how to start so that just 1 select the binary file using file browser and DLL argument using text item from any page (like :p1_dll) and display the data from table1 in report region or sql report

>
Welcome to the forum: please read the FAQ and forum sticky threads (if you haven't done so already), and update your profile with a real handle instead of "979467".
When you have a problem you'll get a faster, more effective response by including as much relevant information as possible upfront. This should include:
<li>Full APEX version
<li>Full DB/version/edition/host OS
<li>Web server architecture (EPG, OHS or APEX listener/host OS)
<li>Browser(s) and version(s) used
<li>Theme
<li>Template(s)
<li>Region/item type(s) (making particular distinction as to whether a "report" is a standard report, an interactive report, or in fact an "updateable report" (i.e. a tabular form)
With APEX we're also fortunate to have a great resource in apex.oracle.com where we can reproduce and share problems. Reproducing things there is the best way to troubleshoot most issues, especially those relating to layout and visual formatting. If you expect a detailed answer then it's appropriate for you to take on a significant part of the effort by getting as far as possible with an example of the problem on apex.oracle.com before asking for assistance with specific issues, which we can then see at first hand
(s1) In database package (PL/SQL), i witten the package P1 to pass the aggument as a binary file alongwith complete path and DLL argument file and generate the txt file and finally it create table dynamic table "table1" wirh dynamic columns and data inserted in to table "table1" What are "binary file" and" DLL argument file"? What do they have to do with Oracle, PL/SQL and APEX? What "txt file"? "Dynamic" tables, columns and data is usually a warning sign...
Q : in APEX : i want to use this package P1 (from S1) and pass the argument file alongwith complete path using file browser (already availble in apex application builder). As has been noted in many previous threads on this topic:
>
For security/privacy reasons recent versions of browsers by default do not send local file path information from File Browse items to the server, nor expose the file path in the control's JavaScript methods. Firefox, Safari and Chrome only provide the filename. IE6 & IE7 still yield the path in Windows format. IE8+ and Opera have adopted an irritating approach of replacing the path with a wholly imaginary "C:\fakepath\"—and this monstrosity has sadly had to be enshrined in the HTML5 spec...
Changing IE's security config setting "Include local directory path when uploading files" enables the path to be exposed in IE, but unless you're working in an intranet environment where: IE is the only browser used; it's possible to make remote changes to this setting on every desktop; and this won't break/expose anything else, then trying to achieve this is pointless.
>
For more information see:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-March/018980.html
http://blogs.msdn.com/ie/archive/2009/03/20/rtm-platform-changes.aspx
http://developers.whatwg.org/number-state.html#file-upload-state
{thread:id=2385659}
Basically you can't get local file path information from a current browser in its standard configuration.
The HTML FileAPI may be useful, depending on browser support.

Application builder labview 2010

Bonjour
J’utilise l'application builder pour créer un fichier exécutable,
la création se déroule normalement
à l'activation du fichier .exe de nombreux sous-vi et librairies ne sont pas chargés ou trouvés
j’ai déjà utilisé cette application sans problème sur des versions
précédentes de labview
y-a-t-il des chemins à déclarer pour que l’application builder puisse retrouver ses
sous-vi ou librairies utilisées ?
merci

Bonjour,
Il faut ajouter les fichiers que vous appellez (sous VIs, controles, classes, etc) dans la partie "Toujours inclus" de votre executable ainsi que de définir la destination de vos fichiers sources vers votre exécutable et non le dossier de support (tout dépend de la façon que vous appellez vos sous VIs, XControl, classes, etc).
Cordialement,
Da Helmut

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

Problem with "Application Builder"

Hello!
I have problem when I am using application builder to convert my program to exe files. MY PROGRAM: I use a main program to copy a template VI in to other VI´s, and then I can execute the copied VI´s from main. When I have tried to convert my program to a EXE file, everything works but not executing the copied VI. The following error messages apperies when I try to execute the copied VI. What does this mean???
BR
Kristian K
Attachments:
error.jpg ‏152 KB

Hello!
Information for users on this discussion forum: the problem was due to 'Build Text' function and when that function was removed the program worked fine. The functionality in the 'Build Text' function could easily be replaced by the 'Format Into String' function.
Regards,
Jimmie A.
Applications Engineer, National Instruments
Regards,
Jimmie Adolph
Systems Engineer Manager, National Instruments Northern Region
Bring Me The Horizon - Sempiternal

Problem with Application build in JDeveloper 11.1.5 to WLS 10.3.5

Hi to everyone, I have a problem with a application build in JDeveloper 11.1.5 and deployed to a standalone WLS 10.3.5 ( with the JRF template appliied , to run adf applications )
When I try access to the page : localhost:7001/myApp , it show me :
"Error 403 Fordbbiben ".
but when I put :
localhost:7001/myApp/index.jspx, it show me :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 8, 2012 9:06:22 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
What can I do to fix the problem ??
Thanks

Analyzing the problem, I created a new ADF application with only a web page (index.jspx) , and deploy it to the WLS, and I access to URL of page and it runs !! ( http:localhost:7001/myApp/faces/index.jspx ).
But, when I ADD A TASK FLOW to the application and deploy to the WLS newly , and try to access to the URL application's ( http:localhost:7001/myApp/faces/index.jspx ) . It show me again :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 10, 2012 19:02:57 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
Why it show me that error when I ADD a Task Flow to the Application ???
Can Anyone help me please ?? I m varios days with this problem. Thanks

Application Builder and Closing

Hi
Already, another problem has arisen. I have developed a simple VI with no big thing inside. I am using an event structure for handling button presses. To quit my application, I have one button, labeled Quit (who would've guessed) which quits the application. I simply wired that button to the quit terminal of the event structure (ok, to the quit terminal of the while structure around the event structure).
I have also built this application with the Application Builder into a .exe file. I managed to get that Run/Pause buttons away. by checking the appropriate checkboxes inside AppBuilder. But now, what happens is as follows:
* I quit my application by using the red X of the window - everything closes down fine, the window disappears *perfect*
* I quit my application by using the button - the program stops, but the run button appears.
How can I avoid that behaviour?
Thanks for your advice

There's a function in Application Control which is used to close LV once everything's done executing. Be careful when using it while developing, as it will close all open vi's. Granted you get the option to save them, but it's annoying nonetheless.
See the attached image
Message Edited by Novatron on 07-10-2006 11:17 AM
Attachments:
Quit.jpg ‏4 KB

Build dll error in application builder 8.6.1

Hello,
I get always an error in the LV 8.6 application builder, when I build a dll. There is only one function in it, that has a string and an error input, and nothing else. I attach a screenshot of the VI prototype, and hier is the error description:
Error 1 occurred at Building DLL.
A component needed for Application Builder does not support the required functionality. This might have been caused by installing an older version of LabVIEW after this version was installed. Reinstall the current LabVIEW version to correct this issue.
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
After that I reinstalled LV8.6, I tried to reinstall only the 8.6 app builder, but no success.

Hello,
thank you for the reply.
I have solved the problem. I uninstalled the last installed LV version, this was 8.0. Then ran appbuilder again in 8.6, then I have got an instruction to run applibs\lvdllbuilder\lvdb.exe. Since then works.
regards
Mitulatbati

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.

Passing arrays with Call Library Function does not work after application builder

Calling a DLL with Call Library Function which requires an array of data works correctly in Labview, but after building an exe with application builder, the call no longer works. Dereferecing the pointer in the DLL retuns all 0s and not the actual values.
Solved!
Go to Solution.
Attachments:
TEST.zip ‏28 KB

I did not run your code because it is a little unclear to me what it does.
Two things:
First, is the DLL you are calling the DLL-ified version of PopUpNames.vi? Then the problem is likely that the panel is not being built into the DLL.
When LabView builds an application / dll, it strips the front panel and block diagram from all VIs that it doesn't think need to show a panel at run time. This reduces file size and increases code security. The App Builder's panel inclusion logic can be overridden by Build Specifications -> Source File Settings -> Remove front panel. A better method is to put a property node on a control in a window you want to show marking it "visible"; this is sufficient to tell the App Builder it should keep the panel.
Currently Source File Settings shows "no dependencies" (clearly incorrect---another evil side effect of Express VIs I guess) but if you change the settings as shown below to keep ALL panels, one might hope the App Builder can figure it to keep the panel when it deconstructs the Express VI. (Alternatively convert the Express VI into a regular one.)
A second comment: I am a bit flummoxed at the larger goal here. You are calling LabView DLL from LabView, which doesn't make a lot of sense, so I assume your larger goal is to call LabView from C or vice-versa. In that case be aware that your DLL is x86 (32-bit) but you are passing 64-bit ints as your pointers. In this case it is 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers calling 32-bit LabView with 32-bit pointers in embedeed in 64-bit containers, so it all works, but if your going to call this from C or whatnot you're going to have to follow that same design.
When calling C code the LabView Call Library Function does have a "unsigned pointer-sized integer" data type that always appears to be 64 bits in the dev env but which actually passes a 64 or 32-bit int to the DLL depending on the environment. The "pointer sized int" has to be 64 bits in the "LabView" part of the code because LabView's strong typing requires the data type to be determined at compile time. Casting all pointers to the largest data type in LabView makes it possible to write platform-independent code, but down at the Call Library level you still have to put the right number of bytes on the stack.

Error 7 occurred at Open VI Reference with Application Builder

Using Labview 5.1, I am building an application where all the vi's are placed in a single .LLB file. I have one top level vi (with sub-vi's), and one vi that is opened by the Open VI command. The program runs fine with labview installed. I want to make an executable file. I select the top level vi and select the vi that is opened by the Open VI command as a dynamically loaded file. I get an error when I attempt to build the file.
"Error 7 occured at Open VI Reference in Dist Build LLB Image.vi -> Dist Build App Image.vi -> Build application.vi"

Dear Sir;
There are two things that are good to try:
First, create the application in a folder that is closer to the root directory (e.g., c:\myApp). There is a limit to the length (or depth) of the path name to your application's target directory, so, if you are choosing a too long path you might get an error.
Second: The Application Builder reads certain information from the VI in order to determine how to build the executable. To avoid possible errors, either in the build process or in the built executable, make sure the VIs are LabVIEW 5.1 VIs. You can convert your VIs to LabVIEW 5.1 VIs by using the Mass Compile feature (File >> Mass Compile) in LabVIEW before you build your executable. The Mass Compile feature will allow you to select either a directory or a LabVIEW
.llb file to compile.
Regards

Application Builder for labVIEW 7 Doesn't support any report generation function

I'm Using LabVIEW 7.0 to build an application My Application is exporting data to an excel report. the vis were working great until i tried to creat an .EXE file. The application is working fine but when i try to generate the report nothing happens.
So, I decided to test the report generation functions alone (New Report.vi, Append report text.vi and Dispose Report.vi). The Problem Still there, the .EXE file takes no action when i attend to generate a report. any suggetions please.

Shady Yehia wrote:
> I'm Using LabVIEW 7.0 to build an application My Application is
> exporting data to an excel report. the vis were working great until i
> tried to creat an .EXE file. The application is working fine but when
> i try to generate the report nothing happens.
>
> So, I decided to test the report generation functions alone (New
> Report.vi, Append report text.vi and Dispose Report.vi). The Problem
> Still there, the .EXE file takes no action when i attend to generate a
> report. any suggetions please.
Another possible reason besides of possible path problems: Are you
running that application on the same computer? If not you need not only
to install the Runtime-Engine (automatic when you create an installer)
but also the Report Active X support.
To include that into the installer
you go into the Installer Settings Tab, then press the Advanced button
and make sure that you check the NI Reports Support checkbox before
creating an application build.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Application builder-Office report generation toolkit

Hi,
I remember there was a trick to get the executable work with different
versions of Microsoft office but I cannot find it now. The problem it to get
the exe work with some other office version that it was made. I use LabVIEW
7.0 - 7.1 and Report generation toolkit 1.01 for Microsoft office. Was that
possible?
Thanks Eki

Eki,
When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work.
Zvezdana S.

Application builder 7.1 sous Xp ne marche pas avec vista

Similar Messages

Maybe you are looking for