K
Kevin Farless
Hi all,
I'm having trouble viewing any .aspx pages on my hosting company's server.
The server is a new box running Windows Server 2003 default installation.
I'm the first client to try using ASP.NET on this box and the administrator
of the server has never setup an ASP.NET site before, so most likely the
problem I'm experiencing is server settings related.
Note in the Web.config below that the <customErrors mode="Off"/> is present,
but is having no affect on the error message the server is producing. What
server settings should I suggest the administrator change?
Thanks in advance, Kevin.
Here is the Web.config file:
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Here is the 'test.aspx' page I'm trying to view:
<%@ Page Language="VB" ContentType="text/html" ResponseEncoding="iso-8859-1"
%>
<html>
<head>
<title>Test ASPNET</title>
</head>
<body>
Test ASPNET
</body>
</html>
This is the error I'm getting:
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>
I'm having trouble viewing any .aspx pages on my hosting company's server.
The server is a new box running Windows Server 2003 default installation.
I'm the first client to try using ASP.NET on this box and the administrator
of the server has never setup an ASP.NET site before, so most likely the
problem I'm experiencing is server settings related.
Note in the Web.config below that the <customErrors mode="Off"/> is present,
but is having no affect on the error message the server is producing. What
server settings should I suggest the administrator change?
Thanks in advance, Kevin.
Here is the Web.config file:
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Here is the 'test.aspx' page I'm trying to view:
<%@ Page Language="VB" ContentType="text/html" ResponseEncoding="iso-8859-1"
%>
<html>
<head>
<title>Test ASPNET</title>
</head>
<body>
Test ASPNET
</body>
</html>
This is the error I'm getting:
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>