Click here to Skip to main content
15,897,518 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
I published project after that error comes .Please solved This error.


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




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






Advance Thanks
Regards : Bhushan Gupta
Posted
Updated 17-Nov-17 20:41pm
v2

Try setting custom errors to Off on the web.config
XML
<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
Note: use capital O on Off


Another idea:
This error can be caused by a virtual directory not being configured as an application in IIS.
And if the server is remote (and it probably is) then perhaps you have this line:
XML
<authentication mode="Windows" /> 
if so, you might be blocked by the server with Windows Authentication, you might want to remove that line...


Best,
H
 
Share this answer
 
v5
Comments
[no name] 28-Aug-13 7:12am    
I already used this <customerrors defaultredirect="~/Error.aspx" mode="On">
[no name] 28-Aug-13 7:13am    
and I accept your suggestion but again error.
Herbisaurus 28-Aug-13 7:28am    
See update about configuring the virtual directory as an application...

Also, if the server is remote (and I guess it is) then perhaps you have this line:
<authentication mode="Windows">
if so, you might be blocked by the server with Windows Authentication, you might want to remove that line...
just add this line of code in global file

GlobalFilters.Filters.Add(new HandleErrorAttribute());
 
Share this answer
 
I fixed this issue by changing the x64 bit in Microsoft azure since our project which was converted to x64 bit but needs to do the same changes in Azure.
 
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