Updating to same version (Azure swap & environments)
I am using several environments for testing, local, a staging one and the final production environment which has a swap. Each environment has it's own DB.
I updated from 8.6 to 8.13.0 and everything went well on the minor environments, I hit update and they did their thing.
Now on the swap & production slots it is giving me errors that the db has columns not in the schema, cannot find the cmsDictonary, etc.
it says it is updating:
current version 8.13.0 (2ab29964), which needs to be upgraded to 8.13.0 (d6a8d863)
The dictionary error: Cannot find the object \"cmsDictionary\" because it does not exist or you do not have permissions
Any ideas appreciated I am already investigating permissions on the login and will post here if that is the issue.
For anybody else who gets this, the permissions were at fault.
The client had modified the permissions on the production sql user login and disallowed any schema/view modification to the user being used by Umbraco.
This of course stopped the system from being able to make table updates etc.
Updating to same version (Azure swap & environments)
I am using several environments for testing, local, a staging one and the final production environment which has a swap. Each environment has it's own DB.
I updated from 8.6 to 8.13.0 and everything went well on the minor environments, I hit update and they did their thing.
Now on the swap & production slots it is giving me errors that the db has columns not in the schema, cannot find the cmsDictonary, etc. it says it is updating:
current version 8.13.0 (2ab29964), which needs to be upgraded to 8.13.0 (d6a8d863)The dictionary error:
Cannot find the object \"cmsDictionary\" because it does not exist or you do not have permissionsAny ideas appreciated I am already investigating permissions on the login and will post here if that is the issue.
For anybody else who gets this, the permissions were at fault.
The client had modified the permissions on the production sql user login and disallowed any schema/view modification to the user being used by Umbraco.
This of course stopped the system from being able to make table updates etc.
is working on a reply...