Web Service & Web.Config

Discussion in 'ASP .Net Web Services' started by Raj, Dec 18, 2009.

  1. Raj

    Raj Guest

    I have created a web service using .NET framework 2.0

    after uploading and trying to access 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 -->

    <customErrors mode="Off"/>

    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 -->

    <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>

    My Web.Config is:
    <?xml version="1.0"?>
    Set compilation debug="true" to insert debugging
    symbols into the compiled page. Because this
    affects performance, set this value to true only
    during development.
    <compilation debug="true">
    The <authentication> section enables configuration
    of the security authentication mode used by
    ASP.NET to identify an incoming user.
    <authentication mode="None"/>
    The <customErrors> section enables configuration
    of what to do if/when an unhandled error occurs
    during the execution of a request. Specifically,
    it enables developers to configure html error pages
    to be displayed in place of a error stack trace.-->
    <customErrors mode="RemoteOnly" defaultRedirect
    <!-- defaultRedirect="WebForm1.aspx">
    <error statusCode="403" redirect="NoAccess.htm" />
    <error statusCode="404" redirect="FileNotFound.htm" />
    <add name="HttpGet"/>
    <add name="HttpPost"/>

    I have tried changing mode to On/Off no respite

    The same is working fine on the local server

    Anything else to be done?

    Any help would be appreciated

    Thank you

    Raj, Dec 18, 2009
    1. Advertisements

  2. Raj

    andyMac Guest

    I am having the same issue. was this resolved? Anyone know a solution to
    andyMac, Feb 15, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.