Internet Explorer cannot display the web page

[Mary]

Hi,

I'm experiencing problems with the RadUpload sometimes working great with progress indicator for files up to 2GB and sometimes I get "Internet Explorer cannot display the web page."  The files can be as smaller than 1MB and I can still have the same problem.  I did not seem to have this problem when the server was on our internal network, where of course the network speeds are much faster.  Tthe "Internet Explorer cannot display the web page" can come up after 10 seconds, 20 seconds, 30 seconds, 40 seconds, ...after executing the Submit button to perform the upload.  I've played with client browser timeout settings, set IIS 7.5 uploadReadAheadSize to 5MB, set IIS 7.5 connection timeout to 3 hours (10800 seconds), but I can't seem to solve this problem.  The RadUpload utility logs in the IIS web logs that it is uploading, and the last log when I get "Internet Explorer cannot display the web page" is that it is uploading.  There are no other logs anywhere.  Even if the network is dropping packets or something, is there a way to build in some better error control handling so that when this happens the upload session can stay in progress?

Mary

[Peter Filipov]

Hello Mary,

RadUpload control is using standard <input type='file' /> control. The RadUpload object is giving you a reference to the uploaded file through the UploadedFiles collection. All the limitation of the standard html control will be reflected on the RadUpload.
Do you have a pattern to reproduce the issue? Could you please try to reproduce the issue with standard html element <input type='file'/>? Could you confirm that your web config is setup as here?

All the best,
Peter Filipov
the Telerik team

[Mary]

Peter, Thanks for your response.

Yes, we are using standard html element <input type='file'/> (coding below).

function AddFileIE(iNumber)

  

{

  

var sHTML;

  

sHTML='';

  

for(i=1;i<=iNumber;i++)

  

{ 

  

//if(i>=10)

  

// sHTML= sHTML + "File " + i + ": "

  

//else

  

// sHTML= sHTML + "File " + i + ":   "

  

  

sHTML= sHTML + "<INPUT id='file" + i + "' name='file" + i + "' type='file' style='width:300px'><br />"; 

  

}

  

  

oP1 = document.getElementById("p1") ;

  

oP1.innerHTML=sHTML;

  

}

I cannot precipitate when the upload will or will not work. Tested with a 36.5MB .PDF file yesterday. Received the below results.  There were no other accesses to this webserver or this website by anyone else at these times.

09:57 AM - upload failed, received Internet Explorer Cannot Display the Webpage
09:59 AM - upload failed, received Internet Explorer Cannot Display the Webpage
10:00 AM - upload successful, about 45 seconds to upload
01:17 PM - upload successful, about 1 minute 10 seconds to upload
04:56 PM - upload successful, about 1 minute 17 seconds to upload

Our config settings are as follows.

Execution Timeout=30000000 (seconds)

maxRequestLength=2097151 (this is in KB)

maxAllowedContentLength=”2147483648” /> (this is in Bytes)
<section name="requestFiltering" overrideModeDefault="Allow" />

Execution Timeout=30000000

maxRequestLength=2097151

These have not changed from their defaults

ResponseDeadlockInterval=”00:03:00”

responseRestartDeadlockInterval=”00:09:00”

I also tested changing the uploadReadAheadSize to sizes larger than the file size I was uploading, but it would just take longer until it got to the progress window, and then it still sometimes would fail with the "Internet Explorer Cannot Display the Webpage."

Thanks for your assistance

[Peter Filipov]

Hi Mary,

My suggestion is that the ResponseDeadlockInterval is restarting the thread before the file is uploaded. Could try to set it e.g. to 10 seconds and upload a file which will take longer than 10 seconds? Do you experience the same error again.

Kind regards,
Peter Filipov
the Telerik team

[Mary]

Peter,

Thanks for the reply and assistance.

The responseDeadlockInterval is already set to "00:03:00" which is the equivalent to 3 minutes.  There are no deadlock errors or messages in the Windows event log.

I did fiddle with the uploadReadAheadSize, and it seemed to be more reliable starting an upload.  The progress window would not show on the client side until the uploadReadAheadSize was met, so when I increased it to 500MB, it did not show the RadUpload progress window for about 20 minutes and then continued with the upload and completed.  As I increased the uploadReadAheadSize, the RadUpload progress window was more reliable at coming up and the file transfer beginning.  As I increased the uploadReadAheadSize, I had to increase the memory allowances on the application pool for it to work.  However, also as I increased the uploadReadAheadSize the upload was more apt to fail to the "Internet Explorer Cannot Display the Webpage" after the progress window appeared even after 2 hours into an upload especially with multiple simultaneous uploads (3 or less simultaneous uploads).  With a smaller uploadReadAheadSize of 5MB, as long as the progress window came up, the upload was always successful after that which is much more desirable.  Results are that even with different uploadReadAheadSizes, the application is still having problems with the "Internet Explorer Cannot Display the Webpage."  I see no errors or problematic worker process shutdown messages in the Windows Event Logs. (I had received some worker process shutdown messages before due to timeouts, virtual memory limits, but I have tweaked all of these and they are no longer a problem).  No Windows Event logs and no IIS log entries exist when an upload fails.

Mary

[Peter Filipov]

Hi Mary,

Probably there is some kind of limitation of the IIS and <input type='file' /> control. I am afraid that we have no experience with such behavior. Could you try to deploy your application on other machine and test it?
Other possibility is to replace RadUpload with RadAsyncUpload control in your application.

Regards,
Peter Filipov
the Telerik team