NI_FileType.lvlib location conflict

We're seeing a bit of a strange problem - I wasn't sure whether to place it in the TS discussion forum or here. Anyway, we have a sequence file (TS4.0) that contains a number of calls to LV8.5 VIs. When logged in as technician, we'll run some tests, and we'll get an error message saying "Error Message: LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located...[Error Code: -18002]. I know this sounds simple - just go fix the broken code dummy. However, if we log in as Admin, the problem is not there. Then, if we log back in as Technician, the problem doesn't appear. Now this doesn't always happen, but it happens enough that we can't send this out to our customer like this.
One of our guys did some digging and he said, Even though the error is seen in TestStand upon loading this particular VI, it appears to be traceable to NI_FileType.lvlib and more specifically to the GetFileType.vi contained therein. The issue might be deeper than this. It appears the libraries "C:\Program Files\National Instruments\Shared\Variable Manager\dialog (and/or dialogs)\NI_FileType.lvlib" and C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Utility\lvfile.llb\NI_FileType.lvlib" can "mirror" each other as attempts to load various polymorphic LV vi's (including check if file exists.vi) periodically leads to cross loading (i.e. loading from an alternate location when I start them up even on my office PC).
I'm wondering if anyone has seen anything like this, or knows a way to specify that LV use a particular version of GetFileType.vi

Hi mrbean,
Most likely, NI_File Type is being called from both locations in your application. This may be because you pulled the VI from different locations in the functions palette. You can check the path in Project Explorer (Project >> Show Item Paths). You can also right-click on the NI_File Type and select Find >> Callers. If, indeed, there are different paths for the same function. Try replacing the VI so they all call the same path. I hope this helps!
Kristen H.

Similar Messages

Image Server location: conflicting instructions

Plumtree Corporate Portal v5.0.2
The Enterprise Web Development (EDK) guide says on page 19-18 to use the following folder structure for storing custom images, stylesheets, etc.:
<ROOT>/<domainname>/<productname>/private or public/help or img or js or styles or custom/
However, the UI Customization Guide says on page 4-20:
[The designated] location is \ptimages\imageserver\plumtree\portal\custom\img(in a standard portal installation).
Which is the best practice?

Here is what I do and find it very easy to manage.
{drive}:\BankersbankImageServer\<product>\[<public>|<private>]\[img | js | help]\
It then create a virtual directory under the imageserver virtual directory in IIS that points to BankersBankImageServer. This way, my files are not in any danger of getting distroyed when I do an upgrade of portal. Of course these files are on the imageserver machine. It also follows the recomendations of the EDK and UI Customization guide.
Michael [email protected]

Flash CS5 location conflict with dreamweaver

upon instaling flash CS5 is not allowing me to save changes i made on dreamweaver. there is this msg saying it will stop my dreamweaver communicating from a remote location and when i click on settings, it does nothing. it stop me from updating my website. did some reasearch, many place suggest to go on to the adobe website storage settings panel. not sure how to use it but it seems like i have to entrust every single page of my website to the list as a trusted site in order for it to work. and i test it on one page and it didnt seems do anything.

My two A's '(Apple and Flash CS5) stopped struggling. It had nothing to do with Indesign... it was just a problem of permissions. Why it happened I do not know. The only constatation I dare to make is... Guys from Adobe... you put the right diagnosis... thank you,thank you very much....
Permissions that's all!!
Sniff11

LR4.2 - Error when moving files

I can repeatedly reproduce an error when moving files into folders within LR4.2.
My current folder structure is setup like:
F:\pictures\YEAR\Folder name\Sub folder\
When I'm moving files from "Folder name" to "Sub folder" I will be moving approx 6 - 20 photos at a time when sorting them into sub folders. After a while of moving files, LR will stop allowing you to move files and will show up the O symbol with a line through it. Until you close and re-open LR will it allow you to start moving photos again.
I've had this happen 3 times on me now and is completely reproducible. As above, move a small amount of files from a parent folder into a child folder repeatedly and eventually it will refuse to move any more photos until you restart LR.
Windows 7 x64 SP1 Professional
Intel Core i7 950 3.07Ghz
24Gb DDR3 Ram
Nvidia GTX470 Video Card
Intel 520 Series 240Gb SATA3 SSD
Lightroom 4.2 x64
Catalog recently optimised with no issues ever experienced with the catalog.

Hi,
I experienced the same problem and error message this morning ...and found that the following steps will resolve the error (at least when using LR 3 on a MAC):
(1) Open LR and rename all the files that you are trying to move by hitting the F2 button, (MAC shortcut)
(2) Look for any images that may have a '?' mark next to them and resolve if required. (The '?' indicates a file 'location' conflict within the catalogue, - ie you may have moved the files around outside of LR)
(3) While still within LR ....highlight all the files that need to be moved ....and drag and drop them into your preferred new location in the usiual way.
Hope this helps.
Cheers
Simon

I often receive photos as attachments to emails.s there Ian easy way to save them directly to Photoshop Elements? Or do I have to save and then import?

Is there an easy way to save them directly to Photoshop Elements? Or do I have to save and then import?

Well... I appreciate both of your responses. However... I believe that lvlibs cause more frustration then anything else. My team has come across issues with lvlibs and conflicting paths (when using CM tools) and have resorted to using LLBs because they offer a clean set of file dependencies. I understand that lvlibs are probably more robust, but they are not an option right now. Therefore... the question I originally asked still remains. Is there a quick and easy way to add a bunch of VIs to an LLB without having to save each one of them separately to the LLB?

Error 7: File not found for executable

Hello all,
I have a problem with a VI server call. I am currently using LV 2011 on Windows 7. Here's the problem - I have a subpanel in a larger VI into which I drop the interface of a (potentially) stand-alone VI. The path to the called VI is good (in both the exe and in the development application). However, I am getting an error 7 when I try to use the "Open Config Data.vi". More specifically, I am getting the description that it can not find the VI in the library Load.vi (called by Open Config Data). I have tried specifically adding the whole config library into the build, but this does not seem to help. Also, the config VIs are called in the main application with no problem. Does anybody have any thoughts?
Thanks, Matt
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC
Solved!
Go to Solution.

OK - so maybe my description was not so great. First - I know that the file paths are good because when they are not, the VI run dynamically in the subpanel via a VI server call will not load (there will be nothing in the subpanel). In this case, it loads and is running (can check this through debugging). Second, the error is occurring in both the exe and in the development system. The absolute path (although this is not an issue - see previous comment) is not possible given that this is built into an installer and deployed on other platforms (on which the directory structure is not necessarily duped). And finally, the VI that is loaded dynamically is already in the "always included". I don't have a problem calling and running this VI, the error crops up when I attempt to use "Open Config Data.vi" in that is called by that VI. This VI that is not loading (Load.vi) is located in the NI library NI_LVConfig.lvlib (located on the disk under the folder vi.lib). I currently have a workaround for this, but it is not the best (a pop-up dialog comes up that allows the user to configure everything from the UI rather than from the config file).
One thing that may help that I neglected to mention is that, in the development environment, I can run the calling VI one time and I get the error. However, in subsequent runs, I do not get the error.
Thanks for all of your responses. I hope this further explanation helps.
Cheers, Matt
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC

K7N420Pro memory upgrade doing strange things

i just recently upgraded from 2x256 in slots 1/3 to 2x512 in the same slots. memory is at a low now (US$75 per 512), so i thought might as well. both before and after rams are kingston made, and certified on the nvidia website. the only difference is that the 256s were USA manufactured, and the 512s were taiwan made. both rams non-ECC.
since changing memory i've experienced 'strange things'. sometimes windows does things i never intended. it created a shortcut by itself, right before my eyes, and i swear google did a search for some gibberish phrase without my intervention. last night i experienced my first win xp blue screen (i thought the blue screen was obsolete?!?). can't remembered what exactly it said, but i believe to be some memory location conflict.
my BIOS is set to high performance and i din't change anything before and after upgrade. i din't activate any shadowing or chaching in memory that i'm aware of. auto precharge on, cl 2.5 as rated by my ram.
if anyone can offer advice please do!
setup:
athlon xp 2000+ w/ amd issue fan
k7n420 pro bios 2.4
2x512 kingston ddr ram (kvr266x64c25/512) slots 1/3
msi geforce 4 ti 4200 64mb agp 8x
terratec dmx 6fire 24/96
philips 17" dual crt monitors

thanks for the link to the software!
Quote
Hi performance settings mean X, 2, 2. (X is the CAS setting, set in BIOS).
what do you mean X,2,2? is it something i need to set in memtest?
Quote
If you have errors in memtest, try default (and change the rest of the options back to your settings).
i did not get errors after 1 pass with default test setup. i guess that is ok?
Quote
also, what is your power supply? i see you have a XP2000 plus a GF4. If you were just marginally supplying your RAM a bigger bank could cause instability.
i run a 430watt enermax.
well since i last posted, i removed and reinserted my ram into their slots as i had a feeling i din't do it properly the last time (gfx card got in the way). so far no strange glitches, keeping my fingers crossed.
will cooling the ram with a heatsink help stability?

Metadata conflict: Doesn't show location data

Hello there,
I imported some pictures to Lightroom and edited them there normally. After closing lightroom I edited the location information via GeoSetter (www.geosetter.de). Looking at the images via ACDSee, I see correctly entered City, Sublocation, Procince, Country Code and Country Name in the IPTC data.
Firing up Lightroom 2, I do not see these metadata changes, location fields are all empty. So I click on Synchronize folder and synchronize Metadata. Lightroom now gives all images a Metadata status of "Has been changed". When I click on "Resolve conflict", the location data still is not shown, but actually the location data is deleted when looking at the image again via GeoSetter (or ACDSee) - basically the Lightroom-state-of-things (no locationdata) has been restored I guess. Ok, moving on.
I go back to GeoSetter and reset the location to where it should be, click on synchronize metadata in Lightroom again and the Metadata status is "up to date" - no "resolve conflict" possible, the problem now is:
The location data is STILL in the IPTC fields, Lightroom doesn't show it though, location fields are empty and stay empty even after synchronizing, or Lightroom deletes it as previously stated.
What is the correct way to edit metadata externally and how to tell Lightroom to resolve the metadata conflict by ACCEPTING the external changes and not reverting to the status quo?
Sincerely,
Dennis

>will this method not revert any prior changes made to the images? (e.g. Crop, Keywords, Local Adjustments).
It will, which as you have already figured out, isn't a good idea.
I don't know anything about Geosetter, but my guess is that it's writing the data back into the original photos. Unfortunately, Lightroom doesn't see these changes when Sync folder command is used because it's looking for a Metadata Change date, which is normally stored in XMP. There is a workaround though.
You haven't mentioned the type of files that you're working with, but I'll assume they're raw. If so the workaround is to use the Lr "Save Metadata to file" command before working on them with the external application (Geosetter). This will create an XMP file for each photo that contains all your existing metadata plus any Develop adjustments. Now you can save the new IPTC back to the files using Geosetter. Once that part is completed you can use the "Read Metadata from file" command knowing that all your original Lr metadata and develop adjustments will be copied back along with the new IPTC info.
Above also works with JPEG and TIFF files

IOS8 iMessage Location Share Conflicts with Find my Friends

In iOS 8, when I try to delete iMessage threads from people who follow my location in Find my Friends it always pops up a dialog asking if I want to stop sharing location. This would make sense if I initiated the sharing in iMessage but I didn't. It's a pre-existing location share from FMF.
Driving me crazy.
Even persists after factory restore.

My problem was as described by DavidHeady on 11-7-2014. In Find My Friends > Me, the Share Location slider was ON, but grayed out and unresponsive. Here's what it took to fix it on iPhone 6, current OS: Settings > General > Reset > RESET LOCATION AND PRIVACY. Both the Reset choice and Reset Location and Privacy are at the bottom of their respective pages (iOS 8.1.3). Of course you then have to go to all the appropriate places and enable Location Services, Share Location etc.

Somehow my iTunes library or libraries got messed up - songs missing, can't be located, don't exist in locations Spotlight says they do, conflict between finder and spotlight, what a nightmare!

I think it be due to choosing "Reset" in Preferences/Advanced/iTunes Media Location" some time ago. Do I need to rebuild the whole finder/spotlight thing and if so, how?

Thanks a lot for no response I discovered Disk Utility.

Save As... Duplicate lvproj file doesn't work correctly with lvlibs/lvclasses

I am trying to save a copy of a project with all dependencies so that I can sent a subset of our code to NI technical support for another issue. I have been unable to do this successfully and have isolated this to limitations of "Save As..." --> "Duplicate .lvproj file and contents (Include all dependencies)" when handling lvlibs and lvclasses. I am wondering if I am doing something wrong or if there is a workaround.
I am using LabView 8.6.1 under Windows. A sample project displaying this issue is attached. To repro the problem I am having,
Open library.lvproj. This is simple project with one library (SimpleLibrary.lvlib) and two VIs that are member of that library. (Add.vi and Subtract.vi).
File -> Save As... -> Duplicate .lvproj file and contents (Include all dependencies)
Pick a new location in your filesystem somewhere.
The save starts, then LabView puts up a dialog box "Cannot save library 'SimpleLibrary.lvlib'. Another library in memory is already loaded from that path." (Note that this is not true; the library is loaded from the original project path; nothing has as of yet been saved to the new project path.)
LabView it gives you a file dialog in the target location. If you click OK (opting to save it to the new location in the same relative path as in the original project), it returns to the "Cannot save library" dialog box. If you create a new folder (i.e. "New Folder") in the target and descend into the target, then the save is allowed, but when you re-open the project it looks for the library at the old location (relative to the new copy of the project), and it opens it as conflicted. The conflicts must be resolved manually.
The manual move-and-unconflict process is tolerable with a simple project containing one library, but it is impractical in a large project with dozens of lvlibs and classes.
Can anyone suggest a workaround for this behavior so that a project can be exported with all of its dependencies and without path corruption?
Thanks,
Rob
Message Edited by Rob Calhoun on 08-24-2009 03:10 PM
Attachments:
libraryproject.zip ‏9 KB
cant-save-lvlib.png ‏7 KB

I loved Ben's suggestion because it promised to be a low-effort workaround, but, alas, I get the same problem: "lvlib is already loaded from this path...".
I tried Olivia's workaround for CAR 124214. It worked great for the simple lvproj that is posted above. (Hooray!) It didn't work so well in my real project, that has about 30 lvlibs and lvclasses. About 3/4 of the way through the save, I got a compiler error and LabView crashed. (Boo!) I submitted the crash log on this, but it's hard to imagine how anyone in R&D could make any progress debugging this without the source code. (And I can't submit the source because I can't export a copy of it!)
Anyway, thank you very much Ben and Olivia for your suggestions. I have lvclasses embedded in lvlibs (primarily for organizational reasons) and since LabView tanked while saving one of those, perhaps the workaround doesn't work in this case. I may try again after removing the lvclasses from the lvlibs so that the hierarchy is flatter.
-Rob

Is there a trick to moving classes without causing project conflicts?

I've been using OOP for a few months, but I've been frustrated a handful of times trying to move classes. With other files, I just go to Files View, and right-click "Move on disk" which has always worked great.
But if I try to move a folder containing multiple classes, or classes nested into subfolders, the project FREAKS out. It's almost like LabVIEW is moving files one at a time, but not updating all the other classes about new locations of methods, dependencies, etc. So it moves something out of order and then all the classes that relied on that file freak out, wondering where the file went.
Then about a thousand individual warnings pop up, and I can't dismiss them all at once. Also, conflict resolution fails to work because LabVIEW's confused about where files loaded in memory are now located on disk.
I've had to do source control reverts on my entire workspace to get back into a working condition. Then I usually have to move the classes over one at a time, which is a painful and frustratingly slow process.
Am I doing something wrong here?
http://linkd.in/mikele
Solved!
Go to Solution.

I have run into similar issues before. The project and library files are just text. I have moved things and edited the pathes in the project/lvlib file. Can also use a save as on the library file. Your move turns into a copy and rename operation.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Reference conflict project

LV2009: if I try to use a linera algebra function in a new VI in a new project, it produces a huge amount of dependencies to totally remote VIs in several other llbs and lvlibs. I guess these are linked to some of the other more complex VIs in NI_AALBase.lvlib and therefore appear as dependencies, even if I am not actually using them.
It seems that at a certain point of time I have messed up one of these now unused VIs by saving it with a reference to a copy of a linear algebra VI in an application distribution that I generated once.
As a consequence, every time I open any of my VIs that contain whatsoever linear algebra VIs, a conflict warning pops up, showing me a certain conflicting linear algebar VI in the path of my former distribution (which is not existing any more). The conflict appears also transiently in the project tree and vanishes if I close the warning message. After that, everything is fine.
As the conflicting item is removed from the project tree immediately, I cannot locate where the problem is.
Any ideas how I could find the damaged VI that refers to the "wrong" linear algebra function ?
Thanks,
Dirk

Hello Dirk.
Please reinstall LabVIEW.
Ulrich
AE NI-CER

Resolving LabVIEW Conflicts

Hello,
I recently converted to labVIEW 2012, and I'm trying to clear up conflicts in my project. The problem I'm running into is that when selecting a conflict there are no options available to remove the item from the project. Further the conflicts are dependencies and aren't physically on the C drive. Any advice on how to proceed is appreciated.
-Bob
Let me share some screenshots:
The first of several conflicts is the Agilent 86100 Series.lvlib conflict as shown in the Project Explorer window. The path shows that the file is located on the C: drive. In fact the file does not exist at the specified path.
Then using the Resovle Conflict dialog I get this screenshot, which shows the conflict is the same file showing up on the T: drive as well as the C: drive. The file does indeed exist on the T: drive, but not on the C: drive. The problem is that I have no options for removing the C: drive reference from the project. All options are either not there or grayed out.
Thanks for the help.
Solved!
Go to Solution.

Sometimes you have to solve "sub-conflicts" (for lack of a better term) in order to resolve other conflicts. From your screen shot, it looks like you can resolve some of the conflicts. Once you get those resolved, maybe you can resolve the others.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Move things to lvlib

I am creating a folder structure of code that I copy from another folder. Both folders reside on the same PC, so I thought I would put everythign in the new folder in a lvlib to avoid naming conflict. When I tried that, it didnt' work. Some subfolder would refuse to get into the lvlib. There is no error message, so I don't know why. What is the best way of doing what I want to do?
Kudos and Accepted as Solution are welcome!

Lets take the easilly reproducable case of a pair of instrument drivers -Plug-n-Play (Project style).
Call them "ABC.lvproj" and "XYZ.lvproj" and locate them in seperate folders inside <LabVIEW>\Instr.lib\
Each driver project contains a lvlib The lvlib members know they belong to a lvlib (and their scope- but thats not important here)
Assuming each driver has a "Initialize.vi" (no real stretch there) "ABC.lvlib:Initialize.vi" and "XYZ.lvlib:Initialize.vi" are located at different disk locations and have different fully qualified names. Code within "Test.lvproj" will know they are different and load both dependancies.
Project Templates let you protect the fully qualified names too. Creating your project template with good use of lvlibs (like you see in the examples) helps but is only part of what you buy with your own template project. When creating your "use projects" from template you get to add to the namespacing. Lets assume your template project contains some semi-reuse code like "Display Time.vi" that you might want to appear slightly different in each project you create. The project creation wizard helps by allowing an optional prepended rename. So, "Display Time.vi" scripts out to the new project as "TestX_Display.lvlib:TestX_Display Time.vi on TextX_Test.lvproj/My Computer" assuming you just created "TestX_Test.lvproj" from template and "Display Time.vi" is a member of Display.lvlib on your template "Test.lvproj" and is targeted to My Computer.
That "Fully Qualified Name",TestX_Display.lvlib:TestX_Display Time.vi on TestX_Test.lvproj/My Computer, is hard to mistake and not likely to exist in "TestY_Test.lvproj"
I probably could have been clearer. But, you can avoid creating projects that have vis with identical Fully Qualified Names but different code.
Jeff

NI_FileTyp​e.lvlib location conflict

Similar Messages

Maybe you are looking for

NI_FileType.lvlib location conflict