Hello, Good Day,
Following error getting save the drawing.
please help me, how i am comply.
*Warning* Multiply owned object, handle "29"
*Warning* Multiply owned object, handle "2A"
*Warning* Multiply owned object, handle "28"
i am not use "HANDET"COMMAND. (Please share details how to use this command.
It looks like you need more to the command. Enter the following in the command line.
(entdel(handent"29"))
Also check this thread to see if it helps
CADnoob
This is what happens when I try this...
*Warning* Multiply owned object, handle "3DD6"
*Warning* Multiply owned object, handle "3DD6"
*Warning* Multiply owned object, handle "3DD6"
Command: entdel(handent"3DD6")
**** System Variable Changed ****
2 of the monitored system variables have changed from the preferred value. Use SYSVARMONITOR command to view changes.
Unknown command "ENTDEL(HANDENT"3DD6")". Press F1 for help.
Suggestions?
@TheCADnoob wrote:It looks like you need more to the command. Enter the following in the command line.
(entdel(handent"29"))
@pendean wrote:
Do you need to fix your file(s) and Xref(s) first perhaps https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/AutoCA...
There are no xrefs in the file. There was one image file, but I removed that and I get the same error.
I have the same problem with a drawing here at the office, it's an old drawing that came from another office.
There are thousands of (*Warning* Multiply owned object, handle "50E1B9F") errors in it.
The handet command didn't work and too be honest with this amount of errors it's an endless job (Would be a lot of work to type every code manually).
It's a big file and at the moment we can basically just throw it away. It has no xrefs, no images nothing of all of that. Tried everything so far but can't fix those errors. Anyone has an idea how to fix this?
If you like..
Share the data package (command: etransmit the fiel with all 'include options' ON)
I am sure we can help.
Sebastian
Thank you very much for the offer, unfortunately company policy doesn't allow that.
We found the blocks with the errors and are now in the process of redrawing the blocks to get ride of the errors.
Can't find what you're looking for? Ask the community or share your knowledge.