May 6, 2011 at 11:39 am
Local System is the account running the SQL Server Agent (MSSQLSERVER)
Is there something else I should change it to? Maybe to my account name instead (Don't know if that is possible)
May 6, 2011 at 11:43 am
I just tested to see if I could make my user the only user and I can, but I don't know what you're next suggested course of action would be to solve this issue.
May 6, 2011 at 11:52 am
stormsentinelcammy (5/6/2011)
Local System is the account running the SQL Server Agent (MSSQLSERVER)Is there something else I should change it to? Maybe to my account name instead (Don't know if that is possible)
Check to make sure you have created a credential with Admin Permission and mapped that to the proxy system, I checked this in SQL Server 2008 R2.
Kind regards,
Gift Peddie
May 6, 2011 at 12:22 pm
I have attached JPEG files that show my configurations. Let me know if there is any other things you want to see as far as my configurations go.
May 6, 2011 at 12:39 pm
stormsentinelcammy (5/6/2011)
I have attached JPEG files that show my configurations. Let me know if there is any other things you want to see as far as my configurations go.
You are missing Credential which you need to create under security where you add an account and create password, which you then use to configure the SSIS proxy. So create new credential in security and use it to create the proxy.
Kind regards,
Gift Peddie
May 6, 2011 at 12:53 pm
Woops I forgot to add that one to the list. Its attached now.
May 6, 2011 at 1:14 pm
stormsentinelcammy (5/6/2011)
Woops I forgot to add that one to the list. Its attached now.
Delete the existing Job create new one and make sure you select the proxy from the drop down under ran as and add all the other needed information.
Kind regards,
Gift Peddie
May 6, 2011 at 1:32 pm
I redid the job, calling the proxy in the Run As section and even declaring the datasources for all of the package datasources in the "DataSources" tab in the Job Step Properties page. Still the same error. I only get this error when running the package manually. Now after going through entire process with you I know it has to be some permission setting that is not allowing me to run the SQLServerAgent, but I really wish I could track it down. Maybe during this weekend you or I can come up with some new possible reasons why I'm getting these issues. Again, thanks for your help so far. I'm leaving work now, so I will try to get on when I can later on or Monday.
May 9, 2011 at 7:25 am
I did a lot of changes on package rights and on what user runs the package, I'm kind of stuck now because I can't remember how or where I changed the settings to where now the user that runs the package is always [Servername]\SYSTEM. Could someone please tell me where I can change this back where the user who runs the job shows up as the user running the job and not [Servername]\SYSTEM all the time?
May 9, 2011 at 8:15 am
Any new suggestions on how I would be able to fix that connection issue with the server that I've posted before, I have exhausted a lot of options, just wondering if there is anything else I can do to make this SSIS package run from the SQL Agent properly on a schedule. I'm able to run powershell on a daily schedule, just don't understand why I can't run the SSIS package on a daily schedule. Maybe run the SSIS job using powershell or cmd?
Viewing 10 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply