Why are you using OPENROWSET to do this and not issuing the commands directly?

I suggest you do this using TRY/CATCH:

BEGIN TRY
--Perform your INSERT here
END TRY
BEGIN CATCH
--Send your e-mail here
END CATCH

What...

Can you confirm that you tried connecting from SSMS installed on the same machine as where SQL Express is installed?

If you wade through this document, you will find that this is a supported upgrade, so the short answer to your question is 'yes'.

Which version of SQL Server are you using?

OK, not sure what to do next.
I have no trouble loading a table with a NONCLUSTERED columnstore index using SSIS OLEDB source and target, so if that's an option...

If you disable the OLEDBCommand, does the error stop happening?

If yes, you need to reengineer your package. Direct the 'changing' rows to a work table and then call...