Home > Article > Backend Development > Why am I getting an error about missing script component dependencies when executing SSIS 2012 packages from an external application?
Executing SSIS 2012 Packages from External Applications: Addressing Script Component Error
When attempting to execute an SSIS 2012 package via your application using the Microsoft.SqlServer.ManagedDTS v 11.0 assembly, you may encounter errors related to missing script component dependencies. This is typically caused by the absence of the SQL Server Integration Services Service on the machine where the application is running.
Issue
Your script components are likely referencing external assemblies that are not available on the target machine. The error message "To run a SSIS package outside of SQL Server Data Tools you must install [Script Component Name] of Integration Services or higher" indicates that the necessary component is not installed.
Solution
To resolve this issue, you must install the SQL Server Integration Services Service on the machine where the application will be executing the packages. This service provides the required runtime environment for SSIS packages, including the ability to load and execute script components.
Additional Information
<code class="xml"><?xml version="1.0" encoding="utf-8" ?> <configuration> <startup useLegacyV2RuntimeActivationPolicy="true"> <supportedRuntime version="v4.0"/> <supportedRuntime version="v2.0.50727"/> </startup> </configuration></code>
By following these steps, you should be able to successfully execute SSIS 2012 packages with script components from your external application.
The above is the detailed content of Why am I getting an error about missing script component dependencies when executing SSIS 2012 packages from an external application?. For more information, please follow other related articles on the PHP Chinese website!