Re: Execution permission cannot be acquired on SqlConnection open() within .NET exposed as COM

From: Dax Westerman (daxwesterman_at_hotmail.com)
Date: 08/22/03 

Date: 22 Aug 2003 04:46:35 -0700

As usual the wierder the problem, the simpler the solution. I did not
have execute privleges on the bin directory. I'd still be curious to
see if there's an alternate solution using .NET security management if
anyone's game.

Thank you,
Dax

daxwesterman@hotmail.com (Dax Westerman) wrote in message news:<6ce84b5a.0308211040.7f80f42a@posting.google.com>...
> I have an application in ASP that I am attempting to migrate to
> ASP.NET, and in the course of this migration I've become snarled in a
> .NET security issue on which I need some expert help. From the 50,000
> ft level, I've got a .NET project that wraps database access
> (SqlConnection for one), and in turn this class is wrapped by another
> .NET classes that's been exposed as a COM object. This COM interface
> was created for use in an ASP page.
>
> As of yesterday afternoon, I was able to call the COM reference, and
> the appropriate database interaction took place within the
> aforementioned .NET classes, no sweat. However, after this morning's
> WindowsXP update (grumble), security on the machine got slammed down,
> and I've had to claw my way back to pseudo-functionality. This was
> achieved by using the .NET 1.1 wizard to give full trust to the
> generated assemblies in the bin of my web app.
>
> Currently, I can access the COM interface and use its methods.
> However, when I try to "open" a SqlConnection member variable, I get
>
> Execution permission cannot be acquired
>
> Notes of interest:
> - I can run the same code via a test app in .NET, and everything works
> great.
> - There are two .NET projects being used, one wrapping database access
> and a second one calling it. The second one exposes the interface.
> Neither is named or has a key or anything like that (I don't pretend
> to know where to start with that, yet, as I'm still new to it, and I'm
> not sure it's part of my problem.)
> - I've added full trust to the System.Data assembly as well. I
> actually had everything working for a few minutes, then the magic
> passed, so I'm not sure it had any effect.
>
> Can anyone give me some insight into the direction I should be going
> to solve this issue?
>
> Thank you very much,
> Dax