Script Timed Out, Error ASP 0113

I sometimes get this error after about 60 seconds of "waiting for
mazes.com" (but when the page works, it usually loads in less than 12
seconds).

[color=blue]
> Active Server Pages error 'ASP 0113'
> Script timed out
> /asp-maze/amazingtest.asp
> The maximum amount of time for a script to execute was exceeded. You can
> change this limit by specifying a new value for the property Server.ScriptTimeout
> or by changing the value in the IIS administration tools.[/color]

but if I click refresh, I usually get the page.

There is a very remote chance that there might be a loop causing this
problem, but I don't think so. I've added timer-checks to the loops
that might cause a problem, and have added other escape methods to
other places that I think have caused the problem.

My questions:

1) Can the system be set to tell what line of the program was executing
when it timed out? (This would certainly help figure out if there's a
particular place that is causing an occasional problem). I'd have to
tell my hosting person how to do it, so be specific if you can.

2) Could this be caused by too many people accessing ASP pages at the
same time? How would he increase the number of users allowed to be
loading pages simultaneously?

3) What steps would he use to reduce the time for this parameter, or
should I reduce it. 60 seconds seems awfully long, but I do have
another page that I