Conflict in Schema when Loading a file

[mylesXGYYA]

Hi All, 

I have an issue when working in my file where I get the conflict in Schema. Revit and all plugins are up to date including twin motion. 

The conflict occurs in the "DatasmithRevitexportsettings" 

And "DataStorageUniqueld"

It looks like this has corrupted my central file, I luckily have a saved file I can use. However when working in the file i keep getting the message, then followed by a termination of Revit.

How can I resolve this? 

Thanks 

Myles

[mylesXGYYA]

I may have fixed it, this may however only be temporary.  

I opened a room tag family that when being edited caused the issue. Not the only family to cause the crash, but once I opened and saved the family then loaded into the Revit file again the family works and dose not cause the error message and the crash. 

Now to find the other couple of Families also causing an issue. 

Thanks 

Myles

[mylesXGYYA]

I now have an issue saving the file as a central file again!

When setting up the central file, 

Collaborate causes a conflict with the schema - "DatasmithRevitExportSettings" this is not causing the termination of Revit, but preventing saving the file as a central file. 

Next message to appear is "Initiate Collaboration Failed. Check the Journal for more information" 

What journal and where should I look?

Thanks 

Myles 

[ridantuo]

Had the same issue recently with a central model file. All of my fixing attempts where in vain. The reason for the issue was - if I remember correctly - an upgraded model from 2024.0.2 > 2024.1.1 The schema issue came months later from the upgrade so it wasn't possible to revert that. You can try these fixes:

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Schema-Conflicts-w...

The only way that I was able to get it fixed was send the file to Autodesk (so do a ticket for them) and redo the central model with the fixed file. Haven't seen the schema conflict since. They were fairly quick with it; I think from sending the file at morning (my time) it took maybe around 2h to get back from them fine and dandy.

Also recommended things:

Everyone working on the central must have the same Revit versions.

Some plugins/addins might cause this. So if it remerges after the fix, start looking there.

While Autodesk demigods are working on the fix, do not work on the file.

[mhiserZFHXS]

Are you using the most up-to-date version of Revit? They seemed pretty confident that they resolved this issue in the vast majority of cases, though I think they did admit that it may still pop up every now and then.

[mylesXGYYA]

Thank you, I will have a read over the possible fixes.

We are all update to date with Revit and the extensions as I can see.

Thanks

Myles