Unexpected Termination but successful

Sam Garth 26 Reputation points Microsoft Employee
2021-02-24T11:16:29.143+00:00

Hello

I have an SSIS Package that writes to an Excel file.

It works successfully when...

  • Running through Visual Studio under my login and my colleagues
  • Running manually from the SSIS server under my login only
  • Running through a job from another SQL instance under my login only

When my colleague runs it manually or under the job it fails with Unexpected Termination BUT it actually writes to the file.

After testing, the table it copies has over 30K rows. I have changed this to SELECT TOP 100 and it works if the excel file is empty, but if the Excel File already a fairly large size that will fail. (even though it has written to the file).

So it seems to be writing to Excel that is the issue.

Does anyone know why this would be? And why would it work for my login but not two others?

Thanks

Sam

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

3 answers

Sort by: Most helpful
  1. Monalv-MSFT 5,896 Reputation points
    2021-02-25T05:48:10.993+00:00

    Hi @Anonymous ,

    1.Could you please share the detailed error messages?

    2.We can set protection level in SSIS package.
    To protect the data in an Integration Services package, you can set a protection level that helps protect just sensitive data or all the data in the package. Furthermore, you can encrypt this data with a password or a user key, or rely on the database to encrypt the data.

    Please refer to Access Control for Sensitive Data in Packages.

    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.


  2. Sam Garth 26 Reputation points Microsoft Employee
    2021-02-26T09:04:39.96+00:00

    Just an FYI the issue is fixed. It was because I was a local admin on the SSIS server. I am not sure if I can get a lower level or rights to get access to global shared memory but will look into that.


  3. Divyesh Patel 16 Reputation points
    2021-12-29T14:50:27.057+00:00

    Was this ever resolved if so how .I have the same issue

    0 comments No comments