Schema Conflict when Loading a File

Schema Conflict when Loading a File

lshannonEQEBT
Advocate Advocate
14,672 Views
24 Replies
Message 1 of 25

Schema Conflict when Loading a File

lshannonEQEBT
Advocate
Advocate

Hello all,

 

I know that there are some other posts about this issue, but it doesn't look like they are live anymore. My whole team is getting this error when we open our newly upgraded Revit 2021 project. I have no idea what a schema is or how to find it, so that doesn't help. We have followed Autodesk's advice to just ignore it and bypass the error, but it pops up each time we load the file and I would really rather if it did not. Advice?

 

image.png

0 Likes
Accepted solutions (2)
14,673 Views
24 Replies
Replies (24)
Message 2 of 25

DarrenP
Consultant
Consultant

the screenshot didn't come through

DarrenP
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

0 Likes
Message 3 of 25

lshannonEQEBT
Advocate
Advocate

That's weird, it's showing on my side. Lets try this again:

 

image (1).png

0 Likes
Message 4 of 25

DarrenP
Consultant
Consultant

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

or https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/sfdcarticles/sfdcarticles/F...

 

DarrenP
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

0 Likes
Message 5 of 25

lshannonEQEBT
Advocate
Advocate

@DarrenP 

 

I've read this and we are all up to date and on the same versions. Other ideas?

0 Likes
Message 6 of 25

David_Robison
Advocate
Advocate

Looks like it is a known bug:

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

 

The "RPCA" is the name the developer used for themselves. Searching on Google for that name looks like it is Autodesk themselves and not a third-party developer.

 

I wrote up this page to help developers solve the error. There's nothing you can do as an end user to fix it. Whoever "RCPA" is needs to solve the problem.

https://stackoverflow.com/questions/58136546/what-causes-the-schema-conflict-when-loading-a-file-in-...

 

Most likely you need to wait for a patch from Autodesk at this point.

0 Likes
Message 7 of 25

lshannonEQEBT
Advocate
Advocate

@David_Robison 

 

Yeah, I've read those too 🙂 I looked at yours on stack overflow and decided I have no idea what you were talking about so I figured to start this new post. In your opinion, should we just overwrite the schema so the error does not come up each time the project is opened?

0 Likes
Message 8 of 25

David_Robison
Advocate
Advocate
Accepted solution

Assuming Autodesk is correct, pressing "Continue loading the file" is the right thing to do. In my instance doing that did cause data loss, but Autodesk says that doesn't happen in this case.

 

If you are worried they might not be right, try closing and reopening Revit. Then open the file again. There is a chance it will open without the warning.

 

If it opens fine, then that's your "solution". When the error happens, restart Revit.

 

If it doesn't open, you will just have to open it as is and hope Autodesk is correct. Or continue using a previous version of Revit until Autodesk fixes the bug in Revit 2021.

Message 9 of 25

lshannonEQEBT
Advocate
Advocate

@David_Robison 

 

Gotcha. What data did you lose when you opened it and overwrote the schema?

0 Likes
Message 10 of 25

David_Robison
Advocate
Advocate

A schema is were a third-party developer can store extra information in the Revit model.

 

In my case, I have an electrical add-in that stores information about wire sizes and things like that. All our extra data was lost when the model was loaded. It was not pretty for my customers who had this data lost happen to them. We made adjustments to our internal processes to make sure that doesn't happen again.

 

In your case, I don't know what may or may not get lost. It all depends on what is being stored in that schema. It looks like Autodesk created the schema. They say there are not negative impacts to erasing the data on that schema. You have to trust that they've look at what they are storing and confirmed it is nothing important.

Message 11 of 25

lshannonEQEBT
Advocate
Advocate

@David_Robison 

 

I see. Well thank you for the information! If anything weird happens as a result, I will be sure to let you all know.

0 Likes
Message 12 of 25

Lance.Coffey
Autodesk Support
Autodesk Support
Accepted solution

Thank you for the question @lshannonEQEBT!

 

From the screenshot provided (InternalSchema_Data_Version_4 from RPCA), it looks like you are encountering the warning described in the article that @David_Robison posted.

 

I’m updating that document, to clarify some of these points:

  • This warning is related to the schema for the Revit Precast Extension.
  • This warning can be safely ignored (the change introduced in a fix to the extension was relatively minor, just the addition of a documentation field).


Lance Coffey

Technical Support Specialist
0 Likes
Message 13 of 25

lshannonEQEBT
Advocate
Advocate

@Lance.Coffey 

 

Thank you for the update Lance! Should we expect this error to happen with every project we upgrade form 2020 to 2021 moving forward?

0 Likes
Message 14 of 25

Lance.Coffey
Autodesk Support
Autodesk Support

This would depend on the usage of the precast extension in the project being upgraded.



Lance Coffey

Technical Support Specialist
0 Likes
Message 15 of 25

eric.stimmel
Advocate
Advocate

Is there a way to clear the error from a model experiencing this issue? No one on our teams is using this add-in, however the warning is appearing on several architectural models. It's both annoying to users who must repeatedly click through it and troublesome as users who aren't familiar with it stop working for fear of damaging the model.

Message 16 of 25

ahagner
Explorer
Explorer

We are in the same boat; we're the engineers and the error is coming from the Architect's model. Quite annoying.. wish there was a way to purge these things out of the copy of the arch model if we're not using BIM360

0 Likes
Message 17 of 25

lshannonEQEBT
Advocate
Advocate

So we continued having the issue until we all updated to the most recent hotfix. Then it stopped happening. We also noticed that is any of our consultants were on an older release, it continued ot happen on our model too unitl they updated. Maybe this could help you?

 

Be wary, however, that there is a bug in the most recent release (at least we didn't have it until the most recent release) that affects performance with materials and the material browser. It's pretty bad for us and there is still no solution, so consider the possability of that exchange of problems.

0 Likes
Message 18 of 25

kahumbert
Contributor
Contributor

I'm having the same issue on a model that we received from a consultant that we are linking into our model. We get this warning everytime we open the project. On top of that, we are not able to append the revit model into Navisworks unless we unload their model. This is causing major headaches...

0 Likes
Message 19 of 25

RobDraw
Mentor
Mentor

Have you tired any and/or all of the suggestions already posted?


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 20 of 25

kahumbert
Contributor
Contributor

The only suggestion is to make sure everyone is updated to the latest hotfix and to click the button to bypass the error. Internally, we are current on our revit install. I have asked the consultant to do the same and waiting to hear back.

 

Bypassing the error is not a solution. It doesn't solve the problem. I'm hoping that they just need to update their revit to the latest hotfix. If that doesn't take care of it, what are the next steps?

 

In searching for "revit 2021 precast extension" on google, it appears this extension no longer exists and was built-in to revit in 2021. So, there is no add-in for me to update.