I’m posting this here, and I do have a ticket placed with Epicor this morning. This is happening on a couple of users and has just started with the upgrade to 2025.1.5 (we never did .4) - on-prem.
With my User, every time I log in, I’m consuming three to five full session licenses.
Here are some things, maybe of relevance:
I’m a Sec. Manager, the other user is not.
“allow multiple sessions is NOT checked”
Only one browser is open, not multiple computers, windows, or InPrivate sessions, etc.
Only a single company in Epicor
These are “Default User sessions, and not Enterprise Processing or MES” (See photo).
I have tried disabling, reenabling, removing account user settings, etc. I’ve read a couple of posts here, related -but not really.
Has anyone else seen this before, or are you experiencing a similar issue? I’ll keep you all posted on the ticket.
Joseph, we definitely ran into this at my previous company. It was either in 2023.2 or 2024.1 if I recall correctly. Support did deny it for a while but this was definitely an issue in collaborate. Eventually we were able to get them to deactivate collaborate and that fixed the issue for us. It was a week of constant emails saying users were locked out. Good luck!
Edit: Just wanted to add, in that previous post I said we didn’t have collaborate. At the time I wasn’t aware we did have collaborate we had just decided as a company not to use it. So deactivating it wasn’t an issue for us. I hope you’re in a similar position where you don’t rely on it.
Our third environment on 2025.1.5 looks like it’s doing this as well. I am a security manager and unchecked the allow multiple sessions for my account but opening collaborate consumes a second license under my username.
Yes, that week I just left session manager pulled up and was constantly looking for sessions to kill when we got a ticket. Vast majority of our users were never approved for multiple sessions but they would still have multiple running. It was almost like the sessions just didn’t die, so I would sort it by oldest sessions and try to end those first, then anyone with multiple sessions. We’d have days old sessions running if we let them.
Epicor escalated this to the “Collaborate” Team. I was told it was a reported/known problem. Which leaves a bad taste for me, as regular support didn’t know anything about it and they assigned me a problem number for it (if it was known, why wasn’t there already a problem number → I worked with them for two hours documenting it, afterwards which I determined it was def. related to Collaborate and that is when they moved it to the COLL team). As a side note, the Epicor tech I worked with was great as we explored the problem remotely together.
The COLL team suggested we turn it off, can you imagine? Something we are paying for and have programmed extensively, so it delivers notifications for us from quote-to-cash? I suggested they double my license temporarily until they fix it.
I 'm escalating it. I’ll keep you posted.
Here is the number: PRB0299785 (I can’t find it yet in the repository).
The odd thing, Randy, is the only reason I knew this was the issue back in 2024.1 is the same day it started occurring I had received an email saying this issue was fixed for collaborate users. At the time I did not think we had purchased collaborate. But I believe they have said it was fixed for almost a year now. I might be wrong and the email may have been to notify users of the issue, but I’d think a year would be plenty of time to fix such a paralyzing bug.
They had a meeting about it yesterday, and escalated it… I have submitted a request to our Epicor manager to temporarily increase our licenses, but I haven’t received a response yet.
This is now a tracked problem with “high” status - you can follow via:
PRB0299785 inside of Epicor
I have not heard from my account manager about additional licenses to offset the madness. The workaround is to kill sessions, which is an incredibly tedious and daunting task and not actually a workaround IMHO.
They are getting close to a resolution for us. Latest update from Epicor:
Development informed me that they identified the cause, have fixed the code and are currently in a testing phase. They should have an ETA very soon and I will share that as soon as it’s provided.
