I have seen this issue in a few threads out here.
On XP;
the default is 90. To set this to a higher limit...
check this KB :
There are three ways to resolve this problem:
You can increase the time that is allowed to process ASP scripts for a
particular Web site. To do this, change the metabase value in Internet
Information Server (IIS):
Open Internet Services Manager.
Expand the tree and right-click Default Web Site (or the site that has the
problem).
Click Properties.
Click the Home Directory tab.
Under Application Settings, click Configuration.
Click the App Options tab.
Increase the ASP Script Timeout value to a number high enough to prevent
script timeouts.
-or-
You can increase the time allowed to process ASP scripts for all Web
sites. To do this, change the metabase value in IIS:
Open Internet Services Manager.
Right-click the name of your computer.
Click Properties.
In Master Properties, select and then click Edit.
Click the Home Directory tab.
Under Application Settings, click Configuration.
Click the App Options tab.
Increase the ASP Script Timeout value to a number high enough to prevent
script timeouts.
-or-
You can use the Server.ScriptTimeOut property to programmatically increase
the ScriptTimeOut property value at the page level in ASP. For example, if
you want 3 minutes to pass before script processing times out, add the
following line to the ASP page: Server.ScriptTimeout = 180
NOTE: When you set the script timeout at the page level, you cannot set it
to less than the metabase value in IIS (90 seconds by default). However,
you can set the script timeout value higher than the metabase value. For
example, if you don't change the metabase default, and you code the
following: Server.ScriptTimeout = 20
the ScriptTimeOut value is 90. If you code the following:
Server.ScriptTimeout = 120
the ScriptTimeOut value is 120.
On XP;
the default is 90. To set this to a higher limit...
check this KB :
There are three ways to resolve this problem:
You can increase the time that is allowed to process ASP scripts for a
particular Web site. To do this, change the metabase value in Internet
Information Server (IIS):
Open Internet Services Manager.
Expand the tree and right-click Default Web Site (or the site that has the
problem).
Click Properties.
Click the Home Directory tab.
Under Application Settings, click Configuration.
Click the App Options tab.
Increase the ASP Script Timeout value to a number high enough to prevent
script timeouts.
-or-
You can increase the time allowed to process ASP scripts for all Web
sites. To do this, change the metabase value in IIS:
Open Internet Services Manager.
Right-click the name of your computer.
Click Properties.
In Master Properties, select and then click Edit.
Click the Home Directory tab.
Under Application Settings, click Configuration.
Click the App Options tab.
Increase the ASP Script Timeout value to a number high enough to prevent
script timeouts.
-or-
You can use the Server.ScriptTimeOut property to programmatically increase
the ScriptTimeOut property value at the page level in ASP. For example, if
you want 3 minutes to pass before script processing times out, add the
following line to the ASP page: Server.ScriptTimeout = 180
NOTE: When you set the script timeout at the page level, you cannot set it
to less than the metabase value in IIS (90 seconds by default). However,
you can set the script timeout value higher than the metabase value. For
example, if you don't change the metabase default, and you code the
following: Server.ScriptTimeout = 20
the ScriptTimeOut value is 90. If you code the following:
Server.ScriptTimeout = 120
the ScriptTimeOut value is 120.