Anatoliy,

There is a default timeout parameter for web pages (I think it is 20 seconds and if you haven't changed it yourself) that will show this message if your SQL query (or stored procedure) that you are running in your request exceeds this time. Now this could be caused by a number of reasons, e.g. performance issue, database locks, etc.

This is a SQL issue however, as you would normally not have web page requests take so long to return data. If you are using stored procedures for your requests and your data has changed significantly in a short period of time, your stored procedure plans may be outdated and require re-compilation.

How long does it take for this error to happen after a request is submitted? Does it take about 20 seconds between your requests and the error displaying? If not, perhaps the timeout parameter (web.config) was set to a low number which does not allow the request enough time to run.

Bob

>Disclaimer: I have no reasons to link this error message to MM Framework.
>
>For several days for not yet identified reason MM ASP.NET (VB, SQL Server 2005) application keeps slowing down during a day until complete halt.
>
>Eventually users start to receive this message (the application halts):
>
>Timeout expired. The timeout parameter elapsed prior to completion of the operation or the server is not responding.
>The statement has been terminated.
>
>The application is used daily by 30 to 40 concurrent users, and is kept in present configuration for more than 12 months. The last time the application got a minor update was about a month ago, several weeks prior to this issue first got noticed.
>
>Again, I have no reasons to link this error message to MM Framework. But does this message ring any bell? Whoever experienced something similar recently or some time ago, your help and advice is greatly appreciated.
>
>Thank you!