Web.Config Problem - it wont go away

In some testing I set my web config file to :

<customErrors mode="Off"/>

Worked fine on my machine, but I moved it to a web server and got the 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".

Fine, so I changed the entry back to:

<customErrors mode="RemoteOnly" />

The proplem is when I try to load the program from the web server I get the same error with the message showing the web config file containing:

<customErrors mode="Off"/>

In addition, I get the same error with another program that never had the web config file changed.

This still happens if I delete the offending application directory from the web server.

HELP!!!

Can anyone out there tell me how to get rid of this error?

Can anyone explain how web.config works on the server, or point me to information?

again

HELP!!!

Thanksdid you create an application on the webserver? usually this is done via a control panel (or directly in IIS, but if you are using a host, then you probably would use a control panel)
I created (wrote & tested) the application on my pc.

I moved it to the Web host. I have not found the IIS or it's equivalent on the web host. Don't know what the host is, somewhere in ILL. The only options we have found are to enable asp and to set the .net framework. result is the same with both versions of .net.
usually there is a way to create an application on the host. It really just consists of telling IIS that a given directory (the one your app is in) is a web application.
You could place the application in the root, or look in your control panel for an option that says you can create a new directory. (THis will most likely be a new virtual directory) Just ensure that asp.net is enabled for the root or that directory.

Did you make sure to copy the BIN folder, everything over to the new vd?
Looks like Virtual directories is the answer, Now we are having some problems with the server function vs documentation. but that would be for another post.

Now if I just clicked the right button to log this as resolved.
Threat Tools > Mark this thread resolved...