question

VivekD-8637 avatar image
0 Votes"
VivekD-8637 asked Monalv-msft edited

Unable to run a SSIS package from SSMS

We have a production server where we have several SSIS packages. These packages run fine when scheduled via a job and I can run them via SSMS when I remote into the server/VM.

However, when I connect to the server via SSMS on my local machine and try to execute/validate a package it just says Pending execution.

Is there something I need to do to make it work via SSMS from my local machine?

76874-image.png


sql-server-integration-services
image.png (30.8 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

YitzhakKhabinsky-0887 avatar image
0 Votes"
YitzhakKhabinsky-0887 answered

Hi @VivekD-8637,

That's the nature of the beast.
You need to be on the SSIS server via Remote Desktop or Kerberos settings should be setup properly.

Good link on the subject: Getting Cross Domain Kerberos and Delegation working with SSIS Package

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Monalv-msft avatar image
0 Votes"
Monalv-msft answered Monalv-msft edited

Hi @VivekD-8637 ,

1.Please run the ssis package in catalog again.

2.Could you please check if the user in ssis catalog has full permissions to run the ssis package?

3.Please refer to Integration Services Roles (SSIS Service).

Best regards,
Mona


If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, my user id now has ssis_admin as well as db_admin roles in the SSIS Catalog DB but it still did not work.

We have another sandbox server too and I am able to run packages on that server via my machine (SSMS). It doesn't work only in the Production server so I'm guessing it has something to do with permissions.

Only difference between the Sandbox server and the production server as far as how the packages function is that in Production, data is loaded into a database that is on another server whereas in Sandbox both the package and the destination database are on the same server.

0 Votes 0 ·

@VivekD-8637,

I hope you didn't miss my answer.
There is nothing else in addition to what already outlined in my answer.

0 Votes 0 ·
VivekD-8637 avatar image VivekD-8637 YitzhakKhabinsky-0887 ·

No didn't miss. Was just hoping there is some other simple solution :)

Still feel like it's just something I am missing given it works in our Sandbox environment.

0 Votes 0 ·
Show more comments