Convergence Session Not Found On This Server

SOLVED

Good morning.  Our company is seeing an increase in the following error message, "Convergence session not found on this server {session id}.  This can due to an unscheduled server restart.  We recommend you to consult the technical detail to get more information about this issue."

Technical Detail: NodeJS: Convergence Server - x3Dispatch

Currently we are running on a hosted virtual server where both our IIS Application and our SQL server reside and are sharing resources.  We have had the hosting company increase the memory and add processors to the server but we are still getting the error message.

When I go into Administration - Web Client Sessions - Under X3 session, there are numerous lines that have a blank value but everything else has a value.  Also there are Client Sessions in Development - Users Monitoring that aren't listed in the Web Client Sessions.

Also, I followed the steps in the other article and set our session timeout to 20 minutes.

Parents
  • 0
    Have you solved the problem?
    Thank you
  • 0 in reply to fralupo
    The problem is not solved but has been reduced significantly. After trying different solutions, the solution that worked best for us was increasing the new number of processors and memory on our virtual server. Depending on your environment, you may need to test to find the best combination for your environment.

    The other situation we noticed was people were running multiple sessions by clicking on the tab and selecting duplicate instead of using the open new session function within Sage. As a result, both tabs had the same session id.
Reply
  • 0 in reply to fralupo
    The problem is not solved but has been reduced significantly. After trying different solutions, the solution that worked best for us was increasing the new number of processors and memory on our virtual server. Depending on your environment, you may need to test to find the best combination for your environment.

    The other situation we noticed was people were running multiple sessions by clicking on the tab and selecting duplicate instead of using the open new session function within Sage. As a result, both tabs had the same session id.
Children