ArchiCAD 12 Teamwork File Not Loading
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-05-29 02:49 PM
2009-05-29
02:49 PM
i get an error - input file is incorrect or memory full. I/O Error.
Is there any way I can recover my data. It was 6 hours of work I am losing.
I appreciate your help.
3 REPLIES 3
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-05-31 03:08 AM
2009-05-31
03:08 AM
Try - Quit all archicad(s), delete any .lck files for the PLC and PLP. Disconnect from the server and open you PLC file and locate the PLP manually. Then try a send and receive. Do not try to use any crash recovery files. This sometimes works.
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-06-26 08:27 PM
2009-06-26
08:27 PM
darthblav wrote:I get this error message as well when I'm in teamwork and try to send/recieve. I get these darn cryptic messages and it crashes. I've put numerous posts on this forum about it, asking anyone for help, and no one has any clue what is going on...
i get an error - input file is incorrect or memory full. I/O Error..

You'd think one person might be able to help but...
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2009-08-11 08:33 PM
2009-08-11
08:33 PM
We are having the same issues. There does seem to be a bug in ArchiCAD/Teamwork's Issue that is causing this to occur often. It does seem to be an issues related in some way to memory. The best luck we have had is to restart the computer when this error comes up and have as few applications running as possible while working in teamworks. But it also does seem to be computer related to some degree for us. Three people are working on on specific file, all on the similarly spec'd machine and one keeps on getting this error but the other two are not.