Jon, we test the upgrade always in a lab environment first. That’s where I got the error. All previous upgrades went smootlhy without problems, but it’s always good to take time to prepare the upgrade to a new version!
We’re already using the collation that is advised, but two different collations caused my DB error (and I’m not the only one here that got this error). So I had to investigate why I had two different collations on my tables.