Package execution from SSIS Catalog - Failed to execute when running from remote SSMS

Question

Package execution from SSIS Catalog - Failed to execute when running from remote SSMS

SQL!$@w$0ME

SSChampion

Points: 12349
More actions
March 23, 2016 at 11:58 am

#312254

I am able to run the package from the server (manually run from SSIS Catalog ). But it fails when run from my desktop or through SQL agent job. The package writes log files to a shared directory and agent service account has write permissions on the share.
"Log messages about completion of process. Error: Exception has been thrown by the target of an invocation"
Any thoughts on this.
Many thanks!

Viewing 8 posts - 1 through 7 (of 7 total)

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

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

SQL!$@w$0ME (3/23/2016)
I am able to run the package from the server (manually run from SSIS Catalog not through job). But it fails when run from my desktop.
Any thoughts on this.
Many thanks!

Thought #1: You've been here long enough to know this: can you post the text of the error message, please?

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

SQL!$@w$0ME SSChampion Points: 12349 More actions · Answer 2

The package writes log files to a shared directory and agent service account has write permissions on the share.

"Log messages about completion of process. Error: Exception has been thrown by the target of an invocation"

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

It really seems that the Agent service account does not have the necessary rights.

Are you using a UNC path?

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

SQL!$@w$0ME SSChampion Points: 12349 More actions · Answer 4

Are you using a UNC path?

Yes Phil.

Agent service account has been granted Local Launch and Local activation permissions and I am able to run from the agent now.

Still unable to manually run the package from SSIS Catalog from remote SSMS. I am able to run manually from the SSIS server.

Phil Parkin SSC Guru Points: 246986 More actions · Answer 5

Still unable to manually run the package from SSIS Catalog from remote SSMS

When you try this, are you connected to the SQL instance via Windows Authentication or SQL Authentication?

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

SQL!$@w$0ME SSChampion Points: 12349 More actions · Answer 6

Windows authentication. I am able to run other packages except this one package.

tlanfaber Valued Member Points: 66 More actions · Answer 7

I'm having the same issue. One of my packages fails in a sql agent job, but others work. I associated the administrator to a proxy account and made the SSIS step use the proxy, and it still fails. The errors occur in the Script Task:

Any suggestions would be appreciated.
Thanks