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. page cannot be displayed - at sql insertion

page cannot be displayed - at sql insertion

Scheduled Pinned Locked Moved ASP.NET
databasesysadmintoolsquestion
2 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.
  • L Offline
    L Offline
    larbo204
    wrote on last edited by
    #1

    When I run a script that reads from a file and insert into a SqlServer I get "The page cannot be displyed" after approx. 5 minutes. It is 20.000 rows to insert and the script continues to run in the background so the script works and all the rows are inserted. But it's very annoying to get that "The page cannot be displyed"-message 'cause it seems like it would fail. I used Windows 2003 server with IE6, also tried it on Win XP. Any ideas? /larbo

    J 1 Reply Last reply
    0
    • L larbo204

      When I run a script that reads from a file and insert into a SqlServer I get "The page cannot be displyed" after approx. 5 minutes. It is 20.000 rows to insert and the script continues to run in the background so the script works and all the rows are inserted. But it's very annoying to get that "The page cannot be displyed"-message 'cause it seems like it would fail. I used Windows 2003 server with IE6, also tried it on Win XP. Any ideas? /larbo

      J Offline
      J Offline
      Javier Lozano
      wrote on last edited by
      #2

      Your request is timing out from your ASP.NET application. You need to specify a higher timeout. Take a look at the httpRuntime[^] element for your Web.config. In particular, pay close attention to the executionTimeout. ~Javier Lozano (blog)

      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