Upgraded an Umbraco instance the other day. Checked the error logs this morning to make sure everything was running as expected, and noticed a bit of a pattern.
Everyday at sometime between 4:40 Am and 5:00 AM, I will get 2 errors where the stack trace looks like this:
The current functionality of the app has been fine as far as I can tell.
Was browsing some forums/issues and found that the cmsContentType table may be missing the column. When checking though, the column is present in the table.
I currently have Umbraco.CMS.Unattended.UpgradeUnattended set to true from when I was working on the initial upgrade, and am unsure if this can stay true, or needs to be switched to false.
I am unsure if there is anything else to check. Any other table that may need the column, or if some folder/file is missing. I read somewhere that this could also be a result of the folder umbraco/Data/TEMP/DistCache being missing or empty. That folder was not in my instance until I added it.
Any help is greatly appreciated.
Thanks,
Eric
Update, as I’ve done a bit more digging
One thing I noticed is that the table umbracoKeyValue looks a bit off:
For context, I have a dev. instance that looks like this, and has exhibited no errors:
I have ordered these both by updated DESC to get an idea of what the latest thing that was updated.
One very strange thing is that it says the updated date for the Premigration is 7/31, but my time on the machine, and in real life is 7/29. I am completely unsure how or why this date was chosen.
Another thing I noticed was in the deploy settings, our build environment differed between Debug and Release. I’m unsure if that would cause any issues though, but when messing with changing Umbraco to Production mode, and reconfiguring it, it seemed like it did
Also, I’ve been using the following command to try and redo the migration:
update [MyUmbracoProhect].[dbo].[umbracoKeyValue]
set value = '{EEF792FC-318C-4921-9859-51EBF07A53A3}'
where [key] = 'Umbraco.Core.Upgrader.State+Umbraco.Core'
I got the command from here: Downgrades and Re-Running Migrations | CMS | Umbraco Documentation
Thanks,
Eric
Hello y’all, another update,
Deployed in Debug mode to try and get more information. Deleted all of the folders within the umbraco folder and reset the migration as well. I also made sure both the migration and pre-migration came after the Umbraco.Core.Upgrader.Lock entry in the umbracoKeyValue table
So far, there’s been no errors, so starting to think it’s something with the configuration specifically when deploying in Release mode.
Thanks,
Eric
It is a big leap from 13 to 17.
I personally reviewed this for our company and decided to rebuild sites.
In fact, with 18 and the element Library this is the big shift to how we build sites for clients. Since the latter version of 13 and how URL routing works to fit the latter .NET having non URL’ed objects in your node tree is a mess.
So a full conversion with the new concepts and then content migration.
Been an easier process then when we first tried to update. More time and cost for client but better outcome.
Quick update,
Found the root of the problem. We had a task on the machine to restore the database from another instance, since this was a testing environment. The database it restored from was a v13 DB. So when it spun back up, the migration hadn’t applied yet, causing these errors. No problem in Umbraco here, was a personal issue.
Thanks,
Eric
