p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

asp_components thread: Calling a vb DLL from an ASP Page hangs IIS


Message #1 by "=?iso-8859-1?B?QUpBWK4=?=" <ajax@i...> on Fri, 14 Jun 2002 10:09:57 +0530
Hi folks,

Done a lot of stuff in VB. But pretty new to ASP. I have written a COM
component in VB and im trying to use the same in an ASP page. I find that
IIS crashes after a while. This behaviour however is not consistent. Looked
up and found this on MS

Q264957 BUG: VB DLL Has Memory Leaks and Crashes in COM+ if 'Retain In
Memory' Not Set

"The Visual Basic runtime behaves differently based on whether the
Unattended Execution and Retain in Memory options are selected. When these
options are not selected, the Visual Basic runtime unloads custom and
runtime DLLs unexpectedly, which causes the computer to stop responding
(crash or hang) under some multithreaded scenarios. Typical scenarios
include placing the ActiveX DLL in COM+ or Microsoft Transaction Server
(MTS), or calling the ActiveX DLL from ASP pages."


Has anybody encountered any such stuff before, and maybe could shed some
light on it. I have no idea what goes on here.


TIA
ajax®.

PS: Mind you worked fine in PWS


Message #2 by Tai Law <tequilla@C...> on Fri, 14 Jun 2002 09:33:04 -0500
I am sorry that I can't reply through WROX...

I had the same problem, and later, I found out that I used msgbox to 
prompt
err.description in my error handling routines. All of those should be
removed.

-----Original Message-----
From: AJAX=AE [mailto:ajax@i...]
Sent: Thursday, June 13, 2002 11:40 PM
To: ASP components
Subject: [asp_components] Calling a vb DLL from an ASP Page hangs IIS


Hi folks,

Done a lot of stuff in VB. But pretty new to ASP. I have written a COM
component in VB and im trying to use the same in an ASP page. I find 
that
IIS crashes after a while. This behaviour however is not consistent. 
Looked
up and found this on MS

Q264957 BUG: VB DLL Has Memory Leaks and Crashes in COM+ if 'Retain In
Memory' Not Set

"The Visual Basic runtime behaves differently based on whether the
Unattended Execution and Retain in Memory options are selected. When 
these
options are not selected, the Visual Basic runtime unloads custom and
runtime DLLs unexpectedly, which causes the computer to stop responding
(crash or hang) under some multithreaded scenarios. Typical scenarios
include placing the ActiveX DLL in COM+ or Microsoft Transaction Server
(MTS), or calling the ActiveX DLL from ASP pages."


Has anybody encountered any such stuff before, and maybe could shed 
some
light on it. I have no idea what goes on here.


TIA
ajax=AE.

PS: Mind you worked fine in PWS




tequilla@c...
%%email.unsub%%


  Return to Index