It is also outlined in part here and here. This has all been outlined in our BIM manual under the Collaboration section. This forces your local data to rebuild from the server data on the next open/join. The first step in doing this is to periodically leave the projects you are working in. It is critical to keep your local data clean and current. This entry was posted in Attributes, Libraries, Local Data, Teamwork and tagged Error Messages, Teamwork on Octoby wwabim. Send and receive often, every hour at a minimum, to prevent loss of work should ARCHICAD get caught in a cycle of teamwork errors.Any time you plan to be away from your desk, and periodically throughout the day, even while working on the file. If someone else has that attribute reserved, request it before creating new attributes. Always reserve the attribute type you are working on or creating a new attribute for before creating it.These are measures you can take to prevent this from happening in your projects: Now for prevention of this teamwork error. This is definitely a worse case scenario, and should only be done if release all (by all team members) and send and receive does not work. pln, force quit, and kick them out of the file, so that other users can send and receive. When things get this tangled, we normally have to save someones local data to. Users B/C/D can not send their modifications, because User A has the attributes reserved. User A can not release attributes, because Users B/C/D have modified those attributes. At this point, ARCHICAD is caught in a catch 22 situation.

This gets complicated, however, if multiple attribute types are reserved, and modified, all by different users. Also, with regards to attributes, if one team member has an attribute type reserved, the other team member creates a new attribute, they will not be able to send their changes until the first team member releases that attribute type. If one team member reserves the entire embedded library, and another team member loads an image or object to the embedded library, this can block the user who made the modifications from sending and receiving changes. Two examples of this are the embedded library and the attributes. This error happens when one team member has a portion of a file reserved, and another team member modifies a subpart to that. It is not always easy to fix, depending on how many people are in the project. This is a common error in our daily teamwork operations, and an easy one to prevent.

Bim server archicad