Active Server Pages error 'asp 0113 'script timeout

Today, when a local machine tests an ASP code segment, the "Active Server Pages error 'asp 0113 'script timed out" occurs. You can only access the HTML page. The solution found on the internet is:

An error occurred while executing ASP program

Error:
Active Server Pages error 'asp 0113'
Script timeout
/Index. asp
Exceeds the maximum running time of the script. You can specify a new value for the server. scripttimeout attribute or change the corresponding value in the IIS management tool.
Value.

Cause of error:

When querying data in the database, the script times out because the data volume is too large.

Solution:

1. Enter server. scripttimeout = 9999 in the ASP start area of the error page. Or you can set it to a slightly smaller parameter.

2. You can add time to allow ASP scripts to be processed for specific web sites. To do this, set Internet Information
Server (IIS) metabase value:
. Open IIS
. Right-click the properties of the problematic site
. Click main directory
. In applicationsettings @, click Configure.
. Click the application options tab.
. ASP script supervalue is increased to a number to prevent script timeout from being high enough

3. The FSO component is not enabled in the system. The methods for enabling and disabling the FSO component are as follows:
Run the CMD command
Describe the FSO component: regsvr32/U % WINDIR %/system32/scrrun. dll
Run the FSO command: regsvr32 % WINDIR %/system32/scrrun. dll

4. Check whether the message is cleared multiple times or the error still occurs after startup because you do not have the permission and you do not know how to cause it. The solution is provided below.
Permission error. open registry and add permission!
In start-run, enter regedit and find hkey_classes_root/scripting. FileSystemObject.
Right-click the permission and join everyone. The Internet Guest Account (IUSR...) user is OK. Then restart IIS!
If you encounter something like ours, you can find the corresponding field to modify

This error may occur in another case.
The server. Createobject ("ADODB. recordset") is entered incorrectly.
I converted ADODB into Adobe :)

However, these methods have no effect on my situation ......

When I need to share a folder, I am prompted that I have not enabled the server service ...... I think it would be a problem if I ended a process in the morning ......

"Control Panel" -- "Administrative Tools" -- "services" find the server service and start ...... The problem is solved!

Later, I thought about this error. My first reaction was the IIS configuration problem, but this problem was not found at ordinary times. Later I thought it was a code problem, however, the same error still occurs when the previous modification is overwritten. If you are not creating shared folders, you may still be looking for a solution without any clue ...... Alas, it's really ......