You might also ask them to move you to a more current server.  My hosting server @godaddy is IIS 7 and supports .NET 1.1, 2.0, 3.5.

I found a bug in my Web.Config file.. and now I am seeing this :
Line 1 is just what Visual Web Developer puts in there.. and I never really gave it a lot of thought.  Anyone out there have a clue?

Server Error in '/' Application.

---

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 '_Default'.

Source Error:

Line 1: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="test.aspx.cs" Inherits="_Default" %> Line 2: Line 3:

Source File: d:\hosting\barrettken\test.aspx    Line: 1

---

Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407

On godaddy (where I have a site as well) you can check IIS settings from the hosting control center.  It will tell you the version of IIS and .NET your hosting server is running.  You can also see there if your directory is setup as an application or not.  Click the edit directory icon (pencil on the right) and see if the Set Application Root box is checked.

I'm using a provider (godaddy), so I don't have access to that info.  I'm using Xcopy to send my web pages to the site.

This does seem odd.  It SHOULD work.. but doesn't.

Very odd.  Can you see the IIS configuration on the server?  Is this setup as an application in IIS?

Please post the section containing the tag from your web.config.  Be sure to include say 5 lines before and 5 lines after the actual tag.  If it's anything like mine (shown below), the tag is commented out.

          COMMENT ENDS

I modified the Web.config file with customErrors mode set to off, and still got the same error message - the same page instructing me to set customErrors mode to off and everything.

The only thing I can think of is that regardless of what they are telling me, I am not running on a windows server running IIS. The provider swears this is not so however.  I constructed a new page using Visual Web Developer 2005 named test.aspx that does nothing. It just shows text saying "Hello". I'll include these files here just for grins and giggles...

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="test.aspx.cs" Inherits="_Default" %>





   


   

   

    Hello
   

   

The code behind file is..

using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

public partial class _Default : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {

    }
}

So you see, nothing is going on there. Yet I still get the error when I call the page from the server.

What a conundrum.

Ken Barrett

go to web.config
set this


then you will receive the .NET exception, what does it say ?

Look closely at the web config.  Did you just modify the existing tag you found there?  If you did, it is likely commented out.

It doesn't give me much. I've made the changes it suggests in my web.config file, and got the same result.

-------

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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "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 configuration tag to point to a custom error page URL.

What's the error message you get?