WEB CONFIG DRIVING ME CRAZY

USING ASP.NET EXPRESS BETA 2.O
EVERYTHING IS FINE EXCEPT - STILL TRYING TO VIEW PAGES REMOTELY. I GOT FREE HOSTING SERVICES FROM A 2.0 HOSTER, USING A BETA SERVER. WHEN I VEW PAGES LOCALLY, EVERYTHING IS GOOD.. BUT WHEN I VIEW THE ONE IN THE HOST SERVER - RESULTS TO 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>

PLEASE HELP..
have you tried to actually follow the directions that it gives you (setting the mode to "Off") so that you can have the server tell you whatsreally the matter?

yes i have..
i've tried every way i could think of - Off, On, Remoteonly etc.
am i missing something??
i didn't have the same problem with .net 1.1
please advise.
here is a portion of my web.config
<system.web>
<compilation debug="False" />
<authentication mode="Windows" />

<customeErrors mode ="Off"/>

</system.web>
</configuration>

Hello.
Well, I think that you can always handle the error on your global.asax file or, even better, you can configure your app so that it uses the health monitoring api to send you an email with info about the error you're facing (this last option wouldn't need any coding).
Try changing "<customeErrors mode ="Off"/>" to "<customErrors mode ="Off"/>"