Re: Getting: COM object that has been separated from its underlying RCW can not be used.
From: Steen Tøttrup (never_at_mind.com)
Date: 04/05/04
- Next message: Anders Eriksson: "Re: Newbie question"
- Previous message: Ying-Shen Yu[MSFT]: "RE: Calling .Net DLL from Delphi/VB6"
- In reply to: Tom Shelton: "Re: Getting: COM object that has been separated from its underlying RCW can not be used."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 5 Apr 2004 11:30:09 +0200
It's running on a Windows 2003 Server, fully patched, so I'm guessing it's
1.1 ..!?
TIA, best regards,
Steen
"Tom Shelton" <tom@mtogden.com> wrote in message
news:efSmK0uGEHA.3360@TK2MSFTNGP12.phx.gbl...
> On 2004-04-05, Steen Tøttrup <never@mind.com> wrote:
> >
> > I'm working with System.Management (my guess is that it is using InterOp
to
> > use the "old" WMI classes), and suddently I start getting this error:
> >
> > COM object that has been separated from its underlying RCW can not be
used.
> >
> > Why is that?? The methods that fail are called from a windows service.
> >
> > TIA, best regards,
> > Steen
>
> What version of the runtime? I think in 1.0, if you didn't access an
> object for a certain period of time, the object would be released and
> you would get this error... I think that was fixed in 1.1.
>
> --
> Tom Shelton [MVP]
> Powered By Gentoo Linux 1.4
> If you put it off long enough, it might go away.
- Next message: Anders Eriksson: "Re: Newbie question"
- Previous message: Ying-Shen Yu[MSFT]: "RE: Calling .Net DLL from Delphi/VB6"
- In reply to: Tom Shelton: "Re: Getting: COM object that has been separated from its underlying RCW can not be used."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|