Re: "Requested registry access is not allowed" and Web Service call
From: Clint (cjmueller_at_gmail.com)
Date: 12/15/04
- Next message: Peter Jausovec: "Re: Listening on Ports"
- Previous message: Xarky: "Listening on Ports"
- In reply to: Nicole Calinoiu: "Re: "Requested registry access is not allowed" and Web Service call"
- Next in thread: Nicole Calinoiu: "Re: "Requested registry access is not allowed" and Web Service call"
- Reply: Nicole Calinoiu: "Re: "Requested registry access is not allowed" and Web Service call"
- Messages sorted by: [ date ] [ thread ]
Date: 15 Dec 2004 06:49:15 -0800
I think I'm doing something wrong in that I tried setting the Proxy
right after creating a new instance of my service:
ws = new HashTest.iisvm03.Service1();
ws.Proxy = new System.Net.WebProxy("http://foo:80", true);
ws.CookieContainer = new System.Net.CookieContainer();
ws.Credentials = System.Net.CredentialCache.DefaultCredentials;
With no success - still trying to read from the registry. I did find a
work-around, though, in that I'm not always impersonating a user in the
application, only on remote calls. So, when my calling class fires up,
it isn't impersonating, and I can set a private proxy field in the
constructor and use it as needed when I do my calls. That, oddly
enough, seems to work.
I have no problem going that route, I'm more curious now as to what I
was doing wrong for future reference. Either way - thanks again for
helping me out - this has been bugging me for a while!
Clint
- Next message: Peter Jausovec: "Re: Listening on Ports"
- Previous message: Xarky: "Listening on Ports"
- In reply to: Nicole Calinoiu: "Re: "Requested registry access is not allowed" and Web Service call"
- Next in thread: Nicole Calinoiu: "Re: "Requested registry access is not allowed" and Web Service call"
- Reply: Nicole Calinoiu: "Re: "Requested registry access is not allowed" and Web Service call"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
