Shared Varaible Deployment

I am working on shared variable. When my program start i am able to deploy shared variables but after few compilation of program i am not able to deploy shared variables. Kindly help
I am getting error 19506789035. But i HAVE VARIFIED THAT MY PROGRAM GIVES CORRECT OUTPUT INITIALLY

After going through the code again and agian , i am sure that while deplpying varaible issue is there. I have used the attached VI to deploy the varaiables.
Attachments:
deploy library.vi ‏15 KB

Similar Messages

Shared varaible communication

I am trying to connect to my compact field point using a shared varaible. I have done this successfully on my office computer, moved my compact field point into the test area and am trying to run the same softeware on my lab computer. I get the error something like "could not read shared varaible, likely its not been deployed properly." I am using the first release of labview 8.0.
I have tried the following:
-disableing the windows firewall, then rebooting (winXP)
-deleting the shared varaible, and making a new one.
-avoiding putting spaces in the varaible name
I have full communication, and am using the same MAX setup on both computers.
If others could give me a list of things to try that would be great. Have the subsequent two updates to labview8.0 fixed this?
Short list of things I have not tried:
-using a hub with two ethernet cables, i am using a Xover cable, worked fine in office
Thanks for your help,
Kevan -

Hi Kevan,
Here are some steps you should try if you have not done so already:
Run a VI without shared variables from within the same project and verify that front panel communication is working properly
Verify IP address settings on the lab machine (set to static IP, if so, is it the same as your office machine?)
How many network interfaces are installed on the system? If multiple, disable the one not connected to cFP
What is the actual error number that appears?
Verify as well that the gateway and dns settings for the lab machine match that of the office machine - this has been known to cause some odd behavior
Manually deploy the library before running program by right-clicking on the library in the project window and select Deploy All. Additionally, if the library was not set to Autodeploy, this would also explain the situation.
Change the hosting location of the library containing the shared variables (i.e., drag from cFP target to your PC in the project window)
One of the above should expose the issue, if not solve it outright. Please post back once you've had a chance to give it a try. Have a great weekend!
Cheers,
Matt Pollock
National Instruments

Shared Variable Deployment not accessible in Build Specification

Hi everyone,
I have a large project developed in LV 8.6.1 from which I executed numerous applications. I converted the project in LV 11 sp1f1, everything works well in code, everything is saved.
I wanted to build executable without cod change for LV 11 here is what I found:
Build the executable with Build Specifications inherited from LV 8.6 for which I checked on Use Labview 8.x file layout in Advanced. My application programmatically deploys all internal shared variables and when I wanted to access the Shared Variable Deployment in project in Build Specification then labview locked and I have to kill LV. Other time I did not access the Shared Variable Deployment and I start building executable when it looks the build progressing similar as in LV8.6 and last step before popping the attached error all the saved files in the build location were deleted.
I set up a build specification just for this LV 11. Again I wanted to access the Shared Variable Deployment and again labview is looping something from which I had to kill labview. I opened it again, I skipped the shared variable deployment line and I build the application. Because my application programmatically deploys shared variables I included in builder the lvlib where shared variables belong. The build files does not includes this time as output the file *.lvlib for which my inherited LV8.6 code programmatic deploys shared variables.
My question is should I change the code (very large code) taking out the programmatic variables deployment and to relay on the build executable to do deploy them then what should I do with Shared Variable Deployment line in Build Specification which for my large application is not accessible or is any way to still use the shared variable as in LV8.6 but for which I need *.lvlib in build location.
Another important issue: when I launched my application built as I showed in previous second case, first thing that I see is that my application is not able to save errors (I have a log file where I save different drivers or communication errors). Any idea why application even without shared variable deployed is not able to write a text file? I am administrator of my computer with all rights.
Thank you,
Virginia

No, I am not able to close Labview because of the windows error with only one button to close application. The application is correct executed. Next time when I start this project it is asking me if I want o recover even if I accept to recover it looks what I had last time it does not save.
For my application also I am building a VI without diagram built as source distribution for which I set in my builder this top vi and I excluded everything from the project because my application copies instances at the run time of this vi as many times as hardware modules I have in the system and also I have this vi included in my application (for the content of this vi). My vi contains interfaces for hardware configuration as well as drivers functions call for each hardware module I have to control in my application. Everything is good building this vi, but in less then one minute after the build is executed and build interface closes again I have the windows error which force me to close project. Next time when I open project I did not see the option to recover the project.
In the mean time I received second message and I wonder if you refer to files names or to folder names or all together. I checked and the maximum size is 122 characters in the vi paths.
Thank you,
Virginia

Build specification freezes when trying to view "Shared Variable Deployment" screen

Labview 2009 f3
For some strange reason, any applications that include shared variable libraries will no longer build into executables.
I was able to build these applications without issue a week ago. However, when I went to make an updated build today, the build failed and I had to force Labview to close. When I view the build specification properties, I can navigate through all the option screens except the "Shared Variable Deployment" screen. As soon as I click on that option, the interface freezes up and I have to force Labview to close.
This problem does not occur for applications that do not include shared variable libraries.
I tried removing the shared variable libraries from the applications that were failing, but that did not correct the issue.

I never did find a proper fix to this issue.
One day I attempted to build the application again, but this time I got distracted doing something else. When I finally checked the build status a few minutes later I expected it to still be frozen, but to my surprise I found that the application did successfully build. To this day, that particular application still looks like it is going to lock up, but about about 8 minutes later it finally takes off and builds like nothing was wrong...like every other shared variable application I have created. So I guess my only suggestion is to let the application sit for a while and see what happens.

Question sur livre blanc NI TestStand Shared Drive Deployment Reference Architecture (7061)

La page suivante http://www.ni.com/white-paper/7061/en (NI TestStand Shared Drive Deployment Reference Architecture) décrit l'architecture possible en utilisant TestStand et lecteur réseau partagé.
Je ne comprends pas l'explication suivante dans la chapitre Engine concernant le moteur TestStand : "A TestStand system can use a number of different engines. With the exception of the TestStand Engine, you must install engines on the systems that utilize them."
Pourquoi "With the exception of the TestStand Engine" ? On doit bien avoir le moteur d'exécution de TestStand installé sur chaque poste/banc de test pour pouvoir executer celui-ci, non ???

Hi,
Thanks to Google translator i could read your question.
TestStand Runtime engine is required in every workstation/test machines if we need to run a test sequence (.seq files).

Shared Services deployed on WebLogic: Lifecycle Management Tool errors

Hi
In our pre-prod environment, Shared Services has been installed in Unix by "hypa" account belonging to "hyperion" group. Deployment on Weblogic has been done by "j2er" unix account belonging to "j2ee" group. j2er is also part of hyperion group.
I have given group level RW access to all directories and files under $HYPERION_HOME.
In Shared Services, user provisioning is wokring fine. When I am accessing LCM toolkit, and trying to run a migration, the msr directory initially did not get created. I had to give public RW access to "$HYPERION/common/import_export so that the PKGnn.xml could get created in the msr directory.
But when I execute the migration, the migration fail with error message:
"Task information defined for Souce connection is invalid"
Can any one suggest what to do? Is this related to file permissions?
In the Dev environment, the hypa and j2er are part of the same Unix group and everything works fine there.
Please suggest.

The error message is as follows:
java.lang.NullPointerException at com.hyperion.interop.lib.helper.ProductHelper.getProducts(Unknown Source) at com.hyperion.interop.lib.CMSClient.getProducts(Unknown Source) at com.hyperion.lcm.handler.RegistrationHandler.isProductCodeValid(Unknown Source) at com.hyperion.lcm.handler.PackageHandler.initialize(Unknown Source) at com.hyperion.lcm.clu.CLUProcessor.execute(Unknown Source) at com.hyperion.lcm.clu.CLUProcessor.main(Unknown Source).Unable to process task - 1. Task information defined for Source connection is invalid.

Shared library deployment error in jdev- 11.4, PS3 release

Hi,
I am facing an shared library reference exception.Please help in resolving it.
Find the below exception.
<Mar 10, 2011 4:39:16 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred
in the execution of deployment request with ID '1299755348296' for task '22'. Er
ror is: 'weblogic.application.ModuleException: Failed to load webapp: '/wcsdocs'
weblogic.application.ModuleException: Failed to load webapp: '/wcsdocs'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedM
oduleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:52)
Truncated. see log file for complete stacktrace
Caused By: weblogic.management.DeploymentException: Error: Unresolved Webapp Lib
rary references for "ServletContext@11873704[app:webcenter module:/wcsdocs path:
/wcsdocs spec-version:2.5 version:11.1.1.4.0]", defined in weblogic.xml [Extensi
on-Name: Resource, exact-match: false]
at weblogic.servlet.internal.WebAppServletContext.processWebAppLibraries
(WebAppServletContext.java:2754)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletCo
ntext.java:415)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletCo
ntext.java:493)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.ja
va:972)
Truncated. see log file for complete stacktrace
>

<Aug 19, 2011 9:56:23 PM CDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'webcenter [Version=11.1.1.4.0]' due to error weblogic.application.ModuleException: Failed to load webapp: '/wcsdocs'.
weblogic.application.ModuleException: Failed to load webapp: '/wcsdocs'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:393)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:180)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: custom.webcenter.spaces.view.SessionInvalidationServlet
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
Truncated. see log file for complete stacktrace
>

Shared Variable Deployment and Hosting

Hi all,
I am writing a labview RT application where a host PC will communicate with a RIO 9074 to write/update some 400 I/O simultaneously..
I have decided to write an entry level VI on the host PC so that I can pass all data to the RIO and then receive the processed data back. Here is my question... Where should I create the network shared variables in my project?? Under the host PC or under the RIO target?? What would be the difference between hosting the network shared variables in my host PC or hosting them in my cRIO??
Cheers,
Harry

There are some questions you need to ask yourself before you make those decisions. The following tutorial has that covered under the title 'Recommendations for Shared Variable Hosting Location'. Have a look and let us know if you have any further questions:
Using the LabVIEW Shared Variable
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Shared Services Configuration & Deployment

Hi,
I have a general query on the Shared Services Deployment. In the config. utlility you find an option to deploy shared services using an application server. After that we dont deploy it using web server. This being the case how are we able to access shared services using the url http://servername:28080/interop ??
I searched many places but couldnt find exactly what i am looking for. Thanks in advance for all your inputs...
Edited by: user12136330 on Nov 13, 2009 5:11 AM

The configuration utility deploys all the components and creates the application to run on the specified port, if you point the configuration utility to the installation location of web logic it does the rest for you. So basically once you have configured using the configuration utility the shared services app should be running and accessible by the standard url.
If you are struggling I think you should have a look at the installation documents
V9 - http://download.oracle.com/docs/cd/E10530_01/doc/nav/portal_1.htm
V11 - http://download.oracle.com/docs/cd/E12825_01/nav/portal_1.htm
Cheers
John
http://john-goodwin.blogspot.com/

Scale cRIO NP Shared Variable AFTER Deploying an Executable

I have a project coming up that has about 140 shared variables deployed on an RT target and sharing data at 1S/s over the network. There is nothing else going on concerning the RT target, just dumping values. I would like to scale these SV's in the .lvproj to avoid having to write a bunch of scaling code in software.
My only concern is what happens when I have an executable application running (without LV 2012 installed on the computer). How would I re-scale these values without having access to the .lvproj? Distributed System Manager doesn't provide for this. Any help would be appreciated. Thanks.
Nathan - Certified LabVIEW Developer

Hy Nathan,
Your Shared Variables are within a library in you LabVIEW project. In your Application Properties make sure to include that library. This is shown in Figure 9 in the below white paper.
http://www.ni.com/white-paper/9900/en/
MJ
Application Engineer
National Instruments

VI cannot find shared variable in engine despite successful deployment

I am unable to use Shared Variables to communicate between VIs located on my PC and the VIs located on my cRIO-9014. This is a new development as I have been running the same VIs for over a year without this problem. The only recent development is that the IT department at my company installed new virus protection software and changed some windows firewall settings on the PC that I am using. This problem first began as soon as I got the PC back from IT. I have since unblocked LabView in Windows Firewall but that has not fixed the problem. The error I get every time I try to read a shared variable on the real time target is:
Error -1950679035 occurred at Shared Variable Read in RT Interface.vi
Possible reason(s):
LabVIEW: (Hex 0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
I have redeployed all of my shared variables and according to LabView the deployment was successful, yet I still get this error every time. Is it likely that something the IT department did with the Antivirus/Firewall software has blocked communication between the cRIO-9014 and my PC? I have used Measurement & Automation Explorer to check communication with the device and as far as I can tell everything seems fine.

After adding LabVIEW to the exceptions list of Windows Firewall, my issue seemed to be cleared up. I am now getting the same error message once again, but now I get it every time I run a VI with shared variables and it actually pops up an error message asking me to continue or stop. Again, according to LabVIEW the shared variables deployed successfully. I looked at the two KB articles that were posted and it seemed like this error has three causes:
1-Unsuccessful deployment - everything seems to have deployed
2-Firewall Issues - were taken care of to fix my original problem
3-Shared Variable Engine not running
I've looked around and I found a reference to 'repairing' the shared variable engine but not a guide for how to do that. I have opened variable manager (I am using LabVIEW 8.5) and have stopped and started the shared variable engine with no effect.
What are steps I can take to ensure the Shared Variable engine is running properly?

Shared Vaiable Manager Operation

Hi All,
Can somebody please advise me about the operation of the Shared Varaible Manager.
I have a project that includes my development pc, a remote pc and several pxi controllers running Labview RT.
I have deployed shared variables on all targets.
In Variable Manager, I can see the deveopment pc (localhost) and the pxi targets but the remote pc doesn't show up. So I can't 'watch' the variables on the remote pc. Should I be able to see the remote PC in Variable Manager?
The remote PC is running an executable vi only with the labview runtime engine installed. The shared variables on the remote pc are deployed by the exe program.
kind regards
Frank Greenslade
New Zealand

Hi Jim,
Thanks for your reply.
Yes , I have tried as you suggested and that does work. When I browse for network variables to bind, I can see the remote computer and the variables deployed on it. I can then watch the new bound variable.
However, this seems to be a round about way of doing something that should be simple and could be a potential source of error.
It seems logical to me that I should be able to add the remote computer as a 'system' in the Variable Manager tree. Then I could deploy and undeploy the variables as happens with other systems in the tree (Local and RT).
Is there a way of adding the remote computer as a system in the tree?
Thanks for your help.
And sorry about the spelling earlier.
cheers
Frank

Why should you explicitly open and close shared variable connections?

I'm looking into switching over from the old Datasocket API to the new Shared Variable API for programmatic access to shared variables, and I noticed that LV doesn't seem to have any problems executing Shared Variable Reads & Writes without first opening the connection explicitly. That is, I can just drop in a shared varaible Read VI, wire a constant to the refnum input, and it will work. I'm wondering, then, what benefits are offered by explicitly opening the conenction ahead of time...?
I guess I could see some cases where you want to open all necessary connections in an initialization state of a top-level state machine, particularly if you want to use the "Open & Verify Connection"---so you could jump straight to an error case if any connections fail. But other than that, why else might one want to explicitly open the connections.
And, along those lines, are there any problems with implicitly opening the connections? One reason why I am hesitant to open them explicitly is because for one of our applications, we need to be able to dynamically switch from one variable to another at runtime. It would be nice to just switch the variable refnum (wired to the input of the Read function), without having to manually close out the old connection and open a new one. A quick prototype of this seems to work. But am I shooting myself in the foot by doing so?
Thanks in advance.

I'd expect there's a very small number of people at NI that would know the answer to the detail you're asking for. But, let's try to extrapolate from this rather old post to see if we can understand what they're forming their impression on.
The shared variable has to have some sort of reference going on in the background. It looks like they're calling this a connection. It's how LabVIEW knows where to find this variable on the network. We can also see this reference certainly exists if we're opening/closing the reference in the explicit method. You see the connection as just a string referencing the variable by URL. This "reference" has to be stored somewhere. No matter how we're looking at this, we're aware there's a reference of some sort stored.
Now, we'd want to look at what would cause this reference to go away. If you open/close explicitly, it's easy to see it goes away at the close. If it's implicit, when would it make sense to close it out? The VI can't be expected to guess where it's done being referenced and close it out. This puts us into a situation where the soonest it could close is when the VI ends. From my experience, references tend to be wiped when you close out LabVIEW. It's this kind of idea that makes the FGV possible. I wouldn't be surprised by Morgan's claim here.
If we look at scalability, you're talking about two different topics. You're talking about adding an extra open, close, read, etc rather than just a few wires. That certainly would look a mess. In terms of the dynamic swap that was being discussed, we wouldn't be adding all of those. The concern would be if enough connections were opened it'd start to behave similar to a memory leak. This could be something that works with a smaller number of variables. If you continue to scale, it becomes problematic. This is why they suggest it's not scalable.
To your questions:
Does LV allocate some kind of session in memory using that string as a lookup?
It would HAVE to allocate some memory to hold that string. Otherwise, it'd be pointless to even have the reference.
Does it reuse that session if other parts of the application reference the same variable, or does it create a unique session for each referencing call to "Read Variable.vi"?
I would expect this to be "it depends." With the implicit method, I would expect it to open a new reference in each point it isn't wired. This is similar to int x,y = 5; x and y share the same value but are their own unique memory location. If you wire the reference to the other points, it should use the same reference. This would make more sense to me than the program seeking out any other potential usage of the variable in the application to see if there's already a reference open. I could be wrong, though.
And what resources does this "connection" actually represent?
At best, this is just the string. At worst, it's the string and the TCP socket. I'd lean towards the first. Opening and closing sockets should be relatively easy in most applications. But, it also wouldn't surprise me if it holds the socket.
I'm sure others have a better understanding than I do. But, that's what I'd expect for anything you've asked.

Shared Variables - Properties

Hello,
I have a couple of questions about properties of Shared Variables (SV). They can be configured either by using the dialog box (right-click on SV -> Properties), or programmatically via the "SharedVariableIO" property node. Have a look at the NI-Examples to see how SV can be created programmatically by using the DSC module.
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
Regards,
Dietrich

dietrich wrote:
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
You can't. The single-process shared variable is an old style LabVIEW global placed under the shared variable abstraction. There is currently no way to create those on the fly. Time-triggered also cannot be created programmatically. I confess I don't know enough about them to know the reason why.
dietrich wrote:
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
Network.On Scan = read/write hardware? - this allows you to programmatically control when you are reading from or writing to configured hardware.
Network.ConnectionType = connect to hardware even when no one is viewing me? - this has 2 choices, UpFront & OnDemand, UpFront means that the variable will be connected to hardware even when no one is connected to the variable. This is useful when you want to reserve hardware or when logging is enabled. OnDemand means that you disconnect from hardware whenever no one is reading the variable.
dietrich wrote:
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
I would advise against using any of these. National Instruments can change, or remove, those underlying files at any time as a result of modifications to the MVE. That could cause issues for any code using those sub-VIs.
Regards,
Robert

Local vs. Shared -- who does what?

One place that the documentation I'm finding is thin in
discussing is how someone who is on a shared server deploys a
ColdFusion/Flex app.
For instance, my host is very helpful, but still, I don't
have direct access to anything above my domain. I'm trying to
figure out where the files that are in
C:\CFusionMX7\wwwroot\WEB-INF (i.e., all of the various xml
documents -- crossdomain.xml, services-config.xml, etc.) need to go
and what I need to tell them to set in them.
Has anyone on a shared sever made this work? Can you share
your wisdom?
Al

One place that the documentation I'm finding is thin in
discussing is how someone who is on a shared server deploys a
ColdFusion/Flex app.
For instance, my host is very helpful, but still, I don't
have direct access to anything above my domain. I'm trying to
figure out where the files that are in
C:\CFusionMX7\wwwroot\WEB-INF (i.e., all of the various xml
documents -- crossdomain.xml, services-config.xml, etc.) need to go
and what I need to tell them to set in them.
Has anyone on a shared sever made this work? Can you share
your wisdom?
Al

Shared Varaible Deployment

Similar Messages

Maybe you are looking for