I’ve not posted or really been on the forum for way too long! Hope everybody is keeping well. Gutted to have missed Insights this year, fingers crossed for next year!
I’m just spinning up a test instance of Kinetic 2021.1, but running into an issues at the Database Upgrade step. It’s failed with this error, trying to update a table that doesn’t even exist. I checked the update guide, and it doesn’t specify that you have to be on a particular version of 10.2 before upgrading.
It seems that the table it’s trying to modify (DynAttrValueSet) wasn’t even introduced until 10.2.600, so it should be running those scripts as part of the upgrade but isn’t doing so. Do I have to upgrade to 10.2.600 first, then 2021.1? Or is this a bug?
It’s giving me the run around for sure! I installed 10.2.700 with latest update (25), and tried to Upgrade the DB using that first. It did all of the DB scripts, but then failed when trying to insert the seed data:
10.2.700 Error
Seed Data
Error Load table from file Ice.ReportStyle Exception thrown loading table: Index was outside the bounds of the array.
Error Load table from file Ice.QueryHdr Exception thrown loading table: Index was outside the bounds of the array.
Error Load table from file Ice.ElementHeader Exception thrown loading table: Cannot insert the value NULL into column ‘InstallationOrder’, table ‘Epicor10UpgradeTest.dbo.Seed_ElementHeader’; column does not allow nulls. INSERT fails.
The statement has been terminated.
Error Load table from file Ice.ReportStyle Exception thrown loading table: Index was outside the bounds of the array.
Error Load table from file Ice.QueryHdr Exception thrown loading table: Index was outside the bounds of the array.
Execute Phase Complete: 238.4923554 seconds
I then tried to run the 11.1.100 upgrade on top of that DB, on the basis of thinking that it would delete and re-insert that seed data anyways. Produced a similar but slightly different error:
11.1.100 Error
Seed Data
Error Load table from file Ice.ReportStyle Exception thrown loading table: System.Data.NoNullAllowedException: Column ‘FormatCulture’ does not allow nulls.
at System.Data.DataColumn.CheckNullable(DataRow row)
at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Boolean suppressEnsurePropertyChanged, Int32 position, Boolean fireEvent, Exception& deferredException)
at System.Data.DataTable.InsertRow(DataRow row, Int64 proposedID, Int32 pos, Boolean fireEvent)
at System.Data.DataTable.LoadRow(Object[] values, LoadOption loadOption, Index searchIndex)
at System.Data.DataTable.LoadDataRow(Object[] values, LoadOption loadOption)
at Epicor.DBMigration.DumpAndLoad.LoadTablesFromFiles.LoadTable(TableLoadTask tlt, Boolean isSeedTempTable, SqlConnection cnx)
at Epicor.DBMigration.DumpAndLoad.LoadTablesFromFiles.<>c__DisplayClass13_0.b__0(TableLoadTask tlt)
I then realised that the SQL Compatability level was set to 120 instead of 140, so just about to start it all off again from a fresh copy DB with that set correctly… not convinced it’ll make any difference, but let’s see!
Started on a fresh copy of the DB, ran the Upgrade DB tool for 10.2.700 first, which also runs 10.2.400/500/600. After that completed, I went ahead and ran the Upgrade DB for 11.1.100 and all is good, got a working database now.
I’ll raise a ticket with Epicor, because the 11.1.100 upgraded should also run those prior conversions. Certainly in the folder that contains the scripts it does have all of those previous ones, it’s just not queueing them up to run.
Good to hear from you Mark - we certainly missed you an Insights!
Not that I can add much, but I’ll confirm that my run-up was the same 10.2.300 → 2021.1 without a problem, so I’ll agree that support needs a ticket - and if you could post back what you find that would be great.
I’m planning my production upgrade on the 9th, and nothing ever goes the same in production as it did in test so any foreknowledge of problems is appreciated!
Well I did what @markdamen did. Deleted my database and restored my 10.2.600 as a new database. Then I was able to upgrade to 11.1.100 then 11.1.200 without any issue.
