I get this problem and cant sort it.. i have read a number of threads
which all seem to point to the fact that it does work..

However, i am connecting to a remote SQL Server and the webserver is
also remote. I cannot debug either.

I have read that i might need debugging permissions on the web server?
Is this the case? The Server OS is windows 2003 so i presume its
running IIS.

The server is in the same office so i should be able to get access to
it.

the error message is as follows:

--------------------------------------------------------------------------------
Server Error in '/myWebApp' 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>

--------------------------------------------------------------------------------

Any help would be much appreciated.

Re: Setting <customErrors mode="Off"> by Ben

Ben
Tue Jul 20 09:32:57 CDT 2004

You're actually not seeing the underlying error because you are accessing
the web page from a remote machine. Your web.config will have the
<customErrors> setting which should be set to "Off" if you want to see the
detailed error message from a remote machine. The other option is to set
<customErrors mode="RemoteOnly"> and then connect to the website while on
the webserver itself.

Ben Lucas
Lead Developer
Solien Technology, Inc.
www.solien.com

"Winshent" <winshent-google@yahoo.co.uk> wrote in message
news:f511cd36.0407200612.287f5470@posting.google.com...
> I get this problem and cant sort it.. i have read a number of threads
> which all seem to point to the fact that it does work..
>
> However, i am connecting to a remote SQL Server and the webserver is
> also remote. I cannot debug either.
>
> I have read that i might need debugging permissions on the web server?
> Is this the case? The Server OS is windows 2003 so i presume its
> running IIS.
>
> The server is in the same office so i should be able to get access to
> it.
>
> the error message is as follows:
>
> --------------------------------------------------------------------------
------
> Server Error in '/myWebApp' 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>
>
> --------------------------------------------------------------------------
------
>
> Any help would be much appreciated.