I'm trying to upgrade a complex project from v11.5.0 to v12.3.5 and getting a DbSchemaSummary Error in the logs - The following tables were found in the database but not in the schema.
The project contains the following DXP packages and all have been bumped to appropriate v12 versions.
This project started life in Umbraco 7 and was migrated using uSync migrations into a fresh v10 project, then bumped to v11. My localdb migrated perfectly, but its failing on our Azure deployments of QA/UAT/Prod.
That "error" is more a warning, have a look in your logs for other errors that might be there. All that that message is telling you is that there are database tables that the migration process doesn't know/expect to be there, but that is expected if you have 3rd party packages / customisations in your solution.
Typically when I've come across migration/upgrade issues that is a more specific error somewhere.
You're absolutely right, I tracked back through the log and the actual error is below, it looks like quite a significant migration error on the database. It's quite odd though as it worked fine on my localdb (local pc).
I've increased the SQL connection timeout to a ridiculously high number but ended up with a request 500 timeout in the migration UI page after a very long wait!
{EDIT} - So..... I had to increase the Azure compute + storage to a premium service to get the migration through to prevent an app service timeout. Says a lot for the size of our project.
Error upgrading from Umbraco v11.5.0 to v12.3.5
Season greetings everyone.
I'm trying to upgrade a complex project from v11.5.0 to v12.3.5 and getting a DbSchemaSummary Error in the logs - The following tables were found in the database but not in the schema.
The project contains the following DXP packages and all have been bumped to appropriate v12 versions.
uSync/uSync Complete
Umbraco Forms
Skybrud Redirects
TagHelpers
Diplo GodMode
Umbraco Storage Providers / AzureBlob / AzureBlobImageSharp
This project started life in Umbraco 7 and was migrated using uSync migrations into a fresh v10 project, then bumped to v11. My localdb migrated perfectly, but its failing on our Azure deployments of QA/UAT/Prod.
Hi Drummerboy,
That "error" is more a warning, have a look in your logs for other errors that might be there. All that that message is telling you is that there are database tables that the migration process doesn't know/expect to be there, but that is expected if you have 3rd party packages / customisations in your solution.
Typically when I've come across migration/upgrade issues that is a more specific error somewhere.
Thanks
Nik
Hi Nik
You're absolutely right, I tracked back through the log and the actual error is below, it looks like quite a significant migration error on the database. It's quite odd though as it worked fine on my localdb (local pc).
I've increased the SQL connection timeout to a ridiculously high number but ended up with a request 500 timeout in the migration UI page after a very long wait!
{EDIT} - So..... I had to increase the Azure compute + storage to a premium service to get the migration through to prevent an app service timeout. Says a lot for the size of our project.
is working on a reply...