Error Code 64: Host not available-when trying to access asp appln

Discussion in 'ASP' started by sareena, Aug 10, 2007.

  1. sareena

    sareena New Member

    Aug 10, 2007
    Likes Received:
    Trophy Points:
    There is a problem with accessing an ASP appln hosted on a dedicated Win '03 load balanced server running IIS 6.0 in worker process isolation mode.
    When the user types in the URl of the appln and hits enter, some times they get a 'Page Cannot be Displayed' error. The details of the error are:
    > The page cannot be displayed
    > Explanation: The Web server connection was closed.

    > Technical Information (for support personnel)
    > * Error Code 64: Host not available
    > * Background: The connection to the Web server was lost.
    When this error happens only restarting the IIS admin services helps. The site then works for a while before it gives the above mentioned error again. This error happens randomly and cannot be simulated on demand. In the DEV server (not load balanced) the error doesn't occur at all. In the Test server this error occurs very often and in the PROD server its's about 1-2 a month. Except for the developmnet server the rest are load balanced.

    When the error occured I checked on the IIS Admin services, the appln logs and the IIS logs. The IIS services are running fine, the appln pool shows as running and the w3wp worker process visible in the task mon. The appln error logs don not show anything wrong. The hhttp error logs too don't show anything when this error occurs. The only error logged there were some 'Connection Abandoned by Appln Pool' errors, but this was not just before the error occured.

    Initially I had thought that it was because of a known memory leak in the appln combined with bad code that was causing the IIS to run out of memory. So I cleaned up the code - released all DB objs by Set conn = Nothing, and set the worker process to recycle every day-yet no effect. Is this an IIS server issue? Or is it an environment issue? If not then what else could be the probable causes? A proxy server/firewall to be blamed here?

    Pls help!!!
  2. pradeep

    pradeep Team Leader

    Apr 4, 2005
    Likes Received:
    Trophy Points:
    Kolkata, India
    Home Page:
    It seems to be a bug in implementation of HTTP1.1. A workaround for this would be turning of HTTP1.1 on the client.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice