My Bartender integration stopped working in pilot.
I am on Flex 2, and my pilot is still on Windows, so no Linux issues here.
Nothing was showing up in my Azure File share.
On a hunch, I decided to look at my FTP..
Guess where my files are… yep.
They changed where ServerFolder.FileShare is pointing. I did not request this.
I did! lol
I have had a ticket opened for 5 months to get them to add a new ServerFolder.FtpRoot enum that would point to the FTP root.
Their genius idea was to point ServerFolder.FileShare to the FTP root if there is a FTP instead, apparently.
Seems we can’t have nice things.
Hey all, Linux container issues are popping up across a ton of threads right now and it’s getting hard to keep track of everything. In order to give the community (and Epicor) a better chance of actually addressing all of this in one place, we’ve put together a summary thread that consolidates all the known issues, workarounds, and asks.
If you’re hitting Linux-related problems, please check in there and add anything we missed. Lets keep it constructive and dealing with the problems at hand, not emotion. Epicor is paying attention so lets get things resolved!
Yup, we just figured out the same thing. Replied here because I like the picture:>)
This isn’t a linux container issue. I’m on windows.
I believe the change was due to that though.
I’m 90% sure it’s indirectly my fault.
CS0005155933
I have been hounding them for 5 months to fix Sandbox.IO to allow reading and writing to FTP root.
I’ve been able to review this case with Development and believe we have a path forward on getting this set up on your Pilot environment for testing. I’ll update you once it’s been completed.
We have discussed your case with development, and this won’t be available until your Pilot environment is moved to Linux. This should happen in the next few weeks. Once done, we can test the process and bring up any issues to development.
I’ve been asked to have you try the following.
/epi/fs/Bartender
Let me know if that helps.
Famous last words…
I doubt it.
Hello Kevin!
I have reverted the changes, ServerFolder.FileShare now is pointing back to Azure file share, instead of your legacy FTP.
Thanks!
Hello Kevin,
We are currently working on this and wanted to share some background.
During the preparation work for your Linux migration, the system detected you previous had FTP related configuration, and to avoid any impact during the migration, the FTP details were added to the YAML file. In your case Since FTP hasn’t been used for a long time, this configuration is no longer needed, and shoulnd’t be insterted. We will update the YAML so that Azure File Share is correctly mapped on the backend and your files continue to route to the right location.
I’ll keep you posted.
Hopefully they don’t close my FTP down lol, since I’m still paying for it and my EDI uses it 
Guaranteed they will. They did it to me too, initially.
I am confused. Our Pilot is also broken and Epicor set us up with an FTP site a very long time ago.
It used to be \ausdtswebprd00\92858\ and now Epicor is saying to use /epi/fs/92858/. It isn’t working and EpicCare has been working on this for weeks with no fix. What is /epi/fs/? It is needing to save to a local server or is it placing the files in Epicor’s FTP site?
/epi/fs/ is a folder/subfolder in the root of the linux filesystem - presumably epicor has configured the ‘siteid’ folder as a symbolic link to either the ftp/azure file share, and your link is broken.
It’s both a local folder and a remote folder (it’s a symbolic link)
Or pointed to one you are not looking at.
We were told to use /epi/fs/ without any site id. That worked for us.
using /epi/fs/ with no siteid worked; thanks!
I know there is a PRB for them to introduce ServerFolder.FileFTP or something like that which would go to /epi/ftp if I recall.
I hope they get that up soon, because our bartender integration works by looking at an FTP connection on our server. Epicor support told us to point our BPM at /epi/fs/ and that fixed the BPM error, but I am not sure what to do about the integration.
We switched our bartender integration to look at the azure file share.
The powershell script Epicor provides, maps the share to the current user, so I had to do a little extra so Bartender could access it.
At first, I tried to switch the bartender services to run as a local user, but bartender did not like that.
In the end, I switched bartender to running back as local system, and used nircmd to run the powershell script to map it so bartender could see it.
Works a treat.
We already have the azure file share on our bartender server. It works fine in the live windows environment, but in the linux pilot we get a BPM error if the BPM points to the azure. That is why I thought to make the bartender integration point to the linux file share. But I do not know if there is a way to do that yet.