I am getting following error while i deployed the website..
Server Error in '/domain/website' 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>
I tried changing customErrors mode="Off" But no Joy ..same error repeats ...
Moreover , GenericErrorPage.htm is missing is this causing the error?
Any helping hands?
This is possibly because there is a syntax error in web.config. You could try replacing your current web.config with one that only contains this and see what happens:
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Are you using dual web.config in your website. eg.
if you are using one web.config in /domain and another in /domain/website. You need to convert the /website as an application.
however, I would suggest you to log into the server and browse the page, you will be able to see the real issue. If you are unsure how to fix it. post it once. We might be able to help you.
Related
I made this website of mine but now , someone E-mailed me and reported the following error:
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>
I wanted to know is this dangerous for my website?Can it be used to hack my website?If yes , how?
I can't change anything because I don't have access to my website for the following 4 months.
In short: Its NOT dangerous, It does NOT give any information about the error, just that it happened. It might give some information about the type of server you have, but thats already probably in your server banner (and elsewhere). I would not worry about it.
Im working with Visual Studio 2012 Web Forms the website is starting normally when i open it from local server but when i move the files to GoDaddy hosting into httpdocs this error appears
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>
Your code is throwing an exception that you can't see. Change your code to mode="Off" as the message indicates. Long term I would recommend using a logging tool like ELMAH so you can see the exceptions and give end users the friendly page. http://www.hanselman.com/blog/ELMAHErrorLoggingModulesAndHandlersForASPNETAndMVCToo.aspx
The situation is described by this question where the user updates the Web.config and he gets a weird error (completely unrelated from the real problem).
https://stackoverflow.com/a/7142817/196210
Is it possible to tell IIS to avoid creating problem when the config file is edited?
It appears that the problem is related to editing the file with VS.NET while editing it with Notepad++ works
Server Error in '/' Application
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>
IIS 7.0 or later will take the settings from web.config files. If your file is not properly edited, it won't be parsed by IIS and will not work at all.
You need to either change the custom error page to view the error outside the server or loginto the server and check the error. this way you will be able to see the error and fix it.
When I am Connecting a website through remote machine, The Website showing the run-time error
Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".
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 configuration tag to point to a custom error page URL.
But i want to display entire site in my website, and one more thing i am using Ajax controls in website, they are CalenderExtender control.
Only Ajax Control tabs showing errors, remaining will be executed perfectly.
enter code here
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
You seem to have an exception somewhere, it may (or may not) be related to your configuration of the AJAX controls, and you need to correct this first. Check the event log on the server to see the exception details, or just configure your site to expose the details in the browser (which is suggested in the error message you're currently seeing.
You should have only a single <customErrors> tag in your web.config:
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Set the mode to "off" if you want the site to display all the exception details. However, on production websites, it's generally recommended never to display these details to users.
I want to open the web site with hosting server is in remote location but i got the error like this
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 tag within a "web.config" configuration file located in the root directory of the current web application. This 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 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>
we need to add below line to get to know exact error. (as suggested by the error msg itself.
<system.web>
<customErrors mode="Off"/> </system.web>