10.2.600 Ice.Common.InvalidSessionException

I guess where im a bit confused if the default was 72hrs before, why hasn’t MES thrown a MessageBox like that after a 3-4 day holiday weekend.

Most Shop Floors have like 10-20 MES Stations and they remain logged in and users just clock in and out.

I’ve also seen that error in the past but only in the Server Logs, but never in a MessageBox unless we abruptly restarted IIS.

We have all done the same thing since 10.1.400 atleast here.

Perhaps the GetRowsKeepIdleTimeWithBallonInfo was waking itself up in the past, and no longer? :smiley:

Or perhaps the Users never reported it and I haven’t seen it

1 Like

We will look at it - maybe we can route to the Change User form.

3 Likes

Joshua,
Thanks very much for the SQL trigger code - a simple but brilliant fix!! We’re having this issue after upgrading to 2022.x recently.

Good to know that it is not an issue with the kinetic MES screens though! We’re in the process of migrating to the kinetic MES, but are working past some barcoding issues there before we can make that leap.

Kudos to you Sir! :slight_smile:

No problem. Only need to use that if you want to extend beyond 3 days. If it wasn’t a problem previously for you then I would advise just setting the timeout back to 3 days in the app server application settings.

If anyone has any additional input or ideas for how Idle Timeouts should be handled more gracefully, checkout the Epicor Idea:
Graceful Session Idle Timeout | Epicor Kinetic Ideas (aha.io)