We are seeing multiple issues this morning inside our ECM platform. Orders are not processing. “Common Language Runtime detected an invalid program”
There was an upgrade to ECM/AWS over the weekend and some hosts were affected by a re-index problem.
Open a Case with Epicor and they’ll kick off a re-index which will fix the issue.
We had the same problem.
6 Likes
We’re having he same issue too.
1 Like
I have a similar Runtime Error. I submitted a case with ECM, should it rather be with Epicor Kinetic?
1 Like
No the issue is with ECM but it should all go through EpicCare (or the Chat in your ECM Console)
1 Like
We are also having ECM issues this morning. We were not notified ahead of time of an update this past weekend to cloud 10 east region.
You need to subscribe to notifications at https://status.epicor.com/
Thanks Randy, we are subscribed and do receive the monthly notifications for monthly version update along with monthly maintenance updates. maybe I missed this one digging through emails now
Either way, I had a user report an error and they went back in to try opening attachment again and now no error… maybe to @josecgomez 's point they did a re-index for everyone.
1 Like
I know we got notified. I always put a calendar reminder in my Outlook so I remember to check post upgrade if something was FUBARed. You know, like what happened today with ECM.
2 Likes
We are still having issues and were told by support that they can’t re-index until tonight.
2 Likes
We do the same, our notification email says we are getting the update Nov 14th on cloud 10. In any event thanks guys, glad to see this appears to be a known issue today that the Epicor ECM team is aware of.
2 Likes
it goes smoothly for you guys. We’re getting the 2025.2 upgrade this weekend and that thread has me scared…
1 Like
how would the backup be done? this is the first time we’re gonna do an upgrade of ecm. So i wonder what things need to be backed up, in case something goes wrong and we need to rollback
Are you on premise or cloud hosted?
Cloud
All you can really do is take an overall export of everything, but this wouldn’t really help with the reindexing issue many have reported.
On Premise
Take backups of the following databases on the SQL server where ECM is installed:
AAAA0001
AstriaHost
SignalRBackplane
Fortunately, upgrading to a new version of ECM is generally straightforward and runs into few issues, but it’s not always 100%, either. Backups are always a good idea and depending on which version you’re upgrading from, you may need to upgrade to a specific version before upgrading to the latest version. There are notes in EpicWeb about this transition as it relates to Solr.
3 Likes