|
|
Rank: Newbie
Groups: Member
Joined: 1/23/2012
Posts: 3
|
We are evaluating the AJAXUploader in ASP.NET 2.0 and thus far we really like it. The progress bar in particular is fantastic. The way you've wrapped it in a template allows me to capture the 'upload' button event and copy the uploaded file to a final destination with a minimum of client-side code, which is also nice.
The site using the control is running on Windows Server 2008, IIS 7.5. But our uploads insist on failing at 3 minutes and we're banging our heads on the reason. I've searched the forums and set everything I can find to set, both in IIS and our application's web.config, and nothing makes a difference. The error message is: AJAX call to the server times out.
From what I've read on the forums this has to be an IIS connection timeout setting somewhere, unless the evaluation version of AJAXUploader has a built in 3 minute timer. Can you point us in any possible direction?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Have you checked your ASP.NET application request time out setting yet? Also when you receive time out error, is the progress bar still at 0 or it has already moved some?
Thanks
|
|
Rank: Newbie
Groups: Member
Joined: 1/23/2012
Posts: 3
|
The progress bar is moving--whatever you can upload in 3 minutes is what you get. Smaller file sizes or fast connections, no problem as long as they complete in 3 minutes.
In our web.config we've set
<sessionState timeout="3600"/>
<httpRuntime executionTimeout="999999" maxRequestLength="250480" shutdownTimeout="3600"/>
<requestLimits maxAllowedContentLength="2097151000"/>
In IIS 7.5 we've set everything we can find.
Sites-->web site defaults-->connection limits-->connection timeout 9999
<our site> -->connection limits-->connection timeout 9999
<our site> -->configuration editor-->request limits all set at web.config and appHost.config level
When you say ' ASP.NET application request time out setting' where are you referring to? The app's web.config, IIS 7.5 or applicationHost.config?
Thanks for the help, I know this isn't the control's fault
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
When we say ASP.NET request time out, we meant httpRuntime executionTimeout. However since you already set that, then it might be something else. Unfortunately we can't think of anything else either. You may want to try to write some test code to just sleep for a long time to see whether your time out setting is indeed working for you.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 1/23/2012
Posts: 3
|
Note you might find interesting: Microsoft's plain-vanilla fileUpload control does NOT have this 3-minute timeout problem.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
That is very interesting. We do not know what can cause that at this point, we will see if we can reproduce the problem on our side. If we can reproduce it, then we should be able to find out the root cause.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 8/17/2007
Posts: 2
|
eo_support wrote:Hi,
Have you checked your ASP.NET application request time out setting yet? Also when you receive time out error, is the progress bar still at 0 or it has already moved some?
Thanks i do have this issue, on larger files the bar does not move and i eventually get the control timeout message. in google crome it shows uploading and a percentage increase until the timeout. small files the progress bar works great. and control completes upload. on my local machine the bar moves, but when serving on any other machine the issue presents itself. Any help would be great
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
Please check whether you have the latest version first. There was one issue on the uploader in our early version that could cause this problem. However that problem has since been fixed. If you are still getting this issue with the latest version, then the problem is on your server side ---- either your IIS is filtering the request out, or ASP.NET is filtering the request out. You might want to use a network monitor to troubleshoot that case.
Thanks!
|
|