7/4/2025 5:33:23 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 06 May 09 12:40 PM
|
Is there any way to not randomly and repeatedly kick the user out of the 7.5.1 web client? Using this thing is at best a headache for users that are in this for any length of time greater than 5 minutes...
|
|
|
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 06 May 09 2:21 PM
|
- Check the Application log and see if there are exceptions that are not being properly handled that could be kicking the user out (sometimes the problem is in the data).
- Keep the Reminders option turned On so that the client is constantly pinging the server for Updates, thus keeping the Session alive.
- Check your IIS Settings and ASP.NET settings to make sure that your sessions are not being timed out.
- Don't use "Web Farms" on an IIS instance, rather use Multiple Instances (better for the Sessions).
- If you are using Multiple Servers and load balancing, synchronize the Encryption keys. This avoids exceptions on the Forms Authentication.
- Review the values of the User Options (specially if this is an upgraded system, there was no conversion for the Options from 6.2 to 7.2, and there may be values that are not compatible with the new version).
- Determine what actions cause a given user to be kicked out. If you are getting an ASP error page, it will have a matching error entry on the Application log, but you could alternatively turn off Custom Errors on the web.config.
I run SLX Web 7.2.2 with over 3500 users on multiple servers each with multiple instances, and had to go through many of these scenarios. 50% of them related to Data, so we fixed the data and added better error handling where appropriate. At this point, the environment is fairly stable and we seldom see any users getting kicked off the system. |
|
|
| |
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 06 May 09 6:29 PM
|
We use a Hardware solution for Load Balancing.
The load balancer has a list of all our Instances (Server:Port) and divides the requests across the instances.
It also query each instance to determine if SLX is functional, if not the instance is taken out of the rotation.
The load balancer is configure to use Cookies to maintain the Session affinity.
As far as configuring the SLX Instances, the only special step we took was Synchronizing the Machine Encryption keys.
Off course, due to the Size of our Database and the expected load of the servers, we fined tuned our indexes and our IIS settings. |
|
|
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 19 May 09 3:48 PM
|
Hey Raul,
How are you doing?
I wanted to know if you could spare some time to answer a couple of questions as it seems that your post relates to some issues we are having.
We are getting timeouts, users getting logged out, the web page comes up but no one can come in, during data entry and after saving, it kicks the user out, etc....
I wanted to know how this was done:
- If you are using Multiple Servers and load balancing, synchronize the Encryption keys. This avoids exceptions on the Forms Authentication.
- Keep the Reminders option turned On so that the client is constantly pinging the server for Updates, thus keeping the Session alive.
- Check your IIS Settings and ASP.NET settings to make sure that your sessions are not being timed out. (what would the optimal settings be)
Thank you for your time and if you can not answer them, it is ok. Your post was beneficial to us anyway.
DP
|
|
|
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 19 May 09 4:11 PM
|
Hello Raul,
I have a couple of questions:
What load balancing device do you have?
How do you synchronize the encryption keys to avoid Form Authentication.
How do you keep Keep the Reminders option turned On so that the client is constantly pinging the server for Updates, thus keeping the Session alive. |
|
|
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 19 May 09 5:18 PM
|
| What load balancing device do you have? |
|
BigIP F5 load balancers, using cookie affinity rules.
| How do you synchronize the encryption keys to avoid Form Authentication. |
|
Generating an Encryption key and then setting it on the machine.config.
| How do you keep Keep the Reminders option turned On so that the client is constantly pinging the server for Updates, thus keeping the Session alive. |
|
This is a user option. By default users can modify it, but you could customize the system to disallow that, and then force the option to always be true for all users. |
|
|
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 20 May 09 9:36 AM
|
Thanks Raul.
We have the same Load Balancer setup.
We currently migrated to 7.2.2 from 7.0 and we were experiencing logouts, signouts, timeouts, etc....
It seems to happen alot when users do searches and when they enter in data. They either get logged off or they get timeouts, etc..
It seemed like you had similiar issues to what we were experiencing now.
Thanks for your help. |
|
|
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 03 Jun 09 2:24 PM
|
In addition to Raul's configuration changes, we supplied 2 Hot Fixes for 7.2.2 which resolved the issues with random Logouts.
We are reviewing the 7.5.1 code to ensure all the changes were ported properly.
Mimi
Sage SLX |
|
|
|
Re: 7.5.1 repeated logouts, signouts, timeouts, whatever...
Posted: 10 Sep 09 6:44 AM
|
This is a question for anyone.. I work the Web Side of the house at my company, and we are implementing said version in an Active /Active scenario for the web component. We are using an F5 for load balancing, and using IP for Session affinity.
What I am interested in is a few things:
Looking at the web.config, it looks like they (SAGE) has disabled the Machine Key need so that does not seem to be of an issue here any more.
Looking at some of the code, it seems that they support Session State for failover, but when I try to enable StateServer, it fails with objects not serialized.
How do we maintain client logon when we fail from Web1 to Web2 when there is no mechanism for state support?
I read the doc on how to install, and it lacks miserably on how to scale this product from 1 to 1+n servers for Web (Apps can not be scaled from what I can tell)
Any help on any examples of how you or anyone solved this would be nice. Like an example web.config or what the machine.config looks like when you added your info.
Are you using any Irules on the F5? Any logic on the F5? Does Cookie persisitence work better than IP?
Thanks in advance. |
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|