Click here to Skip to main content
15,886,518 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
My site runs fine locally but when I publish it I get this error. I remember in college a lot of people would get this error!
Please any help would be greatly appreciated!
.Net Frame work is 2.0
XML
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><pre>
Posted
Updated 14-Feb-18 23:14pm
v2
Comments
Sandeep Mewara 30-Jun-10 1:54am    
Change the CustomError to Off and see what is the reason for error. Try to resolve that, in case needed post the same here.

See, everything is explained in the error itself.There is some error in your application but tha will not display from remote machine.

Go to your server and try to access your application from localhost, then the error details will be displayed the page and you will be able to rectify your actual problem
 
Share this answer
 
You can also check the event log of the server for unhanded exception.
 
Share this answer
 
<configuration>
<system.web>
<customerrors mode="Off">




make the customErrors mode="On" then you will find what is the issue. there can be error anywhere in the application.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900