Re: Cannot Create New Instance of COM+ Object After You Repeatedly Restart the COM+ Object
- From: "Anthony Jones" <Ant@xxxxxxxxxxxxxxxx>
- Date: Sun, 7 Jan 2007 15:36:29 -0000
"Align1912" <align1912@xxxxxxxxx> wrote in message
news:erE96ehMHHA.1248@xxxxxxxxxxxxxxxxxxxxxxx
I've checked that the server I'm working on has win2k sp4 which had a
fix from microsoft for this problem. However, it seems that I still
have this problem. I'm calling a ocx component from asp and after a
reboot everything works fine for a while and then all of a sudden the
graph component stops responding. Using vbscript i can still call the
component but via asp it doesn't work. Can anyone suggest another
solution. I did look in the event viewer and had a message
The server did not register with dcomm for the iusr account. I checked
and the iusr account was linked to active server 2.0. Please let me
know any ideas on how to solve this. Thank you!
This post is a little ambigous, are you saying you've added an OCX component
to a COM+ server application and are calling it from ASP?
Are you sure the OCX is safe to call in the way? Most OCX are designed to
provide UI elements. Components installed in COM+ application whould be
marked for unattended execution and retained in memory.
.
- References:
- Prev by Date: Cannot Create New Instance of COM+ Object After You Repeatedly Restart the COM+ Object
- Next by Date: Re: CDO Message Problem
- Previous by thread: Cannot Create New Instance of COM+ Object After You Repeatedly Restart the COM+ Object
- Next by thread: Re: Cannot Create New Instance of COM+ Object After You Repeatedly Restart the COM+ Object
- Index(es):
Relevant Pages
|