Oh! I see it now.
1 Like
our configurators are screwed with no solution as of yet - and the error we are getting points towards UD methods…
1 Like
@dcamlin @Ernie Thanks for the info…
I guess we ought to take it real slow. I’m just not getting that warm-and-fuzzy feeling. Maybe we tackle the rest of the 2023.2.x patches first…and I’m even leery of doing that as we’ve finally gotten a degree of stability here.
Upgrade cadence for on-prem environments is always a VOLUNTARY leap of faith (as opposed to the involuntary variety for SaaS folks). Almost invariably, something that worked in the previous version is broken in the upgrade.
Your internal testing resources are likely to be the biggest driver of “when” to start. As a general rule, I’d wait until the LIVE SaaS environments are updated (currently scheduled for US datacenters on Friday the 13th of December, probably the .5 release), as that gives a couple of iterations of SOMEONE ELSE doing initial testing.
3 Likes
It’s one of the reasons we flex. We can shake it out and let others be the guinea pig, even in the cloud.
2 Likes
just checked ours, and in our LIVE environment it is calling V1 as is yours, however our configurators are not even getting as far as calling the UD methods in Kinetic but all the API calls that are being made with others are all V2 which were V1 - so i am going to assume we will have the same issue - with an added twist lol
Broken-in-upgrade is a constant fear…and even worse is if it’s something that was missed in testing. As far as internal testing resources go, that’s been a perpetual struggle regardless of ERP platform.
Appreciate the feedback…
I’m seeing the same in our 2024.2.3 pilot too. It does work doing what @aosemwengie1 suggests and shutting off progressive load.
A few people had issues where threatlocker (our antivirus) was flagging the new release as a virus which was just great.
2 Likes
Hey @tonyb1986 we were able to update our client see below. It was an involved process.
It blew up on update over and over.
Auto update - failed
Clear cache - Update failed again
Complete reinstall - it failed.
I had to reboot and immediately do a full reinstall. This allowed me to proceed.
Support was useless. I asked them how to avoid a complete reinstall as manually reinstalling it for all our many dozens of machines that use Epicor is not feasible.
They gave me a checklist of how to manually reinstall the program after I told them I had already done so.
And for more fun, finding out that the classic UI is completely going away in 2026 is a bad blow. We don’t have a big IT department, I guarantee that people will be talking about moving ERPs rather than losing our customizations.
2 Likes
got home tonight and client downloaded and installed fine - apparently this could be an antivirus issue for us - we use Sophos and they really get on well with Epicor 
, i did as you did above but the restart made no difference at all, and as with yourself too many PCs to have to do this on go live in december.
we DONT have an IT department because we are not big enough to warrant having one so based on the limited skills I do have, with the steep learning curve, myself and one other member of staff have been tasked with ‘fixing Epicor’ and I use that term literally!
I will seriously be pushing to go on prem to avoid losing the client…ROI over a VERY short period make it 100% worth while.
We are too heavily customised in classic, i am unsure if what we have is actually do-able in Kinetic and I don’t care what Epicor says - ITS JUST NOT READY, its too buggy still and there’s still some core features missing - I could go on a rant but I think I have enough! 
1 Like
I’ll speak from experience and say that it was “difficult”…and that was years before moving to Epicor.
1 Like
Back in the E9 days we had Sophos and it never bothered Epicor.
Hmm, we have a few users who just gets a blank screen after the update. We’ve been unable to get them working. Clearing cache doesn’t help, nor reinstall. I’ll try the reboot then install before trying to open the client.
1 Like
I guess this is one good thing about moving towards browser first!
1 Like
Crowdstrike has entered the chat…
4 Likes
First Sophos, now Crowdstrike???
2 Likes
1 Like
I had that yesterday but clearing the cache solved it.
1 Like
this is now fixed for us - Sophos was causing the issues - the antivirus exclusions were quietly updated!
See the Epicor KB0073235
3 Likes