If I'm calling a VB 6.0 component that is installed in a COM+ application marked for Server activation (out of proc) from a ASP.Net client using the appropriate InterOp project. The error received for the call generally states that there is a permissions problem.
My question is what are the general permissions issues in this scenario? The ASPNET account doesn't appear to have sufficient privileges to make the cross process call. Do I need to set up DCOM permissions for the application via the dcomcnfg tool? Do I need to create a new account for ASP.Net to run under with elevated privileges(this obviously would not be desireable) Can I somehow use the .Net configuration tool to allow the ASP.Net client to call the out-of-proc VB 6.0 server? Is there another issue or technique to allow this functionality? =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
