INTERNAL SCHEMA error

[KALH]

One of my users got the internal schema error on Revit 2016 SP1.

She had significant work she didnt want to redo and since she wasnt able to save localy or SWC it was a BIG issue.

Solution: 

1. Save as another name the local file
2. Sync With Central (you shouldnt get anymore the error)
3. Close the renamed local file
4. Create new local 
5. Voila all set...
6. Solution applicable on all flavors and versions of Revit from 2013 to now.
7. Please give a kuddo if this solution helped you.

[Anonymous]

Kal,

To be safe, I'd have the team audit, compact and maybe even re-path the workshared central file. Then have the entire team create new locals. If there is an element with a corrupted path you'll want to make sure you isolate it. (Note: some people might think this is overkill / un-related, but it takes 2 minutes.)

All of our files our workshared, so we run into this with new hires. This seems to occour when users are either opening from a local file instead of creating a new local (daily!), or they have accidently opened and are working in the central file. Others have pointed out that it can occour if you have a network drop during a STC or create new local process.

I've also had success with havng teams modify their STC settings and browsing to the central file, which allowed them to sync.

/edited for clarity.

[Chris.Aquino]

Thank you for posting the solution you found for your issue.

As mentioned the issue is essentially a mild form of file corruption which can happen becuase of network hiccups during local creation or syncing to central, and recreating the local file usually fixes the issue.

Also, as mentioned, we would have user clear out old locals and create new ones every day.

Thank you again for your post.