Click here to Skip to main content
16,019,618 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I built a Web application. and i publishedon the server .
now,when i want to visit my application form client ,it show me this error

HTML
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>


Also the my code in web.congif is
XML
<?xml version="1.0"?>
<configuration>
	<system.web>
              <customErrors mode="RemoteOnly" defaultRedirect="Error.html">
	       </customErrors>
	</system.web>

<authentication mode="Forms">
			<forms name="Myappcookie" loginUrl="Login.aspx" protection="All" timeout="30" defaultUrl="Page.html">
				<credentials passwordFormat="Clear">
					<user name="*" password="*"/>
				</credentials>
			</forms>
		</authentication>


i changed the mode to "Off" and add the the trust To "all" but again i have this problem,
how can i fix it?
Posted
Updated 11-Jan-12 5:12am
v2

1 solution

If you are using IIS 7(.5), then I would suggest turning on and using Failed Request Tracing[^]. The failed request logs are a good way to find out where and why your deployed code is failing.

Make sure that the Application Pool your web application is running under is configured to the same dotNet version that you built the application in.
 
Share this answer
 
Comments
bahman7210 11-Jan-12 11:28am    
no,just iis 6

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