Hello,

I'm not sure what happened, but today I noticed that if you go to the main page of this website: http://thedynoroom.com/ DNN generates an error. Then when you click on the Return to Site link, it works as it takes you to http://thedynoroom.com/Home.aspx.

So if you go to just the root, i.e. thedynoroom.com/ you get the error, but thedynoroom.com/default.aspx or thedynoroom.com/home.aspx work fine.

Not sure how to debug this as the event viewer log doesn't specify the name of the file it is trying to find. Any other logs, etc to look at? 

Please....any help is greatly appreciated!

Thanks in advance,
Chad

Here is the error:

AssemblyVersion: 6.0.0

PortalID: 0

PortalName: TheDynoRoom.com

UserID: -1

UserName:

ActiveTabID: 240

ActiveTabName: Home

RawURL: /

AbsoluteURL: /

AbsoluteURLReferrer:

UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: bf1a599f-0b94-49df-8362-e1e6f3aa332e

InnerException: File does not exist.

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: System.Web.StaticFileHandler.GetFileInfo

StackTrace:

Message: DotNetNuke.Services.Exceptions.PageLoadException: File does not exist. ---> System.Web.HttpException: File does not exist. at System.Web.StaticFileHandler.GetFileInfo(String virtualPathWithPathInfo, String physicalPath, HttpResponse response) at System.Web.StaticFileHandler.ProcessRequestInternal(HttpContext context, String overrideVirtualPath) at System.Web.DefaultHttpHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object state) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---

Source:

Thanks for the quick reply Sebastian.

I tried restarting the app pool and the site settings has the Home.aspx page as its designated home page.

No luck.

But I remembered I installed Will Strohl's Open Graph module to test it out...even though it was not on the home page, it still was causing some problems I guess. After uninstalling, the problem went away. I'll reach out to him to make him aware of it.

Thanks again,

Chad