Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hosting company "Server Error" message 1

Status
Not open for further replies.

miteetall

Programmer
Jul 1, 2003
21
US
I am trying to display a simple set of ASP.NET pages at a well-know hosting company. I am working with them to have the ability to host domains from the root (works OK) and also from subfolders that are configured as application folders. The pages display from the root just fine as well as on my local server. But when I move those same pages to a sub folder, regardless if the folder is setup as an application folder, I get the error message below. Any assistance is greatly appreciated!

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>
 
As suggested in the message, try temporarily turning the customErrors "mode" attribute to "Off". Access the page, get the real error, then change it back to "RemoteOnly" or "On".

You can also enable tracing and write to the trace (checking trace.axd at some point) or try having the Global.asax page e-mail error messages to you or something.
 
Thanks for the tip, BoulderBum. I hadn't bothered to edit the web.config file - pretty elementary. When I did, I found that the only way to get the web.config file read was to place it in the root, a couple levels above where the pages are being hosted. So it looks like I still don't have the application root at the folder level where the pages actually reside. This is something the hosting service should have working.

The company states in their FAQs that they allow pointing domains at subfolders, and someone has to be doing this.

Thanks again for your assistance!


Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'test.default'.

Source Error:

Line 1: <%@ Page language="c#" Codebehind="default.aspx.cs" AutoEventWireup="false" Inherits="test.default" %>
Line 2: <!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN" >
Line 3: <html>

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top