plan file becomes corrupt for no reason.

[Anonymous]

does anyone else have the problem of their plan files becoming corrupt for no reason and randomly? I can save a file then try to open it later and it says that the file is damaged or corrupt.

Any help?

I'm on an all Mac network running 10.4.x however the server is a "Snap" brand server.

Thanks

[Anonymous]

File corruption is very rare (in my experience.) If you are experiencing it often then it probably is a problem with the network or server. Try working from your local drive for a while and see if the problem continues.

[KeesW]

We are also having serious file corruption issues. However, the problems only occur on a couple of projects and therefore seem more likely to be caused by a faulty library object. We use lots of add-on libraries and our next task is to find the defective object.

[KeesW]

We are also having serious file corruption issues. However, the problems only occur on a couple of projects and therefore seem more likely to be caused by a faulty library object. We use lots of add-on libraries and our next task is to find the defective object.

[Anonymous]

KeesW wrote:
We are also having serious file corruption issues. However, the problems only occur on a couple of projects and therefore seem more likely to be caused by a faulty library object. We use lots of add-on libraries and our next task is to find the defective object.

Are you unable to open the files or are you getting errors or having other problems with files once they are opened?

The former is typical of file corruption, but, as far as I know, cannot be caused by problems in library parts. It is possible (though rare) for a library part to create an endless loop that will freeze the program, but only after the file is opened. Other library part errors usually generate messages that are often helpful in identifying the cause.

It may be that add-ons created with the API can cause file corruption since this provides deeper access to the workings of the program. Others more familiar with the API can probably speak more to this.

[Karl Ottenstein]

I concur with Matthew... library parts cannot cause corrupted files.

Personally, I've never had a file get corrupted (knock on wood), even with beta versions.

I could be a non-major 3rd party add-on (i.e., one not from Cigraph or Cadimage or Encina or the few other well-known developers) I suppose...

Seems unlikely that it is a server/network issue since if it is actual data corruption, the file shouldn't even be readable...

I recommend that you contact tech support and they will explain how to send (ftp) the corrupt file to them for analysis.

Karl

[KeesW]

Thanks for the advice. I do use a few add-ons. If libary objects can't cause crashes, it could be one of those. I have already contacted tech support and they're looking into it.

[KeesW]

I had another two crashes yesterday and it reminded me of why I thought a library object might be responsible. When it crashes, it closes down completed - suddenly and without warning. Sometimes it happens when saving, at other times when working on the roof. When it crashes, I get the Graphisoft Bug report - which I complete and post to Graphisoft (no they haven't tracked the cause yet).

When I restart, I get the option to open the emergency restored copy of the file I was working on at the time of the crash. Accepting this choice, the program reloads and gives me the warning "error while loading plan file - continue or stop". It also indicates that there is a problem loading a module: library. Whichever option I choose, the file loads, and having done so, it is completely empty!

I am now saving manually more frequently and continue the project using the most recent backup - until the next crash!

I hope that Graphisoft sort it out soon!

[Eduardo Rolon]

See if this helps, it is old but it worked to figure out what was causing the crashes

archicad-talk.graphisoft.com/viewtopic.php?t=3784&start=0&postdays=0&postorder=asc&highlight=merge

[Djordje]

Are you by any chance using any original 7.0 library parts? This might be it ...