Rank 1
Hello,
Suddenly today after latest Chrome 47.0.2526.73m release (Dec 1), latest version of Telerik Asp.Net (2015.3.1111.40) (and previous stable release) AsyncUpload does not work...the progress just shows as it taking forever to upload and never ends.
Works fine in IE 11 and Firefox.
Note that it does this in development and especially when deployed. I've had my code in place for a long time without trouble. Not sure if this is even a Telerik problem, but others may find helpful?
.Net 4.0
<html xmlns="http://www.w3.org/1999/xhtml"><head runat="server"> <title></title></head><body><form id="form1" runat="server"> <div> <telerik:RadScriptManager runat="server" ID="RadScriptManager1"/> <telerik:RadSkinManager ID="RadSkinManager1" runat="server" ShowChooser="true"/> <div class="demo-container size-thin"> <telerik:RadAsyncUpload runat="server" ID="AsyncUpload1" MultipleFileSelection="Automatic"/> </div> </div></form></body></html>33 Answers, 1 is accepted
I replied to your inquiry in the submitted support ticket with the same subject.
Regards,
Ivan Danchev
Telerik
Rank 1
i have exactly same issue with you. let me know if you have any luck to fix it.
Thanks,
Rank 1
No - no fix. In fact, support has stated that they can't reproduce.
But my code which worked last week (and for a year) is broken under Chrome 47.0.2526.73m, and I downloaded a portable Chrome http://portableapps.com/apps/internet/google_chrome_portable version which as of yesterday was the previous 46.x version, and it works perfectly. Side by side the 46 version works, the newer 47 version fails.
If I do stumble on something I'll be sure to post. I haven't gotten back to support yet - been too busy.
Rank 1
Here's where you can get older Chrome portable versions to test for yourself:
http://sourceforge.net/projects/portableapps/files/Google%20Chrome%20Portable/
Rank 1
I just downloaded support's test - and it works fine in Chrome 47*.
I'm now trying to see why - what is the difference between this and my other projects (both C# and VB.Net).
Rank 1
Any luck?
I am using old UI version which is the reason??
<%@ Register Assembly="Telerik.Web.UI, Version=2014.1.403.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4"
Namespace="Telerik.Web.UI" TagPrefix="telerik" %>
Rank 1
I'm using their very latest [stable] release.
I've noticed it works OK in debug on my development machine, but has issues when published on the web server. It's not a publishing thing - I know that for certain.
Rank 1
that same to me, ok in development and VS. But after publishing to server IIS, then broken.
Rank 1
Rank 1
one more update,
when I use IP address in URL then it works fine. change back to server name then failed, only Google chrome after updated.
Yi
Rank 1
Yi,
I appreciate your input! I can confirm that the exact same thing happens to me. Once published, IP address in URL works fine, but not by DNS name.
Rank 1
I got some ideas hopefully that will be helpful for fixing this issue.
I checked Log on IIS showing 401 error that means no permission to upload files to temp folder, I guess New chrome break windows integrated authentication. my case is using windows integrated authentication with IIS 7.0 in Intranet
The reason why IP address is working. when you using IP address as URL, you need enter username and password again. and using servername or DNS name in URL won't do that, and just got your credential from windows. but google chrome didn't take my credential to IIS server rightly, i GUESS.
Rank 1
Rank 1
seems it is working fine for my after I did some change in IIS.
after i google, I found these links and got an ideas that is chrome breake authentication. so I go IIS server to change Authentication Providers. only keep NTLM. then it is working fine.
https://www.reddit.com/r/sysadmin/comments/3v6suu/chrome_47_breaks_ntlm_authentication_squid/
https://code.google.com/p/chromium/issues/detail?id=544255#c41
Rank 1
Wow - what luck you posted John/Yi.... I was just facing the exact same issue fine on local machine but failing when running on server, changed the IIS config to NTLM and the upload is now working. I was tearing my hair out trying to figure out why something that was working had failed for many of my users. Thankyou Yi.
For anyone else that is googling, when debugging I was getting upload stuck on 'orange' as per original post by John and a javascript error message of "uncaught type error: cannot set property 'index' of undefined"
Rank 1
Glen,
Would you mind posting a snippet of your IIS config which includes the NTLM changes?
Rank 1
Thank you, Yi, for posting your solution. There are reports that new Chrome version 47.0.2526.80 fixes the issues with the windows authentication the previous one introduced. We can suggest testing the AsyncUpload with it.
Regards,
Ivan Danchev
Telerik
Rank 1
Glen, thanks a million!
I've been searching for days to resolve this strange issue!
Rank 1
Ivan,
47.0.2526.80 just hit my machine. I immediately tried it - no joy. Does not fix our issue.
Rank 2
Rank 1
Rank 2
Rank 1
Rank 2
Rank 2
Rank 2
I spoke with Chromium developers this morning and this issue is related to the following:
https://code.google.com/p/chromium/issues/detail?id=567692
Rank 1
Justin,
Thanks - that's really great to see they're acknowledging it and working towards a solution.... bad part is they're talking about version 48 stable, and maybe not even the first release.
<<sigh>>
Rank 2
Thank you, Justin, for providing a link to the reported issue. We hope a fix will soon be released by Google.
Currently the only workaround we are aware of is the NTLM provider setting suggested by Yi, earlier in this thread.
Regards,
Ivan Danchev
Telerik
Rank 1
Rank 2
Thank you for getting back to us. We are glad the fix solved the issue for you.
Regards,
Ivan Danchev
Telerik