Data breaks on upgrade to 16.4-rc2 from 13.12; same works on 16.1.1

[BlagoCuljak]

Which Umbraco version are you using?

16.4-rc2

Bug summary

So I tried to upgrade to 16.4-rc2 from 13.12. It renders all my nodes unpublished, all of them having multiple issues, from DataType config to other thing.

I suspect some database migration is not in place. The Output windows displays different things on upgrade one or other version.

Upgrading my database from 13.12 to 16.1.1, works fine, and I see some db migrations executed first.
Detected current version 16.0.0 ({CC47C751-A81B-489A-A2BC-0240245DB687}), which needs to be upgraded to 16.1.1+7e82c25 ({D1568C33-A697-455F-8D16-48060CB954A1}). To compare versions and read a report of changes between versions, use the View Report button below.

I do same thing, same database, code, just I bump Umbraco versions:
Detected current version 16.0.0 ({CC47C751-A81B-489A-A2BC-0240245DB687}), which needs to be upgraded to 16.4.0-rc2+be11643 ({6A7D3B80-8B64-4E41-A7C0-02EC39336E97}). To compare versions and read a report of changes between versions, use the View Report button below.

All nodes become unpublished, when I try to publish one, I get errors:

[16:12:24 ERR] Exception (aa9c86a5).
System.InvalidOperationException: The given ColumnMapping does not match up with any column in the source or destination.
   at Microsoft.Data.SqlClient.SqlBulkCopy.AnalyzeTargetAndCreateUpdateBulkCommand(BulkCopySimpleResultSet internalResults)
   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults, CancellationToken cts, TaskCompletionSource`1 source)
   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts, TaskCompletionSource`1 source)
   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)
   at Microsoft.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount, CancellationToken ctoken)

Specifics

I can not upgrade first to 16.1 and then to 16.4 due to this issue: #20409

No response

Steps to reproduce

Upgrade bit more complex db from 13.12 to 16.4-rc2 directly

Expected result / actual result

Data is visible, but all nodes unpublished. And errors on save.

[github-actions]

Hi there @BlagoCuljak!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

As you say @BlagoCuljak, it looks like the migration isn't complete correctly, leaving you with a database table missing a column that's expected to be there. Is there a chance you can privately share the database with me, so we can try to replicate the migration issue and debug what might be going wrong?

[BlagoCuljak]

How can I send it to you? Pozdrav, Blago Čuljak

…

-------- Izvorna poruka -------- Šalje: Andy Butland ***@***.***> Datum: 25. 11. 2025. 20:46 (GMT+01:00) To: umbraco/Umbraco-CMS ***@***.***> Cc: BlagoCuljak ***@***.***>, Mention ***@***.***> Predmet: Re: [umbraco/Umbraco-CMS] Data breaks on upgrade to 16.4-rc2 from 13.12; same works on 16.1.1 (Issue #20957) [https://avatars.githubusercontent.com/u/1993459?s=20&v=4]AndyButland left a comment (umbraco/Umbraco-CMS#20957)<#20957 (comment)> As you say @BlagoCuljak<https://github.com/BlagoCuljak>, it looks like the migration isn't complete correctly, leaving you with a database table missing a column that's expected to be there. Is there a chance you can privately share the database with me, so we can try to replicate the migration issue and debug what might be going wrong? — Reply to this email directly, view it on GitHub<#20957 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIGXGWLIKBNEDGE2TCKM7FD36SWZVAVCNFSM6AAAAACNFJ3C6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNZXGMYTGNRWHE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[AndyButland]

You can send me a link privately at abl AT umbraco DOT dk.

[AndyButland]

Thanks for sending the database over. I managed to complete the migration OK and didn't see the issue where you found the content unpublished. I did see the same error as you when trying to re-publish a document though.

Digging in I could see it was failing where as part of the publishing process we update the umbracoPropertyData table records via a SQL BulkInsert operations. In this context, column names are case sensitive.

Examining your database I could see you had a field in umbracoPropertyData called propertytypeid. However in new installs - going back a long way to my knowledge - this field is called propertyTypeId. I don't know if you have any idea why the wrongly cased name is in your database?

This bulk insert isn't a new thing, so I'm unclear as to why you report and find this issue only with 16.4 and not earlier versions.

To resolve I've renamed the column via:

EXEC sp_rename 'dbo.umbracoPropertyData.propertytypeid', 'propertyTypeId', 'COLUMN';

After that I could publish OK.

So I think that should resolve your issue - but as you can see, I haven't really tracked down anything that relates to migrations, so maybe there's something else going on. Nor really why you found this working on 16.1.1 (but perhaps you didn't actually try a re-publish there). As of now though, I'll close the issue. Of course please re-open or create a new one if you do find anything further.

[BlagoCuljak]

@AndyButland I change that, I did clean install 13.12, checked db changes with my database, synced schema 100%, then I upgraded to 16.4., I published my root with all of its descendants (no errors), and they seem published, but actually, are not. I get URL, status published in UI, but anytime I navigate it asks me to Save or ignore changes, and there are no changes. I try to open the page, it works, I try to fetch some details with working controllers, it displays as not published. Cleared cache, everything. Any idea?

https://ibb.co/JwmXPbRb

[umbracocommunity]

This issue has been mentioned on Umbraco community forum. There might be relevant details there:

https://forum.umbraco.com/t/http-error-500-after-upgrading-to-16-4-0/6814/9

[arknu]

@AndyButland Is this going to be fixed in v16 as well?