Thanks for you response.
First, I'm not following you about adopting the web.config manually since 4.6.2. Can you clarify that? Do you mean that something in the upgrade process will move all my settings over? How does that work?
I did a couple refreshes of both the full upgrade set of files, plus the web.config and never got the website to respond correctly, so I restored from backup to my pre-4.9 state. My site is working again, but chewing up massive amounts of memory and CPU, so my hosting provider is screaming to get this fixed (rightly so).
I am experiencing the App Pool reset issue in my logs - about every minute, which is probably due to the App Pool recycling. This was happening before the 4.9 upgrade attempt -- that's why I was hoping the upgrade would work.
I'm also seeing something odd just before the app pool recycle:
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
RawURL: /dbartisanboard.htmdefault.aspx?&__U=1226426752221
AbsoluteURL: /dbartisanboard.htmdefault.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.19 (KHTML, like Gecko) Chrome/0.3.154.9 Safari/525.19
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 46900597-1d5b-4441-aa21-964ca00b5f53
InnerException: Unhandled Error:
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.Util.CheckVirtualFileExists
StackTrace:
Message: System.Exception: Unhandled Error: ---> System.Web.HttpException: The file '/dbartisanboard.htmdefault.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.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(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) --- End of inner exception stack trace ---
Source:
So about every minute or so, something is hitting my site looking for this URL. This is partially and old URL from our previous site (notice the ending in .htm), mixed with the default.aspx page. I've checked our SiteUrls and we don't have any special entries for this.
I don't know if this is related, but I thought I'd post it as well.