Okay, this is NOT the typical incompatible version error message that our office is experiencing. We are running (3) versions of AutoCAD ... 2010, 2013, and 2014. ALL, I'll repeat that, ALL, are saving down to 2010. Recently we have been getting errors when opening files on the systems running 2010 that the file being opened (or an xref within a dwg) is an incompatible version. Again, being that ALL machines are saving down to 2010, how is this possible?
We have also audited each of those files and found no errors within them, so I don't even think its a corruption issue.
This is driving us nuts! Is there anything else I should be looking at being the problem? Or any idea as to what the problem may be?
Thank you for any input in advance.
In addition to those quetions, I'd also add:
Are you able to manually save it as 2010 and have it work?
Have you verified that the files that are giving you this trouble are actually in 2010 format?
(the thought being that the save down feature isn't working correctly, not that you have it setup incorrectly)
Just a WAG, but the warning may be about AEC content. This has a version, and it is *not* the same as DWG file format version.
In reply to your questions ..
no, it happens not all the time. Just from time to time. Typically we'll find a file with this issue every few days. We are working on a very large project and there are numerous files involved, but every few days one or more files pop up that are creating a incompaitble version error either when opening them, or when being loaded within another file as an xref.
We are using plain ole AutoCAD 2010/12/13/14. No archtiectural desktop, no add-ons, no frills.
The messages we are getting when opening those files are that that file can not be opened as it is a incompatible version. (EXACT wording? .. waiting for the problem to occur to get the EXACT wording, but thats the basis of what we are seeeing.)
And when we have the issue of it not loading in another drawing as an xref, the exref manager just lists it as being an incompatible version.
So it doesn't happen all the time, just sporadically? never the same file? or does it become 'incompatible' forever?
Aer you using Plain AutoCAD 2010/2013/2014, or a vertical?
What is the exact message you get?
If we encounter the error, we can not open it on that particular machine. But the machines running 2013/2014 are able to open it and save down to 2010 thus solving the problem.
And not sure how to verify that the file has been saved to the 2010 format by looking at it .. but we have verified that ALL machines are saving down to 2010 in their options throughout the programs. So that is why we are a bit stumped .... We have even verified that within the etransmit process and such that it is saving down to 2010.
In addition to those quetions, I'd also add:
Are you able to manually save it as 2010 and have it work? Have you verified that the files that are giving you this trouble are actually in 2010 format?
(the thought being that the save down feature isn't working correctly, not that you have it setup incorrectly)
No, the warning is that the file can not be opened becuase its an incompatible version, not that there are AEC objects that may not be compatible. That warning we will get opening certain files created in 2014 and opened on the older 2010 machines, but are still able to open those (of course having had it saved down to 2010 format).
The next time you have this problem, open the problem drawing with AutoCAD 2013/14 and hit F2 to see what format the drawing thinks it is in. If it says it's in 2013, you know AutoCAD is not automatically saving down to 2010 as you've set it to and Autodesk needs to look into fixing it. If it says 2010, then something else and possibly more troublesome is going on.
Either way, if you are on the subscription service, I would contact Autodesk immediately to start the direct troubleshooting process with them, and so they can get working on fixing this possible bug, if that's what it turns out to be.
The next time you get the error, open the dwg stating incompatible version in Notepad (change file filter in notepad to all files)
Top of the file will state one of the following versions, does it indicate AC1024 as expected?
AC1027 AutoCAD 2013
AC1024 AutoCAD 2010,2011,2012
AC1021 AutoCAD 2007, 2008, 2009
AC1018 AutoCAD 2004, 2005, 2006
AC1015 AutoCAD 2000, 2000i, 2002
AC1014 AutoCAD Release 14
AC1013 AutoCAD Release 13
AC1009 AutoCAD Release 11, 12
AC1006 AutoCAD Release 10
AC1004 AutoCAD Release 9
AC1003 AutoCAD 2.6
AC1002 AutoCAD 2.5
A passing thought. If you xref in a file there is (or usually is ) a warning that it will update the xref to the current running version (whether you want it to or not.). Even if you save back, it will not save back the xref files. Maybe that has changed in 2013,/14 though.
I could be wrong, but I vaguely remember getting caught in a similar trap a long time ago.
Just spitballin'
HTH
Regards,
DJ
We've had this problem in my office a couple of times, now, and I haven't been able to figure it out. We're running AutoCAD 2015, saving down to 2010 file format. Part of the problem is that by the time we realize that a file has been saved in 2013 format instead, it's too late to go back and determine exactly how the file was saved. If some tool or procedure is circumventing the file format setting, I am left to guess as to what it might have been.
Our computers are set by default to save in 2010 format through the Options dialog box --> Open and Save tab --> Save as drop-down list. But occasionally files raise compatibility issues, and when these files are opened in AutoCAD (and clickcing F2), the first line of text reads "Opening an AutoCAD 2013 format file."
This is an intermittent problem. Saving the file again has so far converted it properly to 2010 format.
I am confident that neither XREF nor WBLOCK are involved in this issue.
I would be happy for any suggestions to help me figure out this problem.
Thanks for your reply, pendean. If the only solution is to circumvent AutoCAD's native functions, then this begs the question, has this been reported to AutoDesk as a software bug?
How many and which functions trigger a native format save? I presume that only these functions would have to be disabled and rewritten.
If it comes down to writing the code, then yes, I'd appreciate some direction. I am familiar with coding, but disabling and replacing native commands is something I've never attempted.
Can't find what you're looking for? Ask the community or share your knowledge.