ASP Web Application Timeout

[MrLr]

Greetings,

I have an ASP web application that is written in VBScript, uses MS Access
2000 for record storage, and is running on a Windows 2000 Professional SP4
computer with IIS 5. The application can be started, have a record updated
and stored, and then terminate successfully on demand. I would like to have
the application remain active on the IIS Server without timing out, but when
I attempt to run it in that way, I receive a message (usually first thing in
the morning) of "An Eror Occurred - Your Session Timed Out". I have set the
Session Timeout feature in IIS to 1440 minutes, and the Server Script Timeout
feature in IIS to 1000000 seconds, but the application still times out each
morning.

Can anyone tell me what else I need to do to keep this application available
all day and all night?

Thanks!

MrLr

[Ray at]

> would like to have

the application remain active on the IIS Server without timing out,
WHY?

Ray at work
"MrLr" <Mr**@discussions.microsoft.com> wrote in message
news:05**********************************@microsof t.com... Greetings,

I have an ASP web application that is written in VBScript, uses MS Access
2000 for record storage, and is running on a Windows 2000 Professional SP4
computer with IIS 5. The application can be started, have a record updated
and stored, and then terminate successfully on demand. I would like to
have
the application remain active on the IIS Server without timing out, but
when
I attempt to run it in that way, I receive a message (usually first thing
in
the morning) of "An Eror Occurred - Your Session Timed Out". I have set
the
Session Timeout feature in IIS to 1440 minutes, and the Server Script
Timeout
feature in IIS to 1000000 seconds, but the application still times out
each
morning.

Can anyone tell me what else I need to do to keep this application
available
all day and all night?

Thanks!

MrLr

[Evertjan.]

=?Utf-8?B?TXJMcg==?= wrote on 10 aug 2004 in
microsoft.public.inetserver.asp.general:

I have an ASP web application that is written in VBScript, uses MS
Access 2000 for record storage, and is running on a Windows 2000
Professional SP4 computer with IIS 5. The application can be started,
have a record updated and stored, and then terminate successfully on
demand. I would like to have the application remain active on the IIS
Server without timing out, but when I attempt to run it in that way, I
receive a message (usually first thing in the morning) of "An Eror
Occurred - Your Session Timed Out". I have set the Session Timeout
feature in IIS to 1440 minutes, and the Server Script Timeout feature
in IIS to 1000000 seconds, but the application still times out each
morning.

Can anyone tell me what else I need to do to keep this application
available all day and all night?

Session timeout and application timeout are not the same things.
Script timout is something else again.

It seems to me it is not the timeout but the approach to a solution of your
programming whishes that is the problem.

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[MrLr]

Ray,

That is what management has requested.

Thanks

"Ray at <%=sLocation%> [MVP]" wrote:

would like to have
the application remain active on the IIS Server without timing out,

WHY?

Ray at work
"MrLr" <Mr**@discussions.microsoft.com> wrote in message
news:05**********************************@microsof t.com...

Greetings,

I have an ASP web application that is written in VBScript, uses MS Access
2000 for record storage, and is running on a Windows 2000 Professional SP4
computer with IIS 5. The application can be started, have a record updated
and stored, and then terminate successfully on demand. I would like to
have
the application remain active on the IIS Server without timing out, but
when
I attempt to run it in that way, I receive a message (usually first thing
in
the morning) of "An Eror Occurred - Your Session Timed Out". I have set
the
Session Timeout feature in IIS to 1440 minutes, and the Server Script
Timeout
feature in IIS to 1000000 seconds, but the application still times out
each
morning.

Can anyone tell me what else I need to do to keep this application
available
all day and all night?

Thanks!

MrLr

[Ray at]

I suggest you explain to them how web-based applications work... Is the use
of cookies an option? What is the reason that you need your sessions to
never time out? Is it for login purposes or something?

Ray at work
"MrLr" <Mr**@discussions.microsoft.com> wrote in message
news:2F**********************************@microsof t.com...

Ray,

That is what management has requested.

Thanks

"Ray at <%=sLocation%> [MVP]" wrote:

> would like to have
> the application remain active on the IIS Server without timing out,

WHY?

Ray at work
"MrLr" <Mr**@discussions.microsoft.com> wrote in message
news:05**********************************@microsof t.com...

> Greetings,
>
> I have an ASP web application that is written in VBScript, uses MS
> Access
> 2000 for record storage, and is running on a Windows 2000 Professional
> SP4
> computer with IIS 5. The application can be started, have a record
> updated
> and stored, and then terminate successfully on demand. I would like to
> have
> the application remain active on the IIS Server without timing out, but
> when
> I attempt to run it in that way, I receive a message (usually first
> thing
> in
> the morning) of "An Eror Occurred - Your Session Timed Out". I have set
> the
> Session Timeout feature in IIS to 1440 minutes, and the Server Script
> Timeout
> feature in IIS to 1000000 seconds, but the application still times out
> each
> morning.
>
> Can anyone tell me what else I need to do to keep this application
> available
> all day and all night?
>
> Thanks!
>
> MrLr