I occasionally am getting a script timeout while using an ASP database
connection. Everything I read suggests that I can change the
Server.ScriptTimeout to address this, but I was unable to find out
what the limit is for this setting.

I asked my ISP who is hosting my web site if they have know the limit
and if they have a limit of their own. They replied that the limit is
90 seconds and that it cannot be overridden.

Is my ISP's support team mistaken here?

Thanks in advance.

Randy

> connection. Everything I read suggests that I can change the[color=blue]
> Server.ScriptTimeout to address this, but I was unable to find out
> what the limit is for this setting.[/color]

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

However, increasing a timeout value is like bandaging a broken bone.

See http://www.aspfaq.com/2424 for some better ideas.
[color=blue]
> They replied that the limit is
> 90 seconds and that it cannot be overridden.
>
> Is my ISP's support team mistaken here?[/color]

Yes. However, as I stated above, if your ASP page takes longer than 90
seconds to return a result, your problem is much deeper than a simple
timeout setting.

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

I'm not aware of any setting for this that cannot be overridden.

Someone can correct me if I am wrong on this.

Have you tried adding
Server.ScriptTimeout = xxx
to your page?

Cheers!

Anthony Sullivan

"Randy Weber" <randyweb@yahoo.com> wrote in message
news:8d410073.0312020653.667a07a2@posting.google.c om...[color=blue]
> I occasionally am getting a script timeout while using an ASP database
> connection. Everything I read suggests that I can change the
> Server.ScriptTimeout to address this, but I was unable to find out
> what the limit is for this setting.
>
> I asked my ISP who is hosting my web site if they have know the limit
> and if they have a limit of their own. They replied that the limit is
> 90 seconds and that it cannot be overridden.
>
> Is my ISP's support team mistaken here?
>
> Thanks in advance.
>
> Randy[/color]

"Aaron Bertrand - MVP" wrote:[color=blue]
>
> However, increasing a timeout value is like bandaging a broken
> bone...
>
> ...as I stated above, if your ASP page takes longer than 90
> seconds to return a result, your problem is much deeper than
> a simple timeout setting.[/color]

This is either arrogant or ignorant, Aaron. Even your own article
acknowledges that some script runtimes are beyond the developer's control.

I have a script that uploads (into SQL Server) the contents of a vendor's
proprietary database, the completion of which requires a vendor-supplied
interface. My script takes 15-20 minutes to run (for a mere 15,000 records),
so I crank up the ScriptTimeout.

My script has been functioning flawlessly for two years, and the vendor
finally offered a tool to extract their DB into Access (but no other DB).
Turns out my script is just as fast as the vendor's own tool, so we left it
alone.

Some may question the use of a web script for this, but I find that it
offers many benefits, especially security and the ability to run the job on
demand from anywhere on the network.

On the down side, we had to install the vendor's API on one of our web
servers.


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

> This is either arrogant or ignorant, Aaron.

That's a pretty rude way to tell me I forgot to include the word "probably"
in my statement.

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

"Aaron Bertrand - MVP" wrote:[color=blue]
>[color=green]
>> This is either arrogant or ignorant, Aaron.[/color]
>
> That's a pretty rude way to tell me I forgot to include
> the word "probably" in my statement.[/color]

In that case, it was *probably* arrogant or ignorant. :-P



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

> In that case, it was *probably* arrogant or ignorant. :-P

That's much better.