You may be mixing up the error messages.
The customErrors Attributes are
mode="[On|Off|RemoteOnly]"
On: Always display custom errors
Off: Always display ASP.NET error pages
RemoteOnly: Display custom errors to remote clients
and ASP.NET errors to localhost
defaultRedirect="url" - Url to redirect client to when an error occurs
There's no way you'll get custom error messages,
if you set customErrors to "off", as in
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
That way, you'll only get ASP.NET error messages.
You need to set <customErrors mode ="RemoteOnly"/>
if you only want remote clients to see your custom error
messages.
or
You need to set <customErrors mode ="On"/>
if you want your custom error messages to be
displayed both locally and to remote clients.
Juan T. Llibre
ASP.NET MVP
===========
"Chumley Walrus" <sp*******@yahoo.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...
I'm having trouble seeing my page when I publish it on my live server.
I created a project in VS.net (with MMIT integrated), created a simple
index.aspx mobilewebform page , I can see it in my Mobile Explorer
emulator , but get the following error when trying to look at it from
my remote server, even when changing the CustomErrors mode to Off:
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>
????
chumley
