 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Remoting / January 2004Permission denied for activating type soap
I've currently switched my application to VS 2003 due to the Remoting security level problem. My application is a pair of CAO server-client applications. But my client-side program generates a 'System.Runtime.Remoting.RemotingException' .... Anyone can help me with the problem? usually when you get this exception moving from .net 1.0 to .net 1.1 its because you need to set your typefilterlevel="full" check out my article on this subject. http://www.glacialcomponents.com/Articles/SerializationException/SerializationEx ception.htm However, if that does not fix the problem, can you be more specific on exactly the exception you are getting as well as more details on what you are doing when it comes up? Allen Anderson http://www.glacialcomponents.com mailto: allen@put my website url here.com >I've currently switched my application to VS 2003 due to the Remoting >security level problem. My application is a pair of CAO server-client >applications. But my client-side program generates a >'System.Runtime.Remoting.RemotingException' .... > >Anyone can help me with the problem? i've checked the filter level but that's not the source of error because I've changed the serverprovider and clientprovider tags in my config file as specified by the gotdotnet.com instructions~ the exception was thrown when I activitated the object: i.e. RemoteObject obj = new RemoteObject(); //this is a CAO i used soapsuds to generate the source file of the RemoteObject class and i added the source file in the Client project and compiled it with the Client main code... i've also used soapsuds to generate the dll file of RemoteObject and referenced it in the Client project. in both cases, as i tried to invoke RemoteObject (i.e. RemoteObject obj = new RemoteObject()), i received the following exception: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ An unhandled exception of type 'System.Runtime.Remoting.RemotingException' occurred in mscorlib.dll Additional information: Permission denied for activating type soap:RemoteObject, http://schemas.microsoft.com/clr/nsassem/CAOServer/CAOServer%2C%20Version%3D1.0. 1483.15840%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Dnull. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ thx for helping.... > usually when you get this exception moving from .net 1.0 to .net 1.1 > its because you need to set your typefilterlevel="full" > > check out my article on this subject. http://www.glacialcomponents.com/Articles/SerializationException/SerializationEx ception.htm > However, if that does not fix the problem, can you be more specific on > exactly the exception you are getting as well as more details on what [quoted text clipped - 10 lines] > > > >Anyone can help me with the problem? ah ok, well I will look into that a bit deeper and see if I can come up with an answer for ya. One thing to note though, soapsuds is rife with problems when trying to use it with the 1.1 framework and CAO's. I've heard many complaints over the months. A better way to go about using a CAO is to simply use a shared library. You can do this without shipping your CAO source. Check out my article on this subject. http://www.glacialcomponents.com/Articles/SAOCAOFactory/CAOGuide.htm Allen Anderson http://www.glacialcomponents.com mailto: allen@put my website url here.com >i've checked the filter level but that's not the source of error because >I've changed the serverprovider and clientprovider tags in my config file as [quoted text clipped - 45 lines] >> > >> >Anyone can help me with the problem? sure I used the factory-based as my alternative though, after checking your website, you mind pointing out the some problems with CAO? cuz' i'm thinking about switching my implementation to SAO totally.... > ah ok, well I will look into that a bit deeper and see if I can come > up with an answer for ya. One thing to note though, soapsuds is rife [quoted text clipped - 60 lines] > >> > > >> >Anyone can help me with the problem? the biggest problem with using a CAO is scalability. If that isn't a worry with your project then CAO's are great. Some people get into the mindset that nothing but a highly scalable architecture will do but that is just not the case. >sure I used the factory-based as my alternative > [quoted text clipped - 11 lines] >> >> http://www.glacialcomponents.com/Articles/SAOCAOFactory/CAOGuide.htm Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.