Might just need a simple fix

An old client of mine recently had their site go down and all the data was erased. I had the site (most of it and maybe all of it) on my thumb drive so I re-uploaded everything last night.

But I’m getting this error at http://franciscosautorepair.com/

[INDENT]Server Error in ‘/’ Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a “web.config” configuration file located in the root directory of the current web application. This <customErrors> tag should then have its “mode” attribute set to “Off”.

<!-- Web.Config Configuration File –>

<configuration>
<system.web>
<customErrors mode=“Off”/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the “defaultRedirect” attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File –>

<configuration>
<system.web>
<customErrors mode=“RemoteOnly” defaultRedirect=“mycustompage.htm”/>
</system.web>
</configuration>[/INDENT]

I suspect it only needs a simple fix but I don’t really know ASP.Net at all but I’ve worked on this site before doing some front end stuff. Is there maybe something to do in the hosting control panel to fix it?

I have same problem last year and i didn`t find solution…same eror
“Server Error in ‘/’ Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine”
just let it go…my way…

.NET masks errors by default for security reasons. The error page you see has instructions on how to turn this off, that is where I would start as getting a clear indication of the error would help narrow it down. If you can get administrative access to the server that could also ease things as you can request the page locally thereby getting the errors or just check the event log which will note exceptions by default.

If you make that change and the app still doesn’t fire up it usually means you’ve got a version issue – as in IIS is configured to run a different version of the framework than your client’s site so there might be a configuration incompatibility.