| Author |
 Topic  |
|
|
Alkampfer
Starting Member
Italy
22 Posts |
 Posted - 11 June 2003 : 04:44:12
|
In this week I and my users receive this error many times in a day :
error 'ASP 0113'
Script timed out
/forum/post_info.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.
Could the archiving be a solution?
9911 posts, 1157 topics, 221 users (ACCESS DATABASE) |
Alkampfer |
|
|
joyce
Starting Member
United Kingdom
18 Posts |
Posted - 11 June 2003 : 05:21:06
|
I have the same problem (see 'my forum is on a go slow')
I have archived and it hasn't made any difference.
|
 |
|
|
Alkampfer
Starting Member
Italy
22 Posts |
Posted - 11 June 2003 : 06:22:45
|
I can suggest you to disable the access to the forum to the non-registered users...
There are many (smart!!!) bots out there that read the entire forum... |
Alkampfer |
|
|
|
anarres
Starting Member
25 Posts |
Posted - 11 June 2003 : 07:47:39
|
I was getting this message frequently, even though the rest of the site was quick.
I put in this code to config.asp:
'#################################
'## Added by anares, very angry with all the timeout messages!
'#################################
Server.ScriptTimeout = 1200
No problems anymore  |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
Alkampfer
Starting Member
Italy
22 Posts |
Posted - 11 June 2003 : 09:26:14
|
Yes. Answer? "Your site NOW is online and all is ok". Mmmm...
I don't think the answer is incrementing the script timeout... |
Alkampfer |
|
|
|
anarres
Starting Member
25 Posts |
Posted - 11 June 2003 : 10:16:47
|
quote:
Originally posted by Alkampfer
I don't think the answer is incrementing the script timeout...
Why not?
The default timeout is very low on default IIS installations, adding it in config.asp fixed the very same error for me... |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 11 June 2003 : 12:46:02
|
quote:
Originally posted by Alkampfer
Yes. Answer? "Your site NOW is online and all is ok". Mmmm...
I don't think the answer is incrementing the script timeout...
Me neither. It's obviously a server issue. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 11 June 2003 : 23:21:37
|
I agree it's a server problem in both cases. My best guess is it's related to the database connection. If you are using an ODBC driver try using OLEDB drivers. ODBC requires registry access to the ODBC hive and sometimes permission problems there cause real slow connections.
|
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
|
anarres
Starting Member
25 Posts |
Posted - 12 June 2003 : 09:24:04
|
I am using the jet OLEDB driver, not ODBC, can you come up with more possible solutions?
If the slow response is due to a problem on the server I can get the host to check, but at my site they always come back and say it's working fine... |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
BillPotts
Starting Member
USA
4 Posts |
Posted - 12 June 2003 : 23:28:58
|
quote:
Originally posted by anarres
I was getting this message frequently, even though the rest of the site was quick.
I put in this code to config.asp:
'#################################
'## Added by anares, very angry with all the timeout messages!
'#################################
Server.ScriptTimeout = 1200
No problems anymore
I just solved the same problem in the same way. The default.asp page now comes up in .05 s (typically).
Can anyone explain why setting the script timeout to 1200 makes any difference to something that's executing in .05 s anyway? Is that script timeout value in seconds or some other (possibly arbitrary) increment? 1200 ms would still be much more than enough time. 1200 microseconds would be too short, of course.
Update: 1 hour or so later.
The new timeout doesn't, in fact, solve the problem. I guess the improved performance was random and unrelated. It certainly didn't last.
I informed my web hosting company of the problem, then of the solution I used. I'm about to inform them of the recurrence of the problem.
If it's of any interest, I configured the forum to use MS Access. It won't be a high-volume forum, so I've assumed that MS Access will be adequate.
One last point: In attempting to inform the web hosting company of the latest development, I had huge delays, culminating in a Cannot find server message, when I tried to use the control panel associated with the site. I'm concluding, therefore, that they're having some problems with the server as a whole (which, of course, is shared among many sites).
Further update: Clicking on the forum name to reveal the message headers resulted in the following message:
Microsoft JET Database Engine error '80004005'
Not enough space on temporary disk.
/discussion/new/inc_header.asp, line 114
Obviously a server problem. Now to try to use the control panel associated with that server to report the problem. Sheesh!
|
Edited by - BillPotts on 13 June 2003 00:41:55 |
|
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 13 June 2003 : 02:33:57
|
These types of problems are influenced byt the horsepower of the server hardware, how much ram/disk/mhz the server has, what version of the OS and other software components (things like the version of MDAC, the scripting engine version, etc), as well as bandwidth & more. The performance that we see here at snitz is representative of what you should see with a well-configured server and database.
If you added mods, you might try putting up a basic forum on the same host. It is possible to introduce problems from bad code. The base Snitz code has been well tested but I don't know about all mods.
|
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
|
BillPotts
Starting Member
USA
4 Posts |
Posted - 13 June 2003 : 04:08:09
|
quote:
Originally posted by Doug G
These types of problems are influenced byt the horsepower of the server hardware, how much ram/disk/mhz the server has, what version of the OS and other software components (things like the version of MDAC, the scripting engine version, etc), as well as bandwidth & more. The performance that we see here at snitz is representative of what you should see with a well-configured server and database.
If you added mods, you might try putting up a basic forum on the same host. It is possible to introduce problems from bad code. The base Snitz code has been well tested but I don't know about all mods.
I've added no mods -- just configured the standard options. What I'm suspecting, now, is that the server hosting my site is undergoing a denial of service (DoS) attack. The only forum I've defined took over 900 seconds to come up (i.e., for default.asp to load). After I clicked on the name of the forum to see the message headers, it took about 280 seconds for them to appear. (Those figures are from the standard load time message.) That, along with the fact that the control panel for the site won't load (long wait, then "Cannot find server") reinforces the DoS theory. The web hosting company, by the way, is Infinology.
By the way, message volume isn't a problem. The forum is fairly new and there have been five posts and one reply.
Until a few hours ago, the forum was faster than this one.
Update: 13:15 PST. This morning, I had a message from Infinology, acknowledging that they had, indeed, had an attack on their network, lasting about four hours.
It occurs to me that others posting to this thread may have been victims of the same phenomenon (but did not recognize it). If so, the Snitz software is obviously blameless. That's very reassuring.  |
Edited by - BillPotts on 13 June 2003 16:29:43 |
|
|
|
Image
Average Member
Canada
574 Posts |
Posted - 27 July 2003 : 20:41:12
|
SYMPTOMS
When you attempt to run an Active Server Pages (ASP) page, you may receive the following error message:
Error Type:
Active Server Pages, ASP 0113 (0x80004005) 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.
CAUSE
The ScriptTimeout property specifies the maximum amount of time that a script can run before it is terminated. The error is generated when the processing time of the script exceeds the maximum value that has been designated for the ScriptTimeout property.
RESOLUTION
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):
1. Open Internet Services Manager.
2. Expand the tree and right-click Default Web Site (or the site that has the problem).
3. Click Properties.
4. Click the Home Directory tab.
5. Under Application Settings, click Configuration.
6. Click the App Options tab.
7. 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:
1. Open Internet Services Manager.
2. Right-click the name of your computer.
3. Click Properties.
4. In Master Properties, select WWW Service, and then click Edit.
5. Click the Home Directory tab.
6. Under Application Settings, click Configuration.
7. Click the App Options tab.
8. 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.
Steps to Reproduce Behavior
1. Open Internet Services Manager.
2. Expand the tree and right-click Default Web Site (or the site on which you want to reproduce this problem).
3. Click Properties.
4. Click the Home Directory tab.
5. Under Application Settings, click Configuration.
6. Click the App Options tab.
7. Set the ASP Script Timeout to 5.
8. Create a new ASP page with the following code in the Head section:
<%
EndTime = Now() + (10 / (24 * 60* 60)) '10 seconds
Do While Now() < EndTime
Response.Write ". "
Loop
%>
9. View the ASP page in the browser.
NOTE: An increase in timeout value can have a negative effect on server performance. You should design scripts that run within the default timeout settings. For example, an increase in script timeout value can keep IIS threads occupied and reduce the number of users that the server can serve.
For additional information: http://search.microsoft.com/search/results.aspx?st=b&qu=Server.ScriptTimeout&view=en-us
|
Edited by - Image on 27 July 2003 20:46:01 |
|
|
| |
Topic |
|
Topic Locked
