Migration issues from umbraco 13 to 14

[dennispedersenakqa]

Hi everyone

Im having issues with upgrading from umbraco 13 to 14. I’ve been searching and cant seem to find a solution for it. I can skip the migration, but further down the line Im getting more migration issues, and im wondering if it could be other umbraco 13 migrations that hasnt run correctly. I would love any input on this.

[09:18:32 INF] Starting ‘Umbraco.Core’…
[09:18:32 INF] At {DED98755-4059-41BB-ADBD-3FEAB12D1D7B}
[09:18:32 INF] Execute AddWebhooks
[09:18:32 INF] At {C76D9C9A-635B-4D2C-A301-05642A523E9D}
[09:18:32 INF] Execute RenameEventNameColumn
[09:18:32 INF] At {D5139400-E507-4259-A542-C67358F7E329}
[09:18:32 INF] Execute AddWebhookRequest
[09:18:32 INF] At {4E652F18-9A29-4656-A899-E3F39069C47E}
[09:18:32 INF] Execute RenameWebhookIdToKey
[09:18:32 INF] At {148714C8-FE0D-4553-B034-439D91468761}
[09:18:32 INF] Execute AddWebhookDatabaseLock
[09:18:32 INF] At {23BA95A4-FCCE-49B0-8AA1-45312B103A9B}
[09:18:32 INF] Execute ChangeLogStatusCode
[09:18:33 ERR] Exception (40c5a3a7).
Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot insert the value NULL into column ‘exceptionOccured’, table ‘xxxxxxxxxx.dbo.umbracoWebhookLog’; column does not allow nulls. INSERT fails.
Cannot insert the value NULL into column ‘exceptionOccured’, table ‘xxxxxxxxxx.dbo.umbracoWebhookLog’; column does not allow nulls. INSERT fails.

[Luuk (Luuk Peters (Proud Nerds))]

Why are you upgrading to Umbraco 14 and not 17? You can do a direct upgrade to 17. 14 has some issues and is completely out of support.

[justin-nevitech (Justin Neville)]

Hi @dennispedersenakqa

Please see my comment on the other thread to see if that helps.

Umbraco upgrade from U13 to U14, returning 401 error

Hi @Ajeetkmr154 You will need to using something like uSync Migrations to migrate Nested Content to block list. Likewise, if you have any Grid Layout this will need to be migrated to Block Grid and any RTE macros will need to be converted to RTE blocks. You will also need to update any obsolete data types in the backoffice and switch to newer supported versions. Once you have done this, your upgrade path to v17 should be smoother. You may still have custom backoffice code that needs convert…

Justin

[justin-nevitech (Justin Neville)]

You will also need to be on the latest v13 version before moving onto v17 once you have migrated the data as mentioned.

[dennispedersenakqa]

Ah. I was under the impression that we shuold do one version at a time. After switching to 17.4.2 it seems to work. Thank you!

[Luuk (Luuk Peters (Proud Nerds))]

I understand that feeling However, even the migrations sometimes have mistakes that get fixed in later versions. I think the migration 13 > 17 is much better than 13 > 14 or 13 > 15. As you found out

[dennispedersenakqa]

Im honestly a bit scared it went so smoothly haha. Now its time to comment in the custom code again.