Scott
New Member
Posts:6
 |
| 03/27/2008 4:05 AM |
|
When trying to unify permissions on children I receive the following error.
A critical error has occurred.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Does anyone have an idea how to fix this?
Thanks,
Scott |
|
|
|
|
Guido Kuehler
Basic Member
Posts:149
|
| 03/27/2008 7:45 AM |
|
I am not sure but i think that you you have here Problem with the maxRequestLength in the Web.config
Look for the Settting maxRequestLength in your web.config and user here a higher Value for a Test.
Please make a Backup from Portal,DB or Files before you make Changes!
Thank You
Guido |
|
|
|
|
Peter Donker
Veteran Member
Posts:4536
|
| 03/27/2008 1:27 PM |
|
Scott,
Yes, and check the executionTimeout. It has taken too long to process. We're looking at making this process less prone to timeouts.
Peter
|
|
|
|
|
Scott
New Member
Posts:6
|
| 03/27/2008 2:10 PM |
|
Thanks for the info.
Peter where do I check the execution time out?
Thanks,
Scott |
|
|
|
|
Guido Kuehler
Basic Member
Posts:149
|
| 03/27/2008 3:05 PM |
|
I think Peter mean the optional "executionTimeout" Setting in the "httpRuntime......" line in your web.config
Here a Description about this Setting executionTimeout:
The execution time-out refers to the number of seconds an ASP.NET page is given before the operation is assumed to have failed and the page terminated. If you are uploading a large file the code that is receiving the transfer may time out before the file has been completely uploaded.
A executionTimeout of 3600 is one hour.
Additional here below the Description about the Setting maxRequestLength:
This attribute is used to limit the size of uploads by rejecting any which exceed a certain limit.
The limit refers to the total size of the HTTP upload in KB (approximately equal to the sum of all the files being upload). You should set a sensible limit here to stop malicious visitors using up your bandwidth by uploading excessively large files. If the size of an upload is too great the server will refuse to accept it. Because the server is refusing the request the uploading browser will report that the submission page is not available.
This is a client side error message rather than a server side error message and it means that you cannot normally provide a sensible error message to users if they submit files which are too large.
Sample: (maxRequestLength of 1048576 is set this Value to 1 GB.)
|
|
|
|
|
Guido Kuehler
Basic Member
Posts:149
|
| 03/27/2008 3:07 PM |
|
Scott, please us not one hour for the Timeout or one Gig for the RequestLentgh that only Samples!!!
Thank You
Guido |
|
|
|
|
Peter Donker
Veteran Member
Posts:4536
|
| 04/01/2008 1:47 PM |
|
Thanks Guido,
Yes, that was the timeout. And set it to something like 480 (it's seconds). This will give you enough time normally (8 minutes) to upload the module (3 Mb).
Peter |
|
|
|
|
enno lueckel
New Member
Posts:7
|
| 05/07/2008 2:52 PM |
|
Hi,
I am getting the sanme error, while my web.config is customized:
Any further ideas?
Thanks
Enno |
|
|
|
|
Peter Donker
Veteran Member
Posts:4536
|
| 05/07/2008 8:36 PM |
|
Enno,
I'm not sure. What version IIS are you using. I've seen that in IIS 7 things are different again (sigh ...).
BTW: it's easy to see if the web.config changes work. If you set the executionTimeout to 240, it should last 4 minutes until you get the error.
Peter |
|
|
|
|
Keith Fisher
New Member
Posts:14
|
| 07/29/2008 10:28 PM |
|
Enno,
Do you receive the timeout error after a repeatable interval, like every 30 seconds?
In IIS6 I've seen the "Health Monitoring" settings play havoc with applications that require their processes to go on for any amount of time longer than the defaults.
One obvious place to check (for states being recycled / shutdown /
lost) is the health monitoring portion in IIS.
1. In IIS Manager, expand the local computer, expand Application
Pools, right-click the application pool, and then click Properties.
2. Click the Health tab, and select the Enable pinging check box (if
it hasn't already been set).
3. In the box next to Ping worker process every (frequency in
seconds):, type the number of seconds that you want to elapse between
pings.
4. Click OK.
Regards,
Keith
|
|
|
|
|
Peter Donker
Veteran Member
Posts:4536
|
| 07/30/2008 7:02 PM |
|
Good suggestion Keith. Thanks for that. Another thing just popped in my mind regarding this. I recently had a struggle with the core News module with timeouts. I pinned it down to SQL timing out. So I used the 'Activity Monitor' in my SQL Server Management Studio (under 'Management') to see where it came from and found it that way. It is yet another tool to analyze timeouts in web apps.
Peter |
|
|
|
|
Keith Fisher
New Member
Posts:14
|
| 07/30/2008 10:11 PM |
|
Peter,
Where do you adjust the timeouts in SQL for DMX?
I've run into a similar issue when running a permissions change on a large directory with many sub folders and files - and selecting children to inherit permissions.
The timeout is dead-on 30 seconds each time and none of my usual IIS configs. or changes to the executionTimeOut in webconfig have an impact.
Regards,
Keith |
|
|
|
|
Peter Donker
Veteran Member
Posts:4536
|
| 08/01/2008 11:42 AM |
|
Keith,
This is actually specified in the connection string. Google on SQL Server connection strings and you should find more. Note: if you ever find a blocking/stuck/hanging process using the activity monitor related to DMX drop me an email and I'll see if I can trace it.
Peter |
|
|
|
|
Keith Fisher
New Member
Posts:14
|
| 08/05/2008 4:21 PM |
|
Thanks for that Peter,
I'm at the limits of my knowledge here, but I seem to remember reading that you can't extend execution timeouts from the connection string, you can only extend the connection timeout.
At some point I'd love to see a graphical representation of the route from DMX to SQL (running a time-consuming query, let's say) and back again, with every attendant helper (?) on the way...
I'm sure you would too!!!
We're getting there.
Regards,
Keith
|
|
|
|
|
Peter Donker
Veteran Member
Posts:4536
|
| 08/11/2008 6:32 PM |
|
Hi Keith,
I can't think of anything to help right now. There are possibly more advanced tools to 'sniff' app to SQL traffic, but I'm not in the know. I concentrate on making everything DNN compliant and sticking to general .NET/SQL coding practice. This should keep DMX clear of any SQL issues.
Cheers,
Peter |
|
|
|
|