SQL Error: Invalid column name 'key' when upgradi...
# help-with-umbraco
z
The title says it all. I've gone from v10 to v13, and now attempting v13 to v14, however I get the following error during the install/upgrade process: Internal 500 Error: https://www.mysite.local/umbraco/management/api/v1/upgrade/settings Invalid column name 'key'.\r\nInvalid column name 'key' You cans see the full error here: https://pastebin.com/U1Wid6gY Any help much appreciated.
This was a working v10 site to begin with, so technically I've gone from latest v10 to latest v13 to current v14 release.
c
Do you have unattended upgrades enabled, or do you do the traditional manual upgrade process (ie where you login and approve the database upgrade/changes each time)?
z
ah, traditional
c
I don't know if it's the same thing, but in some of my early playing around with upgrading a site to v14 I did I was also using the traditional/attended method, and ran into a similar SQL error around a missing 'key' column. I was only able to get past it and complete the upgrade by turning on unattended upgrades instead in appsettings.json temporarily after which if it all upgrades fine it can be disabled again. But I never got to the bottom of what caused it as my tests upgrading other v13 sites were all fine. However I do know the problem site in question had also originally been on v10 so if this is the same thing, it could be it's something to do with a site that's seen a few version jumps.
I wrote a little bit on the exact messages and config change to get round it here (from paragraph 4):- https://codebuntes.entrah-net.co.uk/2024/06/17/treading-the-bleeding-edge-path-on-a-big-umbraco-site/
z
@CodeBunTes - thanks. Your suggestion worked just fine. I was indeed coming from v10, I think? Luckily it's a very basic site, so I'm hoping this is it
sorry for the slow reply!
c
No worries, I'm just glad it worked. Thanks for letting me know as well. This gives me some more idea around versions I can play about with locally as if I can reliably reproduce this, it might be possible to raise an issue and get it fixed for everyone.
138 Views