Active Server Pages error ASP 0113 error? Has it been resolved?

IIS defaults to a page script running timeout of 90 seconds, more than 90 seconds before the program finishes running, this error pops up. When the upload file is relatively large, and the network speed is relatively slow, it will time out, which is your current situation.

You can write the program "= time" inside the asp page to facility the script timeout period.

You can also set the script timeout for the site in the Home Directory Configuration option ASP Script Timeout: on the IIS.

I'm having this issue too, which I copied.

sub topiclist

on error resume next

set rs="")

sql,conn

do while not

topic=replacetext(rs("topic"),".*>","$1")

if rs("isrenwu")=1 then""&leftstr(""&topic,13)&"

end if

set rs=nothing

end sub

The landlord runs this and tries it.

First of all, check if the program has an endless loop.

This problem is usually caused by a large number of visits to a single-page database. This problem occurs when there are too many read records in the database table, SQL statements are not optimized, and the machine access speed is too slow.

In addition, the upper limit of the system can be expanded by the following methods:

Method one can increase the time allowed for ASP scripting to a specific **.

1.Open Internet Service Manager.

2.tree and right-click on the default web site (or site with issues).

3.Click Properties .

4.Click the Home Directory tab.

5.In Application Settings, click Configure.

7.The asp script overage is increased to a number to prevent the script timeout from being high enough.

The second option is to increase the amount of time allowed to asp scripting for all Web sites.

1.Open Internet Service Manager.

2.Right-click the name of the computer.

3.Click Properties .

4.Main Properties, select www Services, and then click .

5.Click the Home Directory tab.

6.In Application Settings, click Configure.

8.The asp script overage is increased to a number to prevent the script timeout from being high enough.

Method three: The property can be used programmatically to increase the value of the scriptTimeout property at the page level in ASP.

For example, if it takes 3 minutes to process the supers before the pass, add the script to the asp page with the following line: = 180

asp** appears at the time of generation.

Active Server Pages Error "ASP 0113" script timed out, as shown in the following figure.

Solution: Extend the script time.

As shown in the image below, set the time to be as large as possible to reduce the limit.

The execution time of the IIS default file seems to be 30 seconds, and your file execution time is more than 30 seconds!

So this error occurs!

But a problem arises:

If it is not necessary for the program to run, a page is executed for more than 30 seconds, then, the program is meaningless!

Think about it, how many people will wait for you to open a web page for 30 seconds?

The web pages that can't be opened within 10 seconds are basically not left behind!

You should check the logic of the program to see if there is an endless loop waiting!

There was an error while executing the ASP program.

Error: Active Server Pages error'asp 0113'

Script timeout. The maximum time for the script to run has been exceeded. You can specify a new value for the property or change the corresponding in the IIS management tool.

value to change this limit.

The reason for the error:

When querying data in a database, the amount of data is too large, causing the script to time out.

Solution: 1 Write in the ASP start area of the error page. Or it can be set to a slightly smaller parameter.

2 You can increase the time that is allowed to process ASP scripts for specific Web sites. To do so, add Internet Information

server (iis) metadatabase value:

Open the properties of the IIS right-click on the site in question.

Click Home.

Click the Application Options tab.

ASP script overvalue increased to a number to prevent script timeouts from being high enough3 The system does not have the FSO component turned on: the opening and closing methods of the FSO component, the registration and unregistration of the DLL file:

Run the cmd command.

Note cancel FSO component: regsvr32 U %windir% system32

Enable fso command: regsvr32 %windir% system32 4 The error still appears after multiple injections and startups, the reason is that there is no permission, I don't know how to cause it, and the solution is provided below.

There is a problem with permissions, open the registry to join permissions!

Type regedit in Start-Run and find the hkey classes root

Right-click on the permission to join the Everyone, Internet guest account (IUSR....)The user is OK, and then restart the IIS and you're done!

If you are like us, you can find the corresponding field to modify.

There is also a situation where mistakes in ** cause an endless loop.

Typing is not easy, such as satisfaction, hope.