61
Views
6
Comments
[Custom 404 Pages for Reactive apps] Error in logs System.Web.HttpUnhandledException
custom-404-pages-for-reactive-apps
Reactive icon
Forge asset by Vanguard Labs
Application Type
Reactive

Hi Custom 404 Team,

Firstly thanks for an excellent and clever plugin that fills a much needed gap.

I was wondering if you could help shed some light on an error we are experiencing with the plugin.

We seeing an unhandled exception which looks like it is being thrown during the rendering of the intermediate NotFound.aspx page.

See the stack trace below. I can replicated it by opening the debug tools in Chrome at which point Chrome tries to find a .map file. However, that is just a way I can replicate it, there are other requests coming in causing an error too.

I have double checked, and we have followed the implementation correctly, and the 404 page loads correctly when I enter a non-existent URL on the site.

It is not preventing anything from happening on our site, however we would like stop it from occurring.

Have you seen this error, and/or have any ideas about how to prevent it?

Thanks and kind regards,

Stuart

Here is the stack trace:

[1] Exception of type 'System.Web.HttpUnhandledException' was thrown.   at System.Web.UI.Page.HandleError(Exception e)   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)   at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)   at System.Web.UI.Page.ProcessRequest()   at System.Web.UI.Page.ProcessRequest(HttpContext context)   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) [2] Object reference not set to an instance of an object.   at ASP.notfound_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)   at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)   at System.Web.UI.Page.Render(HtmlTextWriter writer)   at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 

2021-05-14 16-39-03
Vanguard Labs

Hi @Stuart Harris. Thank you for your kind words and for sharing this issue with us.

We were not aware of this behavior. We'll have a look at it and let you know.

Thanks.

2023-04-05 07-54-24
Willem Notten

Hi @Vanguard Labs,

Did you already had the chance to look into the mentioned issue? Having the same issue here.

Thanks,
Willem

UserImage.jpg
Donna Williams

@Vanguard Labs Any update on this? We installed this on a new website and are getting the same error.

2024-11-04 13-29-55
Doug Kantor

We attempted to use the Forge component as prescribed, but are getting tons of errors with no response on a resolution.

It seems to be occurring not on missing pages, but on many different elements on a page.

2015-05-05 17-20-51
João Santos

A new version of the component was just released precisely to address this problem. Please download and confirm if it works for you. 
Thanks.

2024-11-04 13-29-55
Doug Kantor

Thanks! Works so far. It was a little intermittent, so will continue to monitor.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.