Server Error in '/' Application.

Discussion in 'ASP .Net Security' started by MSH, Oct 25, 2009.

  1. MSH

    MSH Guest

    wha is this?
    ----
    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>
    ---
     
    MSH, Oct 25, 2009
    #1
    1. Advertisements

  2. On Oct 25, 10:42 pm, "MSH" <> wrote:
    > wha is this?
    > ----
    > 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>
    > ---


    By default, ASP.NET error message hides details about errors. Go to
    the Web.config file and find customErrors section inside <System.web>.
    By default, this section has

    <customErrors mode="RemoteOnly" />

    Change it to

    <customErrors mode="Off" />

    This should help you to see the detailed error message when error
    occurs again.

    You can also go to Event Log to see what was wrong.
     
    Alexey Smirnov, Oct 26, 2009
    #2
    1. Advertisements

  3. MSH

    lexa_klassik Guest

    "MSH" wrote:

    > wha is this?
    > ----
    > 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>
    > ---
    >
    >
    > .
    >
     
    lexa_klassik, Aug 16, 2010
    #3
    1. Advertisements

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

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Ketul Patel
    Replies:
    1
    Views:
    895
    Alvin Bruney
    Nov 29, 2003
  2. Damian
    Replies:
    3
    Views:
    13,083
    Jim Cheshire [MSFT]
    Dec 30, 2003
  3. Kevin Farless
    Replies:
    13
    Views:
    16,174
    chesterchass
    Oct 3, 2007
  4. Krunom Ancini
    Replies:
    2
    Views:
    5,434
  5. -
    Replies:
    2
    Views:
    715
    Alan Krueger
    Jul 29, 2005
  6. David Lozzi
    Replies:
    4
    Views:
    855
    David Lozzi
    Jul 21, 2006
  7. hutty
    Replies:
    1
    Views:
    781
    hutty
    Sep 11, 2006
  8. ton
    Replies:
    3
    Views:
    804
    Sean Chambers
    Sep 18, 2006
Loading...