Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. error when running in server

error when running in server

Scheduled Pinned Locked Moved ASP.NET
helpjavascriptsysadminsecurityquestion
8 Posts 5 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Subin Mavunkal
    wrote on last edited by
    #1

    Hi , Please help me.I used a javascript method to run my aspx page for edit.It is working fine in my local machine .But when the build is up on the server , it is showing error and we are totally unable to go to that page.Here is the javascript I used. var id=param.id; var url="EditUserDetail.aspx?id="+id; //window.location=url; window.open(url,"_blank","toolbar=no, location=yes, directories=no, status=no, menubar=no, scrollbars=no, resizable=no, copyhistory=yes, width=850, height=500"); and the error showing when it run in the server is , 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". With warm regards

    N A 2 Replies Last reply
    0
    • S Subin Mavunkal

      Hi , Please help me.I used a javascript method to run my aspx page for edit.It is working fine in my local machine .But when the build is up on the server , it is showing error and we are totally unable to go to that page.Here is the javascript I used. var id=param.id; var url="EditUserDetail.aspx?id="+id; //window.location=url; window.open(url,"_blank","toolbar=no, location=yes, directories=no, status=no, menubar=no, scrollbars=no, resizable=no, copyhistory=yes, width=850, height=500"); and the error showing when it run in the server is , 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". With warm regards

      A Offline
      A Offline
      Abhijit Jana
      wrote on last edited by
      #2

      Subin Mavunkal wrote:

      Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

      You can enable the same to check what actually happening over there. I guess the may be some problem in EditUserDetail.aspx page

      Abhijit Jana | Codeproject MVP Web Site : abhijitjana.net Don't forget to click "Good Answer" on the post(s) that helped you.

      1 Reply Last reply
      0
      • S Subin Mavunkal

        Hi , Please help me.I used a javascript method to run my aspx page for edit.It is working fine in my local machine .But when the build is up on the server , it is showing error and we are totally unable to go to that page.Here is the javascript I used. var id=param.id; var url="EditUserDetail.aspx?id="+id; //window.location=url; window.open(url,"_blank","toolbar=no, location=yes, directories=no, status=no, menubar=no, scrollbars=no, resizable=no, copyhistory=yes, width=850, height=500"); and the error showing when it run in the server is , 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". With warm regards

        N Offline
        N Offline
        Nishant Singh
        wrote on last edited by
        #3

        There seems to be an error is occuring when the page loads , do you have any kind of Error Log for your application ? If any error log is there then you can get what exactly is the error . or change the web config as directed and then check Nish

        L 1 Reply Last reply
        0
        • N Nishant Singh

          There seems to be an error is occuring when the page loads , do you have any kind of Error Log for your application ? If any error log is there then you can get what exactly is the error . or change the web config as directed and then check Nish

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          Hi, Try adding this in configuration

          L 1 Reply Last reply
          0
          • L Lost User

            Hi, Try adding this in configuration

            L Offline
            L Offline
            Lost User
            wrote on last edited by
            #5

            <customErrors mode="Off"> </customErrors>

            S 1 Reply Last reply
            0
            • L Lost User

              <customErrors mode="Off"> </customErrors>

              S Offline
              S Offline
              Subin Mavunkal
              wrote on last edited by
              #6

              thank you brothers , I tried <customErrors mode="Off"> </customErrors> this in server and I got the exception on page.It was the problem with DB mismatching Thanks a ton

              A D 2 Replies Last reply
              0
              • S Subin Mavunkal

                thank you brothers , I tried <customErrors mode="Off"> </customErrors> this in server and I got the exception on page.It was the problem with DB mismatching Thanks a ton

                A Offline
                A Offline
                Abhijit Jana
                wrote on last edited by
                #7

                Yes. That's why we suggested you to enable to custom error mode so that you can easily get the stackTrace Details. :thumbsup:

                Abhijit Jana | Codeproject MVP Web Site : abhijitjana.net Don't forget to click "Good Answer" on the post(s) that helped you.

                1 Reply Last reply
                0
                • S Subin Mavunkal

                  thank you brothers , I tried <customErrors mode="Off"> </customErrors> this in server and I got the exception on page.It was the problem with DB mismatching Thanks a ton

                  D Offline
                  D Offline
                  Dinesh Mani
                  wrote on last edited by
                  #8

                  Make sure either remove it or set it to <customErrors mode="RemoteOnly"></customErrors> so that your users don't see the error details. Further better you can redirect your users to a error page like so <customErrors defaultRedirect="Your Error Page" mode="RemoteOnly"></customErrors>

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • World
                  • Users
                  • Groups