VI Name conflicts with "Open VI reference"

I am using LabView RT, where an application loads LLBs at runtime:
1- The user creates/compiles a LLB containg a VI that is loaded at runtime later
2- The user renames the contained VI to an enumerated name so that all names are always unique
3- The user uploads the LLB (containg the VIs with a unique name) to a LabView RT system
4- The LabView RT application openes all available VIs contained by the uploaded LLBs at runtime (the filename hints at the VI's unique name)
5- The LabView RT application executes the now opened VIs
My problem is step 2 where the user needs to rename the VI. This is because the RT application will not be able to distinguish between the opened VIs if their names are equal. I want to eliminate step 2 because it's error prone as the user always forgets to do the renaming or the user does the renaming in a wrong way (e. g. non-unique, typo).
A dirty hack would be to automatically replace all VI name strings (which are alidentical and like a placeholder) inside the LLB binary with unique ones at RT application's runtime. So the application takes over the renaming task.
Any other solution?

Hi Salim,
This CORBA support being moved from SP2 to next release.
Honghsi
Salim Djaffar wrote:
Andy Piper <[email protected]> wrote:
"Eric Green" <[email protected]> writes:
Andy Piper <[email protected]> wrote:
For what it's worth, except for the error message WTC appears to
be functioning fine in a clustered environment.Right. It will mostly work, but there are some issues with the CORBA
support.
When is the ballpark release date for SP2? Is WTC at SP1
now, or is this two updates away?I mean WLS 6.1 SP2. I do not know what the timeline is for these
things.
andy
--I also experienced the same problem, and I planned to go production within a month
or two.
Do you have any estimate when SP2 will be GA for public ?
salim

Similar Messages

I have had a trial version of Acrobat X1 Pro - I have decided not to buy at this stage - for some time it has been conflicting with opening PDF docs after saving as from word 2007 - I uninstalled Pro X1 and now when I save as from word 2007 to PDF it will

Can anyone help with this - do I have to uninstall Reader and then reinstall?

I have had a trial version of Acrobat X1 Pro - I have decided not to buy at this stage - for some time it has been conflicting with opening PDF docs after "saving as" from word 2007 - I uninstalled Pro X1 and now when I "save as" PDF from word 2007 to PDF it will save the document as a PDF but will not open the document to display after publishing - I have to got to where the file has been saved to view the new PDF document - this is really annoying - do I have to delete adobe reader and reinstall it - adobe needs to look at this conflict with acrobat pro as I have even gone it to properties and tried to have adobe reader as the default PDF program - the main issue is that I cannot view the PDF after publishing it from word 2007

PI 7.0 - SMICM - Host Name - Conflict with other places

Hi Friends,
We have host name conflict in SMICM and in other places.
For example, in SMICM it shows the host name 'A' for HTTP protocol and it is green, where as in other places like in RZ10 (Profiles in ABAP), Exchange Profiles (Connection Parameters, Host name), in SLD and in Visual Admin the host name is mentioned as 'B'.
At present, the messages are failing in SXMB_MONI with the error "CLIENT_RECEIVE_FAILED 402 ICM_HTTP_TIMEOUT ".
When we checked the paramter "icm/host_name_full" in RZ11,it shows the empty value.
This problem comes in our quality PI system, ABAP stack.
Could you kindly clarify in SMICM for the HTTP service from where the host name is taken and displays here?
Kind regards,
Jegathees P.

Connect to the operating system. Check this file (replace xxx with your SID and, if applicable, 00 with the correct instance):
C:\usr\sap\xxx\SYS\profile\xxx_DVEBMGS00_ILBNKxxx
Find this line:
icm/host_name_full = hostname.company.corp
Is this maybe empty / incorrect / incomplete?
After changing this the server needs to be restarted.
Sometimes we had strange behaviors after host name changes, which went away after going to sicf -> execute -> right-click on default host -> deactivate -> right-click again -> activate -> in the pop-up click the second activate button, which is for activating the system and all dependent entries.

Adobe Reader conflict with opening pdf in Outlook 2007email

I have Windows7, Outlook 2007, Adobe Reader 8.2 and 9.3. Cannot open pdf doc. in my email with a double-click. Must save first, then open the file. When I double click pdf, this message appears, "...error with the following previewer: PDF Preview Handler for Vista". I do not have Vista...I have W7

I'm having the same exact issue in windows 7 w/ adobe reader X. If I save it to the desktop
it opens fine. I've edited the registery as well as uninstalled reinstalled. and Disabled protection at startu
p with no success. What can we do Adobe to fix this. The product is completley updated and it is a brand new pc

"open vi reference" with run time menue

Hello,
I met some problems with "open vi reference" in labview.i can't parallel run this vi with the run time menue.i can't load the any vi then the run time menue has activation.(the "open vi reference" can run after the run time menue release.). it's means labview is serial running for this both function.but now i want to parallel running in the program.so would you give the some idear?

Now I see what you are talking about. What you are trying to do is expected behavior. If you click on the menu while any state is running that doesn't lock the front panel, then the menu will halt the VI execution until you choose a menu item.
You should check the option in the event to "Lock front panel until event case for this event completes" Then you will not be able to click on the system menu until tthe VI is launched and running. If you wire a True like I suggested before, then you will fall out of the case pretty quickly in non-hoghlight mode, and the user most likely will not notice. If the VI you are trying to open is quite large, it will take a little bit of time for LV to load the VI into memory.
In highlight-mode, you just have to wait for the event to process before you select the menu.
Message Edited by Matthew Kelton on 12-03-2007 10:56 PM
Attachments:
edit events.png ‏27 KB

LabVIEW 8.6.1 Project causes slow Open VI Reference

I have an odd problem with "Open VI Reference.vi".
Case 1.
Open LabVIEW project containing "Main.vi"
Open "Main.vi"
Run "Main.vi"
Execution of "Open VI Reference.vi" take about 2,000ms
Case 2.
Open "Main.vi" - No LabVIEW project open
Run "Main.vi"
Execution of "Open VI Reference.vi" take about 100ms
I converted the project to 8.5 and the problem goes away. I don't have any machines with 8.6.0 to test if this is an issue with 8.6.1 only.
Has anybody else seen something like this?
Solved!
Go to Solution.

Good catch on the type def. It turns out that this is also key to the problem. I cleaned up my example VIs, removed the Type Defs and OpenG VIs. When I ran the cleaned up VIs the problem went away. So, I added a simple type def back to my called VI and the problem was back.
You misunderstand the reason for including gmath into the project. This has nothing to do with the time to load the project from disk. The problem is slow execution of "Open VI Reference.vi" when opening VIs that contain TypeDefs that are in large projects. By including gmath I was able to create a large project without attaching extra VIs.
Open Reference Test - No Project: 11 ms
Open Reference Test - small Project: 105 ms
Open Reference Test - large Project: 753 ms
Code in Zip file is LV2009
Message Edited by Gleichman on 08-21-2009 06:36 PM
Attachments:
Open Ref Test - II.zip ‏62 KB

Open VI Reference LAN Help

Hi!
I have a LAN/TCP connection. On the side A, I have a simple VI, and I would like to call it from side B. How can I do that?
+++ In God we believe, in Trance we Trust +++
[Hungary]

Hi Durnek,
The best is to use the Application Control palette, create a VI server on side A, on side B open a reference to the VI server with Open Application Reference Function, then you can access the VI with Open VI Reference and using the Invoke and Property nodes from the same palette you have access to a lot of information and settings.
Let us know if you have more questions!
Have a good day!
Patricia

Open VI reference in RT

I'm opening dinamically some VIs with "Open VI reference" on a FieldPoint 2210.
I did it many times with 7.1 and 8.2, but now with 8.6 i get error 1124:
LabVIEW: VI is not loadable.
In a built application, this error might occur because the VI being loaded was last compiled for a different OS, in which case you must save the VI on the current platform. [then it talks about polymorphic VIs, but i'm not using any]
But the VIs are under the FP target in the project, have been saved for 8.6 and work on RT when launched directly from the project.
The problem is the same if i call Open VI from an exe or from a vi.

Make sure that you've installed the latest Fieldpoint driver sofware available. I also had the problem that a VI was not loadable when inside the exe, but worked OK in dev mode.
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Win SDK function conflict with CVI library function

I do not have SDK_CONFLICT_PRIORITY defined. Is this new to CVI 2009?
The following code gives me an error "11, 58   Too many arguments to `CVI_WriteFile'."
#include <windows.h>
#include <formatio.h>
void function (void) {
    HANDLE hHandle = INVALID_HANDLE_VALUE;
    char buffer [1000] = {'\0'};
    DWORD dwWriteCount;
if (!WriteFile (hHandle, buffer, 5, &dwWriteCount, NULL)) {
I have included <windows.h> before <formatio.h> but CVI still wants to use the formatio version of WriteFile - it appears to have been renamed CVI_WriteFile ?!?!?
If I eliminate the #include <formatio.h> it compiles OK.
Message Edited by menchar on 03-06-2010 04:00 PM

Well, the complete source for formatio.h I reported before is this one:
#ifdef _NI_mswin32_
extern int CVIFUNC      cviprefix(CloseFile)(int handle);
extern int CVIFUNC      cviprefix(OpenFile)(const char *filename,int rd_wrt, int action, int bin_ascii);
extern int CVIFUNC      cviprefix(ReadFile)(int handle, char *buf, int count);
extern int CVIFUNC      cviprefix(WriteFile)(int handle, const char *buf, int count);
extern int CVIFUNC      cviprefix(SetCommitMode)(int commit);
#define CloseFile       cviprefix(CloseFile)
#define OpenFile        cviprefix(OpenFile)
#define ReadFile        cviprefix(ReadFile)
#define WriteFile       cviprefix(WriteFile)
#define SetCommitMode   cviprefix(SetCommitMode)
#else
In the header this warning is present:
/* This header must be included after any Windows SDK header or any header */
/* that directly or indirectly includes a Windows SDK header.              */
/* Some of the function names conflict with Windows SDK functions.         */
As far as I can understand (but I'm not an expert on these very technical and tricky aspects of C) first of all CVI functions are renamed CVI_xxx, after it a call to WriteFile or any other function in that group is defined to be translated to CVI_WriteFile, so when you call WriteFile the preprocessor actually translates it in the CVI version of the function and SDK one is superseded.
My understandment is that if you undefine WriteFile, you can actually use both functions if you want: native CVI one by calling CVI_WriteFile and SDK one by simply calling WriteFile.
...or I can be missing some other hint, which can surely be possible!
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Possible name conflict flex - java

I have a string property 'comments' in data object A, it was working fine that the data was passing from flex to java, then because of some other properties in A, i need to add @XmlType and propOrder for A, then suddendly 'comments' is always null from flex to java, when other properties are passing ok, after many attempts, i change the property name from 'comments' to some other name and it works again (actual value is passed from flex to java).
So i am wondering, is it flex, web services, or jaxb that might have a name conflict with 'comments'? I have another property in A that also is null from flex to java, but this one is complex object that has a string property and a byte[] property, and it is null, does anyone have any thoughts/suggestions?
Thanks
Shannon

Thanks Michael, i will take a look. My other property is 'uploadedFile' of a class 'uploadedFile' which has 'data' and 'fileName' properties, so i ended up changing all these names, and now it works.
Shannon

Open Vi reference for Vis with same names

Using VI server, is there any way to open reference to a VI on the hard disk even thought a VI with the same name (but different path) is already loaded in memory? I'm trying to see if it's possible without renaming and making sure every single VI I use has a distinct name.

abdel2 wrote:
For now, I can give different names but as the # of modules increases, it will be hard to have some Vis that don't have the same name.
It wont be tough to keep distinct names.
Just prefix or suffix your module name to the original VI name, so that you SDs will have VIs with same/similar functionality, but never conflict with each other when called during run-time. This is the procedure we follow in our project currently. We have gone ahead with the extent of packing all the DUT SDs (LLBs) into one complete auto-installer, so that in the target PC, everything get unbundled & installed into the appropriate folders that we have added while creating the installer.
- Partha
LabVIEW - Wires that catch bugs!

Why do I get a class conflict between the Prepare SQL.vi and the Get Column Name.vi with the SQL Toolkit compatibility vis from the Database Connectivity Toolkit?

I have done extensive programming with the SQL Toolkit with LabVIEW versions through 6.1. My customer now wants to upgrade to Windows 7, so I am trying to upgrade to LabVIEW 2009 (my latest purchased version) using the Database Connectivity Toolkit, and the SQL Toolkit Compatibility vis. Everything seemed to be going okay with the higher level SQL operations, but I ran into trouble with the Get Column Name.vi.
The pictures below show the problem. The original SQL Toolkit connected the Prepare SQL.vi with the Get Column Name.vi with a cluster of two references, one for connection, and one for sql. The new compatibility vis have a class conflict in the wire because the Prepare SQL.vi contains a cluster with connection, and command references, but the Get Column Name.vi expects a cluster with connection and recordset references.
How do I resolve this conflict?
Thank You.
Dan

I've never worked with the old version of the toolkit, so I don't know how it did things, but looking inside the SQL prep VI, it only generates a command, and the the column name VI wants a recordset. I'm not super familiar with all the internals of ADO, but my understanding is that is standard - you only have the columns after you execute the command and get the recordset back. What you can apparently do here is insert the Execute Prepared SQL VI in the middle and that will return what you need.
I'm not sure why it worked before. Maybe the execute was hidden inside the prep VI or maybe you can get the column names out of the command object before execution. In general, I would recommend considering switching to the newer VIs.
Try to take over the world!

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

The action could not be completed because of a conflict with the original item. The conflict may have occurred when an existing item was updated on another computer or device. Open the item again and try making your changes. If the problem continues, cont

I have a user on an iMac 10.6 connected to our domain. She uses Outlook web access for email on our exchange server. Last week she received the following message which is randomly preventing her from sending emails. She claims no attachment was involved in the original email when this all started. I have not been able to look at her account as she is out of the office but maybe someone else dealt with this issue. I realize this may not be Mac related but thought I'd give it a try. She did say it occurred once over two days while working on a PC but it continued over the past weekend.
If an internal user tries to send a message with infected attachment using Outlook Web Access, it may report the following error message: The action could not be completed because of a conflict with the original item. The conflict may have occurred when an existing item was updated on another computer or device. Open the item again and try making your changes. If the problem continues, contact technical support for your organization.
This is because F-Secure Anti-Virus for Microsoft Exchange has detected a virus in the attachment. If the user tries to send the message again, the message will be sent but without the attachment. At the same time a blank message with an attachment named "Attachment_information.txt" will remain in the user's Drafts folder. The "Attachment_information.txt" will contain information about the virus detected in the message.

PS - have found other posts indicating that clips smaller than 2s or sometimes 5s, or "short files" can cause this. Modern style editing often uses short takes ! Good grief I cannot believe Apple. Well I deleted a half a dozen short sections and can export, but now of course the video is a ruined piiece of junk and I need to re-do the whole thing, the sound etc. which is basically taking as much time as the original. And each time I re-do it I risk again this lovely error -50 and again trying to figure out what thing bugs it via trial and error instead of a REASONABLE ERROR MESSAGE POINTING TO THE CLIP IT CAN'T PROCESS. What a mess. I HATE this iMovie application - full of BUGS BUGS BUGS which Apple will not fix obviously, since I had this product for a few years and see just hundreds of hits on Google about this error with disappointed users. Such junk I cannot believe I paid money for it and Apple does not support it with fixes !!!
If anyone knows of a GOOD reasonably priced video editing program NOT from APPLE I am still looking for suggestions. I want to do more video in future, but obviously NOT with iMovie !!!

Need to Install Safari 6.0.2 on a white Intel core duo iMac. Had to throw out 6.0.3 because of conflict with required software. Downloaded wrong version that was for Mountain lion (I am running 10.7.5). It installs but won't open.

Need to Install Safari 6.0.2 on a white Intel core duo iMac. Had to throw out 6.0.3 because of conflict with required software. Downloaded wrong version that was for Mountain lion (I am running 10.7.5). It installs but won't open, says it is for Mountian Lion.
Of course I can't throw it away since I get a message it's part of the sytem. I can show package contents and throw those away, but evidently not a good idea!!

Need to Install Safari 6.0.2 on a white Intel core duo iMac. Had to throw out 6.0.3 because of conflict with required software. Downloaded wrong version that was for Mountain lion (I am running 10.7.5). It installs but won't open, says it is for Mountian Lion.
Of course I can't throw it away since I get a message it's part of the sytem. I can show package contents and throw those away, but evidently not a good idea!!

VI Name conflicts with "Open VI reference"

Similar Messages

Maybe you are looking for