I am upgrading to Kinetic 2024.1 where I installed the application successfully and I need to upgrade an older version of the Epicor database to be accessible from the new Kinetic release.
The source database with version ICE = 3.2.700.31 - ERP = 10.2.700.31 and I need to upgrade it to ICE = 4.3.100.7 - ERP = 11.3.100.7.
I tried to use upgrade kinetic database with using configuration (Use existing database)
But stopped in seed data
Best Regards,
Ramy Essam
I would rerun PostMigrate and DataModel. Seed Data thinks it has a good common db.
Hi Greg,
I am receiving the following error concerning Seed Data, please advise if you have any comment:
Ramy
This is a BIG jump. Have you contacted support or found any KB? I’m always in favor of contacting support, allows support to document issues, and you and your company staff to document too!
Your first query has an AND without a condition in front of it which is causing the error
I give up,
How can I resolve this without needing to recycle IIS on first boot? Latest 2024.1.10 on Server 2022 and SQL 2022
Just on a whim, try repairing the .Net 8 Hosting Bundle.
I have had this issue also, repairing the .net installs did the trick.
Been hearing this a lot lately.
As @FlomE points out the statement is not correct, but the statement is built on the fly from your database and references deleting rows where SystemFlag is 0 in E9 and 1 in E10 and you are well past that so I would still deal with the PostMigrate error and try to get Generate Data Model to complete.
Thanks @Mark_Wonsil @EpicorAnon , that works, but on a reboot the error still persists. Sorry if I’m getting this thread off topic. I guess the ol saying goes…
I am doing a compare of 23.2 to 24.1 and I could upgrade my 21.2 to 23.2 and then from there to 24.1 I could not get thru SeedData going direct from 21.2 to 24.1, so it seems the running theme is if SeedData craps out you need to take a two hop approach.
The Upgrade logic is designed to allow you to go from any version to any newer version - if you are having issues with that, open a case with Support.
I believe the “Failure to Start” issues was a product problem resolved in Update 8. Get the current Update and use that.
@Rich I know it should, but sometimes to be practical especially late night or on a weekend you have to get creative. My 24.1 was .10, but I will restore the database and run it again. The odd thing with the SeedData it was a system baq and ReportStyles that it choked on.
I will open a case if it does not complete on this run.
I had to delete the DB Migration folder and rerun the 24.1.10 upgrade because the db upgrade only had the steps from the previous 23.2 to 24.1 pass. After that it completed from 11.1.200 to 11.3.200. 
