SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Failure of SSIS Package when Executed from SQL Server Agent


Failure of SSIS Package when Executed from SQL Server Agent

Author
Message
virtualeffect
virtualeffect
Valued Member
Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)

Group: General Forum Members
Points: 58 Visits: 71
Well even if I run it manually it won't get the config data from the sql configdb.

So possibly there is something wrong other than what I am thinking?

I'm not sure what you mean by the Scheduled Job owner..

from my understanding, the owner of the schedules job is whatever logon id is used as the longon as for the sql server agent. But in this case, it's part of the proxy user.

Using the xml file way of storing the config data worked well, but the dba for the server that the database is on wants it down with the configdb..
skosanabv
skosanabv
Forum Newbie
Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: General Forum Members
Points: 6 Visits: 128
I found the solution

I experienced the same Issue with my packages, and tried all these solutions posted here, but none of them worked for me.

What I then did:
1. SQL Server Configuration Manager
2. SQL Services
3. Select SQL Server Agent, right click, select properties.
4. Under log on tab, select 'this account' radio button, and select the user who created the package.

Remember the user can be changed in the Solution Explorer in visual studio/SQL Server Data tools of the package in case there is a need to do that. HOW: Right Click the Project, Properties, Common properties, Project, CreatorName, Change it to whatever name you will configure the SQL Server agent to logon using.
Redeploy your package but not necessary. Start job at Step to test execution. Hurrraaaaayyy... Your Job is up and running.

I trust that this helps. Please give me feedback if this has helped you. Thank you.

Bongani
Phil Parkin
Phil Parkin
SSCoach
SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)

Group: General Forum Members
Points: 18634 Visits: 20449
skosanabv (11/19/2013)
I found the solution

I experienced the same Issue with my packages, and tried all these solutions posted here, but none of them worked for me.

What I then did:
1. SQL Server Configuration Manager
2. SQL Services
3. Select SQL Server Agent, right click, select properties.
4. Under log on tab, select 'this account' radio button, and select the user who created the package.

Remember the user can be changed in the Solution Explorer in visual studio/SQL Server Data tools of the package in case there is a need to do that. HOW: Right Click the Project, Properties, Common properties, Project, CreatorName, Change it to whatever name you will configure the SQL Server agent to logon using.
Redeploy your package but not necessary. Start job at Step to test execution. Hurrraaaaayyy... Your Job is up and running.

I trust that this helps. Please give me feedback if this has helped you. Thank you.

Bongani


Are you suggesting that the SQL Agent service needs to run with the same account as created a package?

And therefore that every deployed package needs to be created by the same account?

:-)


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.

Please surround any code or links you post with the appropriate IFCode formatting tags. It helps readability a lot.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search