I have created a ASP.NET application in Visual Studio.

This works locally without any problems at all.

I uploaded to my web host and emailed them to activate the ASP.NET on that folder. But the site does not work. When I visit it I get this message.

Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

My host support tells me that my web.config file is at fault.

As I say it works fine on my IIS in XP Pro. If it works there surely it should work with my webhost?

did you upload the web.config file that works on your local site?

The files on the website and the files on my local host are exactly the same.

Can anyone help on this issue.

My host tells me

..... there is now a scripting issue with the 'web.config' file in your filespace.

However it works fine on my local IIS testing server.

My host also say

..... this is occuring because the [file path] needs to be created as a subdomain.

I questioned this and was told

..... creating a subdomain creates a 'Virtual Directory' on the server

Anyway I tried and it still does not work

When I visit the site via the subdomain I get this error

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 tried makeing the changes the error message tells me and it makes no differance at all.


When I visit the site at the normal URL I get this message

Server Application Unavailable 
The web application you are attempting to access on this web server is currently unavailable.  Please hit the "Refresh" button in your web browser to retry your request. 

Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

It's not an ASP.NET error, it's not a web.config error, it's nothing at all like that. It's an IIS configuration error. Your host didn't do a good job.

You absolutely do not need to put this on a sub domain. They said using a subdomain forces them to create a new virtual folder, and that's the answer. They need to create a new virtual folder. If a subdomain is one way to do this (and that's news to me) it's not at all the only way. Another is to go into IIS, and select Create New Virtual Folder. That's what they need to do. There are no code changes you can make to make this happen, because the problem comes up before your code gets a chance to run.

The <customErrors> section of web.config tells IIS whether to send a default error message, a custom page, or a stack trace down to the client. What's been suggested is to do the last option I just mentioned, which is a form of debugging, but nothing else, and it's also a security breach.

Thanks for your reply - I have emailed them again.