"There are too many elements missing in it"

[Anonymous]

I was working on a local file that was attached to a central file on a server.

I saved as and selected (Create new Central File).

I kept working, saved my work, and closed out.

Today, it won't open the file and give me the following message:  "There are too many elements missing in it"

I'm assuming this means it's looking for elements, but how do I link them back if I can't open the file?

[Anonymous]

You have to use "Detach From Central" when opening a local or a central file when you create a new central file, else it remembers the information of the previous model.

So it is looking at its original location and can't find it.

[Anonymous]

Yes, I don't think I will ever forget that now.  

So if it's looking at the original location, how do I tell it where it is?

[Anonymous]

Well where did you save the original? Only you know that. 

Alternatively, I would try detaching from central for this new file. 

furthermore, I might add, that by your description, when you did the save as and selected central file, did you then close and reopen it as a local file? 

This would apply for detaching from central as well. Users often forget after detaching that they are still working in the central file. You need to remember to syncronise and release 'user created worksets' close it and reopen as local so other can start working on it. 

[Anonymous]

You are right, after I saved as I did not close out and open it again for it to create a local file.

The central file I created (in the server) from the original (in the server) is the one I tried opening, then I searched my local files to see if anything was created, and somehow there was a file in My Documents.  Both give me the same error.  I now realize that not detaching from the orignal central file I created my new central file from was the mistake. 

What I'm trying to understand is if its looking for something that is in the original central file I created the second central file from, how do I tell it where it is?  It doesn't give me an option to browse and find the missing elements.

I worked on the file for a complete day, I printed, and exported from it, so it was working.  I didn't move anything, or rename any files, so why can't it find these elements?

Does this have a solution, or should I give up and start over?   

[Anonymous]

Also, I found this link online and it seems you can create central files both ways...but you mentioned the the key is to close out and open it again to create a local file if you use Save As, is that correct.

Why use one method over the other if both have to detach from the central file?

http://revitoped.blogspot.com/2015/03/detach-from-central-versus-save-as-make.html

[Anonymous]

Ok, so first, what version are you using? This may answer your question:

https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles...

Have you tried opening the file yet by detach from central option? Do you still get the warning? 

Are your links (if any) sitting on worksets? If so, perhaps try opening the file by specifying not to open worksets... you can do this by clicking the down arrow next to 'open' when you select the file. 

finally, the article by Steve explains that to use one method over another results in possible ownership / borrowers being retained. If you read the thread the article was based on the person detached from central using the save as method only to find users still had elements borrowed. He wanted to know why. Steve indicated this method seems to simply redirect to a new central file whilst retaining ownership.

However, the 'detach from central' option completely severs the connection. This is the ONLY method I ever use and is always well communicated to the team and I ensure know-one works on the file while I am refreshing files using detach from central.  

In my opinion, it appears the mistake the person made in that thread was that he dared to do work on the central file whilst other team members were working on the file. 

[Anonymous]

I'm using 2016.  

I have tried detach, audit, everything.  I also tried the worksets option like you mentioned and I get a window (image attached) that doesn't really give me any options. 

At this point I would like to understand why Revit allows you to create central files from central files in two different forms.  My inquiry comes from finding most people say "it may be possible (though unlikley)" to work from one in which you did not detach from the original central file.  There has be more than a hypothetical purpose for creating a central file  from another central file without detaching, otherwise why would Revit have the alternative?  

I hope someone can explain not just the difference between the two methods, but their purpose and application.

Thank you damo3. 

[Anonymous · Accepted solution]

Ok, so your workset window tells us something, that you don't have any worksets setup beyond the defaults. So, this is good, because it means we can start from scratch. 

when you detach from central, instead of preserving worksets, select "Detach & Discard Worksets". Done. Check your file, make sure its all fine, then recreate a worksharing file. 

As for your question about absolutes... , does this article satisfy you? 

https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2016/EN...

Whenever I have to do the above, I simply open the local file directly and select 'detach from central' then save it again. Same thing. 

remember, your using a software program that has a text editor from the 80's and a ramp tool that doesn't make ramps very well (and hardly anyone uses), trying to find rhyme or reason with Autodesk software can sometimes be a path to nowhere, they aren't always the original authors either, sometimes they don't even know the answer (sometimes they pretend to).

Leave a comment for Steve or shoot him an email, perhaps he can expand on the post. 

Sorry, best I can do, perhaps someone else has a better explanation, but I never use it. 

[Anonymous]

Revit Central files remember where they come from....you cannot see it, it's embedded in the code (or the API).  With a recent update to Revit you now get a message on whether you want to save the file as a central, or just open as view only.  I believe this is if someone used the E-Transmit add-in, but e-transmit basically forces you to create a new central file as the Detach and Create local buttons are grayed out.  Opening any other file, even if from the network to your computer, you want to use the Detatch from Central as it wipes away where it was located prior.  If you don't do this, you will get a message saying you are opening a file that has been moved error.  If you try to do anything it will error again as it can't find the central file and whether you have permission to edit.

FYI...years ago the process to create a local file was to:  Copy the Central to your computer, rename it to local, and then open it.  As long as you renamed it, Revit knew it was a local file and still had ties to the central file location.  That functionality is still there, and the reason the Detach from Central is very important if you want a totally separate model.

[Anonymous]

Thank you Damo3.
I had to start over from my original central file (this time detaching) but the link you sent does explain why Save As is an option for creating a central file without detaching.

[Anonymous]

I have tried everything here and am getting no where.  looks like 2 days of work will be down the drain.

[Anonymous]

I know this was posted several years ago, but I've just recently had this problem and couldn't upgrade from Revit 2018 to 2020 due to this error. Here is how I solved it:

https://www.cadlinecommunity.co.uk/hc/en-us/articles/360000059958-Revit-2019-Too-many-missing-elemen...

Go to save As and save all families to a folder. Once you get an error message from one of the families, take note of the name (could be multiple, but it my case it was just one). Delete that family from your model and try to upgrade again. I hope this helps someone; much better alternative than Autodesks solution of going back to an older file, potentially making you lose a lot of work.