AutoScript crashes AutoCad 2015 on second file

[weeddesign]

I have used AutoScript for years, but we recently upgraded to Acad 2015 and AutoScript keeps failing on the second processed file every time. I uninstalled and reinstalled AutoScript 3.4 and it does the same thing.  I have reverted to the OOTB AutoCad 2015 (without custom startup functions).  I have verified the script works.  And I have tried several different drawing files resulting in the same error (crash).  The acad log seems to show the crash on the second file just before the "Opened drawing synchronously..." log input.  The first file in the AutoScript list processes fine.  Since acad crashes, I cannot seem to get a log file for AutoScript.

Am I missing something, or has there been a change in 2015 that I am not accounting for (like a system variable or setting)?  I have attached acad logs for the successful file and the crashed file for reference.

Thanks!

[hencoop]

I ran into issues with the method I used to open files.  What had worked well for years would always cause a crash.  Check the open method used.

I opened a ticket with Autodesk support in July of 2014

"Autolisp (COMMAND ".OPEN" ...) crashes AutoCAD C3D 2015"

*********** Begin From Autodesk Support ************

Looking at your description however, this seems like it could be related to the known issue with having the SDI set to 1. As this itself is a known issue, and causes the software to crash, I would assume that if this was resolved, that your custom lisp routine would then work properly.
*********** End From Autodesk Support ************

My response was:

Thanks,

The thing is that it works fine with C3D 2014 but C3D 2015 crashes.

If SDI=0 and the drawing status is “OpenHere” then the code uses:

(VLA-ACTIVATE (VLA-ITEM (VLA-GET-DOCUMENTS (VLAX-GET-ACAD-OBJECT)) fname));

If SDI=0 and the drawing status is “NotOpen” then the code uses:

(VLA-ACTIVATE (VLA-OPEN (VLA-GET-DOCUMENTS (VLAX-GET-ACAD-OBJECT)) fname))

I had used a vbstatement for opening when SDI=1 until the VB enabler began causing hard crashes (and Autodesk quit supporting it).

My only recourse has been to use the old (COMMAND …) Now I guess I’ll just have to stick with AutoCAD C3D 2014.

I work in SDI=1 all the time.  The only time I’ll change to SDI=0 is when I want to publish using page setup overrides through the SSM.  I depend upon my many application’s variables remaining as they were last set from drawing to drawing and that happens automatically only  if SDI=1.  SDI=0 just kills my productivity for everything except publishing using page setup overrides.