The SQL timeout solution is sometimes not a setup problem. For details, refer.
The SQL timeout solution is sometimes not a setup problem. For details, refer.
Server. scr extends ptTimeout. The default value is 90 seconds.
To increase it, add the following sentence to your asp file:
Server. scr restart ptTimeout = 999,
Set the page timeout to 999 seconds.
Initially, I only set Server. scr restart ptTimeout,
However, there will still be a timeout error, no matter how big the value is.
Later, I saw a post in the community and mentioned the commandTimeout attribute,
So check the Option Pack document, and there is still timeout.
Both the Connection object and Command object have the CommandTimeOut attribute,
The default value is 30 seconds. If you have a time-consuming query or data processing,
It is easy to time out. To increase it, it is also easy. After creating an object,
Set its attributes as follows:
Con. CommandTimeOut = 999,
Set to 999 seconds, where con is a Connection object.
If it is set to zero, there will be infinite waiting without this timeout limit.
The Command object does not inherit this attribute of Connection,
Therefore, you must separately set the CommandTimeout attribute for commands that may time out.
In the end, IE also has a timeout setting. If data is not obtained from the server within five minutes, it also times out.
This situation may be rare,
However, when I save the result of a more than 0.1 million query as an mdb file,
I encountered it. (For the method of saving, please refer to a post in the essence area .)
Solution: (for the original article, refer to Q181050 in Microsoft KB)
Previously, during the IC trading network, the data volume was too large to exceed 10 million, and the memory was added to solve the problem.
1. IE requires version 4.01 sp1 or later.
2. In HKEY_CURRENT_USERSoftwareMicrosoft
WindowsCurrentVersionInternet Settings
Add a DWORD type ReceiveTimeout, and set the value to 8 9.
3. restart computer.
