We tried restarting the app pools for ECMReporting and ECMWeb. Any others you would try?
I also spoke with our IT department about whitelisting some IPs since we have been going through some internet issues and changes that coincidentally started this weekend (same as the 2026.1 update haha)
@mgordon , turned out that our Solr Indexing service was crashing out – not enough memory to run the Java VM. Increased memory in that server and our functionality has been restored.
But, your issue sounds different since you’re not able to successfully test the connection from Attachment Type Maintenance.
So, after all of this, we found out it wasn’t even an Epicor problem… Apparently we had issues with our network provider that ALSO began this weekend and some settings were changed. Once our IT department added the right IP address to the whitelist settings, we were able to view and add new attachments like before!!!
Thank you to everyone on this thread for engaging and suggesting solutions!! Especially @swilliasc111 !!! You all are awesome! 
What it an Epicor site you needed to add? What was it?
Yeah, somehow the setting that was allowing Epicor to look into our On-Prem ECM server got removed. I just used command prompt to ping the url in top right hand corner of our Epicor screens and had IT whitelist the IP that was returned. At least I think that’s all they did
What did you end up bumping your JVM-Memory to, if you don’t mind sharing? I just had to do the same with our on-prem ECM box, and Epicor support seemed baffled that it even needed to be adjusted as “…default Solr memory allocation is 4096 MB and that is the recommended allocation from us…”. The highest usage I’ve seen so far is just over 8GB on ours, so I’m curious what others have witnessed.
We were running out of physical RAM. Our server only had 4GB. We increased that to around 20GB. I’m not real familiar with Java configurations these days, but it looks like the Solr VM is configured for 12GB of heap memory. However, looking at the Solr Admin page, it looks like we’re only using about 1.5% of that.
Ahh, makes sense. Our physical RAM was fine, but the JVM usage topped out twice over the last two weeks and I noticed several items for java.lang.OutOfMemoryError in Event Viewer. Still unclear on the root cause but we’re stable now, so I’ll take it.
