Re: "COM+ Internal Error" when trying to instantiate COM object
From: Erik Anderson (erikba_at_teamworkgroup.com)
Date: 04/12/04
- Next message: IISCF5user: "RE: Help with IISDump file"
- Previous message: Peter Johansen: "Restrict use of AMI, ADSI and WScript.Shell"
- In reply to: Andrey P: "Re: "COM+ Internal Error" when trying to instantiate COM object"
- Next in thread: Andrey P: "Re: "COM+ Internal Error" when trying to instantiate COM object"
- Reply: Andrey P: "Re: "COM+ Internal Error" when trying to instantiate COM object"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Apr 2004 16:36:41 -0700
Okay, a couple responses:
(1) I did write a small program that called the COM object on the same
machine as the production server with no errors
(2) The first link is one that I ran across last week, it appears to only be
meaningful if the error message I was getting did NOT specify "IIS
In-Process Applications" as the name of the COM+ object:
"Note You can only turn off or turn on IISintrinsics on COM+ components.
However, if the COM+ application is one of the IIS-generated COM+
applications (for example, IIS In-Process Applications, IIS Out-Of-Process
Pooled Applications, and others), you cannot turn off the IISintrinsics
property in this way. Check the workaround session about how to turn off
IISIntrinsics when you call a COM+ object from an ASP page."
(3) The second link you passed appears to be instructions to re-synchronize
the user accounts in case the passwords became different between the COM+
objects and the main IIS process. I am successfully serving ASP pages that
do not reference this object, so I doubt that this is the case.
...which means that I'm right back at the beginning, unless I majorly missed
something here.
Right now the COM object I am trying to instantiate is an STA object, could
that have anything to do with it?
"Andrey P" <andrey@paramonov.pp.ru> wrote in message
news:107m8j8t6tuhkf3@news.supernews.com...
> Well,
>
> that's the main problem, when a dev server doesn't have the same setup
> as a production one.
>
> Is it possible to prepare yet another server (even using Virtual PC) and
> tune it as close as possible to the production one, left only one IP
> and give it a try...
>
> From my side (hovewer, I'm not a developer) it seems to be an issue
> with the missed dll or something like this....
>
> Please take a look at the following URLs - it seems to describe the same
> problem:
>
> http://forums.devshed.com/archive/t-67827
>
> and
>
> http://www.winnetmag.com/Web/Article/ArticleID/24474/24474.html
>
> -Andrey
>
> Erik Anderson wrote:
>
> > Lol, spent a couple hours googling this error message (and specific
source
> > code line) on both the web and the groups to find no good answer for
what is
> > happening.
> >
> > I'm not sure what COM+ is and how it compares to COM, this is a
> > LocalServer-based COM object that I've written.
> >
> > This is running under Windows 2000, my "iisreset.exe" file has a version
of
> > "5.0.2195.6620"
> >
> > "Andrey P" <andrey@paramonov.pp.ru> wrote in message
> > news:107lmsoe1e7ik12@news.supernews.com...
> >
> >>There's tons of reasons for "0x8000ffff : Catastrophic failure" error. I
> >>would definitely suggest to look up for more help at
> >>http://groups.google.com. I've run into this situation, my os is Win2003
> >>Web edition / IIS6. Any details on OS/IIS verrsions on which the COM+
> >>component is failing ?
> >>
> >>-Andrey.
> >>
> >
> >
> >>Erik Anderson wrote:
> >>
> >>
> >>>I am trying to get a COM object I developed to work within an ASP page.
> >
> > I
> >
> >>>don't have too much experience with COM objects, so I'm trying to keep
> >>>things relatively simple.
> >>>
> >>>Earlier on (several months ago) the project (ATL) was a DLL that seemed
> >
> > to
> >
> >>>work moderately well with IIS (other than apparent issues with
reference
> >>>counting). I have changed it to an EXE (LocalService) for more control
> >
> > over
> >
> >>>the process.
> >>>
> >>>The COM object is running perfectly in my debugging environment. Now,
> >>>however, most times I attempt to access the ASP page result in the
> >
> > following
> >
> >>>error:
> >>>
> >>>---
> >>>COM+ Internal Error. Please contact Microsoft Product Support Services
> >
> > to
> >
> >>>report this error. Assertion Failure:
> >>>hr == S_OK
> >>>Server Application ID: {3D14228C-FBE1-11D0-995D-00C04FD919C1}
> >>>Server Application Name: IIS In-Process Applications
> >>>The serious nature of this error has caused the process to terminate.
> >>>Error Code = 0x8000ffff : Catastrophic failure
> >>>COM+ Services Internals Information:
> >>>File: .\assoc.cpp, Line: 528
> >>>---
> >>>
> >>>I would appreciate it if someone could push me in the direction of
> >
> > figuring
> >
> >>>out what the heck is going on.
> >>>
> >>>I have not been able to determine what this means, other than the fact
> >
> > that
> >
> >>>I'm not the first one to get this error. I have seen some talk about
> >>>marshalling, but this code uses standard types and should be handled by
> >
> > the
> >
> >>>Universal Marshaller.
> >
> >
> >
>
- Next message: IISCF5user: "RE: Help with IISDump file"
- Previous message: Peter Johansen: "Restrict use of AMI, ADSI and WScript.Shell"
- In reply to: Andrey P: "Re: "COM+ Internal Error" when trying to instantiate COM object"
- Next in thread: Andrey P: "Re: "COM+ Internal Error" when trying to instantiate COM object"
- Reply: Andrey P: "Re: "COM+ Internal Error" when trying to instantiate COM object"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
