


If that is the case, resetting your Internet Explorer settings will make the OneDrive script error go away. The onboard Windows 10 OneDrive application uses the same internet connection settings as the Internet Explorer app on your computer, which means that any corrupted or incorrectly configured Internet Explorer settings will cause OneDrive to malfunction. Solution 2: Reset your Internet Explorer settings

If so, I would suggest you build your sample application which has this issue and upload it to OneDrive and then share its link with us. We will test it to narrow down this issue to help you.You should no longer receive a script error in the OneDrive app and the app should launch successfully after your computer boots up. And you could uninstall and reinstall your Visual Studio to test whether If not, you could share the key difference between that machine and yours like the IE version with us, we could further look at this issue by this information. If you build and copy your web application to another machine and run it without debugging by pressing Ctrl+F5, will it has the same issue? If not, which machine doesn't have this issue?Ģ. If so, if build that web application with these Visual Studios, will it has the same issue? Does the machine which has this issue install VS2008, VS2010 and VS2012?

In order to get more clear about this issue, we need to confirm with you the following information. Thanks for helping make community forums a great place. We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Hopes that blog could help others who has similar issue but don't want to update it from IE9, IE10 or other versions to IE11. Glad that you have solved this issue and thanks for your sharing.Īccording to your description, the key difference is the IE version, and I found a blog whith similar issue, But now that IE is upgraded, IE doesn't have the problem Also, I had noticed that debugging using Firefox didn't have the problem. However, upgrading to Microsoft Internet Explorer 11 did the trick. I only have access to the one machine, but in answer to the second part of your question, Ctrl+F5 runs the program without the exception.Īfter uninstalling and reinstalling, that didn't help. No other versions have been installed on it.Ģ. The machine only has Visual Studio 2013 installed on it.
