Hi All,
We are in the process of updating from 2022.2.9 to version 2024.1.9.
As a bit of context, we are on-prem and use a file system to store our files.
We came across a slight anomaly where the attachment where the panel hangs, spins for a large amount of time, the webpage becomes unresponsive and then eventually loads approx 15 - 20 seconds later if there is any attachment present.
Has anyone experienced anything similar?
As you’re in the middle of an upgrade, is the attachment storage filesystem on a different server than the production server? Is it linked to a mapped drive or is the server location referenced directly?
Hi Kevin,
Yes, the attachment file system is on a server different from our production servers.
The file server is not a mapped drive on the production server, but has access.
In our attachment configuration, we use:
\\fileserver\attachments\company
First thing I would try would be to take a look at the Ice.XFileRef table to make sure nothing looks odd there. That’s where Epicor stores all the attachment paths. Do you know if the same thing is happening in the browser, or if it’s just the client?
Also, does it happen on the same record twice? I mean if it hangs when loading a PO with an attachment, does it still hang if you close that PO and open the same PO again? or does it only happen the first time a record with an attachment loads.?
There doesn’t seem to be anything peculiar in the XFileRef Table, we also tested this in our Education environment.
Behavior is consistent across both client and browser.
It is rather strange from my observations, if there is no attachment the slider is instant, if there is an attachment then the hangs.
It’s hard to tell via the debugging tools as it’s not showing any other network events after getting the doc types.
If you try to open the attachments, do they open quickly?
One thing to try is to add the attachments location as a mapped drive on the app server, and then change the file path value of 1 record in XFileRef to use the mapped drive ( “J:\company\filename.ext” instead of \fileserver\attachments\company\filename.ext" ) and see if that makes it load any faster.
Have you tried running the bo that does the list retrieval manually and seen how long it takes?
Interesting- I will try this out.
I’m pretty sure we also tried uploading directly to the server and the issue still persisted.