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. HTTP 500 Internal Server Error

HTTP 500 Internal Server Error

Scheduled Pinned Locked Moved ASP.NET
helpcsharpasp-netsysadmin
3 Posts 2 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.
  • P Offline
    P Offline
    padvit
    wrote on last edited by
    #1

    My Client ASP.NET Application is working Webservices. Some times it work fine and sometimes it starts giving the above error. Can anyone help me out with this.

    T 1 Reply Last reply
    0
    • P padvit

      My Client ASP.NET Application is working Webservices. Some times it work fine and sometimes it starts giving the above error. Can anyone help me out with this.

      T Offline
      T Offline
      tojamismis
      wrote on last edited by
      #2

      Since this is an unhandled error in your application, I would recommend starting out by writing code into the Application_Error method of the Global.asax. In the Application_Error method, discover what the error is. Write out some diagnostic information to a file, and then the next time the error occurs you can look at the log file to see what happened. Torin Blair
      'In the immortal words of Socrates - "I drank what?".'

      P 1 Reply Last reply
      0
      • T tojamismis

        Since this is an unhandled error in your application, I would recommend starting out by writing code into the Application_Error method of the Global.asax. In the Application_Error method, discover what the error is. Write out some diagnostic information to a file, and then the next time the error occurs you can look at the log file to see what happened. Torin Blair
        'In the immortal words of Socrates - "I drank what?".'

        P Offline
        P Offline
        padvit
        wrote on last edited by
        #3

        HI Than you very much. Anyway I could trace the error. Since Iam using webservices and WSE2.0 settings. The client and server communication is recorded in inputtrace.webinfo and outputtrace.webinfo file. My outputtrace.webinfo size was too much due to which this error was populating

        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