Elements have duplicate 'Mark' values", elements can't be found in model

[Anonymous]

So I have an issue with locating the elements that are giving me a duplicate "Type Mark" value in the Warning dialog box.  This is what I have tried.

• Went to the Warning dialog box and checked the box next to the element but the Show button and More Info are greyed out
• Used the ID for the element to Select by ID. 
  • After clicking Show, I get a message that says "No Good view could be found"
  • Clicked Ok, element was highlighted and saw info of the element in the properties but all fields were greyed out and I couldn't use the drop down in the properties to change the element (type, size, etc)
• Created a schedule to try to locate the element by Family, Type, Type Mark, etc and couldn't be located in the schedule.
• Took a look at the journal file just to see if I could ascertain anything unusual.
• Workset is on
• Created a new Default 3D View and locate the element to eliminate any visibility issues

Any ideas?  Thanks in advance.

[ToanDN]

Check Legend views.

[cbcarch]

-Check nested family ( such as a GM Door Leaf nested into a Door Family) that may not have a Mark, so it doesn't appear in Door Schedule.

-We have had the opposite of this happen--odd doors appearing on the schedule which were not doors on the floor plans. Turned out the nested leaf GMs had a Mark, which showed in the schedule. Removed the Mark and all was good.

[Anonymous · Accepted solution]

So an update but not reason why this is happening.

So I was in Navis and added an entry under Quick Properties for Element ID.  I used the value for Element ID that I found in the Warning Dialog box in Revit and searched for that value in Navis.  A message was returned in Navis saying that object doesn't exist.

Next in Revit, I selected by ID by using the OK option, the item highlighted.  Used a zoom to object tool and it zoomed away from the model.  At this point I knew I wasn't deleting something important so the item was removed.  All I can think of is a bug in the database.  Thanks.