Member Avatar for successalways

hello i am Anand kumar .. the below is the error discription after hosting my web page..
is the webaddress...
i hope u will provide me suggestion to clear it...


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

  • 3 Contributors
  • 2 Replies
  • 132 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by sierrasoft

Dani AI

Generated

This is a common ASP.NET hosting symptom: the site is throwing an unhandled server-side error but the site is configured to hide the details from remote browsers. and point toward showing the error and using tracing — those will reveal the stack trace, but doing so broadly on a production site is risky. A safer approach is to collect the diagnostic data from server-side logs and a controlled trace session, then fix the underlying exception and re-secure the site.

Start with the server logs and request traces. Check the Windows Application event log for the ASP.NET exception and stack trace first. Next, examine the IIS request logs for the failing request (look for the 500 status and any substatus/win32 codes) to narrow whether this is a configuration error, a missing module/assembly, or a runtime fault. If available, enable Failed Request Tracing in IIS for that URL and reproduce the problem once; FREB captures module-level details that the ordinary error page won’t show.

Common causes to verify before changing site-visible settings: ensure the app pool is targeting the correct .NET CLR and pipeline mode, confirm all referenced DLLs are present in the bin folder, check that the app pool identity has read/execute access to the app files and any resource it needs (databases, config files), and validate production connection strings and external service credentials. A mis-compiled or transformed web.config can also cause startup failures — compare the deployed web.config to your working local one.

For safe diagnostics and permanent fixes: use remote debugging or enable detailed errors only for your admin IP, or add a server-side exception logger (ELMAH, Serilog/Seq, or similar) to capture full stack traces without exposing them to the public. After resolving the issue, revert any settings that expose detailed errors.

Recommended Answers

All 2 Replies

Member Avatar for nandhinijp

you should place this code in your web config ,within the

<system.web>
<customErrors mode="Off">
</customErrors>
</system.web>

i dont know the proper reason for this customerrors mode off.But its working.

Member Avatar for sierrasoft

there is an error in your project. To view the error on your local machine from where you are browsing the site--change the web.config settings.

<trace enabled="true"
requestLimit="10"
pageOutput="True"
traceMode="SortByTime"
localOnly="false"
mostRecent="true"/>

This will display the error details on your page.

You can set the Page output to false (this will not display the error details on the page you are viewing) and set the localonly to false.

You can then view the error in the trace.axd file. The Trace.axd file can be viewed like this :

I hope this helps.

Regards
Sunil Punjabi

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.