Hello,

I would be very glad to know about the design Solution mentioned below:

We are probably going to have packages that refresh all the master data views for a region.  This means we’ll be processing maybe 15-20 tables in a single package.  If we have a failure on a single view/table, do we have the ability to log an error message and go on to the next step?  If so, can we keep count and abort if we get errors on more than a couple of views?  Or is this going to introduce too much complexity?

Regards

Ravi

RaviRocks

SQL Server 2008 R2, VS 2008, XL 2003

I think I know the answer to this based on testing but I was wondering if anyone can confirm if there is a maximum excel sheet name length when loading from MS Excel worksheets?

As an example, I have a package that dynamically creates a variable which forms something like the following:

SELECT * FROM [Cybil Extract CapAd - Singapore$A2:AL]

that fails even though the worksheet name is correct

If I change the worksheet name to Cybil Extract CapAd- Singapore (i.e. remove 1 space), it works fine. Doesn;t matter which character I change / add - the linit seems to be 30 characters...

Hello,
In ssis I am using the database connection manager to be used inside script task.
The property of this connection manager is as follows where DBName I altered here as it refers to databasename

Data Source=.;Initial Catalog=DBName;Integrated Security=True;MultipleActiveResultSets=True;Application Name=SSIS-Name-{3D23E648-1111-40AA-222F-7E054C32180B}DBConn;

Question:
I would like to change the DBName to be a variable instead of it being hardcoded.
So I created a string variable and named it DBName and assigned to it the name of the database i.e. "databaseName"

Then In the DBName connection manager, I went to properties, selected expression and then connectionstring. In there I placed the above line but replaced the hardcoded database name to my variable i.e. @[User::DBName]
But I get an error that it constains invalid token

what is the best way to do what I want here please?

in script task at present I am using:

SqlConnection)(Dts.Connections["DBConn"].AcquireConnection(Dts.Transaction)asSqlConnection);

Thank you

Hi guys, I've got a package that, among other tasks, trigger a .bat file which trigger an .exe file. It does work if I run from my machine but it doesn't work if I run from Agent. No error retrieved but the file .bat doesn't trigger the .exe .

Besides when I run the package from my machine it shows me the dos with the code...and I am guessing if server side is this allowed or not. I mean to run the .bat file.

Any suggestion? Thanks

The bug occurs in the package designer Data Flow when executing a child package from a parent package using an Execute Package Task.

SSIS 2014 child packages shows 0 rows in data flow tasks. This bug occurs when executing child packages from a parent in designer mode. It shows 0 rows in data flow but progress is being updated with correct number of rows. I have tested this on both VS2013 + VS2015 but no change.

Anyone knows any workaround.

I'm not sure where to post this, but anyone else notice how utterly unusable the SSIS designer is when you're working on an item inside a sequence container on SSDT - BI for VS2015? 

1) create a sequence container
2) create an object inside that container, could be an EXECUTE SQL task, could be EXECUTE PACKAGE task, doesn't matter
3) try to click on that execute SQL task or double click it.  

the designer will immediately fly off to some blank part of the canvas far away.  This makes it VERY VERY difficult to work on things.  One has to find the spot on the canvas again, right click on the task, click EDIT and then mess with it that way otherwise it will just keep flying off to an empty part of the canvas.  Trying to move things around inside of that sequence container?  Forget about it.  Does the same flying around crap.  

So, my questions...

1) is this a known problem?

2) is there a fix for this problem?

3) if not a known problem, where would one post this one?  Is it an SSIS thing?  A visual studio thing?  A tools thing?

4) anyone know of some crazy workaround like unchecking the "jerk the screen to center when clicking anything" checkbox or something obvious?

SSIS is pretty flipping hard to work with for my current project when there are dozens of sequence containers and the GUI keeps jerking my screen around for doing nothing other than clicking on a task inside a sequence container.

John Nelson #2

I have an Excel source (in SSIS Data flow) with one worksheet in it , and it is configured as "SQL Command from Variable".

The variable has the Select Query to retrieve column data from the worksheet.

We usually get one file each day.

The previous files work fine in the SSIS package, but the latest ones - are throwing the following error - 

"The SQL command requires 25 parameters, but the parameter mapping only has 0 parameters"

What is causing this ?

Hi Can someone please help me -

 Scenario - Simple Data load from OLEDB Source to OLEDB Destination , Using SSIS 2012 I ma trying to insert into an oracle table residing externally on cloud while accessing this table via a local view ( using DB link) for OLEDB Destination

So    Source : OLEDB Local Oracle Table  

        Destination    : Local view ( connecting external oracle table via DB link)

        Provider used : Oracle OLEDB Provider

1. I can insert into the External Table using the Local view on SQL Dev (so no access issue / connectivity issue here ,I pesume )

2. When destination table is pointed to Local Oracle DB , SSIS I/F runs fine.

3. However when SSIS tries to load to external table , I am getting below error -

OLEDB_DST <my Table> [36]] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.

An OLE DB record is available.  Source: "OraOLEDB"  Hresult: 0x80004005  Description: "ORA-22816: unsupported feature with RETURNING clause".

[OLEDB_DST <my Table> [36]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.  The "OLEDB_DST <my Table>.Inputs[OLE DB Destination Input]" failed because error code 0xC020907B occurred, and the error row disposition on "OLEDB_DST<my Table>.Inputs[OLE DB Destination Input]" 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.

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "OLEDB_DST <my Table>" (36) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (49). 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.

Please can some one help.

Hello, folks!

Yesterday, I ran an SSIS package that has been working flawlessly in VS2008. But, when I try to run it in VS2013, I get the following warning;

Found SQL Server Integration Services 2008 Script Task "[insert task ID here]" that requires migration!

I've looked over the script and can't see what may be the problem. For your assistance, I will post it below;

/*
   Microsoft SQL Server Integration Services Script Task
   Write scripts using Microsoft Visual C# 2008.
   The ScriptMain is the entry point class of the script.
*/

using System;
using System.Data;
using Microsoft.SqlServer.Dts.Runtime;
using System.Windows.Forms;

namespace ST_1276eec7c49c484a9baf0e534b3e18ac.csproj
{
    [System.AddIn.AddIn("ScriptMain", Version = "1.0", Publisher = "", Description = "")]
    public partial class ScriptMain : Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTARTScriptObjectModelBase
    {

        #region VSTA generated code
        enum ScriptResults
        {
            Success = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success,
            Failure = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure
        };
        #endregion

        /*
		The execution engine calls this method when the task executes.
		To access the object model, use the Dts property. Connections, variables, events,
		and logging features are available as members of the Dts property as shown in the following examples.

		To reference a variable, call Dts.Variables["MyCaseSensitiveVariableName"].Value;
		To post a log entry, call Dts.Log("This is my log text", 999, null);
		To fire an event, call Dts.Events.FireInformation(99, "test", "hit the help message", "", 0, true);

		To use the connections collection use something like the following:
		ConnectionManager cm = Dts.Connections.Add("OLEDB");
		cm.ConnectionString = "Data Source=localhost;Initial Catalog=AdventureWorks;Provider=SQLNCLI10;Integrated Security=SSPI;Auto Translate=False;";

		Before returning from this method, set the value of Dts.TaskResult to indicate success or failure.

		To open Help, press F1.
	*/

        public void Main()
        {
            // TODO: Add your code here
            string[] files = System.IO.Directory.GetFiles(@"\\Path\", "Filename *.xlsx");
            string oldestFileName = string.Empty;
            DateTime oldestDate = DateTime.MaxValue;
            foreach (string file in files)
            {
                string fileNameWithoutExtension = System.IO.Path.GetFileNameWithoutExtension(file);
                string datepart = fileNameWithoutExtension.Substring(fileNameWithoutExtension.Length - 10);
                string convdate = datepart.Substring(0, 4) + datepart.Substring(5, 2) + datepart.Substring(8, 2);
                DateTime dt = DateTime.ParseExact(convdate, "yyyyMMdd", System.Globalization.CultureInfo.InvariantCulture);
                if (dt < oldestDate)
                {
                    oldestFileName = file;
                    oldestDate = dt;
                }
            }

            Dts.Variables["User::Variable"].Value = oldestFileName;
            Dts.TaskResult = (int)ScriptResults.Success;
        }
    }
}

All this code does is grab the date of an imported Excel file from the file's filename. Doesn't seem to be all that big a deal.

I see where the script says "Microsoft Visual C# 2008" in the leading comments, but it is - well - a comment, not something executable.

All I can think of is that, perhaps, the C# code compiler has changed for VS2013 and that there might be a command that is not compatible, but I don't know.

Any ideas out there?

Thanx!

Hello,
I am using execute sql task (EST) to execute sp.
At present the connection is set to the one in connection manager so it is hard coded.
I have a variable called DBName and assigned to it "localhost.databasename"

Question:

How is it possible to set the connection property of the EST to the variable DBName.
I did go to expression of the EST and assigned connection to DBName but it says connection manager DBName does not exist

I'm having an OLEDB provider issue in an SSIS package where the source file is an Excel 2013 64 bit file. The following is a breakdown of the environment I am working in:

OS: Windows Server 2012 R2 Standard 64 bit
Excel: 2013 64 bit
Visual Studio Community 2015 version 14.0.25425.01 Update 3
SQL Server 2016 Management Studio
SQL Server database instance is 2016(RTM) 13.0.1601.5 x64 Standard Edition

The problem has shown up in the SSIS package and with the Import/Export wizard. I have the 32 bit and 64 bit versions of the wizard. Using the 64 bit version, I have been able to import the worksheet I need from the Excel file into a table, without issues. The package I created was created from the Import/Export wizard.

The SSIS project's Run64BitRuntime property is set to 'true'. In the package, the Excel connection manager is configured to Excel 2013.  The package runs without issue, but when I try to view the columns from the Excel Source Editor, I cannot view the columns, and I receive the following error message:

'The requested OLE DB provider Microsoft.ACE.OLEDB.15.0 is not registered. I fthe 32-bit driver is not installed, run the package in 64-bit mode.'

In the research I've done, one idea to fix the issue was to install the 64 bit Microsoft Access Runtime. I've done this, but I still have the problem.

What other steps should I take?

Thank you for your help.

Hi,

We have different paths on different servers for holding packages.

Say on WorkStation, it is C:\\SSIS\

On DEV, it may be D:\Packages\

On Test, it may be E:\TestPackages etc.

Management doesn't want to use environment variables to hold the path of config files. They don't want to open package as XML to update the paths of Config files in dts package.

What are the options for us to have config files for packages and not touch the package. No batch file execution of package. We use SQL Agent job to execute package.

Thank You

Hi,

Planning to have one .dtsconfig file for all connections to all databases and use it in all packages like this

<DTSConfiguration>
 <Configuration ConfiguredType="Property" Path="\Package.Connections[cn1].Properties[ConnectionString]" ValueType="String">
    <ConfiguredValue>Data Source=localhost;Initial Catalog=dbA;Provider=SQLNCLI11.1;Integrated Security=SSPI;Auto Translate=False;</ConfiguredValue>
   </Configuration>
 <Configuration ConfiguredType="Property" Path="\Package.Connections[cn2].Properties[ConnectionString]" ValueType="String">
    <ConfiguredValue>Data Source=localhost;Initial Catalog=dbB;Provider=SQLNCLI11.1;Integrated Security=SSPI;Auto Translate=False;</ConfiguredValue>
   </Configuration>
 <Configuration ConfiguredType="Property" Path="\Package.Connections[cn3].Properties[ConnectionString]" ValueType="String">
    <ConfiguredValue>Data Source=localhost;Initial Catalog=dbC;Provider=SQLNCLI11.1;Integrated Security=SSPI;Auto Translate=False;</ConfiguredValue>
   </Configuration>
</DTSConfiguration>

Package 1 has only cn1 connection manager.

Package 2 has only cn2 connection manager etc.

When I run package 1, everything works fine but in logs, I see that

Error:

The connection "cn2" is not found. This error is thrown by Connections collection when the specific connection element is not found.

The connection "cn3" is not found. This error is thrown by Connections collection when the specific connection element is not found.

How can I have only one xml config file for all database connections. I was to use this config file by all packages.

Thanks,

I have two sequence containers “A” and “B” in package “Z”. They run from a preceding expression task which sets a variable value. Depending on the value set in the expression task:

1.       Only “A” sequence container can run.
2.       Both “A” and “B” sequence containers can run in parallel.

 Next, there is an Execute SQL task “C” that follows immediately afterwards. It is the “constrained executable” which follows “A” and “B”. If both “A” and “B” are determined to run, they must both finish (“success”) before “C” runs.  In the constraint editor for precedence constraints for the constrained executable “C” we use a logical “AND” to ensure that is what occurs.  How do we get “C” to execute if only “A” is executed.   The logical “AND” keeps “C” from executing if “B” doesn’t execute. Which is a condition  we may optionally want.  Can we dynamically alter the constraints “LogicalAnd” propert y, depending on the variable value?    Am I missing something? Am I going down a fruitless rabbit hole for trying to alter the constraints at run time?  thanks Michael

Hi,

I have the SSIS 2012 package runs okay. After deploy it to the SSISDB under SQL Server 2012 as ssisadm and public role.

The package export the data from another server which run SQL 2008 to Excel.

The package run failed:  

Combine to one  Excel:Error: There were errors during task validation.
Combine to one  Excel:Error: One or more component failed validation.
Combine to one Excel:Error: Excel Destination failed validation and returned error code 0xC020801C.Combine to one IAPRO Excel:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager IAPRO Des" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

ThPackage:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available.  Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005  Description: "The Microsoft Office Access database engine cannot open or write to the file '\...\TEST.xlsx'. It is already opened exclusively by another user, or you need permission to view and write its data.".  

Thanks for any idea.

Daphne

Good day

I've tried to run my package through the command line using `dtexec /f Package.dtsx /ConfigFile debug.dtsConfig /Decrypt ######`.

When I set the security mode, I generate my dtsConfig file that results in:

<?xml version="1.0" encoding="UTF-8"?><DTSConfiguration><DTSConfigurationHeading><DTSConfigurationFileInfo GeneratedBy="INFOTECH-CARIB\dclarke" GeneratedFromPackageName="Package" GeneratedFromPackageID="{1F85FCBF-3B69-4958-8D3A-CABC59BAC841}" GeneratedDate="10/14/2016 7:10:59 PM" /></DTSConfigurationHeading><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[ConnectionString]" ValueType="String"><ConfiguredValue>Data Source=tcp:sssssssssss.database.windows.net,1433;User ID=blah@ssssssssssssssssss;Initial Catalog=blah_test;Provider=SQLNCLI11.1;Persist Security Info=True;database=blah_test;encrypt=yes;trustservercertificate=no;connection timeout=30;</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[Description]" ValueType="String"><ConfiguredValue /></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[InitialCatalog]" ValueType="String"><ConfiguredValue>blah_test</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[Name]" ValueType="String"><ConfiguredValue>idb</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[Password]" ValueType="String"><ConfiguredValue /></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[ProtectionLevel]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[RetainSameConnection]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[Scope]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[ServerName]" ValueType="String"><ConfiguredValue>tcp:ssssssssssssssss.database.windows.net,1433</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[idb].Properties[UserName]" ValueType="String"><ConfiguredValue>ssssssssss@ssssssssssss</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[ConnectionString]" ValueType="String"><ConfiguredValue>Data Source=ICWKS-022\SQLEXPRESS;User ID=;Initial Catalog=test;Provider=SQLNCLI11.1;Integrated Security=SSPI;Auto Translate=False;</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[Description]" ValueType="String"><ConfiguredValue /></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[InitialCatalog]" ValueType="String"><ConfiguredValue>test</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[Name]" ValueType="String"><ConfiguredValue>test</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[Password]" ValueType="String"><ConfiguredValue /></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[ProtectionLevel]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[RetainSameConnection]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[Scope]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[ServerName]" ValueType="String"><ConfiguredValue>ICWKS-022\SQLEXPRESS</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[portaldb].Properties[UserName]" ValueType="String"><ConfiguredValue /></Configuration></DTSConfiguration>

However, when I try to run it using the command line option mentioned above, I get:

Rafael Marvila IT Profissional