Hi Team,
Today I am seeing a lot of error code 1107, 'The Session ID 18 is no longer present on the server', for a couple of hours..
All of the client Apps have RemotePing enabled per default so this suggests a physical disconnection or shutdown of the PC or a full crash of the app.
OK. How do I identify who/what was Session ID 18?
How do I mitigate this Pls?

Regards & TIA,
Ian

A screenshot an entry of the above is attached.

Ian


Look at View Logged Events in EDBManager - either via the menu option or via

select * from configuration.logevents wher

There's a SessionID you can use to select those applicable to session 18. You should get enough info to identify the user

Roy Lambert

Hi Roy,
That is what is being viewed in the screenshot.
Yes it identifies the PC but not what App aside from possibly 'Log Manager' but I am guessing that is within the Server, and the User is 'System'.
So is this suggesting the Server itself lost connectivity??
Regards,
Ian

Ian


Now you say that, I'd hazard a guess that you're right. Someone has logged in, lost their connection, tried to reconnect and its not there. I'm pretty sure that Tim has explained where System is the user, and it would make sense for a reconnect since the user hasn't logged in at that point. Either the user has waited long enough for the connection to be removed or something nasty has happened.

What do you get if you filter for that userID &  Process. Somewhere before the reconnect event you should see a connect (and possibly) a disconnect event and that should identify things a bit more.

If the log files aren't to big email them to me and I'll have a play.

Roy Lambert

Hi Roy,
Sent via email. - 400+kB

Ian

Ian


I'll start tomorrow

Roy Lambert

Ian,

<< Today I am seeing a lot of error code 1107, 'The Session ID 18 is no longer present on the server', for a couple of hours..
All of the client Apps have RemotePing enabled per default so this suggests a physical disconnection or shutdown of the PC or a full crash of the app.
OK. How do I identify who/what was Session ID 18? >>

These errors occur when the session has been removed from the server, and the client is trying to reconnect using that session information (ID, etc.).  It's a fairly typical error and can occur due to network issues, server restarts, etc.

I've added additional information to the logged events so that the client's session name and process information is also included in the error message.  However, the reason why this information isn't included is because this error is typically raised on the client where the client session will already know this information, and handle the issue accordingly with a session shutdown/clean connection attempt.

Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim,
I just had a thoughty...If a workstation PC went into standby/sleep mode for a period, IIUC the Server would eventually see that wkstn session as disconnected and then remove the session.  If then the User 'woke' their PC and tried to access the Server, that would result in the error/issue seen?

Regards,
Ia n

Ian,

<< I just had a thoughty...If a workstation PC went into standby/sleep mode for a period, IIUC the Server would eventually see that wkstn session as disconnected and then remove the session.  If then the User 'woke' their PC and tried to access the Server, that would result in the error/issue seen? >>

The server will only detect a client socket disconnection if it tries to read from the socket and the client socket has already disconnected.  It will actively disconnect a socket if it is waiting on data from the socket and doesn't receive anything within the X session timeout period defined on the server.

So, either of these situations could apply in your case, and yes, they would result in the "session ID not found" error.

Tim Young
Elevate Software
www.elevatesoft.com