- Web Console timing out, not connecting, or being very slow
- An error of HttpException (0x80004005): Request timed out - (ignores executionTimeout)
This kind of issue is typically occurs when a server-side code function or macro executes for a period of time longer than the maximum timeout period allowed for server-side code execution.
This can be caused by multiple things :
-Too many users logging into the web console and overloading the worker processes, causing timeouts and big slowdowns on the web console and in extreme cases unusable
-A windows update slightly changing the .net framework in a unknown way , requiring the.net to be re-registered
-A slow network connection to the core server from the administrators computer
- To Re-register .net
- To increase the query time out for the console and web console
- And Decreasing/Managing load on worker processes associated with the web console
How to Re-register .net
To Re-register the ASP.NET 4.0 components. Please reference Microsoft KB 2015129 for details, or a brief summary follows:
- Open a command prompt with administrative privileges on the core server
- Change directory to
- 32-bit Windows:
- 64-bit Windows:
- 32-bit Windows:
- Re-register the components:
- Reset the IIS services:
How to increase the query time out for the console and web console
You can increase the query time out in the console and web console using this article :
Decreasing/Managing load on worker processes associated with the web console
Finally to decrease the load on the worker processes which for the remote console, you can set them to automatically 'recycle' so that the memory , cache etc. associated with these processes will automatically be cleared and new process be created in their place.
Here are some article on the process of recycling associated with the IIS application web pools
In this example I am going to use the elapsed time option, this way you will know exactly when the application pool gets reset as opposed to every time a certain memory level is reached which can be very sporadic.
Under IIS manager , navigate to the application pools window pane, via the left column.
Right click the LDAppWeb, where the remote console application resides, and click on recycling…
Notice the default time interval for this application is 1740 minutes, change this to 120 minutes and the worker processes associated with this application pool will refresh ' recycle' every 120 minutes. This should relive pressure on the main web console.
This method can also be manually used instead of performing an iisreset cmd, as this will reset only the applications associated with the web console as opposed to the entire IIS infrastructure.
To do this , right click the LDAppWeb, located in the application pools window in the IIS and click recycle. This force the application pool to 'restart' at that moment in time. This can be used in times of urgency to relieve the load on the worker process immediately