Re: Getting: COM object that has been separated from its underlying RCW can not be used.
From: Tom Shelton (tom_at_mtogden.com)
Date: 04/05/04
- Next message: Tom Shelton: "Re: Retrieving unmanaged DLL data attributes from .NET?"
- Previous message: Pascal Cloup: "Re: passing buffer to unmanaged dll function"
- In reply to: Steen Tøttrup: "Getting: COM object that has been separated from its underlying RCW can not be used."
- Next in thread: Steen Tøttrup: "Re: Getting: COM object that has been separated from its underlying RCW can not be used."
- Reply: Steen Tøttrup: "Re: Getting: COM object that has been separated from its underlying RCW can not be used."
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 05 Apr 2004 02:04:44 -0700
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: Tom Shelton: "Re: Retrieving unmanaged DLL data attributes from .NET?"
- Previous message: Pascal Cloup: "Re: passing buffer to unmanaged dll function"
- In reply to: Steen Tøttrup: "Getting: COM object that has been separated from its underlying RCW can not be used."
- Next in thread: Steen Tøttrup: "Re: Getting: COM object that has been separated from its underlying RCW can not be used."
- Reply: Steen Tøttrup: "Re: Getting: COM object that has been separated from its underlying RCW can not be used."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|