Hello,
We have the following setup in our environment:
- Server AP: where the Epicor Application Server is installed
- Server SA: where SSRS and the Task Agent (System Agent) are installed
The EpicorData folder is created on Server SA, shared properly, and there are no access issues.
In the System Agent configuration, both:
- Server Data Directory
- Client Data Directory
are configured to point to the EpicorData folder on Server SA.
However, when users try to download a file using “Server File Download” in Epicor, the system automatically creates and uses a new EpicorData folder on Server AP, instead of using the one on Server SA.
Based on our environment design, we would expect this functionality to use the EpicorData folder on Server SA, since this is where the System Agent, SSRS, and task processing components are installed.
Also, if the logic were that file operations should occur on the Application Server (AP), we would expect file uploads to also be processed there. However, when files are uploaded for certain processes, they are stored and processed on Server SA, not on Server AP.
Because of this, the current behavior seems inconsistent with the way file processing is handled elsewhere in the environment.
Could you please confirm:
- Whether Server File Download is expected to always use the Application Server (AP) for the EpicorData folder, and
- If there is any configuration that can control or redirect which EpicorData location is used.
Thank you.