locked
problem in publish website RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    User-750112863 posted

    Hi guys,

    I just have problem when I published my website. help please

    problem is:

    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.

    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>

    http://www.issue.uodiyala.edu.iq/

    Thanks
    Sunday, December 1, 2013 4:38 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    User-484054684 posted

    Yes, so as it suggests, modify your web.config file to turn OFF the custom errors.

    There would be already system.web section and customErrors mode in the web.config file, most probably. So change the value of mode to Off.

    If the section doesn't exist, add it manually.

    Once you switch off custom errors, you can observe the actual error when you browse the page anywhere out side also.

    If you set the mode to RemoteOnly, then, you can see the actual error when you browse the page on "local server machine"

    <configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

    Please mark this as answer if this answers your question.

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Sunday, December 1, 2013 4:58 AM