debugsqlMinor
Error: "To run a ssis package outside of sql server data tools you must install [send successful email] of Integration Services or higher."
Viewed 0 times
errorinstallpackageyoumustsqlsendssissuccessfulemail
Problem
NOTE that the title of this qusetion is a verbatim error message specific to this user. The error message illustrates a bug in the dtexec application, which substitutes a user variable into the error message string. In this case, the standard message
The 'standard' error message would be :
Description: To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher.
Version SSIS 2012. Package was originally 2005 ver. Package on file system.
DB Engine / Agent on Host 1, SSIS on Host 2.
Execution from Host 2 runs successfully. Execution from Host 1 gives the error in the question subject. Saw this post, but engine and agent are installed on Host 1. Has anyone seen this? Google returns no results when searching on the exact error (subject line is exact, wording is odd in the error message).
Thank you!
Standard E
dition is replaced with send successful email.The 'standard' error message would be :
Description: To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher.
Version SSIS 2012. Package was originally 2005 ver. Package on file system.
DB Engine / Agent on Host 1, SSIS on Host 2.
Execution from Host 2 runs successfully. Execution from Host 1 gives the error in the question subject. Saw this post, but engine and agent are installed on Host 1. Has anyone seen this? Google returns no results when searching on the exact error (subject line is exact, wording is odd in the error message).
Thank you!
Solution
SSIS 2012 components had to be installed on Host 1 to resolve the issue.
*If anyone knows of a way to resolve this without installing SSIS 2012 components where they aren't intended, please post and I'll accept your answer.
*If anyone knows of a way to resolve this without installing SSIS 2012 components where they aren't intended, please post and I'll accept your answer.
Context
StackExchange Database Administrators Q#49786, answer score: 8
Revisions (0)
No revisions yet.