SSIS package with MODIFYSCRIPT problem

Hi guys,
I've created an SSIS package which had 2 variables: MODIFYSCRIPT with some commands and an Object variable to pass sql query data from one task to another.
The problem that I faced was that the MODIFYSCRIPT variable was totally ignored when I ran the package. In fact, MODIFYSCRIPT will work fine unless there is another variable of type Object, in other words, you seem to be unable to have Object variables in SSIS packages if you want to change dynamically the tasks' properties from BPC.
The only solution that I managed to find for the problem is to set a different namespace to the Object variable. Only in this case the MODIFYSCRIPT does changes to tasks' properties and the whole package works fine.
Is there any logical explanation for this problem?
Thanks.
Valera

Hi shylin,
Here is an example. Edit the package in SQL and add the following two lines to the MODIFYSCRIPT variable to run the AllConsol logic:
TASK(Execute formulas,LOGICMODE,1)
TASK(Execute formulas,LOGICFILE,%APPPATH%..AdminApp%APP%AllConsol.lgx)
Hope this helps,
Regards
SN..

Similar Messages

Problem Running SSIS Package with a SQL Server Agent

SQL Server: SQL Server 2012
VS: Visual Studio 2012
Hello,
      I have been having a problem running SSIS packages by using a SQL Server Agent job. I first created these SSIS packages in a separate IS project in Visual Studio. I imported the packages to the Integration Services (Package
Store) instance on my SQL Server and tried to create a job that would run them from there.
      At first I read around about needing a proxy account to allow the agent/packages to access the file system since these packages are importing data from a flat file in the SQL database. So I created a temporary admin user to
use as the user for the agent. I did this by going to Services.msc on the server and linked the account the agent's "logon as". Then arose another issue where I am getting an error about using the incorrect type for my connection managers.
The connection manager "TestFile" is an incorrect type. The type required is "OLEDB". The type available to the component is "FLATFILE". Source: Data Flow Task Flat File Destination [2]     Description:
Cannot open the datafile "O:\*****\Success.txt"
I am not sure what this even means as I am getting this error even with a test package that doesn't do anything with the database. I have just two flat file connection managers in this test project one for grabbing the source file and one for
creating the new test file.
I am not sure what to do.
Thanks in advance,
Matt

I accidently created two posts. The newest one has the details.
I did not mean to.
SQL Server: SQL Server 2012
VS: Visual Studio 2012
Hello,
      I have been having a problem running SSIS packages by using a SQL Server Agent job. I first created these SSIS packages in a separate IS project in Visual Studio. I imported the packages to the Integration Services (Package
Store) instance on my SQL Server and tried to create a job that would run them from there.
      At first I read around about needing a proxy account to allow the agent/packages to access the file system since these packages are importing data from a flat file in the SQL database. So I created a temporary admin user to
use as the user for the agent. I did this by going to Services.msc on the server and linked the account the agent's "logon as". Then arose another issue where I am getting an error about using the incorrect type for my connection managers.
The connection manager "TestFile" is an incorrect type. The type required is "OLEDB". The type available to the component is "FLATFILE". Source: Data Flow Task Flat File Destination [2]     Description:
Cannot open the datafile "O:\*****\Success.txt"
I am not sure what this even means as I am getting this error even with a test package that doesn't do anything with the database. I have just two flat file connection managers in this test project one for grabbing the source file and one for
creating the new test file.
I am not sure what to do.
Thanks in advance,
Matt

Can't change the connection string of SSIS package with derived columns?

We upgraded SQL server 2008 to 2012, copied and converted all SSIS packages from Visual Studio 2008 to 2010. When I opened a package in VS 2010 and tried to change the connection string, in the local connection managers, if the data source is another
SSIS package B(.dtsx file) with derived columns, I can't change the connection string of package B. When I opened the file connection manager editor for package B and tried to locate a dtsx file in another location, saved the change, reopened the project.
Package B still pointed to previous file. Other packages without derived columns work fine. Any thoughts?

We are using the package deployment model and refer to other packages in the same project. If
we changed the path of package B (with derived columns) to "D:\Visual Studio 2010\xxxx", and refer it in package A, in the A's connection manager, the connection string of package B is still its previous location "D:\Visual
Studio 2008\xxxx". When we ran the package A in the SQL server agent, the data source is still
"D:\Visual
Studio 2008\xxxx", so how can I change it to "D:\Visual
Studio 2010\xxxx"? Why has the package C (without derived columns) no such problem? thanks.

SSIS Package with Scheduled Task

Hi there,
We have on a SQL-Server some SSIS Packages which refers to Navision. If I start the job manually directly in Navision, it works fine. If I start the Job in MSSQL manually (SQL Server Agent --> Jobs --> 'MyJobPackage' --> Start Job at Setp) or through
the Job Activity Monitor ('MyJobPackage' --> Start Job at Step) it works also fine without any problems. But if the Job starts automatically (Scheduled Job in MSSQL) it will never end. So the Job is running endless. Now, we thought we could try to start
this SQL Job with a Scheduled Task in Windows. So I created a cmd-File with the following line:
dtexec /f "E:\SSIS Schnittstelle\TEST_Navision2XAPF\Navision2X.APF\bin\EGHU.dtsx" /De MyPassword
And then I get this errors:
C:\Users\exprma\Desktop>dtexec /f "E:\SSIS Schnittstelle\TEST_Navision2XAPF\Navision2X.APF\bin\EGHU.dtsx" /De MyPassword
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 10:17:44
Progress: 2014-03-12 10:17:45.32
   Source: Dimensionen
   Validating: 0% complete
End Progress
Error: 2014-03-12 10:17:45.34
   Code: 0xC0047062
   Source: Dimensionen Dimension [134]
   Description: System.Data.Odbc.OdbcException: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
   at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)
   at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle)
   at System.Data.Odbc.OdbcConnectionOpen..ctor(OdbcConnection outerConnection, OdbcConnectionString connectionOptions)
   at System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.Odbc.OdbcConnection.Open()
   at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
   at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
   at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
   at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error
Error: 2014-03-12 10:17:45.34
   Code: 0xC0047017
   Source: Dimensionen SSIS.Pipeline
   Description: component "Dimension" (134) failed validation and returned error code 0x80131937.
End Error
Progress: 2014-03-12 10:17:45.34
   Source: Dimensionen
   Validating: 4% complete
End Progress
Error: 2014-03-12 10:17:45.34
   Code: 0xC004700C
   Source: Dimensionen SSIS.Pipeline
   Description: One or more component failed validation.
End Error
Error: 2014-03-12 10:17:45.34
   Code: 0xC0024107
   Source: Dimensionen
   Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 10:17:44
Finished: 10:17:45
Elapsed: 0.999 seconds
So what could I try at the next step?
Regards
ÖFES

Hi Öfes,
Based on the error message when executing the package from batch file and the solution provided by Visakh, we can conclude that the package uses 32-bit ODBC drivers. Now let’s go back to the original SQL Server Agent job issue. Since you can run the job
manually from SSMS, the package should run in 32-bit SSIS runtime mode, e.g. the “Use 32 bit runtime” option should be checked for the package executions with in the job step. In this case, SSIS automatically uses the 32-bit DTExec utility, therefore, we don’t
need to specify the 32-bit DTExec utility in the command line for the job step.
Based on the current information, the issue may occur due to two possible factors:
The Dimension component in the package uses User DSN rather than System DSN.
The user account under which the job runs doesn’t have sufficient permissions to execute the package.
So, please try the following steps:
Open the C:\Windows\SysWOW646\odbcad32.exe, and make sure the DSN is a System DSN which can be accessed by any user on the server.
Create a new SQL Server Agent proxy account which has sufficient permissions to execute the package, for example, the user account that you execute the job manually from SSMS.
Reference:
http://technet.microsoft.com/en-us/library/ms190698(v=sql.105).aspx
Regards,
Mike Yin
TechNet Community Support

How to Create a SQL Agent Job For A SSIS Package with Sql Server Authentication

Hi ALl,
I have a SSIS package which basically has a data flow task in which i pull the data from one server and copy it into another server and my source server is the one where i dont have windows authentication and i have to only use a sql server authentication
. This package runs fine if i click the server connection properties type the password and save it.
Now, my task is to set up a sql agent job which basically uses a proxy account and takes this package from the file system and runs it.But when i try to run this package, its failing with an error saying
"Login Failed For rpt5user" where rpt5user is the username for my sql server authentication of the source connection.
Can someone please help me with any suggestions on how to do this?
I have heard that we can achieve it by using xml config file which i have never used and i am trying to google around but for no luck.
So, If someone can please throw any suggestions or ideas on this it would be great.
Thanks

You need to add password as a config item and set it from the file source or sql table
see this as an example
http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
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 with OData connection - can't connect

I need to read some data from a SP list. I have the OData connection manager setup. When I test the connection to my sharepoint site, it says it's successful. I added in a data flow task and then an OData Source. In the OData Source editor, I select the
Odata connection manager. I want to use a collection. However, it says "Unable to load collection for the connection Odata Source, reason: Cannot open this connection"
Anybody know how to resolve this?

Hi kayla,
Just as you said, the current
SharePoint List Adapter that extracting and loading SharePoint Data in SQL Server Integration Services supports x86/x64 systems using SQL 2005 / SQL 2008 / SQL 2008 R2/ SQL 2012. It doesn’t support SQL 2014. Maybe we need waiting the update.
The
OData Source component can be used to read data from SharePoint lists in SSIS 2014. Please download and install the 64 bit ODataSourceForSQLServer2014-amd64.msi or 32 bit ODataSourceForSQLServer2014-x86.msi from the
Microsoft® SQL Server® 2014 Feature Pack.
Reference:
Tutorial: Using the OData Source
Using the SSIS OData Source Connector to read data from SharePoint lists
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support
Hi Katherine,
I did install that already. I added the OData source to my SSIS package. The odata connection manager successfully connects to the sharepoint site. However, when I use the data source in the Odata Source within the Data Flow, it gives me the "cannot
open this connection" in the Collection list within the Odata source editor. I'm stumped as to why the connection manager has a successful test connection, but the collections don't pull up. Does the list need some special permissions? I'm able to access
it directly on the sharepoint site and add items (the odata connection manager is running with my windows credentials)

Running a SSIS package with SQL Job and Linked Server

I have a SSIS 2008 package. In one of the Script task I am calling a stored procedure which is using Openquery using linked server. I deployed this package with protection level as "EncryptWithPassword" and gave a password to the package.
Created a SQL job and edited its command line to include the password. If I login to SQL Server Mgmt Studio with Windows Authentication and run the job manually it runs fine. But when I schedule it then I get an error that "The Communication link to Linked
server failed".
Please help

Hi Vivek.B,
The issue should occur because the SQL Server Agent Service Account or SQL Agent Proxy account under which the job step runs doesn’t have sufficient permissions on the linked server.
If the job owner is the sysadmin fixed server role, the job can be run under the SQL Server Agent Service Account or a proxy account, then please make sure the SQL Agent Service Account or the proxy account has corresponding login on the linked server. If
the job owner is not a sysadmin fixed server role, the job must run under a proxy account. In this case, make sure the proxy account has a corresponding login on the linked server.
Reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
Regards,
Mike Yin
TechNet Community Support

Executing SSIS Package using C# problem

Hey,
I developed an WinForms App and SSIS package which I want to run using this App.\
I'm using folliwng script to run it:
using Microsoft.SqlServer.Dts.Runtime; class PackageExecutor
public string PackageFolder = ConfigurationManager.AppSettings["PackageFolder"];
Logger _logger = new Logger();
public void ExecutePackage(string location, string packagename)
Package pckg;
Microsoft.SqlServer.Dts.Runtime.Application app;
DTSExecResult pckgResult;
Variables vars;
app = new Microsoft.SqlServer.Dts.Runtime.Application();
pckg = app.LoadPackage(location, null);
vars = pckg.Variables;
vars["User::PckgConnection"].Value = ConfigurationManager.ConnectionStrings["SSIS"].ConnectionString;
pckgResult = pckg.Execute(null, vars, null, null, null);
if (pckgResult == DTSExecResult.Success)
MessageBox.Show("Wykonano poprawnie");
string msg = DateTime.Now.ToString() + " " + ExtensionMethods.LoginData.strUserName + " " + packagename + " Success";
_logger.WritePackageLog(msg);
else
string err = "";
foreach (Microsoft.SqlServer.Dts.Runtime.DtsError local_DtsError in pckg.Errors)
string error = local_DtsError.Description.ToString();
err = err + error;
MessageBox.Show("Wystąpił błąd więcej informacji w logu.");
string msg = DateTime.Now.ToString() + " " + ExtensionMethods.LoginData.strUserName + " " + packagename + " Failure with error: " + err;
_logger.WritePackageLog(msg);
This one works perfectly on my PC which have SSIS installed, however a client is reciving an error:
"An Integration Services class cannot be found. Make sure that Integration Services is correctly installed on the computer that is running the application. Also, make sure that the 64-bit version of Integration Services is installed if you are running
a 64-bit application".
Inside SSIS project I turned of "Run64BitRuntime".
I'm running on x64 bit windows with x32 SSIS installed, can't tell on what Windows (x32/x64) is client running. I can get that info if necessary.
Any idea how may I solve this? Point of everything was to run SSIS package placed on server on any machine without installing any additional software there.

You needed to do proof of concept before embarking on this design. There is no workaround, and each client needs to have a paid SQL Server license in this case
Arthur
MyBlog
Twitter

SSIS packages - Dynamic MODIFYSCRIPT :: SAP BPC 7.0 MS

Hi,
I want to know if it is possible to create a Dynamic MODIFYSCRIPT, so if the user selects a RADIOBUTTON option, the next SSIS screen will show or a SELECTINPUT with a specific selected member or a TEXT with a value.
The idea is that a parameter can change another in debug time.
Thanks in advance.

HI Lara,
Kindly go through the below link may be helpful
PROMPT(COMBOBOX... is a useful statement in DM advanced script to provide user selection of some text values that can be later used in script logic
DM PROMPT(COMBOBOX behavior in BPC NW 10 and 7.5
Shrikant

How can I troubleshoot an SSIS package with errors ?

I am testing a package which is a straightforward move from Oracle table-A to Oracle table-B
I have the header and table tables working fine, but the detail table is getting an error, with the errors not being helpful at all. The detail data flow has around 300+ columns, but the error doesn't say anything that points to the specific error. I
did review the warnings and found two columns that I needed to substring to be able to fit into the destination. But still getting an error.
A colleague said the error "The "input "OLE DB Destination Input" (4781)"
means this is for Column 4781 - but how do I find that ? We looked in Advanced Settings but the column ID's are all above 5000.
So how do I troubleshoot this ? In SSIS, I can only think to un-map 1/2 the columns, see if that works, then narrow it down from there. I can try to replicate the insert statement in Oracle but that's crazy, imo.
Here are the errors:
Error: 0xC0202009 at Load Detail Data, Caremark CET Claims Destination [4768]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x00040EDA.
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x00040EDA Description: "Multiple-step operation completed with one or more errors. Check each status value.".
Error: 0xC0209029 at Load Detail Data, Caremark CET Claims Destination [4768]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (4781)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (4781)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.
Error: 0xC0047022 at Load Detail Data, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Caremark CET Claims Destination" (4768) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (4781). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
Error: 0xC02020C4 at Load Detail Data, Argus PCT Claiims Source [5281]: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
Error: 0xC0047038 at Load Detail Data, SSIS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Argus PCT Claiims Source" (5281) 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.

I figured out the error outside of SSIS, by trying to insert the data directly in Oracle ("insert into [my_dest_table select * from [my_source_table"), and that showed me the error (trying to insert varchar-2 into varchar-1). so I corrected and got my package
working.
Basic takeaway is the error messages don't tell you anything. It seems like the Oracle error would be readable by Sql Server/SSIS and so it would write that in the log.
So I basically did your "1>" suggestion and that worked.
I would like to do "3>" but don't know how . . . if you can point me in the right direction I could probably figure it out, I have a couple of books and I have colleagues whom I can ask.
thanks !

Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

Hi,
how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
This question has worried me for days.
Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
Or just an new solution instead of using the catalog.deploy_project?
best wishes from Qingyuan Lee.

Sorry, my description may be confusable.
I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
In fact, I don't care about the authority.
I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
so, using EXECUTE AS to change the execution context is accaptable.
The requirement for a Windows Authentication Account makes sense.
I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
Thanks very much for your help.

How Can I Kill Excel.exe Process After finish my Execution of SSIS Package in Sqlserver2008r2

Hi !,
am new for c# and SSIS Package Creation , I am Trying to Read Excel file, and load the value into Sqlserver using SSIS package . My Problem is , After Execution of SSIS package Still Running EXCEL.exe Process in my server. i need to
kill that process . I post my Code Exactly where am release my excel file object , please guide me where am going to wrong?
Server Configuration
OS:windows7
SqlServer :2008r2
Framework:3.5
please give me some suggestion to correct my error .
Here is My Code:
Microsoft.Office.Interop.Excel.Application xlApp;
Microsoft.Office.Interop.Excel.Workbook xlWorkBook;
Microsoft.Office.Interop.Excel.Worksheet xlWorkSheet;
var missing = System.Reflection.Missing.Value;
xlApp = new Microsoft.Office.Interop.Excel.Application();
xlWorkBook = xlApp.Workbooks.Open(filename, false, true, missing, missing, missing, true, Microsoft.Office.Interop.Excel.XlPlatform.xlWindows, '\t', false, false, 0, false, true, 0);
xlWorkSheet = (Microsoft.Office.Interop.Excel.Worksheet)xlWorkBook.Worksheets.get_Item(1);
Microsoft.Office.Interop.Excel.Range xlRange = xlWorkSheet.UsedRange;
Array myValues = (Array)xlRange.Cells.Value2;
int vertical = myValues.GetLength(0);
int horizontal = myValues.GetLength(1);
System.Data.DataTable dt = new System.Data.DataTable();
bool isNameRead = false;
// get header information
for (int i = 1; i <= horizontal; i++)
string cellValue1 = "";
object cellObj = myValues.GetValue(1, i);
if (cellObj != null)
cellValue1 = myValues.GetValue(1, i).ToString();
if (cellValue1 == "Name")
if (!isNameRead)
dt.Columns.Add(new DataColumn(cellValue1));
isNameRead = true;
else
dt.Columns.Add(new DataColumn(cellValue1 + 1));
isNameRead = false;
else
dt.Columns.Add(new DataColumn(cellValue1));
// Get the row information
for (int a = 2; a <= vertical; a++)
//string cellrowvalue = "";
string isemt = "";
object[] poop = new object[horizontal];
for (int b = 1; b <= horizontal; b++)
isemt =(string) myValues.GetValue(a, b);
if (isemt != null)
poop[b - 1] = myValues.GetValue(a, b);
DataRow row = dt.NewRow();
row.ItemArray = poop;
dt.Rows.Add(row);
xlWorkBook.Close(true, missing, missing);
xlApp.Quit();
releaseObject(xlWorkSheet);
releaseObject(xlWorkBook);
releaseObject(xlApp);
return dt;
releaseObject
private void releaseObject(object obj)
try
System.Runtime.InteropServices.Marshal.ReleaseComObject(obj);
obj = null;
catch (Exception ex)
obj = null;
MessageBox.Show("Unable to release the Object " + ex.ToString());
finally
GC.Collect();
GC.WaitForPendingFinalizers();
GC.Collect();
GC.WaitForPendingFinalizers();
Thanks
Parthasarathi Purushothaman

Why are you programmatically opening an Excel sheet in C# instead of using the DataFlow task with an Excel input?
Since your task is programmatically starting Excel via "new Microsoft.Office.Interop.Excel.Application();", it is your responsibility to stop it.
Please see "Quit":
http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel._application.quit(v=office.15).aspx

Copy SSIS Packages

Can we copy all SSIS packages with folder structure from one SQL Server to another SQL Server ? is it can be done by SSIS packge or Sp

I had no problem copy/paste the SSIS folder to another server (SQL Server 2012), open it, change a connection string (in terms that is same database structure) and just deployed it.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Error While executing a SSIS package which contains a script task through SQL Server Agent job

Hi,
I have a SQL Server 2012 SSIS package with a script task along with other tasks [data flow, execute sql tasks ]. When I manually executed the job through BIDS, its completed successfully.
Then I have automated the execution of the package through SQL Server Agent Job. But when I executed the package through SQL Agent job, it runs successfully for all the tasks except script task. When it comes to execute the Script Task, it is getting failed
with the below error message.
"Error: 2012-08-29 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
I have installed the SSIS on the 64-bit environment and SSIS service is running. Also I tried to run the job through 32 bit [job option] but I am getting the above error in all cases.
Any help will be greatly appreaciated !
Thanks,
Navin
- naveen.reddy

Hi Arthur,
My script task access the excel files in a network share, refresh them all and save them. When I execute the ETL manually or thru DTEXEC, it is executing successfully. I am facing the issue when I am executing thru SQL Agent Job only. Logging also showing
the same error.
"Error: 2012-08-23 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
- naveen.reddy

How to create a dynamic SSIS package for multiple flat file destinations

Hi,
I have to create a ssis package which has single data flow task and inside that I have 23 source (sql- select * from - statements)- destination (flat files, 23 distinct) connection.
Now for each product I have to create separate SSIS package (i.e. if prod=abc then these read select * from abc_tables and 23 abc_ txt files)
I want to do it dynamically, means only single package and inside that variables will take select * values for each source-dest connection (so i believe 23 variables) and same for destination flat files.
Let me know. :)
ANK HIT - if reply helps, please mark it as ANSWER or helpful post

Sorry It seems you're contradicting yourself. you say I know my source and dest structure and the you're
asking all I want is to have a dynamic structure
what does that mean?
and reading your next sentence
I want to run a package for 5 products, instead of creating 5 ssis packages with 23 source- dest connection, I would
like to have one with only 23 source- dest connections
What I feel is what you're looking for is to have a looping structure to loop through each of the 5
products.
In that case what you could do is this
1. Create a object variable in SSIS
2. Use a Execute SQL Task to populate the variable with all available products (I think you'll have a master table for that). Set ResultSet property to Full ResultSet and then in ResultSet tab map Object variable to 0 th index
3. use a ForEachLoop container with ADO .NET recordset enumerator and map to object variable. Create a variable of datatype same as that of Product identifier field to get individual values out
4. Inside loop create your data flow task with 23 source destination connection. In the query part use a parameter for product field and map it to the variable containing product value to get only data for the product.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS package with MODIFYSCRIPT problem

Similar Messages

Maybe you are looking for