Can't save to older LLBs

[sth]

I have a bunch of LLBs from various versions of LabVIEW. When upgrading to version 8.0.1 I get an error in trying to save an updated VI to one of these LLBs. This happened for some LLBs that I got from a manufacturer that are very old (ie LV 5 or 6) and some are ones that I have successfully updated to a more recent version. The attached LLB file if you open it and try to open some of the contents. If you then try to save them, you will get an error "Duplicate path. Cannot save VI "LogWrite.vi". LabVIEW Save error code 48: Could not move temporary file to destination.

If I try to mass compile the LLB, I get an error 10:
#### Starting Mass Compile: Fri, Nov 3, 2006 15:12:05
Directory: "sthMac:Users:sth:sth-nhmfl:LabView Info:Bugs:Bug Examples:LV 8.0.1:Can't save old LLBs:LOG-8.0.1.llb"
CompileFolder: error 10 at sthMac:Users:sth:sth-nhmfl:LabView Info:Bugs:Bug Examples:LV 8.0.1:Can't save old LLBs:LOG-8.0.1.llb
#### Finished Mass Compile: Fri, Nov 3, 2006 15:12:05

This problem persists in LV 8.20, in fact one library (the PID toolkit, so I can't post it), I successfully updated to LV 8.0.1 and cannot update it to LV 8.20. The only work around is to explode the LLB into files that can be saved.

Mac OS X, LV 8.20 and LV 8.0.1. I have read and write permission to the folders and files involved. They have group read permisssion only. This has happened on several different machines and with both versions of LV.

[Spex]

sth,

Can you attach the LLB?  I have Mac OSX with LV 7.1, 8.0, and 8.20.

Cheers,

[sth]

Sure. I have LV back to version 3.1.1 on my desktop machine. I have actually had 9 versions of LV running simultaneously!!!

One of the problem LLBs is the PID toolkit from NI. I am also attaching one other that is a good example. I usually can open one or two of the vis and close them with saves. But then the third or 4th has a problem. Tell it to ignore the missing vi on one of the sub vis.

Now there is a theory and an active discussion on Info-Labview that this is due to a bad copy of the Tigertools metadata importer. However, I have seen this on a machine with no LV metadata importer. Also I just installed the "fixed" version of the metadata importer that Christina Rogers posted <ftp://ftp.ni.com/outgoing/Spotlight/LabVIEW Metadata
Importer.mdimporter.zip> and can still see the problem.

Just to avoid duplication I have an open SRQ on this, but it has not made much progress. If you can shed some light on this I would be very grateful. This is happening on multiple machines with multiple LLBs. It gives one of two error codes. "Duplicate path. Cannot save VI "blah.vi". Or can not copy temp file to location.

-Scott

[sth]

Alright, the problem is resolved (sort of). The problem is that the LabVIEW metadata importer for the spotlight search engine is not releasing the file so that subsequent saves do not work. NI has posted a fixed version, but I am not sure that it is a public URL but a real fix will be released soon. If you need the new one, ask NI, it has been publicly listed in info-labview.

To remove the Labview MD importer, go to /System/Library/Spotlight and trash the file "LabVIEW Metadata Importer.mdimporter". This is bad that the MD importer is installed in the /System folder. Bad, bad, bad.... If you get the new improved importer from NI install it in /Library/Spotlight folder instead.

The importer and other great tools for using LabVIEW under Mac OS X are at http://zone.ni.com/devzone/cda/tut/p/id/3585.

[Spex]

Scott,

Removing the metadata importer on my machine took care of the issue on my end also.  Any idea why you were experiencing this issue on a machine without the importer?

Cheers,

[sth]

Spex,

YES. Because on most of my machines, I fixed the evil, evil, installation of the importer into /S/L/Spotlight and moved the importer to /L/Spotlight where it should be. On my desktop which is sort of my experimental machine it was still in the default /S/L/Spotlight. I had forgotten that tweak and so when I went looking for it on my desktop it did not seem to be there.

So, yes it actually was installed on my desktop machine. I got fooled by my bad memory. I installed those tools about a year ago.

I think an updated Tigertools installation is in the works by Marc Page(?). Since it is sort of a non-supported feature (though really, really nice) does it get a CAR? What is the protocol here? The importer is fixed, but the installer had a bug (IMHO). Hopefully the new installer will delete any Labview files from /S/L/spotlight and install in /L/Spotlight.

Thanks a lot for your help on this. It nailed down why I was having trouble reproducing the bug at NI!!

Cheers,
Scott

Message Edited by sth on 11-07-2006 02:16 PM

[Roy_F]

This was reported to R&D (CAR # 43F96B3A) for further investigation.

Roy

[sth]

Thanks Roy!

Great, I know there is one other person who is still having severe problems with this and the fix hasn't completely solved it for him. I was told that since a fix was being done there was no CAR but it seemed strange to me!! I'll put it in my database as well.

-Scott

[Travis_M.]

Hello!

For those interested, the fixed version of the utility has been uploaded to ftp site, meaning that you can find it by visiting www.ni.com/mac (the link is toward the bottom of the page).  The update is not quite up on the Apple website yet, but that is on the way.  If anyone needs the old version for any reason, I have kept it available in the same (NI) ftp folder as the updated version.  The tutorial on the utility’s use can be found here.

Thanks to all of you who helped report and fix this problem!

[sth]

Great! Thanks!

Scott