3
  • SQL Server 2016 SP1 Enterprise Edition Data Engine (with SQL Agent) installed on an FCI called inst1.
  • SSIS 2016 SP1 Enterprise Edition installed on comp2. (comp2 is not in the inst1 cluster)
  • Filesystem SSIS packages on comp2.
  • SQL Agent job using the SSIS step type on inst1 calls the package store on comp2.

When I run the job on inst1, I get this error:

To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services or higher.

I have run the edition upgrade wizard, just in case the wrong edition was installed. The error persists.

Any ideas?

closed as off-topic by dezso, McNets, Erik Darling, Andriy M, Marco May 24 '17 at 10:03

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – dezso, McNets, Erik Darling, Andriy M, Marco
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Does this package use Excel files? – McNets May 23 '17 at 18:38
  • No it does not use Excel files. – SQL Hammer May 23 '17 at 18:55
  • What package deployment model is it using? – Shawn Melton May 23 '17 at 19:20
1

Turns out I didn't have SSIS installed on the inst1 server(s) and that is where the dtexec.exe process was being kicked off. It was not an edition problem, just a missing service problem.

Not the answer you're looking for? Browse other questions tagged or ask your own question.