By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,018 Members | 870 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,018 IT Pros & Developers. It's quick & easy.

Need to keep client from being logged out at timeout.

P: n/a
I've researched this question on internet, and I've tried a number of things
I found to no avail to solve this problem...

I work for a company using Visual Studio 2003 to maintain a website for
realtors.

This webside allows a realtor to fill out a series of forms to get market
analysis among other involved stuff.

There is a lot of data for the realtor to enter and typically they will
start to enter data into a large form, while they are doing so, they
typically need to contact others and play phone-tag with them to get the
data to be submitted.

Because of the default 20 minute timeout, the user ends up timing out before
they can submit the data because it is incomplete and so they try to enter
the next bit of data and rudely find themselves staring at a login screen -
all their data lost!

My boss sold them on an ISP on the strength of being able to setup the app
on their server and being able to solve this logout issue and your's truly
is now charged with solving this mess.

I've worked with the timeout values in IIS default web server and tried a
few other ways to try to prevent them from being rudely bounced, to no
avail.

Nothing seems to have any effect but to waste my time and raise my fear
factor.

Any hints as to some real solutions to this problem would be appreciated. It
appears that the source of the problem is the server logging out users.

Thanks.
Nov 21 '07 #1
Share this Question
Share on Google+
7 Replies


P: n/a
The keyword here is "Default". Both the Session Timeout and the Forms
Authentication cookie timeout both are easily configurable with settings in
the web.config file. RTFM!
---Peter
"Inside every large program, there is a small program trying to get out."
http://www.eggheadcafe.com
http://petesbloggerama.blogspot.com
http://www.blogmetafinder.com

"Garry Freemyer" wrote:
I've researched this question on internet, and I've tried a number of things
I found to no avail to solve this problem...

I work for a company using Visual Studio 2003 to maintain a website for
realtors.

This webside allows a realtor to fill out a series of forms to get market
analysis among other involved stuff.

There is a lot of data for the realtor to enter and typically they will
start to enter data into a large form, while they are doing so, they
typically need to contact others and play phone-tag with them to get the
data to be submitted.

Because of the default 20 minute timeout, the user ends up timing out before
they can submit the data because it is incomplete and so they try to enter
the next bit of data and rudely find themselves staring at a login screen -
all their data lost!

My boss sold them on an ISP on the strength of being able to setup the app
on their server and being able to solve this logout issue and your's truly
is now charged with solving this mess.

I've worked with the timeout values in IIS default web server and tried a
few other ways to try to prevent them from being rudely bounced, to no
avail.

Nothing seems to have any effect but to waste my time and raise my fear
factor.

Any hints as to some real solutions to this problem would be appreciated. It
appears that the source of the problem is the server logging out users.

Thanks.
Nov 21 '07 #2

P: n/a
"Garry Freemyer" <ga************@pacbell.netwrote in message
news:rK******************@newssvr14.news.prodigy.n et...
Because of the default 20 minute timeout
So increase it...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Nov 21 '07 #3

P: n/a

"Peter Bromberg [C# MVP]" <pb*******@yahoo.NoSpamMaam.comwrote in message
news:F2**********************************@microsof t.com...
The keyword here is "Default". Both the Session Timeout and the Forms
Authentication cookie timeout both are easily configurable with settings
in
the web.config file. RTFM!
"RTFM!"

Oh aren't you a piece of work? My boss tried those things already, they
didn't work. I've tried a bunch of things.
---Peter
"Inside every large program, there is a small program trying to get out."
http://www.eggheadcafe.com
http://petesbloggerama.blogspot.com
http://www.blogmetafinder.com

"Garry Freemyer" wrote:
>I've researched this question on internet, and I've tried a number of
things
I found to no avail to solve this problem...

I work for a company using Visual Studio 2003 to maintain a website for
realtors.

This webside allows a realtor to fill out a series of forms to get market
analysis among other involved stuff.

There is a lot of data for the realtor to enter and typically they will
start to enter data into a large form, while they are doing so, they
typically need to contact others and play phone-tag with them to get the
data to be submitted.

Because of the default 20 minute timeout, the user ends up timing out
before
they can submit the data because it is incomplete and so they try to
enter
the next bit of data and rudely find themselves staring at a login
screen -
all their data lost!

My boss sold them on an ISP on the strength of being able to setup the
app
on their server and being able to solve this logout issue and your's
truly
is now charged with solving this mess.

I've worked with the timeout values in IIS default web server and tried a
few other ways to try to prevent them from being rudely bounced, to no
avail.

Nothing seems to have any effect but to waste my time and raise my fear
factor.

Any hints as to some real solutions to this problem would be appreciated.
It
appears that the source of the problem is the server logging out users.

Thanks.

Nov 21 '07 #4

P: n/a

"Mark Rae [MVP]" <ma**@markNOSPAMrae.netwrote in message
news:ug**************@TK2MSFTNGP04.phx.gbl...
"Garry Freemyer" <ga************@pacbell.netwrote in message
news:rK******************@newssvr14.news.prodigy.n et...
>Because of the default 20 minute timeout

So increase it...
I don't come to forums but as a last resort after trying everything within
reason including what you said to do to no avail.

I guess thats what happens when some folks attend a forum to feed their ego
instead of helping as well as getting help.
>
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

Nov 21 '07 #5

P: n/a

"Garry Freemyer" <ga************@pacbell.netwrote in message
news:XU****************@newssvr22.news.prodigy.net ...
>>Because of the default 20 minute timeout

So increase it...

I don't come to forums but as a last resort after trying everything within
reason including what you said to do to no avail.
What do you mean by "no avail"? You are not able to change the default? Or
you are not able to set the timeout high enough?

Too much of this thread has been snipped for me to remember for sure, but I
think you are using ASP.NET membership, right? If so, there are methods of
making the authentication cookie permanent (no expiration), which would keep
users "logged in" indefinitely. In fact, there is "Remember Me"
functionality built in to the standard Login control that does just that.

Someone alluded to session timeouts, but considering your situation you
really shouldn't be using sessions at all. Sessions can be lost in a variety
of ways, not just as a result of a timeout.

Nov 21 '07 #6

P: n/a

"Scott Roberts" <sr******@no.spam.here-webworks-software.comwrote in
message news:OM**************@TK2MSFTNGP06.phx.gbl...
>
"Garry Freemyer" <ga************@pacbell.netwrote in message
news:XU****************@newssvr22.news.prodigy.net ...
>>>Because of the default 20 minute timeout

So increase it...

I don't come to forums but as a last resort after trying everything
within reason including what you said to do to no avail.

What do you mean by "no avail"? You are not able to change the default? Or
you are not able to set the timeout high enough?
Good question. I mean that what I have tried so far has not had any effect
on anything, as if my changes were completely ignored. I'll speak to my
boss - He's a programmer too, Im going to foreward your message to him.

Thanks kindly!
Too much of this thread has been snipped for me to remember for sure, but
I think you are using ASP.NET membership, right? If so, there are methods
of making the authentication cookie permanent (no expiration), which would
keep users "logged in" indefinitely. In fact, there is "Remember Me"
functionality built in to the standard Login control that does just that.

Someone alluded to session timeouts, but considering your situation you
really shouldn't be using sessions at all. Sessions can be lost in a
variety of ways, not just as a result of a timeout.

Nov 21 '07 #7

P: n/a
RMFQ!!

"Peter Bromberg [C# MVP]" <pb*******@yahoo.NoSpamMaam.comwrote in message
news:F2**********************************@microsof t.com...
The keyword here is "Default". Both the Session Timeout and the Forms
Authentication cookie timeout both are easily configurable with settings
in
the web.config file. RTFM!
---Peter
"Inside every large program, there is a small program trying to get out."
http://www.eggheadcafe.com
http://petesbloggerama.blogspot.com
http://www.blogmetafinder.com

"Garry Freemyer" wrote:
>I've researched this question on internet, and I've tried a number of
things
I found to no avail to solve this problem...

I work for a company using Visual Studio 2003 to maintain a website for
realtors.

This webside allows a realtor to fill out a series of forms to get market
analysis among other involved stuff.

There is a lot of data for the realtor to enter and typically they will
start to enter data into a large form, while they are doing so, they
typically need to contact others and play phone-tag with them to get the
data to be submitted.

Because of the default 20 minute timeout, the user ends up timing out
before
they can submit the data because it is incomplete and so they try to
enter
the next bit of data and rudely find themselves staring at a login
screen -
all their data lost!

My boss sold them on an ISP on the strength of being able to setup the
app
on their server and being able to solve this logout issue and your's
truly
is now charged with solving this mess.

I've worked with the timeout values in IIS default web server and tried a
few other ways to try to prevent them from being rudely bounced, to no
avail.

Nothing seems to have any effect but to waste my time and raise my fear
factor.

Any hints as to some real solutions to this problem would be appreciated.
It
appears that the source of the problem is the server logging out users.

Thanks.

Nov 29 '07 #8

This discussion thread is closed

Replies have been disabled for this discussion.