Session Timeout ASP

[Guest]

Hi,

I have built a custom application using ASP (called BETA) using FrontPage
2000. The website is hosted at an ISP running Windows2003 Server with
FrontPage extensions etc...

The website has a login screen, called index.asp, which basically takes the
login of a user. Once the user fills in his/her username and password, the
form is sent to a page called validate.asp, which looks up the user's account
from an Access table called [Users] using a DRW. If the user exists, then
the website is redirected and the user is given a session=True to
authenticate him throughout the site. Each page is then looking for the
session=True. If the user's details are not in the Access table, then the
login is rejected and a page appears informing the user that their login is
incorrect.

The application has a series of hyperlinks to external websites that open in
a new window. If a user spends more than 5 minutes on the external site,
BETA is open in one Internet Explorer window and an external site in another
window, then user's are complaining of timeouts. User's say that this
happens when they are on an external website for around 5 minutes.

How do I increase this timeout slot?

Please help.

Thanks in advance.

 

[Thomas A. Rowe]

First check with your host, as the default session timeout value is 20 minutes. It is never a good
idea to direct the user away from the site when using sessions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Guest]

Thomas,

I have emailed the host for the value of the timeout in IIS.

THe user's are not directed away to another site altogether - they are
simply clicking links within the site that fire off new pages to other
website. Is this a problem?

SKC

First check with your host, as the default session timeout value is 20 minutes. It is never a good
idea to direct the user away from the site when using sessions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

Hi,

I have built a custom application using ASP (called BETA) using FrontPage
2000. The website is hosted at an ISP running Windows2003 Server with
FrontPage extensions etc...

The website has a login screen, called index.asp, which basically takes the
login of a user. Once the user fills in his/her username and password, the
form is sent to a page called validate.asp, which looks up the user's account
from an Access table called [Users] using a DRW. If the user exists, then
the website is redirected and the user is given a session=True to
authenticate him throughout the site. Each page is then looking for the
session=True. If the user's details are not in the Access table, then the
login is rejected and a page appears informing the user that their login is
incorrect.

The application has a series of hyperlinks to external websites that open in
a new window. If a user spends more than 5 minutes on the external site,
BETA is open in one Internet Explorer window and an external site in another
window, then user's are complaining of timeouts. User's say that this
happens when they are on an external website for around 5 minutes.

How do I increase this timeout slot?

Please help.

Thanks in advance.

 

[Stefan B Rusynko]

It is not the external links triggering the session timeout, but their lack of activity on the main site w/ a session running

--




| Thomas,
|
| I have emailed the host for the value of the timeout in IIS.
|
| THe user's are not directed away to another site altogether - they are
| simply clicking links within the site that fire off new pages to other
| website. Is this a problem?
|
| SKC
|
| "Thomas A. Rowe" wrote:
|
| > First check with your host, as the default session timeout value is 20 minutes. It is never a good
| > idea to direct the user away from the site when using sessions.
| >
| > --
| > ==============================================
| > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > WEBMASTER Resources(tm)
| >
| > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > ==============================================
| > To assist you in getting the best answers for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| >
| > | > > Hi,
| > >
| > > I have built a custom application using ASP (called BETA) using FrontPage
| > > 2000. The website is hosted at an ISP running Windows2003 Server with
| > > FrontPage extensions etc...
| > >
| > > The website has a login screen, called index.asp, which basically takes the
| > > login of a user. Once the user fills in his/her username and password, the
| > > form is sent to a page called validate.asp, which looks up the user's account
| > > from an Access table called [Users] using a DRW. If the user exists, then
| > > the website is redirected and the user is given a session=True to
| > > authenticate him throughout the site. Each page is then looking for the
| > > session=True. If the user's details are not in the Access table, then the
| > > login is rejected and a page appears informing the user that their login is
| > > incorrect.
| > >
| > > The application has a series of hyperlinks to external websites that open in
| > > a new window. If a user spends more than 5 minutes on the external site,
| > > BETA is open in one Internet Explorer window and an external site in another
| > > window, then user's are complaining of timeouts. User's say that this
| > > happens when they are on an external website for around 5 minutes.
| > >
| > > How do I increase this timeout slot?
| > >
| > > Please help.
| > >
| > > Thanks in advance.
| >
| >
| >

 

[Guest]

Stefan,

You have hit the nail on the head! What can I do then to sort this problem
out?

skc

It is not the external links triggering the session timeout, but their lack of activity on the main site w/ a session running

--




| Thomas,
|
| I have emailed the host for the value of the timeout in IIS.
|
| THe user's are not directed away to another site altogether - they are
| simply clicking links within the site that fire off new pages to other
| website. Is this a problem?
|
| SKC
|
| "Thomas A. Rowe" wrote:
|
| > First check with your host, as the default session timeout value is 20 minutes. It is never a good
| > idea to direct the user away from the site when using sessions.
| >
| > --
| > ==============================================
| > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > WEBMASTER Resources(tm)
| >
| > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > ==============================================
| > To assist you in getting the best answers for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| >
| > | > > Hi,
| > >
| > > I have built a custom application using ASP (called BETA) using FrontPage
| > > 2000. The website is hosted at an ISP running Windows2003 Server with
| > > FrontPage extensions etc...
| > >
| > > The website has a login screen, called index.asp, which basically takes the
| > > login of a user. Once the user fills in his/her username and password, the
| > > form is sent to a page called validate.asp, which looks up the user's account
| > > from an Access table called [Users] using a DRW. If the user exists, then
| > > the website is redirected and the user is given a session=True to
| > > authenticate him throughout the site. Each page is then looking for the
| > > session=True. If the user's details are not in the Access table, then the
| > > login is rejected and a page appears informing the user that their login is
| > > incorrect.
| > >
| > > The application has a series of hyperlinks to external websites that open in
| > > a new window. If a user spends more than 5 minutes on the external site,
| > > BETA is open in one Internet Explorer window and an external site in another
| > > window, then user's are complaining of timeouts. User's say that this
| > > happens when they are on an external website for around 5 minutes.
| > >
| > > How do I increase this timeout slot?
| > >
| > > Please help.
| > >
| > > Thanks in advance.
| >
| >
| >

 

[Guest]

Thomas,

My host just emailed me back to say that it is set to 90 seconds !!!

Can you tell me where abouts the timeout is located on a Windows 2003 Server
in IIS - so I can double check with him.

Furthermore, it is a shared server - so do you think they will be happy to
increase the timeout to 900 seconds? What is a good timeout?

SKC

First check with your host, as the default session timeout value is 20 minutes. It is never a good
idea to direct the user away from the site when using sessions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

Hi,

I have built a custom application using ASP (called BETA) using FrontPage
2000. The website is hosted at an ISP running Windows2003 Server with
FrontPage extensions etc...

The website has a login screen, called index.asp, which basically takes the
login of a user. Once the user fills in his/her username and password, the
form is sent to a page called validate.asp, which looks up the user's account
from an Access table called [Users] using a DRW. If the user exists, then
the website is redirected and the user is given a session=True to
authenticate him throughout the site. Each page is then looking for the
session=True. If the user's details are not in the Access table, then the
login is rejected and a page appears informing the user that their login is
incorrect.

The application has a series of hyperlinks to external websites that open in
a new window. If a user spends more than 5 minutes on the external site,
BETA is open in one Internet Explorer window and an external site in another
window, then user's are complaining of timeouts. User's say that this
happens when they are on an external website for around 5 minutes.

How do I increase this timeout slot?

Please help.

Thanks in advance.

 

[Ronx]

In IIS MMC the properties for my web site show:
Web Site tab:
Connection Timeout = 600 seconds

Home Directory Tab->Application Configuration button->Options Tab:
Session Timeout = 20 minutes
ASP Timeout = 90 seconds

These are the default values for a website in IIS6.

--
Ron Symonds (Microsoft MVP - FrontPage)
Reply only to group - emails will be deleted unread.

Thomas,

My host just emailed me back to say that it is set to 90 seconds !!!

Can you tell me where abouts the timeout is located on a Windows 2003
Server
in IIS - so I can double check with him.

Furthermore, it is a shared server - so do you think they will be happy to
increase the timeout to 900 seconds? What is a good timeout?

SKC

First check with your host, as the default session timeout value is 20
minutes. It is never a good
idea to direct the user away from the site when using sessions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

Hi,

I have built a custom application using ASP (called BETA) using
FrontPage
2000. The website is hosted at an ISP running Windows2003 Server with
FrontPage extensions etc...

The website has a login screen, called index.asp, which basically takes
the
login of a user. Once the user fills in his/her username and password,
the
form is sent to a page called validate.asp, which looks up the user's
account
from an Access table called [Users] using a DRW. If the user exists,
then
the website is redirected and the user is given a session=True to
authenticate him throughout the site. Each page is then looking for
the
session=True. If the user's details are not in the Access table, then
the
login is rejected and a page appears informing the user that their
login is
incorrect.

The application has a series of hyperlinks to external websites that
open in
a new window. If a user spends more than 5 minutes on the external
site,
BETA is open in one Internet Explorer window and an external site in
another
window, then user's are complaining of timeouts. User's say that this
happens when they are on an external website for around 5 minutes.

How do I increase this timeout slot?

Please help.

Thanks in advance.

 

[Stefan B Rusynko]

IMHO 90 seconds for server session timeout is absurd
(I think they were reporting Script timeout)
To retrieve that use
<% strScriptTimeout = Server.ScriptTimeout %>

If you have IIS on any server it is in the root web Properties (Web Site tab - connection timeout)
(open the IIS MMC)
Unless they are blocking it at the server level you should be able to change it in your session start using
<% Session.Timeout = 20 %>
(20 minutes)
- use caution in setting it higher
To retrieve that use
<% strSessionTimeout = Session.Timeout %>

You could also warn users their session is about to timeout
See http://www.aspfaq.com/show.asp?id=2265

Also check your DB connection in the global.asa or
Tools Site Settings Database (select your DB & Modify - Advanced)
- that would control the session timeout from the time a DB is opened
--




| Thomas,
|
| My host just emailed me back to say that it is set to 90 seconds !!!
|
| Can you tell me where abouts the timeout is located on a Windows 2003 Server
| in IIS - so I can double check with him.
|
| Furthermore, it is a shared server - so do you think they will be happy to
| increase the timeout to 900 seconds? What is a good timeout?
|
| SKC
|
| "Thomas A. Rowe" wrote:
|
| > First check with your host, as the default session timeout value is 20 minutes. It is never a good
| > idea to direct the user away from the site when using sessions.
| >
| > --
| > ==============================================
| > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > WEBMASTER Resources(tm)
| >
| > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > ==============================================
| > To assist you in getting the best answers for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| >
| > | > > Hi,
| > >
| > > I have built a custom application using ASP (called BETA) using FrontPage
| > > 2000. The website is hosted at an ISP running Windows2003 Server with
| > > FrontPage extensions etc...
| > >
| > > The website has a login screen, called index.asp, which basically takes the
| > > login of a user. Once the user fills in his/her username and password, the
| > > form is sent to a page called validate.asp, which looks up the user's account
| > > from an Access table called [Users] using a DRW. If the user exists, then
| > > the website is redirected and the user is given a session=True to
| > > authenticate him throughout the site. Each page is then looking for the
| > > session=True. If the user's details are not in the Access table, then the
| > > login is rejected and a page appears informing the user that their login is
| > > incorrect.
| > >
| > > The application has a series of hyperlinks to external websites that open in
| > > a new window. If a user spends more than 5 minutes on the external site,
| > > BETA is open in one Internet Explorer window and an external site in another
| > > window, then user's are complaining of timeouts. User's say that this
| > > happens when they are on an external website for around 5 minutes.
| > >
| > > How do I increase this timeout slot?
| > >
| > > Please help.
| > >
| > > Thanks in advance.
| >
| >
| >

 

[Kevin Spencer]

Session times out after 20 minutes. You have to ask the right question.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

Thomas,

My host just emailed me back to say that it is set to 90 seconds !!!

Can you tell me where abouts the timeout is located on a Windows 2003
Server
in IIS - so I can double check with him.

Furthermore, it is a shared server - so do you think they will be happy to
increase the timeout to 900 seconds? What is a good timeout?

SKC

First check with your host, as the default session timeout value is 20
minutes. It is never a good
idea to direct the user away from the site when using sessions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

Hi,

I have built a custom application using ASP (called BETA) using
FrontPage
2000. The website is hosted at an ISP running Windows2003 Server with
FrontPage extensions etc...

The website has a login screen, called index.asp, which basically takes
the
login of a user. Once the user fills in his/her username and password,
the
form is sent to a page called validate.asp, which looks up the user's
account
from an Access table called [Users] using a DRW. If the user exists,
then
the website is redirected and the user is given a session=True to
authenticate him throughout the site. Each page is then looking for
the
session=True. If the user's details are not in the Access table, then
the
login is rejected and a page appears informing the user that their
login is
incorrect.

The application has a series of hyperlinks to external websites that
open in
a new window. If a user spends more than 5 minutes on the external
site,
BETA is open in one Internet Explorer window and an external site in
another
window, then user's are complaining of timeouts. User's say that this
happens when they are on an external website for around 5 minutes.

How do I increase this timeout slot?

Please help.

Thanks in advance.

 

[Guest]

Stefan,

See my answers below...

IMHO 90 seconds for server session timeout is absurd Why is it absurd?
(I think they were reporting Script timeout)
To retrieve that use
<% strScriptTimeout = Server.ScriptTimeout %> I have not tried this yet!

If you have IIS on any server it is in the root web Properties (Web Site tab - connection timeout)
(open the IIS MMC)
Unless they are blocking it at the server level you should be able to change it in your session start using
<% Session.Timeout = 20 %>

I add this into the header for each .asp page?

(20 minutes)
- use caution in setting it higher
To retrieve that use
<% strSessionTimeout = Session.Timeout %> I have not tried this yet.

You could also warn users their session is about to timeout
See http://www.aspfaq.com/show.asp?id=2265

I will try this and let you know.

Also check your DB connection in the global.asa or
Tools Site Settings Database (select your DB & Modify - Advanced)
- that would control the session timeout from the time a DB is opened
--




| Thomas,
|
| My host just emailed me back to say that it is set to 90 seconds !!!
|
| Can you tell me where abouts the timeout is located on a Windows 2003 Server
| in IIS - so I can double check with him.
|
| Furthermore, it is a shared server - so do you think they will be happy to
| increase the timeout to 900 seconds? What is a good timeout?
|
| SKC
|
| "Thomas A. Rowe" wrote:
|
| > First check with your host, as the default session timeout value is 20 minutes. It is never a good
| > idea to direct the user away from the site when using sessions.
| >
| > --
| > ==============================================
| > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > WEBMASTER Resources(tm)
| >
| > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > ==============================================
| > To assist you in getting the best answers for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| >
| > | > > Hi,
| > >
| > > I have built a custom application using ASP (called BETA) using FrontPage
| > > 2000. The website is hosted at an ISP running Windows2003 Server with
| > > FrontPage extensions etc...
| > >
| > > The website has a login screen, called index.asp, which basically takes the
| > > login of a user. Once the user fills in his/her username and password, the
| > > form is sent to a page called validate.asp, which looks up the user's account
| > > from an Access table called [Users] using a DRW. If the user exists, then
| > > the website is redirected and the user is given a session=True to
| > > authenticate him throughout the site. Each page is then looking for the
| > > session=True. If the user's details are not in the Access table, then the
| > > login is rejected and a page appears informing the user that their login is
| > > incorrect.
| > >
| > > The application has a series of hyperlinks to external websites that open in
| > > a new window. If a user spends more than 5 minutes on the external site,
| > > BETA is open in one Internet Explorer window and an external site in another
| > > window, then user's are complaining of timeouts. User's say that this
| > > happens when they are on an external website for around 5 minutes.
| > >
| > > How do I increase this timeout slot?
| > >
| > > Please help.
| > >
| > > Thanks in advance.
| >
| >
| >

 

[Guest]

Kevin,

What do you mean by this?

SKC

Session times out after 20 minutes. You have to ask the right question.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.

Thomas,

My host just emailed me back to say that it is set to 90 seconds !!!

Can you tell me where abouts the timeout is located on a Windows 2003
Server
in IIS - so I can double check with him.

Furthermore, it is a shared server - so do you think they will be happy to
increase the timeout to 900 seconds? What is a good timeout?

SKC

First check with your host, as the default session timeout value is 20
minutes. It is never a good
idea to direct the user away from the site when using sessions.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
To assist you in getting the best answers for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp

Hi,

I have built a custom application using ASP (called BETA) using
FrontPage
2000. The website is hosted at an ISP running Windows2003 Server with
FrontPage extensions etc...

The website has a login screen, called index.asp, which basically takes
the
login of a user. Once the user fills in his/her username and password,
the
form is sent to a page called validate.asp, which looks up the user's
account
from an Access table called [Users] using a DRW. If the user exists,
then
the website is redirected and the user is given a session=True to
authenticate him throughout the site. Each page is then looking for
the
session=True. If the user's details are not in the Access table, then
the
login is rejected and a page appears informing the user that their
login is
incorrect.

The application has a series of hyperlinks to external websites that
open in
a new window. If a user spends more than 5 minutes on the external
site,
BETA is open in one Internet Explorer window and an external site in
another
window, then user's are complaining of timeouts. User's say that this
happens when they are on an external website for around 5 minutes.

How do I increase this timeout slot?

Please help.

Thanks in advance.

 

[Stefan B Rusynko]

See inline below

--




| Stefan,
|
| See my answers below...
|
| "Stefan B Rusynko" wrote:
|
| > IMHO 90 seconds for server session timeout is absurd
| Why is it absurd?

Because server session timeout should never be that short
(unless you want users to be speed readers and continually timing out)
- as indicated that is probably Script timeout

| > (I think they were reporting Script timeout)
| > To retrieve that use
| > <% strScriptTimeout = Server.ScriptTimeout %>
| I have not tried this yet!

Try it

| >
| > If you have IIS on any server it is in the root web Properties (Web Site tab - connection timeout)
| > (open the IIS MMC)
| > Unless they are blocking it at the server level you should be able to change it in your session start using
| > <% Session.Timeout = 20 %>
| I add this into the header for each .asp page?

No you don't want it in very page as it will start a new session w/ each page
- set it in your global.asa or your login page to start a session

| > (20 minutes)
| > - use caution in setting it higher
| > To retrieve that use
| > <% strSessionTimeout = Session.Timeout %>
| I have not tried this yet.

Try it

| >
| > You could also warn users their session is about to timeout
| > See http://www.aspfaq.com/show.asp?id=2265
| I will try this and let you know.
| >
| > Also check your DB connection in the global.asa or
| > Tools Site Settings Database (select your DB & Modify - Advanced)
| > - that would control the session timeout from the time a DB is opened
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| > | Thomas,
| > |
| > | My host just emailed me back to say that it is set to 90 seconds !!!
| > |
| > | Can you tell me where abouts the timeout is located on a Windows 2003 Server
| > | in IIS - so I can double check with him.
| > |
| > | Furthermore, it is a shared server - so do you think they will be happy to
| > | increase the timeout to 900 seconds? What is a good timeout?
| > |
| > | SKC
| > |
| > | "Thomas A. Rowe" wrote:
| > |
| > | > First check with your host, as the default session timeout value is 20 minutes. It is never a good
| > | > idea to direct the user away from the site when using sessions.
| > | >
| > | > --
| > | > ==============================================
| > | > Thomas A. Rowe (Microsoft MVP - FrontPage)
| > | > WEBMASTER Resources(tm)
| > | >
| > | > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
| > | > ==============================================
| > | > To assist you in getting the best answers for FrontPage support see:
| > | > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > | >
| > | > | > | > > Hi,
| > | > >
| > | > > I have built a custom application using ASP (called BETA) using FrontPage
| > | > > 2000. The website is hosted at an ISP running Windows2003 Server with
| > | > > FrontPage extensions etc...
| > | > >
| > | > > The website has a login screen, called index.asp, which basically takes the
| > | > > login of a user. Once the user fills in his/her username and password, the
| > | > > form is sent to a page called validate.asp, which looks up the user's account
| > | > > from an Access table called [Users] using a DRW. If the user exists, then
| > | > > the website is redirected and the user is given a session=True to
| > | > > authenticate him throughout the site. Each page is then looking for the
| > | > > session=True. If the user's details are not in the Access table, then the
| > | > > login is rejected and a page appears informing the user that their login is
| > | > > incorrect.
| > | > >
| > | > > The application has a series of hyperlinks to external websites that open in
| > | > > a new window. If a user spends more than 5 minutes on the external site,
| > | > > BETA is open in one Internet Explorer window and an external site in another
| > | > > window, then user's are complaining of timeouts. User's say that this
| > | > > happens when they are on an external website for around 5 minutes.
| > | > >
| > | > > How do I increase this timeout slot?
| > | > >
| > | > > Please help.
| > | > >
| > | > > Thanks in advance.
| > | >
| > | >
| > | >
| >
| >
| >