Straight ASP problem

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Joe Coppola
    #1

    Straight ASP problem

    Hi there.

    I am having a weird problem. Currently I have a straight ASP page that
    queries an Access database and returns the large recordset on a page that
    loops through the recordset and writes the appropriate <td> tags in order to
    put the data into a table. Now when I run it in my test environment it runs
    no problem, however when I upload to my ISP I get a iis 500 error. But no
    error on test server.

    A few things: I have noticed that if I decrease the the number of
    Response.Write and rstSearch.Field s("FIeldName" ) code lines that it works
    ok on the ISP server.

    Any ideas?

    Joe


    Tags: None
    • Brian Lowe
      #2
      Re: Straight ASP problem

      Part of the web configuration in IIS is the time allowed for a page to run.
      If it goes beyond say 900 seconds IIS thinks it's hit an error and declares
      a problem.

      Another part of the configuration tells IIS what to do with errors; either
      give an unhelpful 'an error occurred...' message or give full details to
      help the developer figure out what went wrong. In a production environment
      IIS is usually set to give no help to potential hackers.

      It may simply be that having so many response.write lines in your page takes
      too long to process. That would explain why removing some of them fixes the
      problem.

      Suggestions:

      Increase the time-out period by alering the config on your IIS server.

      Decrease the size of the recordset. Maybe use paging?

      Brian Lowe
      ---------@

      "Joe Coppola" <jocojr@hotmail .com> wrote in message
      news:OyBzKycUEH A.3420@TK2MSFTN GP12.phx.gbl...[color=blue]
      > Hi there.
      >
      > I am having a weird problem. Currently I have a straight ASP page that
      > queries an Access database and returns the large recordset on a page that
      > loops through the recordset and writes the appropriate <td> tags in order[/color]
      to[color=blue]
      > put the data into a table. Now when I run it in my test environment it[/color]
      runs[color=blue]
      > no problem, however when I upload to my ISP I get a iis 500 error. But no
      > error on test server.
      >
      > A few things: I have noticed that if I decrease the the number of
      > Response.Write and rstSearch.Field s("FIeldName" ) code lines that it works
      > ok on the ISP server.
      >
      > Any ideas?
      >
      > Joe
      >
      >[/color]


        Comment

        • Joe Coppola
          #3
          Re: Straight ASP problem

          Brian,

          Thanks for the reply. I too thought about the timeout setting, but
          interestingly I changed the timeout setting on my test server to be like 1
          second and I dont get the error, the page just doesnt finish loading
          completely. Note I also set the timeout or ASP pages as well.

          Is there a way to get a more complete error message?

          You are correct the # of response lines is sort of the cause, and I have
          thought of paging the results, however, I need the users to be able to
          export the whole results to another program... any ideas of this?

          Well thanks for the help.

          Joe


          "Brian Lowe" <no@reply.addre ss> wrote in message
          news:%23ZJsgHeU EHA.2580@TK2MSF TNGP12.phx.gbl. ..[color=blue]
          > Part of the web configuration in IIS is the time allowed for a page to[/color]
          run.[color=blue]
          > If it goes beyond say 900 seconds IIS thinks it's hit an error and[/color]
          declares[color=blue]
          > a problem.
          >
          > Another part of the configuration tells IIS what to do with errors; either
          > give an unhelpful 'an error occurred...' message or give full details to
          > help the developer figure out what went wrong. In a production environment
          > IIS is usually set to give no help to potential hackers.
          >
          > It may simply be that having so many response.write lines in your page[/color]
          takes[color=blue]
          > too long to process. That would explain why removing some of them fixes[/color]
          the[color=blue]
          > problem.
          >
          > Suggestions:
          >
          > Increase the time-out period by alering the config on your IIS server.
          >
          > Decrease the size of the recordset. Maybe use paging?
          >
          > Brian Lowe
          > ---------@
          >
          > "Joe Coppola" <jocojr@hotmail .com> wrote in message
          > news:OyBzKycUEH A.3420@TK2MSFTN GP12.phx.gbl...[color=green]
          > > Hi there.
          > >
          > > I am having a weird problem. Currently I have a straight ASP page that
          > > queries an Access database and returns the large recordset on a page[/color][/color]
          that[color=blue][color=green]
          > > loops through the recordset and writes the appropriate <td> tags in[/color][/color]
          order[color=blue]
          > to[color=green]
          > > put the data into a table. Now when I run it in my test environment it[/color]
          > runs[color=green]
          > > no problem, however when I upload to my ISP I get a iis 500 error. But[/color][/color]
          no[color=blue][color=green]
          > > error on test server.
          > >
          > > A few things: I have noticed that if I decrease the the number of
          > > Response.Write and rstSearch.Field s("FIeldName" ) code lines that it[/color][/color]
          works[color=blue][color=green]
          > > ok on the ISP server.
          > >
          > > Any ideas?
          > >
          > > Joe
          > >
          > >[/color]
          >
          >[/color]


            Comment

            Previous template Next
            Working...