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


DTEXEC returning Exit Code 5


DTEXEC returning Exit Code 5

Author
Message
Scott Nicholson-254313
Scott Nicholson-254313
Valued Member
Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)

Group: General Forum Members
Points: 55 Visits: 31
I have a simple SSIS package that retrieves data from a formatted Excel spreadsheet. The Stored Procedure has the appropriate permissions and executes correctly. xp_cmdshell is active and the user group has execute permissions. The spreadsheet source location has the permissions set. I am the originator of the package and it works correctly for me on any desktop in the domain. When another user tries to execute the SSIS package, the package exit code of 5 (The utility was unable to load the requested package. The package could not be loaded.) comes back.

msdb roles for db_ssisoperator, db_ssisadmin, and db_ssisltduser have been assigned to the user group.

What permission am I missing? This is getting frustrating.

Thanks in advance
Scott
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6408 Visits: 2243
What's the package protection level ?

--
SQLBuddy
Scott Nicholson-254313
Scott Nicholson-254313
Valued Member
Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)

Group: General Forum Members
Points: 55 Visits: 31
Currently set to do not save sensitive data.
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6408 Visits: 2243
Did you create a server proxy account for the non-sysadmin users to run XP_cmdshell ? Are you a sysadmin on the server and is it not possible to schedule the package to run by your ID ?

--
SQLBuddy
Scott Nicholson-254313
Scott Nicholson-254313
Valued Member
Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)

Group: General Forum Members
Points: 55 Visits: 31
1. This package is on-demand execution triggered from an application. Setting it as a job won't work.
2. I am sysadmin on the server. The users will be activating the process. This is the main issue.
3. Will a proxy fix this issue? I have used the login context before with other applications, and they are functioning correctly.
sqlbuddy123
sqlbuddy123
SSCertifiable
SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)SSCertifiable (6.4K reputation)

Group: General Forum Members
Points: 6408 Visits: 2243
Scott Nicholson-254313 (4/1/2014)
1. This package is on-demand execution triggered from an application. Setting it as a job won't work.
2. I am sysadmin on the server. The users will be activating the process. This is the main issue.
3. Will a proxy fix this issue? I have used the login context before with other applications, and they are functioning correctly.

It could fix it .. First create the server proxy account (SSMS --> SQL Server Properties --> Security )

Check this

http://sqlblog.com/blogs/tibor_karaszi/archive/2007/08/23/xp-cmdshell-and-permissions.aspx

--
SQLBuddy
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