I have a colleague who cannot load my R14 dwg. He works in 2006 and my dwg is R14. He provided me with the base info which I converted to R14 and then I added some information to his drawing as well as some details that I use regularly. Ever since I worked on his drawing he can no longer load it in 2006. It gets so far and then crashes.
We have done work before like this and its never caused a compatibility problem.
I sure would like some help if anyone can figure out what might be causing this as I am at a complete loose.
And a new development just happened as I was writing this. It happened again with an entirely different person and a different project. I worked on their drawing for a bit after which they were unable to load it as AutoCAD would crash at about 87%. This is the second time in as many days. I'm starting to get really concerned. I think there must be a bit of corrupt info inside the dwg file but I don't have the ability to look inside the dwg file to sort out what's causing this.
Have they tried opening the drawings using the Recover command? I used to run into something like this on R14 drawings coming from our MEP guy...
Yes I tried recovery using R14 as well as R2006. I purged the drawing in R14, did an audit and finally did a write block to make sure it was absolutely clean of any unused info.
It made no difference at all. Nothing seams to work to get rid of the problem. I just had another consultant who is using R2009 say he can't open my drawings as well. I sent it to another associate using R14 and R2000 and they had no problem at all.
Have you tried starting writing the entire drawing to a block?
Yes I tried that. I used every conceivable means to eliminate whatever is in the drawing file that might be causing the issue. I even did audits on the newly created drawings from write blocking... Nothing.
Some time ago a fellow by the name of Art Cooney on the R2010 forum spent some time analyzing an R2010 drawing of mine that wouldn't convert down to R14 without R14 crashing everytime it tried to open it. He found there was an element in the file that I assume was corrupt and it kept causing R14 to crash. I also assume this is the same kind of thing. There is something in the drawing file that is corrupt and R2006 crashed when it sees it. I just don't know how to find it. Or maybe of way off base I just don't know. Very frustrating.
Are you saying the same drawing opens fine on some machines but crashes on others?
I'd suggest opening the problem file in R14 and creating a fresh drawing in 2006 (make sure the template isn't corrupt). Then with both versions open, copybase and paste one portion at a time from the problem drawing to the target drawing. You may at least be able to narrow down which object or objects is/are causing the problem...
No, it has nothing to do with what machine is used but it does have an issue with R2006 and R2007 as it crashes on both versions. I cannot speak to any other versions (except R14 and R2000) as I have not had anyone try and load it on anything but R2006 and R2007.
One thing I just noticed, and I don't know if this is relevant, but I get a message when doing a save as "Warning about a multiplier for handle AD07, AD14 and AD21". I don't know what that is.
I am not familiar with that. Have you tried my other suggestion?
Please find attached the drawing that started all of the problems.
It also appears that there are several other drawings prepared in R14 that cannot be opened by other cad operators using R2006 and just as recently reported to be unable to open in R2009.
I have been trying to remove sections of the drawing to isolate what might be causing the problem but I haven't been able to narrow it down yet. Now with the discovery of several other drawings not able to be opened and being totally unrelated in content ... this is causing a major concern.
I really hope someone can pin down what it is that is causing this. The other operators report that at a certain point in the loading, the amount of ram usage all of a sudden triples and quadruples almost instantly and then the crash occurs.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register