Autocad Error 0015.111 For Mac Os X
Diann Wald
A little background: I am not well verse (if at not in LISP) and been reading thru some forum on error handling but still can not get it to work. The code was written by person who is no longer with company and I am needing to get this working in AutoCAD 2016 (yes, we currently still on this version) from AutoCAD 2010.
I been hitting the ESC key to cause the error to come up. I am assuming its the custom error handler and it attempting to reset certain setting back. Like I mention, I attempt to search forum and documentation but cant seem to make heads or tails on getting it to work.
It's to do with how the custom error handler is constructed. (*push-error-using-command*) should have been inserted after the the first (setq err *error* *error* trap) and at the end of the file, (*pop-error-mode*) should have been inserted after (setq *error* err) as well as in the trap routine. I'm not sure if these are causing the error though.
Even if i define a bad *error* using command before calling your function (as it stores and restores the content of *error*, it could be caused by another lisp defining a bad *error*, but doesn't make a difference here)
I will look at this tomorrow. There is a lot of redundant code and loop controls, but I think that this is the first program prompt. What should happen is that all the variables are local to the lisp and disappear once the lisp finishes, but the programmer has made them all global by not defining them in the brackets and after the slash at the start of the lisp. This means they stick around in autocad clogging up memory and cause problems when errors occur.
Re: lot of work
Just copy the new *error* defun to the other lisps, the " / *error* " is a copy and paste and you only have to put a semi-colon in front of any setq with err *error* or trap in it.
If you get stuck just pop back here and i'm sure someone will help.
Although i agree with N4mr4hdlanor that the code could use a serious overhaul, pp.lsp is not the source of your problem. If you follow his instructions on making the *error* trap local to the pp function, it should at least not occur while using it.
The loft itself works, but if I try to use polyline guides, it fails (with the error code 98037 - not that there's any way of telling what that means!). I've redrawn the guides three or four times in different ways, but they fail each time. I'm absolutely certain the guides intersect the profiles (although I've been wrong before!), but now they've taken error messages out of CAD 2018, tracking down the problem is nigh on impossible...
I tried repeating what you did and breaking the profiles into quarters, then lofting to create surfaces, but I can't even get it to do that! The lofting works, but any sort of guide line I use throws the same 98037 error.
Does anyone have access to an error code list of explanations? I am working in 3D Modeling using the profile lofting of closed polylines and having a lot of trouble working through the finished solid without get a number of error codes that have no explanation with them. I am using AutoCAD 2018 English.
I could not share the drawings because they are military restricted types. But, I can tell you that 90% of all of the error codes that I receive are when I am lofting closed profiles. When using polylines it is easy to inadvertently hit one of the left or right buttons without knowing it and create a vertex where you don't want it. Then, you have to go back over each profile to see where you have an extra vertex that is keeping the loft from forming. Most of the surfaces on military aircraft are not typical, or of the same origin, so it takes a different profile at each intersection causing there to be as many as a million points of reference on just one drawing. Examples of some of the error codes I have received are: 98066, 98033, and 98011. These originated out of a lofting operation. God Bless all of you out there helping all of us AutoCAD challenged!
Certainly, Autodesk should provide a list of Error Code for us to make use of? How could we possibly complete any drawings without the fix notification of "How to!" Come-on guys! I am getting further behind every minute this remains unresolved. It's quite simple, just share your list of error codes so that we can proceed?!?! Deadlines get quite expensive when not met.
Like the word "my" this code is used very often, and it is used from many different modules. Would it help you that you know that the calculation of "distance between 2 points" had issues if you don't know which module used this calculation. It might be a simple 3D-Solid edge length calculation or during intersection the distance between multiple 3D-faces or ... many possibilities exist here ... more theoretical: it is more interesting now which or the parent modules have called that function, because there is a type of distance that raised the issue (or the parent of the parent of the parent ...) is what you might need. Therefor you would get a list of maybe 100 error numbers showing the hierarchy of the code ... and without seeing this code it again does not help you to get the information what could be helpful to handle your geometry.
Unfortunately I have not found a list of error codes. The codes are not really intended for the end user but more for the programmers anyways. It helps them trace errors in order to find where things might be breaking down in the code (not necessarily in geometry).
Thank you for posting. I don't see a ScreenCast, but can share that most lofting errors are related to intersecting surfaces or an incomplete path for surface to be lofted. Sometimes it is necessary to zoom in very close on the path to see both.
I still have one problem. When I am trying to use red line in the attached file as a "Guide" I just face an error code and not able to fit the surface to red line. Right now, I lofted 3 selected surfaces to make the bowl but need to expand the bowl to red line. Can you please let me know why "Guide" command in loft is not working? I appreciate your time and expertise.
I have been trying to add pattern hatches provided by eldorado stone manufacturer and get message 'error in pattern file'. It seems no matter what I try or where I file the pat file the same problem occurs. I have read so much online, deleted the files to try again, but still can't solve the problem. HELP!
Depending on the AutoCAD release you should know that old versions of AutoCAD had a limit of 80 char's per line. So you can go through that file, clear the spaces (which are not needed), replace the trailing zeros as decimal digits and for that lines, that again are presented as errors you have to round values, but be careful, do not round the first line in the parameter file as that is the angle (rounding that value creates more issues with the distance of the hatch from it's origin)
I cannot tell wether it is a sudden problem or not. I use Autocad in this facility for about a year now on an occasional basis. Main CAD application here is CATIA so there is no IT based Autocad support other than installation and deinstallation. I interface with civil construction projects on our site which is a different world so I use Autocad to check architectural and utility drawings. Sometimes I return drawings with my own proposals and it just happens that for my current drawing working with block definitions is the way to go. And that's where I realized this fatal error issue for the first time. As far as I can tell, the fatal error is exclusively related to the "insert block" functions "recent blocks..." and "blocks from other drawings...".
Using the insert command at the command line gave me a slightly different unhandled exception error with a more detailed log (see file "unhandled exception log text. txt"). It looks like an handling problem between Autocad and Windows...
Background: I am running Autocad with two language packs on this computer: german and english. I prefere the english version since I "grew up" with it and don't know the german commands. For the fun of it I started the german version and voilà: inserting blocks worked just fine w/o any error messages.
I am having this same error occurring with a few machines using AutoCAd Architecture 2011. It seems as though the error occurs on machines that I have installed a software called SpecLink from BSD. I thought it was due to ArcView since it was happening to two machines that had that software, but today it happened to someone who does not have ArcView, but does have Speclink. Is there a fix for this. I tried repairing the install and then uninstalling and reinstalling, but still no success.
I replace the files as always, but even though they're newer, the error message appears as before... The funny thing that sometimes it works, sometimes not. From time to time I can see, that the old dlls are back...
Thank you very much, the transfer of files effectively modifies the condition of being able to create the e-Transmit files, the .dll files I took from the autocad folder.
Best regards
Blas O. Reyes Huerta
That error generates from an error-trap function calling command. You may have a custom textmask routine (overwriting the textmask function provided by express tools) with an error trap calling command. Or your custom routine may have no error trap, but a global custom error trap is already implemented through some startup function, which is then invoked by your custom textmask function? If you have, in fact, implemented a global error function then it may also affect your out-of-the-box express tools textmask routine. Reset AutoCAD to default settings and unload all customization. See if it helps.
When I attempt to UNION the two solids by selecting everything with a window I get the same error you have reported. When I try to UNION by selecting the two solids by clicking on each of them with the cursor I get the same code, unless I have shaded them. With the Visual Style set to Conceptual I get "Error Code Number is 55000" on click-select but still the same error as original with window-select.
aa06259810