• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 241
  • Last Modified:

Clientside software killing session?

Ive been getting a really weird timeout issue lately.  Its only happening to some users where others seem to be fine.
A user logs in, then forms auth is set and some session objects are as well.  However, in 1-2 mins the session objects have been lost and they need to login again.
My guess is some client side software that is killing cookies (or something like that).

I know i cant get a direct answer to this question, but what Im after is ideas on places to start looking.  
Thanks for any help
0
UnexplainedWays
Asked:
UnexplainedWays
  • 3
  • 2
  • 2
2 Solutions
 
LeeKowalkowskiCommented:
Are those users using IE7?  Since I upgraded to IE7 I get timed out of GoogleMail whenever I open a new window from it, or an attachment.  Never found the problem, I just use Firefox instead now.

--
Lee
0
 
DropZoneCommented:
First of all, check the timeout set for the Session Object in the Web.Config file.  Then, like LeeKowalkowski mentioned, see if there's a common browser that these users are using.  If it is indeed IE7, try it yourself and see if there's some sort of special setting for expiring session cookies, etc.

If you can reproduce it with Firefox, then I suggest you install the HttpHeaders extension and inspect the transmission between server and browser to see at which point the cookie is being reset -- if indeed it is being reset.

Another thing that could be causing this issue is a load-balancer or proxy.  We've had problems with load-balancing our systems where subsequent requests are sent to a different server and a new session established.  This is usually solved by configuring the load-balancer for "session persistence" or something like that.

      -dZ.
0
 
UnexplainedWaysAuthor Commented:
Well we finally replicated it on one of our machines.  However, still no clue how we did it and can't do it again lol.

The brower's I'm guessing are mainly IE, it's allot of buisnesses and that seems to be the usual.  The only way i could consistantly replicate it was in FF and killing cookies.  However if that was the case then they wouldn't get past the first screen if cookies were disabled.  Unless something is killing cookies early.  The cook is set to expire @ "end of session".

I'm thinking it must be something funky happening on the server.  We do have third part controls on the page.  "Telerik rad controls", the editor and tab strips.  I've googled and haven't found anything with those controls.

So thats one black box we can't open to see if it's causing it.  We thought about taking them out, but they are needed for the users since allot of them are halfway though the process.  We can't test it on dev because we never once got this error duing all of the development.

Thanks for the help,
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LeeKowalkowskiCommented:
Got it!

http://support.microsoft.com/kb/935778

Are your users using IE7 & opening/closing windows?  - That's the issue I have with GoogleMail anyway, especially because I have my home page set to about:blank.  Seems there are a few workarounds, but essentially there's little you can do, it's an IE7 issue.

Also: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1214771&SiteID=1

--
Lee

0
 
DropZoneCommented:
Can you verify that you are not using a Load-Balancing or proxy firewall on your server?   This is a problem that I have encountered.

Also, check the properties of the ApplicationPool for your web application, in particular the part about thread termination after X seconds.  If the thread is terminated and you are using In-Proc Session State, the session will be lost.  Although I'll admit that it would be weird that the thread is set to terminate after a few minutes.

     -dZ.
0
 
UnexplainedWaysAuthor Commented:
DropZone, I dont have full access to the server cause i'm "down the chain of command" but i did show my boss your exact post in an email and he said it wouldn't be one of those 2 things.
I'll have a look into the ApplicationPool idea now.


LeeKowalkowski, Thanks heaps for finding that link.  You should of seen the reaction when i told them it's a IE7 thing and not just us.  Oh it was priceless.  So many hours trawling the web, playing with settings here and there and turned out to be the browser lol.  

People should just use FF, would make the world allot easier.  So do we tell people to install firefox or a hotfix........

0
 
LeeKowalkowskiCommented:
I'm sure MS will release a patch soon, most people on IE7 would have automatic updates switched on.  Which is the only reason some people have IE7 anyway.  Mind you, a lot of IE7 users would also not have a non-local home page.

I also think it as triggered by save as... dialog too.  If the design of your site encourages new windows or saving files, you're more likely to be affected than others.  

I think the non-local home page suggestion is the most convenient for your users (if it really does fix it!).  Feel free to recommend another browser, but that could be too nerve-wrecking for some users.

--
Lee
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now