|
| | | Forum Newbie
Group: Forum Members
Last Login: 11/19/2008 9:15:42 AM
Posts: 4, Visits: 13 |
| So, 10.02 installed and the problem remains. I just logged in, clicked on some folders. And 10 seconds later I was logged off.
At the same time, one colleague next to me was also thrown out of the web ui.
|
| |
| | | Forum Member
Group: Forum Members
Last Login: 2 days ago @ 3:46:00 PM
Posts: 49, Visits: 80 |
| | What did the event log say? |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 12/22/2008 10:42:34 AM
Posts: 9, Visits: 84 |
| | Phew! I nearly applied the update when it was first offered but our users had been through so much with the logouts that at least I had them being able to use their e-mail with version 10.0. Thanks for sharing this information as I was still comtemplating doing it. Mike |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 11/26/2008 9:37:24 AM
Posts: 4, Visits: 4 |
| | We had this problem a while back. Ipswitch was unable to help us. I wound up solving the problem myself and notifying them of the fix. Don't know if this will apply to anyone here. With the last upgrade Ipswitch removed an iframe that contained a page that refreshed every so often so that the session would not timeout. For some reason it was happening very quickly for us. I simply added the line back in to any page that I wanted the problem to not occur on. Here is the code: < iframe src="ping.aspx" frameborder="0" width="0" height="0"></iframe>I also adjusted the refresh line in there to 180 instead of using their timeout. This is what the line looks like now: < meta http-equiv="refresh" content="180" /> |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 11/24/2008 3:30:53 AM
Posts: 2, Visits: 1 |
| clord (11/21/2008)
We had this problem a while back. Ipswitch was unable to help us. I wound up solving the problem myself and notifying them of the fix. Don't know if this will apply to anyone here. With the last upgrade Ipswitch removed an iframe that contained a page that refreshed every so often so that the session would not timeout. For some reason it was happening very quickly for us. I simply added the line back in to any page that I wanted the problem to not occur on. Here is the code: < iframe src="ping.aspx" frameborder="0" width="0" height="0"></iframe>I also adjusted the refresh line in there to 180 instead of using their timeout. This is what the line looks like now: < meta http-equiv="refresh" content="180" /> Where would we enter that code to test? I am having the same issues, even with 10.02 Mike |
| |
| | | Forum Member
Group: Forum Members
Last Login: 2 days ago @ 3:46:00 PM
Posts: 49, Visits: 80 |
| clord (11/21/2008)
We had this problem a while back. Ipswitch was unable to help us. I wound up solving the problem myself and notifying them of the fix. Don't know if this will apply to anyone here. We've seen this problem when people are idle too long (20 minutes by default) but I am not sure if this would fix the problem where the Application Pool crashes and knocks everyone off. The ping code was supposed to prevent idle timeouts, which is not what is causing the problem in this thread, unless the timed out user is the cause of the app pool crash when they click on something...which I guess is a possibility. Were you getting ASP.NET 1305 errors for "Reason: Unknown" before the fix? |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 11/26/2008 9:37:24 AM
Posts: 4, Visits: 4 |
| | I don't remember if we were getting the errors. Our clients were getting knocked out in a matter of a minute or two instead of the 20 minute timeout period. If the worker process is crashing then it would kick out all users. My company has many ASP.NET apps that will keep a login despite crashes and reboots. In order to accomplish this we changed the Forms Authentication options in the web.config to allow for cookieless authentication for machines not using cookies as well as a sliding expiration on the cookie. The way the web.config in the web client currently works, unless Ipswitch is renewing the cookie somewhere in code, is that it will kick the user out 60 min after login regardless of activity. This is because by default the line looks like this: < forms name="authCookie" path="/" loginUrl="Login.aspx" protection="All" timeout="60"></forms>You can change this by adding a few options but I stress to use this at your own risk. It should not cause any problems unless Ipswitch is doing something wierd with the URLs since the cookieless option will append authentication info to the URL: < forms name="authCookie" path="/" loginUrl="Login.aspx" protection="All" timeout="60" cookieless="UseDeviceProfile" slidingExpiration="true"> |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 11/26/2008 9:37:24 AM
Posts: 4, Visits: 4 |
| | Also, someone had asked to what files I added the iframe. For our case it was just the ComposeMessage.aspx file. We had initially added it to the Folder list control (Folderlist.ascx I think) as well, but decided for security reasons to only stop the timeout while composing a message since that can take some time. Again I stress that this will not solve crashes, but will fix issues for people be kicked out very quickly. |
| |
| | |
|