When 1 User Timesout other users cannot get it

Question

1.00/5 (1 vote)

See more:

I'm using VS 2010 (Code is VB) with SQLServer 2008 R2 on a cloud server with Windows Server 2008.

'**************************************************************************************************************************

In Web Config I set session state as

<sessionstate cookieless="AutoDetect" mode="InProc" timeout="1440">

Authenticatio is:

<authentication mode="Forms">

<forms loginUrl="~/Default.aspx" timeout"30" cookieless"AutoDetect" slidingExpiration"true"/>

'***********************************************************************************************************

Now if/when 1 of my users times out, other users are locked out. What am I doing wrong? Thank you for any advice you care to offer............ Phil Hoop

Posted 18-Mar-14 17:59pm

PhilHoop

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhinav S · Answer 1 · 2014-03-18T18:50:00

Solution 1

Once the application times out, take them to the login page.
Other users should then be able to generate their own authentication ticket and login.

Posted 18-Mar-14 18:50pm

Abhinav S

Comments

PhilHoop 19-Mar-14 1:06am

Thank you for your comment. That is what happens, both the Initial user and all subsequent users are bounced back to the Login Screen after logging in and attempting to navigate through the application's screens, subsequent login attempts continue this vicious circle until I reset the application Pool. The SessionState is: <sessionstate cookieless="AutoDetect" mode="InProc" timeout="1440">. I suspect some conflict between the SessionState and Authentication statements, but that is where I am stuck. ...........Phil Hoop