Calling a COM object inside ASP using 100% CPU

[mdon1]

Hi everybody,

I am calling a COM object inside of ASP using the CreateObject method. This particular COM+ dll is something that was written by someone else (Freely available API COM interfaces).

Well the first time the ASP runs, it is fine, the 2nd time through, the server uses up 100% CPU, and the ASP page doesnt' go through ( I am assuming the CreateObject caused this).
the dllhost.exe is hogging all the CPU . I am running of Windows 2000 Server with sp 2.

Any ideas why this would happen.

I tried calling the same object from a regular VBA in Excel it is fine, have no problems with CPU etc.

Thanks for your help

 

[neillovell]

Could it be that the com object's reference is not being released?

Could it be that a server side object is doing something?

 

[mdon1]

Well here is the situation, I am explicitly destroying the object by obj = Nothing in the VBscript,

Since the COM object is a 3rd party object, I am not sure what is happening to it in the inside.

And I can see that the dllhost.exe hits the 99% CPU usage just when I am doing the login into the server object and not when the object gets created .

e.g
set obj = CreateObject("Application.Server&quot
obj.Login "Servername", "user", "pwd" --> the 2nd time through this is causing the overhead usage.

Unfortunately the 3rd party COM object doesn't have a Logout method.