Package which contains executables in SSIS is not running in SQL Server Agent

Question

Package which contains executables in SSIS is not running in SQL Server Agent

Thinky Night

SSCommitted

Points: 1663
More actions
December 13, 2017 at 8:49 am

#341233

Hi All,
I have an SSIS Packages which call .exe from operating system. It is running when i execute package from SSIS.
But, When I prepare a SQL Server Agent which calls the SSIS package, it is hanging. I see my executable in the task manager with no owner. But it never ends.
What would be the problem. Do you have security config suggestions? Or another suggestions may be?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246723 More actions · Answer 1

Thinky Night - Wednesday, December 13, 2017 8:49 AM
Hi All,
I have an SSIS Packages which call .exe from operating system. It is running when i execute package from SSIS.
But, When I prepare a SQL Server Agent which calls the SSIS package, it is hanging. I see my executable in the task manager with no owner. But it never ends.
What would be the problem. Do you have security config suggestions? Or another suggestions may be?

It's likely to be a permissions problem. Does the SQL Agent user have the necessary rights?

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Thinky Night SSCommitted Points: 1663 More actions · Answer 2

Thanks Phil Parkin,

I find the problem, My executable is generating an output file. Where you run executable, it generates output file there. So i need SQL Server Agent Working Directory to delegate the service account?

Help, please.

Phil Parkin SSC Guru Points: 246723 More actions · Answer 3

Thinky Night - Wednesday, December 13, 2017 9:30 AM
Thanks Phil Parkin,
I find the problem, My executable is generating an output file. Where you run executable, it generates output file there. So i need SQL Server Agent Working Directory to delegate the service account?
Help, please.

Make the SQL Agent service account a Windows domain service account and grant the necessary permissions to that account.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.