Quantcast
Channel: SQLServerCentral » SQL Server 2014 » Administration - SQL Server 2014 » Latest topics
Viewing all articles
Browse latest Browse all 6525

SSIS package fails when run in a JOB regardless if I run the job with the SQL Agent Service Account or a proxy

$
0
0
System(s) Principal Server SQL Server 2014 Enterprise 64 bit32Gb Ram 4 CPU(s) Secondary server same as first Using AlwaysOnI have created a "SSIS package" to transfer Jobs and Loginsfrom Principal server (A) to Secondary server (B). I created a SSIS package in Microsoft Visual Studio 2012 Shell and once completed executed the package in Visual Studio the package works fine.I then Started SSIS on my principal server (A) and imported the package into MSDB without sensitive Data (No encryption).I then executed the package by right clicking on the package and execute, again the package worked fine.Next I created a Job on the Principal Server (A) and then set the Job Step to Execute a SSIS package.When I try and execute the package I get the following error:The SELECT permission was denied on the object 'sysjobs_view', database 'msdb', schema 'dbo' End Error DTExec: The package execution returned DTSER_FAILURE (1).I have created a PROXY and followed all the requirements for running a SSIS package and so for that attempt I get:"The specified @proxy_name ('SSISProxy') does not exist.". Eventhough this Proxy user is displayed in the Drop down list in the job under "Run As"I have set up SSIS packages in the past to run in jobs on SQL Server 2005 and 2008 it seems quite a bit has changed in 2014??? I have looked on the forum as well as Online and so far did not find anyanswers to why this is proving to be so difficult...Any help would be appreciated ...

Viewing all articles
Browse latest Browse all 6525

Trending Articles