SSIS Double Hop Issue

Sam Garth 26 Reputation points Microsoft Employee
2020-12-21T15:36:12.323+00:00

Hello

I have a SQL Server A, SQL Server B and SQL Server C.

SQL Server A holds a table. SQL Server B has a job to run an SSIS Package on SQL Server C.

SPNs are active on all 3 instances.

The SSIS Package on SQL Server C will extract data from SQL Server A and write to an Excel file on SQL Server B.

If I manually execute the package it works successfully, however if I run the package from SQL Server B (so B kicks off the job on C to query A and write to B) then it errors with the below

49919-image.png

If I change the share to a share on C then it works fine. Is this a common issue? Do I need an SPN set up on the SSIS Service?

Any help would be appreciated.

Thanks

Sam

SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,446 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Monalv-MSFT 5,891 Reputation points
    2020-12-22T03:05:47.603+00:00

    Hi @Anonymous ,

    If I manually execute the package it works successfully, however if I run the package from SQL Server B (so B kicks off the job on C to query A and write to B) then it errors with the below

    1. Please check if you opened the shared excel file or you used this file on other process; (If so, please close the file or process.)
    2. Please check if the user to execute the ssis package in SQL Server B has permission to view and write in the shared excel file;
    3. Please check if you download both 32-bit and 64-bit Microsoft Access Database Engine in SQL Server B.

    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.
    Hot issues in November--What can I do if my transaction log is full?
    Hot issues in November--How to convert Profiler trace into a SQL Server table?