Hello.

We've recently gone live with a new installation of DNN (version 4.9.2) and keep seeing errors like this cropping up:

RawURL: /Default.aspxDefault.aspx; 
AbsoluteURL: /Default.aspxDefault.aspx; 
AbsoluteURLReferrer: ;
 UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; MDDR); 
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider;
 ExceptionGUID: 02f04e50-e63a-41fe-be8c-f4ddb3aa4939; 
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 '/Default.aspxDefault.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 ---

Has anyone else seen issues like this?  Is it a DNN thing or an IIS thing?  Any help would be greatly appreciated.

DNN is indeed installed in the root and Default.aspx is setup as the default document.  Bit more about our setup - 2 load balanced web servers, 1 database server.  DNN application files are local the web servers.

This doesn't happen to all users, as I am able to bring up the site just fine.  It does seems to happen consistently on some child portals though.

glad you figured it out! :)