Schema missmatch on fresh local clone of v13.
# help-with-umbraco
m
I just reinstalled windows and cloned my Cloud project down from git. I run the restore and am told there is a Schema mismatch. I tried making a change (uninstalled a package and upgrade from 13.2.2 to 13.3.0) and checked that in to production but still getting the error. The following items are causing problems: Document type Section Home Page Information Block with alias 'sectionHomePageInfoBlock' umb://document-type/aa1f54f0d00a4c149da1722dfaf840b5 Document type does not exist in target environment. Please help, why is a fresh clone failing to let me restore my data.?
w
Something like this typically means it's expecting a doctype to exist in the environment you're restoring to (in this case your new local environment) which is missing - if you search your local repo for the ID after document-type (i.e. aa1f54f0d..) what do you get?
There should be a file in your local repo which has that same ID in it which defines whatever "section home page info block" is, if it's missing then that may explain why it's not restoring locally
m
How do I search for that ID? And I am sure it is going to be missing but how do I fix it. I cloned down the got from my production cloud and can't restore from production cloud so this makes no sense.
w
I mean searching the contents of the code that you've checked out, specifically I think there should be a uda file which contains that ID. The cloud docs have a couple of guides on how to resolve mismatches
m
I looked at the help doc linked in the error and it said just do a new deploy which did not work. So just do a find in all files for that id and delete it?
I know like a dozen or so coded changes I deleted that block and prod has been running that change for a fee months
I did a full find in files for both the id and the block name and found nothing. VS also says no files with that name are in the project.
Ok. I figured it out. Some how there was still a document type running in production with that name. I don't know how it existed but I deleted in production and now I am restored.
4 Views