Microsoft.SqlServer.Dts.Runtime && ASP.NET Identity Problem

Greetings,

I have an ASP.NET web form that calls out to a component which includes the following code which leverages the Application and Package classes in the Microsoft.SqlServer.Dts.Runtime namespace:

Application application = new Application();

Package package = application.LoadFromDtsServer(@"File SystemMyPackagesMyPackage", "MyMachine", null);



string id = package.ID;

Microsoft.SqlServer.Dts.Runtime.DTSExecResult result = package.Execute();

I am logged in to the app as DomainMe.

I have Windows Integrated Authentication configured in IIS and am using Windows Authentication in ASP.NET. I am using impersonation to impersonate a fixed identity, say DomainBob. This has the following effect:

WindowIdentity.GetCurrent() returns DomainBob as expected since the process is being impersonated by DomainBob.

Thread.CurrentPrincipal.Identity.Name returns DomainMe as expected since the ASP.NET application is using Windows Authentication.

The id variable successfuly is initialized to the GUID of the package, proving that the package name is resolving, however, from the ASP.NET application, the package fails.

Issuing the ? package.Errors[0] command at the command window provides the following information:

{Microsoft.SqlServer.Dts.Runtime.DtsError}
base {Microsoft.SqlServer.Dts.Runtime.DtsObject}: {Microsoft.SqlServer.Dts.Runtime.DtsError}
Description: "An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Shared Memory Provider: I/O Error detected in read/write operation [4]. ".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'MyMachine\ASPNET'.".
"
ErrorCode: -1071636471
HelpContext: 0
HelpFile: null
IDOfInterfaceWithError: "{8BDFE898-E9D8-4D23-9739-DA807BCDC2AC}"
Source: "Packages MyPackage"
SubComponent: "Connection manager "DataMart""
TimeStamp: {12/21/2006 2:18:55 PM}

For some reason, the ASPNET process account is being passed to the package!

This makes no sense, because clearly, DomainBob is impersonating the worker process and all downstream resources should be accessed via DomainBob. This includes SQL Server Database Engine and I would imagine SSIS as well. ASPNET should not come into play at all since I am impersonating.

I also tried using regular (non-fixed identity) impersonation (<identity impersonate="true" />), but again, SSIS is trying to authenticate ASPNET, instead of DomainMe as would be expected.

This is definetely isolated to ASP.NET applications, because making the same call from within a unit test succeeds. It would seem that this is a definete issue because the behavior is inconsistent with ASP.NET security principles.

Has anyone else seen this problem?

Any direction or suggestions very much appreciated.

Thanks,

Rick