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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Web Development
  3. ASP.NET
  4. The solution to our ASP.NET page timeout problems...

The solution to our ASP.NET page timeout problems...

Scheduled Pinned Locked Moved ASP.NET
windows-adminhelpcsharpasp-netsysadmin
1 Posts 1 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.
  • A Offline
    A Offline
    AndyBrew70
    wrote on last edited by
    #1

    Hi We have been battling with page timeouts over the last week or to and decided today to get our heads around the problem! The problem has been highlighted by a reporting facility that if used to extract a wide date range can take several minutes to produce the report. We discovered that the browser always displayed the "Internet Explorer cannot display the webpage" message after 63 seconds, firstly we thought this weird because it is the IE error page not a page rendered by ASP.NET 2/IIS 6. So after an age investigating on the net and finding all manner of registry settings that had no effect etc. we set up a test app that simply sleeps our test page for 5 minutes we then managed to deduce that the only setting of consequence was the attribute of executionTimeout which did within reason do exactly as we thought that is displayed the ASP.NET script timeout error. However, once the executionTimeout value exceeded 63 seconds we then received the IE page "Internet Explorer cannot display the webpage" and this behaviour was replicated in some form in Firefox, Opera and Safari! So next we tried running the same page via a remote desktop connection on our server, and guess what, it worked perfectly we then tried from another remote computer using a different ISP and that worked also! Hence we deduced from all this that the problem lies with AVG and after further investigation specifically AVG 8 Web Shield disable this little monster and all works fine. Hope that helps somebody somewhere because it has been causing us sleepless nights for weeks! Andy

    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