RadProgressArea not updated on server

[Sjeff]

Hi,

I have created a simple uploader that I am using to upload and process files.
I am using a ProgressArea for custom use, to show the progress of the file processing and not the file uploading.

On my develment server it is working fine, but after publish to my webserver it is not working.
The area shows, but the bars stay empty and the information shown is not updated in any way.

You can test my Progress Area using the following link: http://diesel.persies.nl
Just get this file, and upload it in te site above. and you will see what happens (or doesn't).

What could be wrong?

P.S. i am using a trial version at the moment, but I do not beleive that has anything to do with the problem.

[Sjeff]

I did a rebuilt and a new Publish. After checking the Area was functioning correct. Then, nothing was changed but again it is not working anymore!!

Please help?

regards,
Sjeff

[Peter Filipov]

Hello Sjeff,

We are aware of that issue. It appears when in the IIS server has a "Default Document" set (e.g. Default.aspx). When the page is requested (e.g. http://diesel.persies.nl/), it opens the Default.aspx page. If the page is requested like this - http://diesel.persies.nl/Default.aspx, the progress area is working properly.

We are working on that issue and it is going to be fixed. Please excuse us for the inconvenience.

Best wishes,
Peter Filipov
the Telerik team

[Christopher Lee]

I'm having the exact same problem.  When will this be fixed?

[Iana Tsolova]

Hello,

Find more information about the issue and how to fix it in this article (the KNown Issues section).

Regards,
Iana Tsolova
the Telerik team

[540YMX]

Ran into the same problem with the progress area working on a development pc but not in a live environment.

On comparing a web.config file created by the Telerik Project Wizard I noticed that several sections were missing various items
So to the system.webserver modules section I added

    remove name="RadUploadModule" />
    <add name="RadUploadModule" type="Telerik.Web.UI.RadUploadHttpModule" preCondition="integratedMode" />
    <remove name="RadCompression" />
    <add name="RadCompression" type="Telerik.Web.UI.RadCompression" preCondition="integratedMode" />

And to the system.webserver handlers section I added
    

<remove name="Telerik_RadUploadProgressHandler_ashx" />
            <add name="Telerik_RadUploadProgressHandler_ashx" path="Telerik.RadUploadProgressHandler.ashx" type="Telerik.Web.UI.RadUploadProgressHandler" verb="*" preCondition="integratedMode" />

And now the progress area works as expected

[Armadous]

I wanted to share my experience with this issue. It was very frustrating and I'd love the opportunity to save some one else the headache.

I use an httpModule called SecuritySwitch to handle moving between http and https for me. For local development I have it disabled to make inspecting web traffic easy. When moving to our production environment it gets turned on.

This is bad news bears for the RadProgressArea, the requests went out over http and never made it to the progress handler.

<add path="~/Telerik.RadUploadProgressHandler.ashx" security="Ignore" />

By adding the .ashx to the SecuritySwitch config the RadProgressArea is now able to poll for its state in my production environment.

[Valera]

From referenced page:

Problem

When RadCompression is enabled and you are using .NET 4.0, event handlers might not be raised in a default document in IIS 7 or IIS 7.5 Integrated Mode.

Solution

This problem is caused by a breaking change in .NET 4.0 described here. To workaround it one can set preCondition="managedHandler" for the RadCompression module. You may also need to remove therunAllManagedModulesForAllRequests setting from your web.config if you have it (or set it to false).

This doesn't solve the issue...
Please advice how to make telerik:RadProgressArea update its status when it is being used on Default.aspx pages where Default.aspx page is not directly referenced ( i.e. www.mywebsite.com/UploadFile/ )

Thank You

[Peter Filipov]

Hello Valera,

I am afraid that the issue described in your last post could not be resolved. It is a limitation of the HttpRequest object.

All the best,
Peter Filipov
the Telerik team