M
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
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