When migrating ssis packages from 2005 to 2012 Activex Script Task component doesn't exist in 2012 version

Hello,
We are migrating the ssis packages from 2005 to 2012.
I'm unable to convert Activex Script Task from 2005 vesrsion to 2012 because in 2012 version Activex Script Task doesn't exist.
Can anyone please let me know what is the alternative way to convert Activex Script Task from 2005 vesrsion to 2012?

Hi Vinay9738,
Have you tried to upgrade the SSIS 2005 packages to SSIS 2012 packages by using the SSIS Package Upgrade wizard? In certain cases, ActiveX script in SSIS won’t work and we need to either modify the script or replace the ActiveX Script with stock SSIS
tasks. You can find the mapping between some most common patterns used in DTS ActiveX Script and SSIS native tasks from the following link:
http://help.pragmaticworks.com/dtsxchange/scr/ActiveX%20Script%20Task.htm
Here is also a useful link about how to convert ADODB object of ActiveX Script to SSIS tasks:
http://help.pragmaticworks.com/dtsxchange/scr/FAQ%20-%20How%20to%20convert%20ADODB%20object%20of%20ActiveX%20Script%20to%20native%20SSIS%20Task.htm
Regards,
Mike Yin
TechNet Community Support

Similar Messages

Getting error code 1 when calling SSIS package from a stored procedure (SQL Server 2008 R2)

Hello,
I am trying to execute a SSIS package from SQL Server 2008 R2 stored procedure but getting error code 1 (as per my knowledge, error code description is as below:
0 The package executed successfully.
1 The package failed.
3 The package was canceled by the user.
4 The utility was unable to locate the requested package. The package could not be found.
5 The utility was unable to load the requested package. The package could not be loaded.
6 The utility encountered an internal error of syntactic or semantic errors in the command line.
Details:
I have a stored procedure named "Execute_SSIS_Package" (see below sp) which executes 'Import_EMS_Response' SSIS package (when I execute this package directly from SQL Server BID it works fine it means package itself is correct) and calling
it from SQL as:- EXEC Execute_SSIS_Package 'Import_EMS_Response'.
Here I receives error code 1.
Can anyone help me to resolve this issue please?
Thanks in advance!
CREATE PROCEDURE [dbo].[Execute_SSIS_Package]
@strPackage nvarchar(100)
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
DECLARE @cmd VARCHAR(8000)
DECLARE @Result int
DECLARE @Environment VARCHAR(100)
SELECT @Environment = Waarde
FROM Sys_Settings
WHERE Optie = 'Omgeving'
--print @Environment
SET @strPackage = '"\W2250_NGSQLSERVER\BVT\' + @Environment + '\' + @strPackage + '"'
SET @cmd = 'dtexec /SQL ' + @strPackage + ' /SERVER "w2250\NGSQLSERVER" /Decrypt "BVT_SSIS" /CHECKPOINTING OFF /REPORTING E'
--print @cmd
EXECUTE @Result = master..xp_cmdshell @cmd, NO_OUTPUT
--print @Result
END

It has something to do with the security.
E.g. cmdshell is not enabled or the caller has not rights over the package.
There could be a syntax error, too.
I suggest you make the package runnable off a SQL Agent job then trigger the job from the stored proc with
sp_start_job <job name>
Arthur
MyBlog
Twitter

Execute SSIS Package from JOB which contains Execute Process Task calling a .bat file

Hi All,
I have a EXCEL Macro needs to be called from SSIS. We could not use Script task because of some internal reason.
So we have taken an approach to call a .BAT file using Execute Process Task. This .BAT file will call a .VBS file which will execute the EXCEL Macro.
The SSIS Package is running good if I execute the package from BIDS.
But the real problem is with the scheduling this SSIS Package using SQL JOB.
If i execute this SSIS package from SQL Server Job, its executing the whole package successfully except the Execute Process Task.
So the overall issue is SQL Server Job is not executing properly if I call any .BAT file from the SSIS Package.
Please give me suggestion to get rid of the issue. Thanks in advance.

Hi Sai.N,
If you run the SQL Server Agent job manually from SSMS, does the package execute properly? If the package executes properly when you run the job manually, the issue should occur due to permission issue. In this case, I suggest that you create a SQL Server
Agent proxy based on the current Windows account which you use to log onto the operating system, and run the job under the proxy account.
If it is not the issue, please enable logging in the package as Visakh mentioned and post the warning/error message for further analysis.
Regards,
Mike Yin
TechNet Community Support

ERROR WHILE MIGRATING SSIS PACKAGE FROM DEVELOPMENT TO PRODUCTION IN EXECUTION

HI,
I have a problem while executing the package after migrating from DEVELOPMENT to PRODUCTION.
We have two SQL database connections DEVMIDDLEWARE and PRODMIDDLEWARE for dev and prod respectively. When we have created package in development we have used DEVMIDDLEWARE and we have credentials in CONFIG file of that package and executed sucessfully. When
we migrated this same package to PRODUCTION when have given credentials of PRODMIDDLEWARE in CONFIG FILE of this package we are getting error as below
"Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic
error. Verify that the correct key is available. End Error Error: 2014-10-28 07:41:44.24     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node
"DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
End Error Error: 2014-10-28 07:41:44.85     Code: 0xC0202009     Source: Package Connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware"     Description: SSIS Error Code DTS_E_OLEDBERROR.
An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'devmiddleware'.".
End Error Error: 2014-10-28 07:41:44.85     Code: 0xC020801C     Source: Package Log provider "SSIS log provider for SQL Server"     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method
call failed. COM error object information is available. Source: "Package" error code: 0xC0202009 Description: "SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE
DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'devmiddleware'.". ". End Error Error: 2014-10-28 07:41:44.98
Code: 0xC0202009     Source: Package Connection manager "AGRDB01.abwr66"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record
is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user 'CC\epsdbuser'.". End Error Error: 2014-10-28 07:41:44.98     Code:
0xC020801C     Source: Data Flow Task OLE DB Source [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "AGRDB01.abwr66"
failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-10-28 07:41:44.99     Code: 0xC0047017
Source: Data Flow Task SSIS.Pipeline     Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2014-10-28 07:41:44.99     Code: 0xC004700C
Source: Data Flow Task SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2014-10-28 07:41:45.00     Code: 0xC0024107     Source: Data Flow Task
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 07:41:44 Finished: 07:41:45 Elapsed: 0.859 seconds. The package execution failed.
The step failed."
Can anyone help for this error.
Many thanx in Advance

Hi Babloo,
According to the error message, the package may have failed are as follows:
The user account that is used to run the package under SQL Server Agent in PRODUCTION server differs from the original package author.
The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
The package may not run in the following scenarios:
The current user cannot decrypt secrets from the package. This scenario can occur if the current account or the execution account differs from the original package author, and the package's ProtectionLevel property setting does not let the current user
decrypt secrets in the package. In this scenario, we can change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword, then modify the SQL Server Agent job step command line to include this password.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. In this scenario, we can create a SQL Server Agent proxy account. This proxy account must use a credential
that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.
References:
SSIS package does not run when called from a SQL Server Agent job step
Run an SSIS Package Under a Different Account
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

How to Migrate SSIS packages from 32 bit to 64 bit environment

Hi,
We developed many SSIS packages in 32 bit environment using SQL 2008 on windows 2003 server 32 bit OS. In order to utilize the 64 bit features we wish to migrate these packages into a 64 bit. Wanted to know.
1. Whether we can execute these packages that are developed in 32 bit environment onto a 64 bit environment. If yes, then do we get the benefits of 64 bit environment. For ex. RAM utilization. If no, then what advantage do we get.
2. Is it possible to develop the packages directly in a 64 bit environment.
Thanks in advance,
Yog

One thing you need to make sure when migrating to 64 bit machines is to have drivers installed for 64 bit ie for providers like excel. One more thing to note is that SSDT/BIDS which is used for developing packages is by itself a 32 bit application. So
you may need to use 3 bit driver at design time and run packages with 64 bit runtime set to false at design time. And while deployed on server it can use 64 bit driver itself for its execution.
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

SSIS Package, Use Datepicker control in VB script task

Dim dateTimePicker1 As New DateTimePicker()
Controls.AddRange(New Control() {dateTimePicker1})
MessageBox.Show(dateTimePicker1.Value.ToString())
dateTimePicker1.Value = DateTime.Now.AddDays(1)
MessageBox.Show(dateTimePicker1.Value.ToString())
In an SSIS package, 2008r2.... I trying to add a messagebox to a script task that contains a datepicker control.
I will pass the date to a variable then stored procedure. The code above almost works except I get "Name Controls not declared". I am using
System.Windows.Forms.
Anyone know how to correct?
Thanks,
MIke

Nope
You cant have forms etc added to script task inside SSIS and make it interactive
If your intention is to pass a value from outside you need to make use of configurations or use command line arguments with utilities like dtexec.
http://www.bidn.com/blogs/DevinKnight/ssis/1655/passing-values-into-an-ssis-package-at-runtime-from-outside-the-package
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS PACKAGE MIGRATION FROM 2005 to 2008 - Script task/component errors

HI All,
We have to migrate ssis packages (about 300) from ssis 2005 to 2008 .
1. I understand that the major concern is regarding the script component/tasks.
I searched a lot about this and also consulted with many friends , all of them are aware of this issue but not able to provide what could be the issues and the solution.
Can some one help me with the common script issues that can happen during migration and the solution for the same.
2. I do have one more question.
As per my understanding given in the below link
http://blogs.msdn.com/b/mattm/archive/2008/03/21/package-upgrade-wizard.aspx
there is this part which says ...
Once the packages have been chosen, the next page asks you to pick the output location. This can be:
Same as the source location
File System
SSIS Service (Package Store)
SQL Server
Does this mean I can deploy in sql server directly on fly while upgrading ?
Any help highly appreciated .
Regards
Praveen..

Hi Praveen,
Question 1: The error may occur if there are duplicate input columns in the Script Task/Component or the current user cannot access the C:\Windows\Temp directory. Except for the link provided by SanBhaumik, you can also refer to the following
threads:
http://www.sqlservercentral.com/Forums/Topic811208-148-1.aspx
http://social.technet.microsoft.com/Forums/sqlserver/en-US/5c11eb57-59d6-4f81-bfdc-13bd6489a0ac/sql-server-2008-ssis-package-script-component-error?forum=sqlintegrationservices
Question 2: We can directly save the package to the File System, SSIS Package Store, or SQL Server by selecting the proper destination during the package upgrade. However, this operation is not equal to the package install operation identically.
For example, if we have enabled package configurations for a package, the package configurations won’t be upgraded or installed during the package upgrade.
Regards,
Mike Yin
TechNet Community Support

When migrating dts package to ssis 2005 version

Hello,
When migrating dts package to ssis 2005 version I'm getting below error.
Component with name "DupCheckXLS" and class ID "{5A0B62E8-D91D-49F5-94A5-7BE58DE508F0}" could not be created because an error was encountered during its upgrade to the current version.
Contact information:
Any help would be helpful.

may be components and properties available on 2005 that are not available on 2000.You need to re create the task in SSIS.
Yes. that has been my experience always. One or more tasks have to be recreated. The architecture itself is different in SSIS. Thats why I feel it might be better to recreate package in SSIS rather than trying to migrate and then fix the issues
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Error when deploying SSIS package in 2012

Hi,
I am trying to deploy a SSIS package to 2012 version. But i am getting error as below,
TITLE: SQL Server Integration Services
There was an exception while loading Script Task from XML: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Tools.Applications, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Microsoft.SqlServer.IntegrationServices.VSTA.VstaHelper.<CleanUp>b__1b()
   at Microsoft.SqlServer.IntegrationServices.VSTA.MtaExecution.Run(Action action)
   at Microsoft.SqlServer.IntegrationServices.VSTA.VstaHelper.CleanUp()
   at Microsoft.SqlServer.VSTAHosting.VSTAScriptingEngine.DisposeVstaHelper()
   at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.MigrateVSTA21ScriptProject(XmlElement elemProj, IDTSInfoEvents events)
   at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)
There are 4 packages of same version, i get this error only for 2 packages and other 2 am able to deploy successfully. Can someone tel mewhat would be the issue.
the same package is successfully deployed from my colleague machine.
Mano

Hi Manon,
According to the error message, the packages that cannot be deployed should include Script Task/Component. But the package that can be deployed without problem include Script Task/Component, right? If so, the issue should occur because certain Visual Studio
Tools for Applications (VSTA) Runtime has been installed:
Microsoft Visual Studio Tools for Application x64 Runtime3.0
Microsoft Visual Studio Tools for Application x86 Runtime3.0
You can check it from the Programs and Features panel. Then, you can install the exact VSTA Runtime from the
\redist\VSTA\runtime\ folder of the SQL Server install media.
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/776248/could-not-load-file-or-assembly-microsoft-visualstudio-tools-applications-core
Regards,
Mike Yin
TechNet Community Support

Error while running SSIS package from Integration service or via Job

Hi All,
I encounter the below error while running SSIS Package from Job or integration service. However on execution completes success fully while running from data tools. The issue occurs after migration to 2012 from 2oo5 dtsx. PFB the error.
SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by
the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
A buffer failed while allocating 10485760 bytes.
The system reports 26 percent memory load. There are 206110765056 bytes of physical memory with 150503776256 bytes.
free. There are 2147352576 bytes of virtual memory with 185106432 bytes free. The paging file has 208256339968 bytes with 145642921984 bytes free.
The package also runs successfully from other servers. This happens only in one of our server.seems like issue with some sql configuration.

Hi ,
Are you running using SQL Agent Job and Data tools on same server or different?
If it is executing fine using Data tools and failing with Job it might be User credentials issue.Try
to run Job with your credentials by using proxy .
Regards,
Prathy
Prathy K

Problem with execute SSIS package from stored procedure

Hi,
I would like to execute SSIS package from stored procedure. Therefore, I implemented sp which exec SSISDB.CATALOG.CREATE_EXECUTION method. When I try to test it from SSMS on remote server, I got error that
I was able to solve by adding “WITH EXECUTE AS …”. Then I got another error: The server principal "Domain\user" is not able to access the database "SSISDB" under the current security context. On Internet, I found a couple post that describe
how to access SSIS catalog (one of them by Ke Yang -
http://blogs.msdn.com/b/mattm/archive/2012/03/20/ssis-catalog-access-control-tips.aspx). It didn’t help. I’m still getting the error message.
How to debug this issue?
Any suggestion?
Thanks
SQL Server 2014 BI

SSMS does not propagate user credentials thus the error
Arthur
MyBlog
Twitter

Getting Error while Execute SSIS Package from Console Application

Dear All,
SSIS package working fine directly.
I got following error while execute SSIS package from C# console application.
The connection "{79D920D4-9229-46CA-9018-235B711F04D9}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
Cannot find the connection manager with ID "{79D920D4-9229-46CA-9018-235B711F04D9}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "OLE DB Destination.Connections[OleDbConnection]"
in the connection manager collection of "OLE DB Destination". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.
OLE DB Destination failed validation and returned error code 0xC004800B.
One or more component failed validation.
There were errors during task validation.
Code :
public static string RunDTSPackage()
Package pkg;
Application app;
DTSExecResult pkgResults;
Variables vars;
app = new Application();
pkg = app.LoadPackage(@"D:\WORK\Package.dtsx", null);
Microsoft.SqlServer.Dts.Runtime.DTSExecResult results = pkg.Execute();
I have recreate the application with again new connection in SSIS.
Still not working, Please provide solution if any one have.
DB : SQL Server 2008 R2
Thanks and regards,
Hardik Ramwani

The connection "{79D920D4-9229-46CA-9018-235B711F04D9}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
Cannot find the connection manager with ID "{79D920D4-9229-46CA-9018-235B711F04D9}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "OLE DB Destination.Connections[OleDbConnection]"
in the connection manager collection of "OLE DB Destination". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.
Are you sure that you are running the same package via .NET which works fine from Visual Studio?
By reading error message, I can say that you have copied OLEDB task from another package OR you have deleted one OLEDB connection manager. Now when package is run this task tries to use the connection manager and not found thus throws error message.
Open all OLEDB destination tasks and you find connection manager missing. Connection Manager name should be provided there
Cheers,
Vaibhav Chaudhari
MCSA - SQL Server 2012

Error executing SSIS packages from Agent

Hi All,
     I designed SSIS package that loads data from Oracle table to SQl server table along with loading data into Diension and fact tables using SSIS packages only. First I created all SSIS packages that loads data into Staging tables from
Oracle table in next level loading data into Dimension table and final level is loading data into Fact table. At lasts I created One master package there I'm calling all packages (Execute package task) differently.
Configuration type: Parent package configuration for All child packages. XML config for parent package.
When I execute SSIS package from BIDS data is loading up to Fact table. When I execute SSIS packages through Sql server agent ( Using File System Deployment)When I execute SSIS package from Sql server agent it is throwing an error message like
Message
Executed as user: . Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 10:45:10 PM Error: 2013-10-17 22:45:12.60
Code: 0xC00220E6     Source: Master Data      Description: There is no project to reference. End Error Error: 2013-10-17 22:45:12.61     Code: 0xC0024107     Source:
Master Data      Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:45:10 PM Finished: 10:45:13 PM Elapsed:
2.59 seconds. The package execution failed. The step failed.
I'm uploaded config file also while at the time of scheduling job.
Regards,
Praveen
Regards, Praveen

Hi Praveen,
The issue may occur if the SQL Server Agent Service Account or Proxy account doesn’t have sufficient permissions. Please create a SQL Server Agent Proxy account that has the permissions to execute the package and perform update operations on the SQL Server
fact tables.
Reference:
http://technet.microsoft.com/en-us/library/ms175834.aspx
Regards,
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

*Error executing SSIS Package from BPC 5.1*

All -
I'm trying to execute a perfectly working SSIS package from BPC 5.1. When I execute the package it instantly completes executing (Failure) with nothin written to the Log file.
After doing further analysis, we have found the root cause to be "Sequence Containers" in SSIS Packages. We can execute the same package if we remove the sequence container.
When we try to edit the SSIS package via BPC, containing the Sequence Containers", we receive the following error:
[QuerytoServer] An error occurred while getting a package information. System.InvalidCastException: Unable to cast object of type 'Microsoft.SqlServer.Dts.Runtime.Sequence' to type 'Microsoft.SqlServer.Dts.Runtime.TaskHost' at Osoft.Services.Application.DataMgr.PackageExecute.DTSX.GetPackageInfor()
When we try to edit SSIS packages via BPC, containing NO Sequence Containers", everything is wonderful.
Does anyone have any suggestions, besides removing all of the Sequence Containers and moving the tasks to the base SSIS package level?
I trully appreciate any help you guys can provide.

Hi Lars,
Could you be more specific the step you did?
1. It works fine in Visual Studio,
2. It is not working with Excel Front-end. Call the package from Excel.
3. It worked few days ago, ==> Do you mean it was working with #2 step?
I think this might be caused by authentication,
1. could you check your athentication you have for #1 and #2?
2. Did you introduce BPC DM to call the package? BPC DM uses impersonated ID even you use ID which has restrictive to use system resource, there will be no problem for the authentication.
3. As you see the log, it points FLOW task and OLEDB SOURCE, check your connection string in OLEDB SOURCE also.
Hope this helps,
Regards,
YH Seo

Executing an SSIS package from TSQL without using xp_cmdshell?

How can I execute an SSIS package from TSQL without using xp_cmdshell?
I have a web-app which calls some SQL which executes my SSIS package (a DTSX file, but stored in the server). But the security policy for my application won't permit me use to xp_cmdshell.
I want to do this:-
DECLARE @returncode int
EXEC @returncode = xp_cmdshell 'dtexec /sq pkgOne"'
Is there another way for executing a Package without going to the command line (e.g. is there some other system stored proc)?
Thanks

Whoa - don't go taking my words as saying "it should work". I never said that - I just said I know less than you :) I'm assuming that since the CLR is .Net, and you can launch a package from .Net code, you may be able to do so from the CLR.
But... I also know that CLR has lots of restrictions on it, and some of those may cause you to be unable to run it from the CLR.
One thing I will say - I've never heard of anyone doing this. That's got to tell you something about:
Whether it can be done at all... although I think I'd have heard/seen something about how it's not possible.
Whether it's a good idea... maybe other routes are less trouble.
Talk to me now on

When migrating ssis packages from 2005 to 2012 Activex Script Task component doesn't exist in 2012 version

Similar Messages

Maybe you are looking for