AutoCAD 2016 script stops running

[Anonymous]

Hi,

I'm running a script to edit drawings. On one computer the script is running without a problem, on another computer the script stops every time after the Lisp routine. On the command line you see a Cancel after the routine. When I run the routine manually, this causes no Cancel. On the other computer I have no issues with this script.

This is the script:

Open
"DUCTING LAYOUT.dwg"
(ConvertLayout "Convert4Vault_20161025_2017.csv" nil)
qsave
close
Open
"02DUCTING LAYOUT.dwg"
(ConvertLayout "Convert4Vault_20161025_2017.csv" nil)
qsave
close

[Alfred.NESWADBA]

Hi,

>> the script stops every time after the Lisp routine

Did you verify that the lisp ended without errors? What happens when you create a dummy-code in the lisp that does nothing, just starts and ends ... is _QSAVE then initiated?

And every time a script should work with multiple drawings make sure that no ACADDOC.LSP blocks something + compare the SDI variable.

HTH, - alfred -

[Anonymous]

Thanx for your quick respons. As I said the script is running with no errors on another computer. The Lisp routines end with no Cancel. It looks that the QSAVE command does it. I have an ACADDOC.LSP. But also on the other computer which has a same environment.

Regards Leo

[Alfred.NESWADBA · Accepted solution]

Hi,

>> As I said the script is running with no errors on another computer. 

I have seen that, but I don't know what's inside the LISP, it might e.g. access pc3-files which might be different on that two systems, there might be a lot of differences, therefor I asked to change the lisp to a dummy one without any functionality just to isolate the source of the problem.

>> I have an ACADDOC.LSP. But also on the other computer which has a same environment.

With the same content?

What you can try too:

• From both systems run command SYSVDLG (from the expresstools), export all system variables and compare that exported files using e.g. Excel.
• Other option: from the working computer export the AutoCAD profile, on the non-working workstation create a new Windows user with admin permissions, login with that account, start AutoCAD and import that arg-file, make sure this new profile is the default for new AutoCAD starts and try your scripts again.

Generally to:

>> the other computer which has a same environment.

I'm quite sure that after a few minutes of working with AutoCAD the environments are not equal any more, especially noting that also system devices of Windows influence the AutoCAD environment too.

- alfred -

[Anonymous]

Hi Alfred,

You were right. An incompatible version of the plot wizard link was the reason the script stopped. I have deleted the file and now the script continues.

Thanks!

Regards Leo