|
 |
asp_databases thread: asp page expires
Message #1 by "andy" <aj_smith@b...> on Tue, 16 May 2000 15:21:17
|
|
Hello
I have an asp page which calls a vb dll to run a
process in sqlserver which will take aprox 4-5 mins to run.
The vb process runs ok but the asp page expires about 1 min
into the process. Why would this happen?
Secondly is there a way to report progress on the job back to the
asp page ?
Any help would be appreciated.
Andy
Message #2 by "Muratbek Mamytov" <muratbek@h...> on Tue, 16 May 2000 21:28:16 +0500
|
|
Did You check IIS on your computer?
----- Original Message -----
From: andy
To: ASP Databases <asp_databases@p...>
Sent: Tuesday, May 16, 2000 3:21 PM
Subject: [asp_databases] asp page expires
> Hello
>
> I have an asp page which calls a vb dll to run a
> process in sqlserver which will take aprox 4-5 mins to run.
>
> The vb process runs ok but the asp page expires about 1 min
> into the process. Why would this happen?
>
> Secondly is there a way to report progress on the job back to the
> asp page ?
>
> Any help would be appreciated.
>
> Andy
Message #3 by "Shawn Steward" <ssteward@a...> on Tue, 16 May 2000 17:49:8
|
|
The asp page is timing out because your script timeout is set to about 1
minute. The default is usually 90 seconds. You can change this in IIS for
that web. You need to go into the Application configuration settings, on
the App Options tab you can set the ASP Script timeout to 360 seconds or
something like that...
As for the progress report, you can turn buffering on at the top of your
page, like this:<% Response.Buffer = True %>.
Then throughout your page, when you want to display what's been processed,
you can use <% Response.Flush %>. You'll probably want to use a
Response.Write with some information about your procedure right before the
Response.Flush so you can see something on the screen to let you know where
it's at.
hope this helps!
shawn
On 05/16/00, ""andy" wrote:
> Hello
I have an asp page which calls a vb dll to run a
process in sqlserver which will take aprox 4-5 mins to run.
The vb process runs ok but the asp page expires about 1 min
into the process. Why would this happen?
Secondly is there a way to report progress on the job back to the
asp page ?
Any help would be appreciated.
Andy
Message #4 by "Andrew Smith" <aj_smith@b...> on Tue, 16 May 2000 18:33:08 +0100
|
|
This is exactly the problem thanks for help.
I am currently developing this web on win95 with pws (not thru choice) - is
there anyway to set script timeout in pws settings?
regards
Andy
----- Original Message -----
From: Shawn Steward
To: ASP Databases <asp_databases@p...>
Sent: Tuesday, May 16, 2000 5:00 PM
Subject: [asp_databases] Re: asp page expires
> The asp page is timing out because your script timeout is set to about 1
> minute. The default is usually 90 seconds. You can change this in IIS
for
> that web. You need to go into the Application configuration settings, on
> the App Options tab you can set the ASP Script timeout to 360 seconds or
> something like that...
>
> As for the progress report, you can turn buffering on at the top of your
> page, like this:<% Response.Buffer = True %>.
>
> Then throughout your page, when you want to display what's been processed,
> you can use <% Response.Flush %>. You'll probably want to use a
> Response.Write with some information about your procedure right before the
> Response.Flush so you can see something on the screen to let you know
where
> it's at.
>
> hope this helps!
>
> shawn
>
> On 05/16/00, ""andy" wrote:
> > Hello
>
> I have an asp page which calls a vb dll to run a
> process in sqlserver which will take aprox 4-5 mins to run.
>
> The vb process runs ok but the asp page expires about 1 min
> into the process. Why would this happen?
>
> Secondly is there a way to report progress on the job back to the
> asp page ?
>
> Any help would be appreciated.
>
> Andy
Message #5 by mkrishna - Internet Mail <mkrishna@c...> on Wed, 17 May 2000 12:10:16 -0400
|
|
As regards the setting in PWS... I have no idea
hey! U can set the timout period of every page by this line on top of every
page
<%response.expires (number) %>
this number could be any integer value. If its 0 then the page timesout
immediately... if its 5 it times out after 5 seconds.
I hope this helps....
good luck!!!
> -----Original Message-----
> From: Andrew Smith
> Sent: Tuesday, May 16, 2000 1:33 PM
> To: ASP Databases
> Subject: [asp_databases] Re: asp page expires
>
> This is exactly the problem thanks for help.
>
> I am currently developing this web on win95 with pws (not thru choice) -
> is
> there anyway to set script timeout in pws settings?
>
> regards
>
> Andy
>
>
>
>
> ----- Original Message -----
> From: Shawn Steward
> To: ASP Databases <asp_databases@p...>
> Sent: Tuesday, May 16, 2000 5:00 PM
> Subject: [asp_databases] Re: asp page expires
>
>
> > The asp page is timing out because your script timeout is set to about 1
> > minute. The default is usually 90 seconds. You can change this in IIS
> for
> > that web. You need to go into the Application configuration settings,
> on
> > the App Options tab you can set the ASP Script timeout to 360 seconds or
> > something like that...
> >
> > As for the progress report, you can turn buffering on at the top of your
> > page, like this:<% Response.Buffer = True %>.
> >
> > Then throughout your page, when you want to display what's been
> processed,
> > you can use <% Response.Flush %>. You'll probably want to use a
> > Response.Write with some information about your procedure right before
> the
> > Response.Flush so you can see something on the screen to let you know
> where
> > it's at.
> >
> > hope this helps!
> >
> > shawn
> >
> > On 05/16/00, ""andy" wrote:
> > > Hello
> >
> > I have an asp page which calls a vb dll to run a
> > process in sqlserver which will take aprox 4-5 mins to run.
> >
> > The vb process runs ok but the asp page expires about 1 min
> > into the process. Why would this happen?
> >
> > Secondly is there a way to report progress on the job back to the
> > asp page ?
> >
> > Any help would be appreciated.
> >
> > Andy
Message #6 by "richard guthrie" <richardgu@s...> on Thu, 18 May 2000 4:54:47
|
|
just wanted to clarify this is straight out of the msdn in the index goto
response object sub heading properties
When your .asp file calls Response.Expires, IIS creates an HTTP header
indicating the time on the server. If the system time on the client is
earlier than the system time on the server (due to either the client or
server having an inaccurate time setting, or time-zone differences) setting
the parameter to 0 will not have the effect of expiring the page
immediately. You can use the Response.ExpiresAbsolute property to achieve
immediate expiration of a page. In addition, you can use a negative number
for the Expires property. For example
<%Response.Expires = -1 %>
will expire the response immediately.
If there are multiple calls to Response.Expires on a single page, the
server will use the shortest time period.
Message #7 by "Ken Schaefer" <ken.s@a...> on Thu, 18 May 2000 11:18:54 +1000
|
|
> hey! U can set the timout period of every page by this line on top of
every
> page
>
> <%response.expires (number) %>
>
> this number could be any integer value. If its 0 then the page timesout
> immediately... if its 5 it times out after 5 seconds.
This is crap.
response.expires helps set the time at which the page is be expired from
proxy and user caches - it does not determine when a page times out.
Not only that, but the syntax is incorrect.
Cheers
Ken
PS Quote from MS ASP documentation:
<quote>
Expires
The Expires property specifies the length of time before a page cached on a
browser expires. If the user returns to the same page before it expires, the
cached version is displayed.
Syntax
Response.Expires [= number]
Parameters
number
The time in minutes before the page expires. Set this parameter to 0 to have
the cached page expire immediately.
Remarks
If this property is set more than once on a page, the shortest time is used.
</quote>
Message #8 by Richard Guthrie <richardgu@s...> on Wed, 17 May 2000 20:39:25 -0700
|
|
the msdn list -1 as the immediate timeout value for response.expires
1. Re: asp page expires
----------------------------------------------------------------------
Subject: Re: asp page expires
From: mkrishna - Internet Mail <mkrishna@c...>
Date: Wed, 17 May 2000 12:10:16 -0400
X-Message-Number: 1
As regards the setting in PWS... I have no idea
hey! U can set the timout period of every page by this line on top of every
page
<%response.expires (number) %>
this number could be any integer value. If its 0 then the page timesout
immediately... if its 5 it times out after 5 seconds.
I hope this helps....
good luck!!!
> -----Original Message-----
> From: Andrew Smith
> Sent: Tuesday, May 16, 2000 1:33 PM
> To: ASP Databases
> Subject: [asp_databases] Re: asp page expires
>
> This is exactly the problem thanks for help.
>
> I am currently developing this web on win95 with pws (not thru choice) -
> is
> there anyway to set script timeout in pws settings?
>
> regards
>
> Andy
>
>
>
>
> ----- Original Message -----
> From: Shawn Steward
> To: ASP Databases <asp_databases@p...>
> Sent: Tuesday, May 16, 2000 5:00 PM
> Subject: [asp_databases] Re: asp page expires
>
>
> > The asp page is timing out because your script timeout is set to about 1
> > minute. The default is usually 90 seconds. You can change this in IIS
> for
> > that web. You need to go into the Application configuration settings,
> on
> > the App Options tab you can set the ASP Script timeout to 360 seconds or
> > something like that...
> >
> > As for the progress report, you can turn buffering on at the top of your
> > page, like this:<% Response.Buffer = True %>.
> >
> > Then throughout your page, when you want to display what's been
> processed,
> > you can use <% Response.Flush %>. You'll probably want to use a
> > Response.Write with some information about your procedure right before
> the
> > Response.Flush so you can see something on the screen to let you know
> where
> > it's at.
> >
> > hope this helps!
> >
> > shawn
> >
> > On 05/16/00, ""andy" wrote:
> > > Hello
> >
> > I have an asp page which calls a vb dll to run a
> > process in sqlserver which will take aprox 4-5 mins to run.
> >
> > The vb process runs ok but the asp page expires about 1 min
> > into the process. Why would this happen?
> >
> > Secondly is there a way to report progress on the job back to the
> > asp page ?
> >
> > Any help would be appreciated.
> >
> > Andy
---
END OF DIGEST
---
You are currently subscribed to asp_databases
Message #9 by "Shawn Steward" <ssteward@a...> on Thu, 18 May 2000 19:52:42
|
|
That will just basically stop the browser from putting the page into the
cache, but it doesn't have anything to do with the script timeout
settings...
shawn
On 05/18/00, "Richard Guthrie " wrote:
> the msdn list -1 as the immediate timeout value for response.expires
1. Re: asp page expires
----------------------------------------------------------------------
Subject: Re: asp page expires
From: mkrishna - Internet Mail <mkrishna@c...>
Date: Wed, 17 May 2000 12:10:16 -0400
X-Message-Number: 1
As regards the setting in PWS... I have no idea
hey! U can set the timout period of every page by this line on top of
every
page
<%response.expires (number) %>
this number could be any integer value. If its 0 then the page timesout
immediately... if its 5 it times out after 5 seconds.
I hope this helps....
good luck!!!
> -----Original Message-----
> From: Andrew Smith
> Sent: Tuesday, May 16, 2000 1:33 PM
> To: ASP Databases
> Subject: [asp_databases] Re: asp page expires
>
> This is exactly the problem thanks for help.
>
> I am currently developing this web on win95 with pws (not thru choice) -
> is
> there anyway to set script timeout in pws settings?
>
> regards
>
> Andy
>
>
>
>
> ----- Original Message -----
> From: Shawn Steward
> To: ASP Databases <asp_databases@p...>
> Sent: Tuesday, May 16, 2000 5:00 PM
> Subject: [asp_databases] Re: asp page expires
>
>
> > The asp page is timing out because your script timeout is set to about 1
> > minute. The default is usually 90 seconds. You can change this in IIS
> for
> > that web. You need to go into the Application configuration settings,
> on
> > the App Options tab you can set the ASP Script timeout to 360 seconds or
> > something like that...
> >
> > As for the progress report, you can turn buffering on at the top of your
> > page, like this:<% Response.Buffer = True %>.
> >
> > Then throughout your page, when you want to display what's been
> processed,
> > you can use <% Response.Flush %>. You'll probably want to use a
> > Response.Write with some information about your procedure right before
> the
> > Response.Flush so you can see something on the screen to let you know
> where
> > it's at.
> >
> > hope this helps!
> >
> > shawn
> >
> > On 05/16/00, ""andy" wrote:
> > > Hello
> >
> > I have an asp page which calls a vb dll to run a
> > process in sqlserver which will take aprox 4-5 mins to run.
> >
> > The vb process runs ok but the asp page expires about 1 min
> > into the process. Why would this happen?
> >
> > Secondly is there a way to report progress on the job back to the
> > asp page ?
> >
> > Any help would be appreciated.
> >
> > Andy
|
|
|
View Cart
