Can also open Receipt Entry without issue. My image tag is
ud12110010-17-hotfix-d
Receipt Entry not an issue here either. Sorry @tpynepeak, not sure how to help on this one.
I had issues loading PO Entry for me and received errors after a recent update. Maybe this is similar. Go to App Studio, look for the ReceiptEntry app, go to the Personalizations tab and see if there are any for your user. Delete if so and try again. Not saying that it will work but a similar issue was resolved for me recently by doing that.
We already had this happen for one of our users, but it cleared it after they cleared their browser cache. May be worth a try if you haven’t done so already.
w/r/t the azure issue my case - CS0005318184 - was escalated and I did receive a response, albeit brief.
–
‘It is my understanding that there are a couple pathing related issues that are currently being looked into. Once I get more information on what is happening, I will be happy to pass that on with.’
That almost seems like they are in the process of updating your environment?
I agree, this reads like that to me.
And this is dumb.
Epicor did maintenance last night on Pilot and we got the all clear.
I was able to work this morning until I logged out…
And now this is stuck at 44%. I honestly do not know what they are thinking.
But I am effectively shut down. I can’t develop or test any of the items they pushed on us recently (FTP, Linux containers) or Kinetic conversions. Or gee like work for my company that is not related to Epicor upgrades.
From what I gather the mapping for ServerFolder.FileShare for some of us needs to be remapped. I got instructed our remapping was done and to test. Our export is now going to our FTP and is working as we need it too. Hopefully yours gets fixed soon too.
Sorry anyone if you see this multiple times, but there have been multiple threads with this issue. I was able to get my labels working in Pilot by updating the Output Location in Report Style from:
\tenantid.file.core.windows.net\tenantid\Pilot\Bartender\AGM
to
/epi/fs/Pilot/Bartender/AGM
So, replace anything that has '\tenantid.file.core.windows.net\tenantid' with ‘/epi/fs/’ and it may work for you.
Update: I had a meeting with Epicor about this.
With Linux containers you can apparently have FTP or Fileshare but not both.
Found this out when testing the fileshare solutions that had been working.
I was able to prove to Epicor that you can do both with Windows however. Linux seems to be a step backward when they are forcing us to retire FTP.
You can’t test incrementally anymore, its all or nothing.
From the case notes
Just wanted to chime in that this worked for me too.
Still waiting on an official word/fix from Epicor but at least we have something if they decide to push this to production before it gets fixed properly.
Same…base Import EDI Process wasn’t working but it does now. Changed the path and to the /epi/fs/ prefix instead of the full Azure path (and reversed the slashes)
Same issue here, MES link (Data-Collection License) now opens the Home Page (Office License). Epicor has acknowledged the issue in the PRB list. Suggested workaround from Epicor - use the Office menu which consumes Office licenses and does not allow for shared Epicor accounts with individual employee logins for clock in/out on shared computer stations in a shop environment. Alternate work-around from Epicor - use Classic??? This would be a show-stopper in Production.
That workaround would be so vile.
This whole rollout has been vile. Announced in November, rolled out on us without warning in February while in the middle of testing 2025.2…
Not amused.
And you won’t even get as much as “sorry” from Epicor.
And I’m not saying that to start a 
, it’s just the truth. They do not care even the slightest about the inconvenience this causes customers.
Nope…they left our code in ruins and now we’re scrambling. They started the with a halfbaked rollout.
It could’ve been a collaborative rollout of Linux. They chose the vile rollout. This community could have made the Linux migration great. Instead they’ve opted to create further distrust.