'current custom error settings for application prevent details of application error from being viewe

  • Thread starter Thread starter Damian
  • Start date Start date
D

Damian

Hi everyone

I'm having an issue with one of our applications. I'm getting the
following error when attempting to log in to the site:

Server Error in 'xxxxxxxxxxxxxxxx' 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.

Details: To enable the details of this specific error message to be
viewable on the local server machine, 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 "RemoteOnly". To enable
the details to be viewable on remote machines, please set "mode" to
"Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</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="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
The customErrors setting appears to make no difference, whether it's
the one on the machine.config file (.NET FWK 1.0) or the one on the
application's web.config file, or both, or any of the combinations
I've tried. The error stays the same

As I mention the current .NET version on the system is 1.0, however by
mistake I first installed (and uninstalled) the newer 1.1 version.

The machine is a W2K domain controller and the user I'm logging in to
the application with has been granted admin rights. The ProcessModel
line on the machine.config file is set to 'SYSTEM', and security on
IIS is set to Basic for the application. 'Impersonate' is set to True.

I checked the application mappings part of the Configuration dialog
for the application and the Microsoft .NET Framework entries are
pointing to the proper (installed) version.

I'm really not sure what else to check and I really need to get this
going. I'll appreciate any and all help you could give me.

Thanks in advance, regards

Damián
 
Hi Damian,

The fact that a change in the web.config does not illicit a change in
behavior means that we aren't successfully parsing the configuration file.
We aren't getting that far.

The easiest way to figure out what's going on would be to create a simple
inline ASP.NET page and place it in the folder for the default Web site.
(If there is a web.config there, rename it first to web.config.old or
something.) Here's a sample file you can use. Just paste this into an
empty file and save it as test.aspx:

<%@ Page Language="C#" %>
<script runat="server">

private void Page_Load(object sender, System.EventArgs e) {
lblWho.Text = "ASP.NET running as : " +
System.Security.Principal.WindowsIdentity.GetCurrent().Name;
}

</script>
<html>
<head>
</head>
<body>
<form runat="server">
<asp:Label id="lblWho" runat="server">Label</asp:Label>
</form>
</body>
</html>


Jim Cheshire, MCSE, MCSD [MSFT]
ASP.NET Developer Support

This post is provided "as-is" and confers no rights.


--------------------
From: (e-mail address removed) (Damian)
Newsgroups: microsoft.public.dotnet.framework.aspnet
Subject: 'current custom error settings for application prevent details of
Click to expand...
application error from being viewed. '
 
As another possible way to diagnose web.config problems, trying running
the web site though VS.NET using the Start without Debugging (Ctrl-F5)
option. That causes the errors associated with web.config to be
displayed (within the restrictions of remote debugging, of course).

HTH

Bruce Johnson
http://www.ObjectSharp.com/Bruce
 
Bruce,

That's not going to help here. We shouldn't be attempting to attach a
debugger anyway. In this scenario, the user is simply browsing to the
ASP.NET application. If there is something wrong with the ASP.NET worker
process running the app and the app domain loading, you will get this
error. It really isn't related to the web.config file. There's an problem
somewhere else.

Jim Cheshire, MCSE, MCSD [MSFT]
Microsoft Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: BruceJohnson <[email protected]>
References: <[email protected]>
X-Newsreader: AspNNTP 1.50 (ActionJackson.com)
Subject: RE: 'current custom error settings for application prevent
Click to expand...
details of application error from being viewed. '
 
Back
Top