IIS Crashes - unhandled exceptions in UploadDataInternal

Mehdi@irslogics.com

Posted on
Oct 21 2014

Hi

we have been experiencing intermittent IIS crashes for the last few weeks. we use ??Mindscape.Raygun4Net, Version=3.3.2.0 after sending crash dumps to Microsoft their analysis was mindscape assemblies cause unhanded exceptions and that causes the crash: "we would suggest to handle the exception thrown by MindscapeRaygun4Net!Mindscape.Raygun4Net.RaygunClientBase.Send and also can you please verify UploadDataInternal function. Systemni!System.Net.WebClient.UploadDataInternal(System.Uri, System.String, Byte[], System.Net.WebRequest ByRef)"

Thanks,

Mehdy Mohajery


Jason Fauchelle

Raygun

Posted on
Oct 22 2014

Hi Mehdy,

Thanks for pointing this out, sounds like this may be the same issue: https://raygun.io/forums/thread/13055#13056 (FlagAsSent is an internal method called by the RaygunClientBase.Send method). This is scheduled to be resolved early next week. I'll update this thread when a fix is available.

-Jason Fauchelle


Mehdi@irslogics.com

Posted on
Oct 22 2014

if the next release will handle the exception mentioned below, we would be fine. the other thing that may help is fixing 403 errors which comes from server side.

Exception object: 0b375e04 Exception type: System.Net.WebException Message: The remote server returned an error: (403) Forbidden. InnerException:


Jason Fauchelle

Raygun

Posted on
Nov 03 2014

Hi Mehdy,

The issue in RaygunCientBase that I mentioned previously is now fixed in the latest version of Raygun4Net (4.0.1) which is available right now from NuGet.

If there are still issues with sending exception reports, please let me know.

-Jason Fauchelle


Mehdi@irslogics.com

Posted on
Nov 05 2014

The IIS Crash issue seems to be fixed but we get "The remote server returned an error: (403) Forbidden." Like 20 times a day from Raygun (we have throwOnError=true)


Jason Fauchelle

Raygun

Posted on
Nov 06 2014

Hi Mehdy,

403s should only occur if you send an empty or invalid API key. Please double check that the Raygun API key(s) that you use in your application(s) do match up to valid API keys for your application(s) in Raygun. It may be that someone reset an API key in Raygun, but didn't update it in the app. Or an empty or incorrectly copied key may be being used somewhere in your app.

Hope that helps get to the bottom of this issue! Please let me know if the problem remains.

-Jason Fauchelle


Reply