file contain an incorrect schema

[amro.ayas]

Pleas help >>> :S 

I was working on a file and all of a sudden asked me to send a report and save recovery file will I did save a recovery file (after working for 14 min without saving or auto sync-15 min - with the server file). 

the problem is the recovery file wont open with the massage (file contain an incorrect schema) I tried to audit it but wont work and giving me the same massage so what to do I don't want to go through the Elc equipment again pleas :(((

[Anonymous · Accepted solution]

Hello Mr.,

If you are seeing this in a central file, creating a new central file by going through the steps below has fixed the issue for some users:

1. In Windows Explorer, move the central file and it's backup folder to a new location.
2. Find a suitable local file.
3. Open, Purge all unused.
4. Use Save As to save the file as a new Central file.
5. Relinquish all ownership. (You will have to do this for all Revit files host and linked before creating new locals)
6. Close Revit.
7. On all of the client workstations, open Windows Explorer (Windows key +E).Type %temp% in the address bar.
8. Delete as many files as possible from this folder. Some files may not be able to be deleted if they are in use by other applications on your machine.
9. Move the local file backups to a different location.
10. Create new local files.

If the error is limited to the existing local file, you can create a new local file to clear the error by going through the process below:

1. Close Revit.
2. Open Windows Explorer (Windows key +E).Type %temp% in the address bar.
3. Delete as many files as possible from this folder. Some files may not be able to be deleted if they are in use by other applications on your machine.
4. Move the local file backups to a different location.
5. Create a new local file.

If you are seeing this error in a non-workshared file, you can try recovering a previous version by going through the steps on the page below:

Recovering non-workshared files

[kadmonkee]

are you working off a Central file on a network server or are you using Revit Server in your Network?

the "incorrect schema" message relates to a disconnect of network resources.

the simple solution is:

discuss with the entire team.

IF-

Model A is good do nothing

Model E is bad find the latest

Model FP is good do nothing

Model M is good do nothing

confirm all users are out of all revit models (linked or otherwise)

find the latest valid local file - confirm with all users.

Model E is bad - find whomever has the latest valid Local file have them save and sync to central and relinquish all and close the local file.

depending on access to the Network (creating files rights & permissions) have someone who can open and detach from central (preserve worksets)

this will give you the opportunity to create new Central model to correct the issue.

once the new central file has been reestablished on your network all users are encouraged to create a new Local file and overwrite the previous one.

if you have multiple users working in 1 model and each has done considerable amounts of work that has not been saved back to the central file, then each user can open THEIR LOCAL FILE DETACH from central, to create a dummy file and transfer their work to the new VALID central file.

[syman2000 · Accepted solution]

Hi there,

Recently our user has experience this issue on regular basis. What I am noticing is that your IT may default each user profile (c:\users\<<your user name>>\My documents) 20-40gigs limit. When your user profile already at that 20-40gigs limit, Windows will prevent your Revit file from saving hence you get that error. To fix this, you want to go to that folder and get rid of all the older Revit project. If you want to avoid that error in the future, the best way would be to change your Revit local path to C:\Revit Projects\.

[Anonymous]

In my experience, this can be caused by a corruption in the naming of your local file, preventing it from saving or syncing under its current name. A solution is to save-as the local file with a different name and then syn. You can then sync back to the central, close the now renamed local file, and open a new local the way you normally would. Once you have a new local file with your usual local name, you can delete the one you created to fix the problem.

[Anonymous]

Thanks, this work for me in R2020