RE: Windows 2000 COM+ Com Surrogate Errors
Brian Muth
>
> We are using VB6 Components through OCX pages running in an ASP.NET
> 2.0
> enviornment.
What are OCX pages? I'm not familiar with this term. Do you mean that the
VB6 components are actuall full-fledged ActiveX controls with the *.ocx
extension? The reason I'm asking is that full ActiveX controls have
interfaces that cannot be marshaled, and therefore should not be registered
as COM+ objects (which obviously require marshaling).
Perhaps you can clarify your terminology.
> It also seems that the issues started to surface around
> the time
> of the upgrade from .NET 1.1 to .NET 2.0,
I'm lost here. What does .NET have to do with VB6 or Component Services?
Regards,
Brian
Brian Muth
"Jody Greening" <jodygr...@gmail.com> wrote in message news:1186672028.2...@o61g2000hsh.googlegroups.com...
> We are experiencing a significant problem surrounding COM+ on our
> clients
> productions servers. We have been investigating this for quite some
> time now,
> and answers are few and far between.
>
> We are using VB6 Components through OCX pages running in an ASP.NET
> 2.0
> enviornment.
What are OCX pages? I'm not familiar with this term.
Do you mean, perhaps, that the VB6 components are actually full ActiveX controls with the *.ocx extension? If so, I hope you
appreciate that these are technically disallowed as COM+ objects, since full ActiveX controls are meant to be hosted by a full
ActiveX container, and the DLLHOST.exe is not one of these.
Perhaps you can clarify your terminology.
It also seems that the issues started to surface around
> the time
> of the upgrade from .NET 1.1 to .NET 2.0, have done some searching,
> but no
> concrete answers or solutions, any thoughts?
I'm lost. Where does .NET come in to play? What does this have to do with Component Services?
Brian
Brian Muth
"Jody Greening" <jodygr...@gmail.com> wrote in message news:1186672028.2...@o61g2000hsh.googlegroups.com...
> We are experiencing a significant problem surrounding COM+ on our
> clients
> productions servers. We have been investigating this for quite some
> time now,
> and answers are few and far between.
>
> We are using VB6 Components through OCX pages running in an ASP.NET
> 2.0
> enviornment.
I'm a but confused. What is an OCX page? Do you mean the VB6 Component is an *.ocx file (implying that it is a full ActiveX control
rather than a simple COM component)? The reason I ask is because full ActiveX controls require a proper container and should never
be registered in COM+.
It also seems that the issues started to surface around
> the time
> of the upgrade from .NET 1.1 to .NET 2.0, have done some searching,
> but no
> concrete answers or solutions, any thoughts?
Where does .NET come in to play?
>
> We cannot seem to get a valid dump from the machines either, and this
> adds
> to the frustration with this problem.
>
> There are some COM+ Rollup Packages available have these solved the
> issues
> for anybody here? And how can we access these items as quickly as
> possible?
>
> Here are examples of the errors:
>
> Event Type: Error
> Event Source: COM+
> Event Category: SVC
> Event ID: 4097
> Date: 8/8/2007
> Time: 3:47:44 PM
> User: N/A
> Computer: NAUSTNA-SRV019
> Description:
> The run-time environment has detected an inconsistency in its
> internal
> state. Please contact Microsoft Product Support Services to report
> this
> error. *** Error in __FILE__(926): Application image dump failed.
> C:\WINNT\system32\com\dmp\{46ECC084-83B1-4A1A-B851-
> C2516315C0A5}_2007_08_08_15_47_44.dmp
>
>
> Event Type: Error
> Event Source: COM+
> Event Category: SVC
> Event ID: 4194
> Date: 8/8/2007
> Time: 3:47:44 PM
> User: N/A
> Computer: NAUSTNA-SRV019
> Description:
> The system has called a custom component and that component has failed
> and
> generated an exception. This indicates a problem with the custom
> component.
> Notify the developer of this component that a failure has occurred
> and
> provide them with the information below.
> Component Prog ID:
> Server Application ID: {46ECC084-83B1-4A1A-B851-C2516315C0A5}
> Server Application Name: Nexterna Clearview
> The serious nature of this error has caused the process to terminate.
> Exception: C0000005
> Address: 0x1001011F
> Call Stack:
> FPWebCommonServicesWin2000 + 0x1011F
>
Jody Greening
> questions....
>
> "Jody Greening" <jodygreen...@gmail.com> wrote in messagenews:1186672028.2...@o61g2000hsh.googlegroups.com...
>
> - Show quoted text -
Sorry for the confusion.
They are aspx pages that simply render the OCX to the browser with
Javascript.
Example:
function embedactivexcontrol(FPClientOCX,strOCXGUIDVal,strCABNameVal)
{
document.write('<OBJECT width="100%" height="100%" id=FPClientOCX
classid="clsid:');
document.write(strOCXGUIDVal);
document.write('" CODEBASE="../../CABs/');
document.write(strCABNameVal);
document.write('" onresize="return window_onresize();" </
OBJECT>');
}
The page also does some more asp.net work (dynamically writing js and
some html code) but there is no great asp processing going on here.
We also have another communication site (just a sub site) that
instantiates com object in tradition asp (old old asp) for use in the
request processing. Could there be a problem here with recent updates/
service packs.
We just started noticing the problems after upgrading the machine
to .NET 2.0, that is why I mentioned it.
Thanks.
Brian Muth
>
> They are aspx pages that simply render the OCX to the browser with
> Javascript.
>
> Example:
>
> function embedactivexcontrol(FPClientOCX,strOCXGUIDVal,strCABNameVal)
> {
> document.write('<OBJECT width="100%" height="100%" id=FPClientOCX
> classid="clsid:');
> document.write(strOCXGUIDVal);
> document.write('" CODEBASE="../../CABs/');
> document.write(strCABNameVal);
> document.write('" onresize="return window_onresize();" </
> OBJECT>');
> }
>
> The page also does some more asp.net work (dynamically writing js and
> some html code) but there is no great asp processing going on here.
>
> We also have another communication site (just a sub site) that
> instantiates com object in tradition asp (old old asp) for use in the
> request processing. Could there be a problem here with recent updates/
> service packs.
>
Thanks for the clarification.
I doubt .NET 2.0 is playing a role here. Ultimately what is generated is html code with embedded Javascript.
The error example you gave shows an Exception code of 0xC0000005, which is a memory access violation. This strongly suggests a bug
in your COM+ application. There isn't much more to comment on since you haven't provided much other information.
You have some debugging to do. Is the error(s) reproducible?
Regards,
Brian
Jody Greening
+ that would cause these memory problems. We did not see any of this
until we upgraded to .NET 2.0.
One other aspect that I didnt mention (but we are having indicators
pointing towards this as well) is that we have an "intergration" app
that is basically a traditional ASP page that uses WSH files
(VBScript) that instantiates COM+ (VB6) objects during processing. Is
there anything that stands out here as a problem with a .NET2 upgrade?
Thanks,
Jody
> Brian- Hide quoted text -
Brian Muth
"Jody Greening" <jodygr...@gmail.com> wrote in message news:1187719721....@22g2000hsm.googlegroups.com...
> Do you think that there could be anything happening between IIS and COM
> + that would cause these memory problems. We did not see any of this
> until we upgraded to .NET 2.0.
If you are using ASP.NET anywhere, you need to check if the web site is using ASP.NET 1.1 or ASP.NET 2.0. That's the only think I
can think of.
>
> One other aspect that I didnt mention (but we are having indicators
> pointing towards this as well) is that we have an "intergration" app
> that is basically a traditional ASP page that uses WSH files
> (VBScript) that instantiates COM+ (VB6) objects during processing. Is
> there anything that stands out here as a problem with a .NET2 upgrade?
No, this has nothing to do with .NET whatsoever.
You haven't answered my earlier questions... is this reproducible? Have you tried to do any debugging on your component at all?
Brian