why 'Server Error in Application' occuring?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • lrg
    New Member
    • Jun 2007
    • 8

    why 'Server Error in Application' occuring?

    I'm encountering this error while attempting to run my application. Not always this error is occuring. Without any change in code itself the same application was running previously.


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

    <configuratio n>
    <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 "defaultRedirec t" attribute of the application's <customErrors > configuration tag to point to a custom error page URL.


    <!-- Web.Config Configuration File -->

    <configuratio n>
    <system.web>
    <customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
    </system.web>
  • nateraaaa
    Recognized Expert Contributor
    • May 2007
    • 664

    #2
    Originally posted by lrg
    I'm encountering this error while attempting to run my application. Not always this error is occuring. Without any change in code itself the same application was running previously.


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

    <configuratio n>
    <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 "defaultRedirec t" attribute of the application's <customErrors > configuration tag to point to a custom error page URL.


    <!-- Web.Config Configuration File -->

    <configuratio n>
    <system.web>
    <customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
    </system.web>
    Was this application moved to a server with different authentication requirements? Have you tried placing a break point in the page load of this application and stepping through the code to see if it fails anywhere?

    Nathan

    Comment

    • TRScheel
      Recognized Expert Contributor
      • Apr 2007
      • 638

      #3
      What nathan said, and allow errors to be shown so you can gather more information about the problem

      Comment

      • Frinavale
        Recognized Expert Expert
        • Oct 2006
        • 9749

        #4
        I don't think that you will be able to place any break points in your application once it has been deployed to a server...debugg ing will be trick.

        However, we need to see a better error message than the one you are getting so I suggest temporarily changing your web.config so that this line:
        [code=xml]<customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>[/code]
        is changed to
        [code=xml]
        <customErrors mode="Off" defaultRedirect ="mycustompage. htm"/>
        [/code]

        Once you make the changes, deploy your website and try to access it again...then post the error message that you get.

        Thanks

        -Frinny

        Comment

        • lrg
          New Member
          • Jun 2007
          • 8

          #5
          Application was moved to server and then error started occurring. In my local machine it was working fine. Is there anything in particular that should be taken care of while moving the application to server to prevent this error? Because i am getting the same error at times for other applications also.

          Comment

          • Frinavale
            Recognized Expert Expert
            • Oct 2006
            • 9749

            #6
            Originally posted by lrg
            Application was moved to server and then error started occurring. In my local machine it was working fine. Is there anything in particular that should be taken care of while moving the application to server to prevent this error? Because i am getting the same error at times for other applications also.
            Did you make the changes to your web.config as suggested earlier?

            Comment

            • Plater
              Recognized Expert Expert
              • Apr 2007
              • 7872

              #7
              Also, please try and get us the actual error message given, as well as any and all related information. (Stack trace and the like). It could be very useful to know what the actual error is.

              Thanks

              Comment

              Working...