Re: asp application problem.

["Jim Markley" <jimmarkley () dallasmeetingmanagement com>]

Greetings,

    In addition to Dennis Hurst's comments, I have also seen dllhost.exe
hungup when I am initially prototyping an application and have made one of
the following errors:
    (1) Attempt to access a table not in the current database connection.
    (2) Query a table with an incorrect SQL statement, either with a syntax
error or with an invalid field name within the table.

Jim

----- Original Message -----
From: "Dennis Hurst" <dhurst () spidynamics com>
To: <ssgill () gilltechnologies com>; <webappsec () securityfocus com>
Sent: Friday, March 07, 2003 1:06 PM
Subject: RE: asp application problem.


> Gill,
>
> I have seen this happen if you have a database connection that does not
> get closed.  It will typically look something like this:
>
> Set rs = oConnection.Execute("Select * from myTable")
> Do until rs.eof
> ' do something here
> rs.movenext
> Loop
>
> '
> ' Here is what they probably are not doing that should be done
> '
> rs.close
> Set rs = nothing
> oConnection.Close
> Set oConnection = nothing
>
>
> As a rule you should explicitly close any opened recordsets and set any
> COM object you create to nothing when you are finished with them.  This
> is true for ADO COM objects as well as any other COM objects.
>
> I don't know if you have a virus but I do know that the error shown
> above will cause what you are describing.
>
> Have a great day,
>
> Dennis Hurst
> SPI Labs
>
>
>
> -----Original Message-----
> From: Sarbjit Singh Gill [mailto:ssgill () gilltechnologies com]
> Sent: Friday, March 07, 2003 12:32 PM
> To: webappsec () securityfocus com
> Subject: asp application problem.
>
>
> Greetings folks,
>
> I have a problem with a ASP classic application on W2k.
>
> After a day, the application gets hang. On the task manager, we could
> see
> three dllhost.exe. The third one is the problem. One dllhost.exe will be
> running under System. The second will be IWAM_<computername> and the
> third
> will also be IWAM_<computername>.
>
>  ON doing "end process" on the IWAM_<computername> dllhost.exe process,
> the
> application starts working fine. This happens
>  once in a day. One a heavy load day, it happens a couple of times.
> Every
> time after removing the IWAM_ related dllhost.exe and application starts
> working fine.
>
> There is  a SQL server(on the same box as IIS) in this application(IIS5,
> SQL2000, asp classic). Could this be a virus. I have been told that the
> Slammer affects the win32.dll(my guess) and/or dllhost.exe. When ever i
> am
> removing(killing process from Task Manager) the third hostdll and our
> application works fine.
>
> I am more confused and i do not where to start to trouble shoot.
>
> Could it be my IIS config? or Active X dll managment in my application.
> I
> have checked the dll. They are ok coding wise.
>
> Cheers
> Gill