Hello agibbles,
This looks like two separate issues hah!
The missing EPiServer.Events.ChangeNotification assembly is expected if the CMS 13 dependencies are not fully aligned. The CMS 13 breaking changes docs mention that ChangeNotification was moved to a separate package and should be registered with
AddCmsChangeNotification()
The second error
is a database collation issue during the ChangeNotification schema update, not really a Commerce type scanner issue, so I would first align all CMS 13 & Commerce 15 package versions, then register ChangeNotification as described in the CMS 13 docs, then fix the database collation mismatch and rerun the migration.
In other words adding the package probably fixed the missing assembly problem, but then exposed a separate database/schema issue.
Cheers,
Wojciech
Thanks Wojciech. It's not missing after all, I just missed it in the docs.
As for the 2nd issue, I thought initally that the error was saying that the upgrade script was specifying a specifc collation. I didn't realize that it was saying we actually had different collations between the databases -- we do :( Wild!
Has anyone successfully upgraded to Commerce Connect 15 and CMS 13? I'm trying but...
On startup, the Optimizely type scanner fails with:
"Failed to scan some types (Failed to load types from Mediachase.Commerce) (Failed to load types from Mediachase.Search)
Inner exception:
Could not load file or assembly 'EPiServer.Events.ChangeNotification, Version=13.0.2.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7'. The system cannot find the file specified."
Then when I try to add that package manually, I get "Failed to update database during execution of statement 'ALTER PROCEDURE [dbo].[ChangeNotificationDequeueString]" because "Cannot resolve the collation conflict between "Latin1_General_BIN2" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation"