Scriptpro Not Saving due to AEC object - Version Conflict(?)

[tmorrison8KTHE]

I've started using scriptpro to make changes across about 20 drawings successfully a few times. I've noticed at times it will complete the script with the "done" status. However, it won't actually save the file (there is an extra line after "QSAVE').

Log script:

...

Command1: complete.
Command2: complete.

Command3: QSAVE
You are trying to save AEC objects to a previous version file format. This is not permitted.

These objects can be viewed in a previous version if Proxy Graphics are enabled,
but AEC commands will be disabled.

Users of 2004, 2005 and 2006 versions should install an updated Object Enabler (available from www.autodesk.com/enablers) before opening these drawings.
Previous versions will display error messages.

Command: 

Setting options to 2018 omits the bug and saves it! Great! Except I'd like to continue saving in 2013. I can run the commands literally from the command line in the same order without any issue. . . It's only error prone when using scriptpro. The biggest frustration is that I executed on the exact files earlier today without issue. 

Thanks for any input

-Thaddeus

See attached script. It's a fairly simple replace and update scheme for blocks/attributes. It's saved me a ton of time already.

[mike.pool]

I abandoned ScriptPro a few years ago when Autodesk stopped supporting it.  I've since moved the freeware app from CADIG called AutoScript ( http://www.cadig.com/products/autocad-script-pro.php ).   It has an automatic save feature as part of the Option settings, so you would be able to eliminate the "Qsave" in your script file.  That might help get you around the AEC object compatibility issue.AutoScript Options

[tmorrison8KTHE]

@mike.pool  Thanks!

I'm kinda bummed Autodesk no longer supports ScriptPro. Doesn't really seem like I should be responsible for 3rd party downloads when the premium is involved. Unfortunately, I'm not a huge fan of downloading files from an unknown/unsecure website so I'm gonna have to figure something else out. 

[RobDraw]

When trying to "save as" a previous version, AEC objects do not get converted to be compatible with those versions. They need to be exported. Plus, the .dwg format changed in 2018 so again, a save as to a previous version is not going to work. The drawings need to exported.

[tmorrison8KTHE]

Hey @RobDraw,

So the options are set to "saveas 2013". The file itself opens as a 2013 file type document (at least thats what the F2 window shows when opening), I'm using 2019. I tried running on 2015 and was still getting the error. I think it's a dialogue box that is preventing the save command from finishing.

I'm looking into Acadcoreconsole.exe now. I get the feeling it's gonna give me the same problem though.

Thanks

[mike.pool]

I completely understand @tmorrison8KTHE .  CADIG is a reputable company and I have purchased and downloaded a number of their add-on products without issues.  Just thought AutoScript might be a good free option to try.  I wish you the best of luck on getting this resolved.

[RobDraw]

I'm not sure what to add to my previous post to explain it any clearer.

[pendean]

---

@tmorrison8KTHE wrote:

I'm using 2019

---

You need to use AECTOACAD to convert your file to the older DWG format correctly first in 2019 to remove all AEC content, or go grab a freebie from the Autodesk App Store called ZOMBIEKILLER to do the same.

[maratovich]

Can you attach your sample dwg file for verification?