We recently migrated from a SQL 2008 Standard server to SQL 2012 Enterprise. In doing so we had to move an SSIS package to the new server. This package is called via a stored procedure. Even though the package is installed on the new server and it runs fine, it will not execute from the stored procedure.
It returns "The SQL Server Execute Package Utility requires Integration Services to be installed by one of these editions of SQL Server 2008: Standard, Enterprise, Developer, or Evaluation. To install Integration Services, run SQL Server Setup and select Integration Services."
The sproc is using xp_cmdshell to execute dtexec from the command line.
I'm aware that 2012 changes the SSIS landscape drastically but I have not seen any documentation that the above method of executing a package from a sproc is not supported.
I did attempt to go the new way of executing a package from an sproc by using SSISDB.Catalog.Create_Execution, Set_Execution_Parameter_Value, and Start_Execution. This works but will only run if the executing user is a windows account. This sproc is fired off from a web application and the connection string to the database is a SQL user.
I tried using Execute As and specifying a windows account but I get the error "The current security context cannot be reverted. Please switch to the original database where 'Execute As' was called and try it again."
Lefka