After patching, IceCommon Database can't be reached despite no deployment error

Kinetic ERP Service Packs and Major Upgrades (any → 20XY.Z)
,
1

Oh help - anyone seen this and figured it out?

Background:

  • Upgraded dev on-prem to 2024.1.4 from 2022.1

  • Lots of issues but resolved all except the Paste-Insert issue in order lines, a registered PRB

  • Patched a dev environment to 2024.1.19 and paste-insert fixed

Problem

  • When attempting to deploy ran into the issue where IceCommon database has wrong name, ICECommon_4_3_1004_3_100 for example

  • Solved for the purposes of deploying as found elsewhere on this forum, renaming the database

  • Printing doesn’t work.

  • Have tried the “Update Database” command and it says it worked;

  • Did a full quote-to-cash (minus printing) and everything works, so connection to DB is fine

Tried So Far

  • deleted and recreated the IceCommon DB using the New Database function

  • deleted and created the IceCommon DB using the new Demo Database function

  • redeployed the appserver

  • created a new appserver

  • tried basic auth vs windows auth

Error Details

Program Ice.Services.Lib.RunTask when executing task 3561200 raised an unexpected exception with the following message: RunTask:
System.TypeLoadException: Could not load type ‘Ice.Tables.ReportStore’ from assembly 'Ice.Data.Model, Version=4.3.100.0, Culture=neutral

Edit: redoing this I’ve ended with a database name ICECommon_4_3_1004_3_100

but it’s looking for

image
image736×119 7.28 KB

I can rename it and it deploys without error, but will not print

2 Likes
2

Wow, I joined the popcorn brigade… I’m about to strip and rebuild my whole dev setup (22 hours) later this week… so if anyone has any ideas or can point me to info I haven’t read yet, it’s sure to help hapless future epipeople…

1 Like
3

The only person I know that posted on it thoroughly was @hkeric.wci and @josecgomez (who wrote about it more recently during an upgrade).

I’ll try and find the posts for you, but I imagine you already did.

4

[ FAQ ] Epicor ICECommon Database - Kinetic ERP - Epicor User Help Forum

and

5

Ugh! Hopefully you don’t have to go that far. Have you submitted an EpiCare case? Once you get through to the higher tiers, they’ve been able to get me going. Get a Teams meeting early to save days of back and forth trial and error.

What happens if you copy ICECommon_4_3_1004_3_100 to ICECommon_4_3_100 manually? Can’t screw things up worse if you’re already considering bare metal.

What about skipping 2024.1 and going to 2024.2 on your dev playground? Lots of improvements it seems…

6

So @SteveFossey there are two views in the Epicor DB which point directly to the Common Db I suspect yours are pointing to the wrong one

I have to look and see which they are this bit me cause we do replication

But look at views in your db two of them are expecting the Common Db with a specific name and I suspect your renaming etc broke em

7

Found them

See if those views are broken : pointing to somewhere else

2 Likes
8

Wow thanks everybody.

@utaylor yes I did, but thanks anyways, appreciate it. More links is better for future Steves.

@askulte good idea. I did try renaming but I noticed that on my production server, after I installed 2024.1 base for Pilot I got the ICECommon_4_3_100 DB and then when I added the 2024.1.4 update, I got an additional ICECommon_4_3_1004_3_100 database. In this case Pilot works fine, except for the paste-insert bug. Maybe i actually need both and I’ll try copying one to the other.

@josecgomez that might be it. Support had us try running

create view [Ice].[ReportStore]
as
select PrintProgram, Content, ContentHash, Ice.SetReportStoreSystemFlag(PrintProgram) as SystemFlag
from ICECommon_4_3_100.Ice.ReportStore 
GO

But maybe I need to do the same for Ice.Fieldhelp

Thanks all, I’ll report back.

2 Likes
9

Please do so we can learn with you!

1 Like
10

Thanks Jose!

11

Also we ran into an issue @jgiese.wci where if you upgrade your Test to a new version, to try it and then later upgrade your Development (they both share the same IceCommon) if its a major version, somehow the IceCommon got stuck in a corrupt state where we had to mark it as WRITEABLE so MS SQL can upgrade the database, or we upgraded MS SQL, something odd, the Readonly state of it causes issues.

3 Likes