It’s definitely related to the containers, so I would guess not a known issue.
Funny how all my Epicor case contacts are using the container issue to declare their cases resolved.
No. What I asked for is -not- working. That is not a resolution.
Although the silver lining is if I give enough of them 1 stars Epicor calls me.
One of the few ways I’ve been able to move items up the chain faster.
In my opinion Epicor should not be allowed to close a case and the user should be able to reopen the case within a week or two if something Epicor missed negates what was done on the case. Most modern ticketing systems allow for this.
I have 3 cases asking for this. Linux containers are causing problems with this functionality so can we close the case? No I opened it before Linux was implemented, you never got it working and now you want to close it? Hah.
Considering at least half the time I end up figuring it out before they do this is doubly bad.
We’re no closer to a resolution than this time Friday (or whenever it was when the issue was discovered). Escalated, senior this and that…we’re still hosed.
Just not been added to the known issues.
I also have many customers where the workaround for SSRS report designer is also not working therefore no way to modify reports.
That’s great.
Dear Epicor Kinetic Customer, As a follow-up to our previous communications regarding the migration of Kinetic pilot environments from Windows to Linux… *** - Be aware that certain functionality may not behave as expected during this pilot phase.
I hope they are planning to re-deploy to PILOT any changes to fix these known issues that are not “behaving as expected” for additional testing before migrating Production to Linux. On-going issue seems updates are too rushed and not thoroughly tested and not allowing enough time for testing before Production resulting in the PRB list continuing to grow and possible interruptions/work-arounds for customers.
This doesn’t help when we’re testing 2025.2 that goes into production next Friday.
This may be the biggest issue. People are using Pilot/Test (whatever they are called in SaaS) for go-live planning and testing. And they keep pushing major breaking changes. You can’t test and plan for go-live on botched Linux containers. Then go to Windows when you go-live.
The beautify on on-prem, is that when we get Linux self-hosted containers, we can have 10 pilots if we want to… we have a DEV, TST, TRN, PRD, PRB, SBX, EDU… Costs us 0$ we keep them off, until we need them. 
Friends dont let friends go SaaS. 
What a classic…
“This is your Container… This is your Container on SaaS.”
Containers for everyone!
Hey you on-prem people said you wanted containers. You never said you wanted them to actual work. 
Who would have thought we had to specify working containers
Not sure if this is part of the Linux Container issue but this was working before then.
If I open receipt entry it blows up immediately. It doesn’t get to the landing page let alone me be able to enter a PO# or pull up a receipt.
It can be the Epicor base application or a menu option with a layer. Same result.
I was going to set dates for testing to move functionality to Live and now I can’t.
AND I can’t test items on the Linux container report - BPMs that are on receiving - post processing BPMS.
Tickets were set up days ago, our CAM is involved and set them to urgent and the Director of support is involved and not one hint of a fix in sight yet.
This is bad.
Do I have to go back and test -everything- that is migrating to Kinetic AGAIN?
The number of items that just blow up without the user having to do anything is growing. They really need to up their testing game.
We’re spinning wheels too…so far all we’ve gotten from Support is the FAQ on Linux Pilot. Big help. Seems to me like any automated conversion/updating of code either wasn’t done right or not done at all. Happy Wednesday.
What so you mean? Have you worked out how to install an on prem install on a Linux container? Wow if you have…
More importantly is this thread going to meet meet the goodbye on-prem threat count?
I doubt that. Its got a long way to go 
But with all the issues the Linux containers are causing, I suppose its possible.