It works for me on my development machine I'm always using Integrated mode. As long as you have this in the <modules> section of Web.config it should work:

<add name="PageNotFoundHandler" type="mojoPortal.Web.PageNotFoundHttpModule, mojoPortal.Web" />

you might try changing it like this:

<add name="PageNotFoundHandler" type="mojoPortal.Web.PageNotFoundHttpModule, mojoPortal.Web" preCondition="managedHandler" />

and see if it makes a difference or also it could be an issue using extensionless urls vs using .aspx as I'm not using extensionless urls on my machine.

Hope it helps,

Joe

According to that message the PageNotFoundHandler handled it which means it should have shown the custom 404. What are you seeing in the browser? Maybe it can't find the custom404 page. Are you using the one included with mojoPortal or a different one?

Are you running any additional IIS modules like url re-writers or anything that might be affecting it? Like , if you look at the modules list in IIS if there is a module listed higher in the list than the PageNotFoundHandler that may be doing something ith 404s before PageNotFoundHandler can respond.

Try also:

<add name="PageNotFoundHandler" type="mojoPortal.Web.PageNotFoundHttpModule, mojoPortal.Web" preCondition="" />

Also if you have this:

<modules runAllManagedModulesForAllRequests="true">

try changing to this:

<modules>

which will mean extensionless urls won't work but worth ruling out as a factor.

Hope it helps,

Joe

I think I am going to try setting up a new site on a clean install of 2008 with IIS 7. I am having this issue on two different servers with any site using Integrated Pipeline. I was using the URL Rewrite tool from MS but I disabled it on one site and I still have the same issue. I have also tried moving the PageNotFoundHandler module to different locations in the <modules> section but to no avail.

I have been testing this on different sites on different servers. I am not sure if my control panel (DotNetPanel) has set something up in IIS that is messing with this or not. That is why I want to try using a clean install.

Thanks for your help. I will let you know what happens with the different server.

Thanks,
Joe D.

Hey Joe,

I have two different results in the log for the PageNotFoundHandler depending on whether I use Integrated vs Classic app pools.

When using Integrated App Pool I get:

2010-01-20 17:32:49,257 ERROR mojoPortal.Web.PageNotFoundHttpModule - 10.117.198.60 PageNotFoundHttpModule handled error.
System.Web.HttpException: The file '/whois.aspx' does not exist.
at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)

at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
  at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

When using Classic App Pools I get:

2010-01-20 17:34:27,725 ERROR mojoPortal.Web.PageNotFoundHttpModule - 10.117.198.60 PageNotFoundHttpModule handled error.
System.Web.HttpException: The file '/whois.aspx' does not exist.
at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
  at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

You'll notice that everything is the same until the bolded line above. Does that shed any light on the issue?

Thanks,
Joe D.