topic Re: Cache Library synchronization error in Libraries & objects

Cache Library synchronization error

owen — Fri, 29 Sep 2006 01:44:21 GMT

We have created a single office library based on the Archicad 10 Library with our custom objects included, stored on the server as an .LCF file. Unlike the AC10 Library we created the .LCF from all the library sub-folders including texture, list template folders etc. We did this as we think its cleaner to have a single file to load as the library rather than a folder structure (as the AC10 Library has) whilst also rendering all contents read-only (yes this could be done with permissions).

We are trying out the local library caching method rather than using software to mirror the LCF to each machine as this will also cache the project libraries.

Occasionally we are getting the following error when something is updated in one of the cached libraries. This error has happened previously on non-LCF project libraries - in that instance it actually lists the specific object it cannot synchronize. I assume an object within the LCF is the cause of the inability to sync the entire LCF.

Can anyone enlighten me as to possible causes of an object or entire library having synchronization errors? File access permissions appear to be ok.

Cache Library synchronization problems:

1 library parts from the source library failed to be updated in the Cache Library:

Name: fjmt Library 10.lcf
Read from: fjmt:Library:CAD:ArchiCAD:Libraries
Write to: Macintosh HD:Users:jredman:Library:Caches:Graphisoft:Local Cache Library

Re: Cache Library synchronization error

Laszlo Nagy — Mon, 02 Oct 2006 21:45:25 GMT

I think LCF files and PLA files work similarly.
I know that Library Objects located within PLA files cannot be updated. You have to extract the PLA file into a folder, change the extracted Library Object, and then again save the PLA. Or, you have to save the modified Library Object file under a new name, but that will be located outside of the PLA file.
I am not completely sure but I thought LCF files worked the same way.
This behavior could be causing your problem.

Re: Cache Library synchronization error

owen — Tue, 03 Oct 2006 10:14:05 GMT

laszlonagy wrote:
I think LCF files and PLA files work similarly.
I know that Library Objects located within PLA files cannot be updated. You have to extract the PLA file into a folder, change the extracted Library Object, and then again save the PLA

Yes this makes sense but I would assume that when comparing the server and local cached libraries AC would understand that in order to update a changed object in the cached PLA/LCF it would need to replace the entire PLA/LCF file? If not then i guess library caching would not work with library containers.

Not sure what to do about this. The problem arose when i updated an object in the office library - now the cached libraries on each machine are out of date and will not update. I guess i could clear out the cache but then if i have to do this everytime it changed it may as well not be cached

Re: Cache Library synchronization error

SeaGeoff — Tue, 03 Oct 2006 16:48:31 GMT

I am following this with interest. I have always found the cache library system to be unreliable and slow. But I have always thought that this should be a feature robust enough to be used as standard practise and hope that it will become so.

I just switched our office (at the time of AC 10 upgrade) from having the entire library on the server to having the bulk on each workstation with a very small office library and any project library on the server. This seems a good compromise that lets me easily add/modify the office objects.

As a side note, I have unpacked the Object Library.lcf so I could eliminate some marker objects and find when loading locally it loads just as fast as the lcf. I think the main advantages of the lcf are it's locked nature and size (if compressed).