I submitted a post earlier today about upgrading to Gallery Beta and getting a timeout issue.

 

I tweaked the httpRuntime in the DNN web.config

basically - search the web.config for httpRuntime, then append executionTimeout="1200" just after httpRunTime

<httpRuntime executionTimeout="1200" maxRequestLength="

This seemed to fix the problem right up.

I was then able to remove this change and things worked after the first load of the Gallery.

Cheers,

Rich

Actually, it may very well be related to the Gallery if you were upgrading from a gallery instance which contained a large number of images. Upon hitting the gallery the first time after the upgrade, entries for each album (folder) and image/movie/flash file are added to the core DNN Folders and Files tables. As part of that process each image file has to be read into a bitmap to determine its width and height. That operation alone is an expensive one in terms of processing time.

I would be particularly interested to know approximately how many albums and images the existing gallery contained.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

In this case I would have to dis-agree. It is my understanding that unlike the ConnectionTimeout specified for a SQL connection object or the CommandTimeout specified for a SQL command object, the executionTimeout attribute of the httpRuntime section sets the maximum number of seconds that the request may execute before it is assumed to have failed. In otherwords, the total time permitted from first hitting the page through the unloading of the page upon completion of the request. No where do I see mention that executionTimeout only relates to SQL timeouts.

In fact, MSDN defines executionTimeout as follows:

"Specifies the maximum number of seconds that a request is allowed to execute before being automatically shut down by ASP.NET."

If I am correct then increasing the executionTimeout value would have been expected to have solved this upgrade issue.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner