It went to the regular Epicor landing page.
3 Likes
No cigar just went to Kinetic homepage
1 Like
The list of issues is growing…
1 Like
Interesting. A different workaround to the published one.
Published one is to navigate to office mes once logged in via the dc / mes url.
https://gist.github.com/Epic-Santiago/c82c06989fec4d3a6d9fc2b59e7da2a3
1 Like
One might wonder why this isn’t a KB in EpicCare…
2 Likes
When are they going to roll this out to production do you know? So as it stands right now, our entire shop is not going to be able to get to MES via the URL they use right now?
1 Like
From the last dates they offered around Dec 2025 Prod rollout was scheduled for April-ish. But they’ve said nothing since so 
1 Like
Was the linux move on Pilot also announced and expected for right now?
The maintenance notices said nothing about it. So, I’d say, NOPE.
It’s a surprise. Never know when it will happen.
This was their most recent official update I think.
1 Like
Did. Not. Happen.
4 Likes
Which does work but allows the shop floor access to Epicor.
I did ask in the case that I submitted why they gave me a different answer than the knowledge article.
Right now we have an automatic sign in (which has issues in Kinetic) that takes them to a custom MES screen in classic.
This work around will not automatically run your MES with the custom layer even if you have set up the process menu to do so. You have to make an additional menu option to call the MES with the custom layer.
1 Like
When they fixed this a while back I was so relieved, that was wild when they used to be able to do that, and now it looks like they can again?
1 Like
Correct. I had no idea it had happened until someone quoted me here from an old thread. My quote was from an email that Epicor sent me prior. No I had no idea that it had been moved to Linux. I got an email from Epicor to continue testing when I had not been informed to start testing. Then I got an email from this thread referencing something I posted on another thread. I would have had no idea - thank you forums for bailing me out again.
I am a customer and do not work for Epicor. I said a lot of bad words today finding out that not only does the MES no longer work in Pilot but also all of our labelling.
So I cannot test the final parts of retiring FTP tested-ANOTHER- project that Epicor dumped on me. I probably spent a good portion of last year testing Kinetic for existing applications rather than new things for my company. Unbelievable that they think this is acceptable.
I added to my FTP ticket that AZ fileshare no longer works in Pilot environments of customers who have been moved to Linux containers. Please fix.
3 Likes
Don’t feel bad, I’ve been doing it since Friday when all the fun started.
1 Like
You weren’t the only one. And the words weren’t without justification. Epicor has handled this very poorly.
This thread has spilled over into this one too.
2 Likes
@tpynepeak, Do you have anything special about your MES setup? Mine appears to be working okay on Linux.
The only thing I gleaned out of your earlier posts was that you’re using an automatic sign-in that goes to a custom MES screen.
I have custom layers on my MES… but are you directing to a different (custom) MES form all together?
My MES appears to load fine, with my custom layers. I’m able to log-in etc. Just curious as I’m waiting for the shoe to drop.
1 Like
The automatic sign in is for Classic. Haven’t gotten it working for Kinetic yet.
My issue is that when I use the link to use the MES it goes to the regular Epicor landing page. This link has been working for months. Linux containers happen it stops working. Cannot use the fileshare either.
Right now the only way I have of getting to the MES is by using the Office MES menu option which defeats the purpose of using the MES.
1 Like
Does it do anything different in incognito? There’s a known issue with Kinetic and caching that causes MES to go to full Kinetic.
1 Like