ASP.NET web app works on some, not all, workstations

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • =?Utf-8?B?SkdASEc=?=

    #1

    ASP.NET web app works on some, not all, workstations

    I have a client that has contracted with a bank to process checks over the
    Internet. The solution includes a check scanner and APS.NET web application.

    The application does not work for all workstations at the client site.
    There are two laptop computers than can run the web application and all it's
    functions w/o failure. They have been able to do this from day one w/o
    modification.

    No other PC workstations can run all of the web application functions. Some
    page return an 'Internal Server Error' message. The page displayed is a
    custom error page with no other details.

    For some reason the owners of the web application have no clue why their
    application will work for some, but not others.

    Some facts:
    All workstations are XP SP2
    There is a mix of IE6 and 7 but this does not seem to be an issue because
    each laptop has a different version (1 has IE7, the other has IE6).
    Application will not allow browsers other than IE5.5 or higher (Firefox is
    out)
    The application requires an ActiveX control to interface with the scanner.
    Check scanning is not an issue.

    I have tried the following:
    Disabling local Windows Firewall, Defender, AV
    Running as local administrator

    Has anyone seen something like this before?


  • Eliyahu Goldin

    #2
    Re: ASP.NET web app works on some, not all, workstations

    I have a scanning application that used to give me odd errors on posting
    scanned images. The culprit was the browser who would take a cached version
    of one of the pages instead of going for it to the server.

    Start from finding out what server error causes the 'Internal Server Error'.
    For that, you may need to ask the developers to provide better error
    reporting or at least put the exception messages into the http response.
    With that, you can use an http analyzer tool to see the errors. You can also
    look in the server's http logs but they are not always helpful.

    --
    Eliyahu Goldin,
    Software Developer
    Microsoft MVP [ASP.NET]




    "JG@HG" <JGHG@discussio ns.microsoft.co mwrote in message
    news:3868CA53-0EA8-4A0D-B76E-F3C77C6603D0@mi crosoft.com...
    >I have a client that has contracted with a bank to process checks over the
    Internet. The solution includes a check scanner and APS.NET web
    application.
    >
    The application does not work for all workstations at the client site.
    There are two laptop computers than can run the web application and all
    it's
    functions w/o failure. They have been able to do this from day one w/o
    modification.
    >
    No other PC workstations can run all of the web application functions.
    Some
    page return an 'Internal Server Error' message. The page displayed is a
    custom error page with no other details.
    >
    For some reason the owners of the web application have no clue why their
    application will work for some, but not others.
    >
    Some facts:
    All workstations are XP SP2
    There is a mix of IE6 and 7 but this does not seem to be an issue because
    each laptop has a different version (1 has IE7, the other has IE6).
    Application will not allow browsers other than IE5.5 or higher (Firefox is
    out)
    The application requires an ActiveX control to interface with the scanner.
    Check scanning is not an issue.
    >
    I have tried the following:
    Disabling local Windows Firewall, Defender, AV
    Running as local administrator
    >
    Has anyone seen something like this before?
    >
    >

    Comment

    • =?Utf-8?B?SkdASEc=?=

      #3
      Re: ASP.NET web app works on some, not all, workstations

      I'm going down that route as well. The challenge is that the bank does not
      own the web app. I recently found out they have outsourced this piece. They
      are working with that vendor at this time.

      As for the cached scenario: My client claims they just tested the web
      application on a brand new workstation that had never navigated to the site
      before and still got the failure. Since I have not seen this test (plus it
      was performed by an end user) I'm taking their results with a grain of salt
      at this time. I will have someone a bit more technical than the receptionist
      test before I come to any conclusions.

      Thanks for the input!

      "Eliyahu Goldin" wrote:
      I have a scanning application that used to give me odd errors on posting
      scanned images. The culprit was the browser who would take a cached version
      of one of the pages instead of going for it to the server.
      >
      Start from finding out what server error causes the 'Internal Server Error'.
      For that, you may need to ask the developers to provide better error
      reporting or at least put the exception messages into the http response.
      With that, you can use an http analyzer tool to see the errors. You can also
      look in the server's http logs but they are not always helpful.
      >
      --
      Eliyahu Goldin,
      Software Developer
      Microsoft MVP [ASP.NET]


      >
      >
      "JG@HG" <JGHG@discussio ns.microsoft.co mwrote in message
      news:3868CA53-0EA8-4A0D-B76E-F3C77C6603D0@mi crosoft.com...
      I have a client that has contracted with a bank to process checks over the
      Internet. The solution includes a check scanner and APS.NET web
      application.

      The application does not work for all workstations at the client site.
      There are two laptop computers than can run the web application and all
      it's
      functions w/o failure. They have been able to do this from day one w/o
      modification.

      No other PC workstations can run all of the web application functions.
      Some
      page return an 'Internal Server Error' message. The page displayed is a
      custom error page with no other details.

      For some reason the owners of the web application have no clue why their
      application will work for some, but not others.

      Some facts:
      All workstations are XP SP2
      There is a mix of IE6 and 7 but this does not seem to be an issue because
      each laptop has a different version (1 has IE7, the other has IE6).
      Application will not allow browsers other than IE5.5 or higher (Firefox is
      out)
      The application requires an ActiveX control to interface with the scanner.
      Check scanning is not an issue.

      I have tried the following:
      Disabling local Windows Firewall, Defender, AV
      Running as local administrator

      Has anyone seen something like this before?
      >
      >
      >

      Comment

      Working...