Server.ScriptTimeout

[Bryan]

I'm looking for a definitive answer to a Server.ScriptTimeout question.

if I add <% Server.ScriptTimeout = 300 %> to a page, does that then alter
the default 90 second script timeout for ALL pages (if so, is it for that
session or until??) or does it just alter the timeout for THAT individual
page?

I've been through the IIS docs and I haven't been able to find the
definitive answer.

Thanks!

[Aaron Bertrand [MVP]]

If you put it in that page, it applies to that page (not all pages, and not
session-wide either).

http://www.aspfaq.com/2066
http://www.aspfaq.com/2366



"Bryan" <ne**@psacake.com> wrote in message
news:eu**************@TK2MSFTNGP09.phx.gbl...

I'm looking for a definitive answer to a Server.ScriptTimeout question.

if I add <% Server.ScriptTimeout = 300 %> to a page, does that then alter
the default 90 second script timeout for ALL pages (if so, is it for that
session or until??) or does it just alter the timeout for THAT individual
page?

I've been through the IIS docs and I haven't been able to find the
definitive answer.

Thanks!

[Ray at]

Try it:

<%

Server.ScriptTimeout = 4
Do
Loop
%>

Then make a second page with:
<%
Do
Loop
%>

page1 shoud time out in 4 seconds. Then page2 should timeout in <server
setting> seconds.

Ray at work

"Bryan" <ne**@psacake.com> wrote in message
news:eu**************@TK2MSFTNGP09.phx.gbl...

I'm looking for a definitive answer to a Server.ScriptTimeout question.

if I add <% Server.ScriptTimeout = 300 %> to a page, does that then alter
the default 90 second script timeout for ALL pages (if so, is it for that
session or until??) or does it just alter the timeout for THAT individual
page?

I've been through the IIS docs and I haven't been able to find the
definitive answer.

Thanks!

[Dave Anderson]

"Bryan" wrote:

if I add <% Server.ScriptTimeout = 300 %> to a page,
does that then alter the default 90 second script timeout
for ALL pages (if so, is it for that session or until??)
or does it just alter the timeout for THAT individual
page?

In my experience, it only affects the current script. I have a script that
is set to 14400 because 7200 wasn't enough time -- at least it wasn't on our
old server. It affects no other scripts, though I can't speak for sessions.
In any case, you can try manually resetting the ScriptTimeout at the end of
your processing, if you are really worried about it.

Of course, Server.ScriptTimeout is a read/write property, so you could
simply set up a test involving two scripts if you want to see for
yourself...
--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

[Dave Anderson]

"Ray at <%=sLocation%>" wrote:

[p1] Server.ScriptTimeout = 4
Do
Loop
[p2] Do
Loop

How about this?

[p1] Server.ScriptTimeout = 10000
[p2] Response.Write(Server.ScriptTimeout)

--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.

[Payal]

Setting Server.ScriptTimeout = 0 does not work..
Also in IIS when we try to give 0 as the scripttimeout value, it will not accept it, since it demands a value from 1 to 2000000000

So its a wrong conception that setting Server.ScriptTimeout to 0 will set the script time to infinity...

Or may be i m wrong.. if i m missing anything please suggest.