Hello,

I'm hoping someone's seen this because I'm at wits end. I am running DNN 4.8.2 with SQL Server 2005. Whenever I try to install a module, I get the following server error:

Request timed out. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Request timed out. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Request timed out.]

 Normally when if I saw this error, I would go looking at the executionTimeout attribute of the httpRuntime element in my web.config file. The problem is, it's already set to a longer time than it takes for the page to time out. I've created a test ASPX page that outputs Server.ScriptTimeout and even outputted it to the module definitions list page, just to make sure it was being set properly. It was. There is no reason I can see why this would happen. But no matter what, if I try to install a module, this is what I get.

It happens whether I install the module from the list of available modules (on the Module Definitions screen) or if I upload a PA file.

Does anyone have any ideas?

The attribute I needed...

is the shutdownTimeout attribute of the httpRuntime element. It controls how long a thread can run when an application shutdown has been triggered. This is exactly what I want, as it gives the install thread the extra time it needs to complete its intsall. Here is my new httpRuntime element:

  <httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="8192" requestLengthDiskThreshold="8192" shutdownTimeout="300" />

I finally wrote a standalone ASP.NET page would simulate the types of updates so I could get a handle on the timing and effects of configuration changes.

A couple tidbits:

• For the benefit of searches, let me note that the exception I saw in the logs was not what was on the error page. It was:
  ThreadAbortException: Thread was being aborted While upgrading
  There are a lot of forum posts about this exception, and I think it all comes back to the shutdownTimeout needing to be increased.
• I fruitlessly spent a lot of time messing with the waitChangeNotification and maxWaitChangeNotification attributes. As far as I can tell, these do not apply to assembly updates - only to file updates.
• As noted in my previous reply, updates to the application pool shutdown timeout didn't do it. Ditto the shutdownTimeout attribute of processModel (in machine.config). Neither of these work. It had to be the one in httpRuntime

I am a little surprised I didn't find this fix elsewhere in the forums or blogs. I am still a little nervous that this isn't it, but it really seems to be working. We shall see.