Karen Grube - Tuesday, February 13, 2018 9:58 PM

Remove alert|Edit|Delete|Change type
HI!
I'm running the most recent versions of SQL Server, Integration Services (SSDT) and Visual Studio on a Windows 2012 R2 server

Using an Integration Services Project, I created an SSIS package.  It runs perfectly.I deployed that package to the SSIS Catalog.  I created a stored procedure that runs that SSIS package.  It runs perfectly

However,I need to execute the stored procedure from an ASP.net web page, and when I do, I get the following error:
    "The server principal \"WORKGROUP\\MYSERVERNAME$\" is not able to access the database \"SSISDB\" under the current security context."

The account I'm signed in as is in the Windows Administrator Group.  That account is a sysadmin on the database server.  I have added that account to the "ssis_admin" role in SSISDB.

The Server has four databases, including SSISDB.  The stored procedure runs from one of the other databases, we'll call it "ITDatabase"

The stored procedure actually starts when it runs from the VS Debugger.  The initial steps of that stored procedure execute, but it stops when it tries to execute the SSIS package from the catalog.

In IIS 6.2 , when I go to the Application Pools and look at the Default App Pool and look at the "Advanced" settings" I can see that Default App Pool is running under Local System.  I experimented and changed the Process Model Identity to the login I use to sign on to the server. When I did that then ran the ASP.Net page in the Visual Studio debugger, the process completed without error.

Of course, I changed the App Pool Process Model Identity that back to Local Service.  I can't have the app pool running under my login.

I hope someone has some suggestions.  I'm not sure how to configure security so this package will run from ASP.Net

Thanks!