Unwind Skipped on Exception

[rwatson654]

I'm trying to run the program Killdots in a drawing provided to us.  Killdots reports the below error, which only happens in this one drawing.

; error: Exception occurred: 0xC000001D

; warning: unwind skipped on exception

; error: Exception occurred: 0xC000001D

I receive the same error when running the following

(defun c:erasepoints(/ a)
(setq a (ssget "X" (list (cons 0 "POINT"))))
(command "erase" a "")
)

Any suggestions?

Civil 3D, 2009 & 2011

Win 7 Enterprise 64bit

8 GB

[devitg]

There is any way you can upload the dwg or send it offline ?

[Moshe-A]

do AUDIT / RECOVER

if this does not help

purge all and/or WBLOCK the drawing

Cheers

Moshe

[rwatson654]

File is to large to post here. email sent

[rwatson654]

I had ran an audit, and purge.  Purged all items, including Regapps.  Attempting to insert the file into another dwg failed, wblock all failed, wblock and select all objects seems to have solved the issue.  Still wondering what caused the problem.

[devitg]

It make the same error here

[hencoop]

I have had this problem off and on for a long time. I have finally been able to isolate at least one cause. I have employed the VLA-GETINTERFACEOBJECT function to access AECC_POINT and AECC_COGO_POINT objects up through AutoCAD C3D 2012. When I upgraded to AutoCAD C3D 2013 I experienced the error "unwind skipped on unknown exception" when using any of my applications that relied on this function. The problem was in the C3D application ID string supplied to the function. I had coded what had been the appropriate string in an if statement that defaulted to the correct string for C3D 2012. Running my functions in C3D 2013 would always produce the error.

I corrected the problem by changing the if statement to a conditional which included the correct string for C3D 2013.

In your case I suspect a reactor was involved that depended upon an application that was either not available or its identification string was incorrect for your installation, or some similar mismatch happened in a call to some other visual Lisp function. In the case of a reactor that you did not attach, using Wblock as you did is probably the easiest way to separate the problem reactor from the drawing.