Hi,
My classic asp code is throwing the following error when i run a large query on a sql server 2005 db.
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
However, this is fine. I'm running a ridiculously large query (purely for testing purposes) and after 30 secs it throws this error. I do not want to increase command or scrip timeouts within the pages as i do not want anything to run longer than this as it would use up unnecessary resources etc.
But what i DO want to do is to TRAP this error. I have implemented a custom error 500 page which works fine at displaying a friendly message and allows me to properly trap other errors. However, the page does not show when the timeout occurs, i'm just left with this ugly error message which a)looks horrible and b) doesn't allow me to trap the error.
Any ideas would be much appreciated. Thanks.
This is a hosted db and webserver so i have limited control over parameters such as query timeouts etc.
My classic asp code is throwing the following error when i run a large query on a sql server 2005 db.
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
However, this is fine. I'm running a ridiculously large query (purely for testing purposes) and after 30 secs it throws this error. I do not want to increase command or scrip timeouts within the pages as i do not want anything to run longer than this as it would use up unnecessary resources etc.
But what i DO want to do is to TRAP this error. I have implemented a custom error 500 page which works fine at displaying a friendly message and allows me to properly trap other errors. However, the page does not show when the timeout occurs, i'm just left with this ugly error message which a)looks horrible and b) doesn't allow me to trap the error.
Any ideas would be much appreciated. Thanks.
This is a hosted db and webserver so i have limited control over parameters such as query timeouts etc.
Comment