Error on reading large files

[DannyMoerkerke]

The script breaks when I drop files that are larger than approx. 75MB. It exits with the following error:

SCRIPT5022: Unhandled Error in Silverlight 2 Application [ScriptObject_InvokeFailed]

Arguments:

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=8.0.60831.0&File=System.Windows.Browser.dll&Key=ScriptObject_InvokeFailed at System.Windows.Browser.ScriptObject.Invoke(String name, Object[] args) at DropFile.MainPage.LayoutRoot_Drop(Object sender, DragEventArgs e) at MS.Internal.CoreInvokeHandler.InvokeEventHandler(Int32 typeIndex, Delegate handlerDelegate, Object sender, Object args) at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName)

[MrSwitch]

Thanks for that, never tried uploading anything that large. Have you looked at any fixes for it?

Regards, Switch

On Fri, Feb 10, 2012 at 9:38 PM, DannyMoerkerke < [email protected]

wrote:

The script breaks when I drop files that are larger than approx. 75MB. It exits with the following error:

SCRIPT5022: Unhandled Error in Silverlight 2 Application [ScriptObject_InvokeFailed]

Arguments:

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=8.0.60831.0&File=System.Windows.Browser.dll&Key=ScriptObject_InvokeFailed at System.Windows.Browser.ScriptObject.Invoke(String name, Object[] args) at DropFile.MainPage.LayoutRoot_Drop(Object sender, DragEventArgs e) at MS.Internal.CoreInvokeHandler.InvokeEventHandler(Int32 typeIndex, Delegate handlerDelegate, Object sender, Object args) at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName)

---

Reply to this email directly or view it on GitHub: https://github.com/MrSwitch/dropfile/issues/6

[DannyMoerkerke]

Hi,

I had a look at dropfile.js and the error occurs somewhere in the window.dropfile function. I know nothing about Silverlight but my guess is that somehow the file is too large. I'm trying to upload videofiles which can be quite large. Maybe I would have to dive into the Silverlight code but as that will take some time to learn I'm not sure it's worth the effort. The error message is not very helpful either, which is quite often the case with Microsoft products ;-)

I'll try Google to maybe find some more info on this, if you have any suggestions I'd love to hear them.

Regards, Danny Moerkerke

On 02/11/2012 09:23 AM, MrSwitch wrote:

Thanks for that, never tried uploading anything that large. Have you looked at any fixes for it?

Regards, Switch

On Fri, Feb 10, 2012 at 9:38 PM, DannyMoerkerke< [email protected]

wrote: The script breaks when I drop files that are larger than approx. 75MB. It exits with the following error:

SCRIPT5022: Unhandled Error in Silverlight 2 Application [ScriptObject_InvokeFailed]

Arguments:

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=8.0.60831.0&File=System.Windows.Browser.dll&Key=ScriptObject_InvokeFailed at System.Windows.Browser.ScriptObject.Invoke(String name, Object[] args) at DropFile.MainPage.LayoutRoot_Drop(Object sender, DragEventArgs e) at MS.Internal.CoreInvokeHandler.InvokeEventHandler(Int32 typeIndex, Delegate handlerDelegate, Object sender, Object args) at MS.Internal.JoltHelper.FireEvent(IntPtr unmanagedObj, IntPtr unmanagedObjArgs, Int32 argsTypeIndex, Int32 actualArgsTypeIndex, String eventName)

---

Reply to this email directly or view it on GitHub: https://github.com/MrSwitch/dropfile/issues/6

---

Reply to this email directly or view it on GitHub: https://github.com/MrSwitch/dropfile/issues/6#issuecomment-3919445

[DannyMoerkerke]

Could it be that the maxRequestLength property has to be set at a higher value?