Warning* Multiply owned object, handle "D0D6FD3"

Warning* Multiply owned object, handle "D0D6FD3"

PascalJ_87210
Enthusiast Enthusiast
11,939 Views
8 Replies
Message 1 of 9

Warning* Multiply owned object, handle "D0D6FD3"

PascalJ_87210
Enthusiast
Enthusiast

I get the following warning after every save in one CAD file I have been working on. I am running Autocad 2017.

 

I have searched this forum and found a post by DGORSMAN on 02-04-2015 that seems to explain the problem:

 

"The DWG file is a database, with every piece of data existing as a record in it.  Everything in the database has a unique ID, called a handle, used to identify it.  Handles are guaranteed unique to each drawing but not between drawings ie. in another drawing handle 508 could be assigned to something different.  So the error is telling you something is wrong with a very specific object in that specific drawing: object 508.

 

Certain parts of the drawing have a parent/child relationship (more like master/slave, actually).  Each master can have many slaves, but any slave can have only one master.  An error that says an object is "multiply owned" means some customization has forced ownership of that object (identified by handle 508) to another owner without removing it from the previous owner."

 

It makes sense to me. But I have not found any help to get rid of the warning. The warning is annoying. What is the severity of the problem indicated by this warning?

 

Anyone?

0 Likes
Accepted solutions (1)
11,940 Views
8 Replies
Replies (8)
Message 2 of 9

user181
Mentor
Mentor

Try this at command line (entdel(handent "D0D6FD3"))

 

Here is a link to article about it in civil 3d but I think it's the same for Autocad

 

https://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticl...

EESignature


Message 3 of 9

PascalJ_87210
Enthusiast
Enthusiast

Is there a way to identify the object associated with that handle?

 

The proposed solution will delete the object associated with the handle. I would like to visualize the object before going forward with its deletion.

0 Likes
Message 4 of 9

cadffm
Consultant
Consultant
Youre right (blind) delete isn't clever.
Paste here the Result of

(foreach dp (entget (handent "D0D6FD3") '("*"))(print dp))

Sebastian

Message 5 of 9

PascalJ_87210
Enthusiast
Enthusiast

This is the result after entering (foreach dp (entget (handent "D0D6FD3") '("*"))(print dp)) in Command line:


(-1 . <Entity name: 20b2703fab0>)
(0 . "DICTIONARY")
(5 . "D0D6FD3")
(102 . "{ACAD_REACTORS")
(330 . <Entity name: 20b2703faa0>)
(102 . "}")
(330 . <Entity name: 20b2703faa0>)
(100 . "AcDbDictionary")
(280 . 0)
(281 . 1)
(3 . "ACDB_ANNOTATIONSCALES")
(350 . <Entity name: 20b2703fac0>) (350 . <Entity name: 20b2703fac0>)

0 Likes
Message 6 of 9

cadffm
Consultant
Consultant
I am away from ACAD now and the best way is to wait for another help (er) or i will check this tomorrow.

If you cant wait, copy your file (as backup) and try this:
(entmod (reverse(cdr(reverse (entget (handent "D0D6FD3"))))))

Sebastian

0 Likes
Message 7 of 9

PascalJ_87210
Enthusiast
Enthusiast

I can wait. Not a problem.

Thank you for the help.

0 Likes
Message 8 of 9

cadffm
Consultant
Consultant
Accepted solution

Hello Pascal,


there will probably only be one problem with assigned annotative-scales to one Object.

If you upload the file or set it by email already (see profile) I would looking for this Object.

Without the file I guess:

If you delete that, you lose only one assignment of one drawing object to a annotativeScale.
(entdel(handent "D0D6FD3"))

If you happen to be lucky, the following line show you the Objects what will lose the annotative-scale.
Turn all layers ON and THAWN, do a ZOOM Extents and:
(sssetfirst nil (ssadd (cdr(assoc 330 (entget(cdr(assoc 330 (entget(handent "D0D6FD3"))))))) (ssadd)))

Is a object highlighted? Check there annotative-scales.
Use (entdel(handent "D0D6FD3"))
Check annotative-scales and correct the assigned scales if necessary

Sebastian

Message 9 of 9

PascalJ_87210
Enthusiast
Enthusiast

It worked. I was able to fix the problem.

 

Thank you very much for your help!

0 Likes