Re: Remoting Error....Clarification, please help

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Jason Schneekloth (JasonSchneekloth_at_discussions.microsoft.com)
Date: 11/03/04 

Date: Wed, 3 Nov 2004 14:34:12 -0800

To answer question 1....
yes, it's a win forms app, I was hoping that I wouldn't have to marshal the
call to the main thread, in fact, I assumed that the main thread would be
holding an instance of the shared object since it's an SAO and being
registered as a singleton, aparently I am wrong in this assumption???

To answer question 2....
No, that did not seem to solve the problem, notepad would still open, but
the mailto call would fail....

Jason

"Ken Kolda" wrote:

> A couple of questions for you:
>
> 1) Is your server a windows forms app? If so, have you tried marshalling the
> call to the UI thread of your main form to see if that works?
>
> 2) I have no idea if this would have any effect, but how about if you set
> the principal on the current thread to be the windows principal before
> invoking "mailto:", e.g. Thread.CurrentPrincipal = new
> WindowsPrincipal(WindowsIdentity.GetCurrent());
>
> Ken
>
>
> "Jason Schneekloth" <JasonSchneekloth@discussions.microsoft.com> wrote in
> message news:C7A90291-D95A-4608-9DBF-1CB0C3850B45@microsoft.com...
> > Hey all-
> >
> > Posted a problem I was having a few days ago, here is a clarification to
> > that problem, I can't find any answers anywhere on how to go about fixing
> > this. I have a .NET remoting app set up, including a server, a client,
> and a
> > shared assembly between them....
> >
> > To test, I called:
> >
> > System.Diagnostics.Process.Start("mailto:someone@somewhere.com");
> >
> > in the server's constructor, all works just fine, pops up the default mail
> > client to handle the mailto call. No problem.
> >
> > Now....my shared assembly takes care of events between the client and the
> > server. I next make a call within the shared interface from the client.
> The
> > shared interface (which is implemented server-side) forwards the call to a
> > method within the server via an event which the server is registered.
> Inside
> > this method, I put:
> >
> > System.Diagnostics.Process.Start("mailto:someone@somewhere.com");
> >
> > and it fails with the following exception:
> >
> > "The requested lookup key was not found in any active activation context"
> >
> > So I think it's a problem using the Process.Start function from a remoted
> > call being started from the client. This isn't the case, however. If I
> > repelace the mailto with something like "notepad" all works, and notepad
> is
> > opened from the call originating in the client....
> >
> > System.Diagnostics.Process.Start("notepad"); <-- This works
> >
> > What is going on here? I really need this mailto functionality, and I dont
> > understand why it is not working....I can email code if someone wants to
> take
> > an in depth look, it's the most basic .NET remoting app you can have which
> > works with shared objects containing events....
> >
> > Oh yeah, both the client and server are running on the same machine and I
> > have no expectations of them ever being separated to different machines,
> and
> > I am using TCP along with binary serialization or whatever it's called....
> >
> > Jason
> >
>
>
>

Relevant Pages

  • RE: Using kerberosSecurity Throws Security Exception
    ... I am experiencing this error while trying to use a Windows XP client ... application to access a web service located on a W2k3 server. ... client app on the server, ... > Account with a Custom Principal Name using SetSPN.exe utility. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Questions about Remoting, objects, threading. lease lifetime and object cleanup, and a couple of
    ... so long as the Client app is ... always refering to the same server object. ... it sets its ClassOne object to nothing and goes away. ... >>The client app at some point is going to become an ASP.Net app also. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Remoting or windows service
    ... Thanks for writing up such a decent overview of the remoting dev process ... the client and the server. ... > 2) Implement this class in the server app and say that it can be accessed ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Schannel and Session Renegotiation
    ... Schannel does not support the server sending app ... We are discussing the option of providing support for the client blowing off ...
    (microsoft.public.platformsdk.security)
  • Re: Getting Events, for Windows Service
    ... else tries to run my client app he gets an timeout error. ... The server application has a public object called logger, ... So it seems that the logger is properly instantiated and works. ...
    (microsoft.public.dotnet.framework.remoting)