Quantcast
Channel: SQL Server Integration Services forum
Viewing all 24688 articles
Browse latest View live

Warning 0x80049304 Data Flow Task 1: Could not open Global Shared Memory to communicate with Performance DLL

0
0

Hello Everyone,

Hope this post finds you well. The attached issue occurred during an import process. Here's the steps I took ingeneral.

DB1 - collation Latin1_General_CI_AS & DB2 - collation SQL_Latin1_General_CP1_CI_AS

1. Generated scripts from DB1 to create new database. selected FT Index and Triggers to script and chose not to script collation.

2. Created new DB named DB2 (collation SQL_Latin1_General_CP1_CI_AS).

3. Disabled foreign key constraints - set simple recovery across the board.

4. Right clicked on new db and chose import data (copy data from one or more tables and views).

5. Edit mappings: checked identity insert and drop and recreate tables.

6. Unchecked all DB views.

7. Launched process.

It reported that it ran successfully except for the attached error under Validating.

I noticed that the mdf and ndf (FText) files were significantly smaller than the original db. I did a data compare and lots of data did not come over. I did this same import in our development environment. Exact versions of SQL Server etc. The only difference between this environment and our development environment is that this one is physical and dev is virtual.

The closest article our there I've seen on the issue is the one I attached at the top. I am thinking there is a problem with the SSIS install on this server. I am going to try the same task on the second node to see if that error occurs.

https://www.reddit.com/r/SQL/comments/2x9hke/ms_sql_import_wizard_truncation_erorrs/

Warning 0x80049304 Data Flow Task 1: Could not open Global Shared Memory to communicate with Performance DLL


A SQL Server MVP or MSFT Eng should be replying soon as well. Hope this helps. Frank Garcia *** Please select "Vote As Helpful" if the information provided was helpful to you. If an answer to your issue solved the problem then please mark it as"Propose As Answer" located at the bottom. Thank you. ***


Object reference not set to an instance of an object.

0
0

I am getting following error when I was trying to run the SSIS packages. I did checked the connections and input and desitnation columns, everything looks perfect. but it throwing an error. could some one help me to solve this error.

Deploy an enhanced SSIS Package out to the Integration Services Catalog

0
0

So first our environment background.

A separate SQL Server for our SSIS Objects and SQL Server Agent for running scheduled SSIS jobs as SQL Server 2012 (SQL Server 11.0.2100)

SSIS Development using Microsoft Visual Studio Professional 2012

So the Integration Services Catalogssits out on the aforementioned SQL Server we use for our SSIS packages and running our jobs. And underneathIntegration Services Catalogsis a catalog namedSSISDB. Our folder structure is by client.

Now our environment is somewhat restrictive but not all the way. Meaning as a developer I can create our client folders within theSSISDB catalog which in turn dynamically creates the Projects and Environments sub-folders. And as a developer I can<Right-Click> on the Projects folder and chooseImport Packages...

So my client folder and Project and Package have already been created by me as the developer. However, our "controlling" DBA insists on creating the SQL Server Agent Job.

Soooo this is actually a two-part question.

  1. Since I have access to the Integration Services Catalogsand the Projects and Packages, and in order to deploy a very simple SSIS enhancement, can I simply Delete the current project and then re-Import Packages...? Is there any physical thread per se within the definedSQL Server Agent Job that will break? Or will it all be good just as long as I ensure the Project and Package that I re-deploy are named the EXACT same so that the SQL Server Agent Job picks it up and runs it correctly.
  2. Is it a better practice to deploy SSIS Packages on the Microsoft SQL Server Management Studio side or from the Microsoft Visual Studio side. My feeling is the less moving parts the better which is why I deploy SSIS using Microsoft SQL Server Management Studio.

Thanks for your review and am hopeful for a reply.

I'm getting these warning when I try to start the debugging. I built an Windows Form application where execute the dtsx.

0
0

When I run the dtsx in the local machine the result is SUCCESS but when I run the Windows Form Application the result is Failure.

My system is:

  1. Processor: Intel Core I5 3210M CPU @ 2.50Ghz
  2. Memory: 8GB
  3. OS: Windows 10 x64

I tried many ways to fix it:

  1. Add different versions of Microsoft.SqlServer.ManagedDTS in the References section any without luck.

  2. Add in App.config the line: startup useLegacyV2RuntimeActivationPolicy="true"

  3. Add and Reinstall SQL 2014 Client Tool SDK features.

  4. Add more Features to Visual Studio 2015.

  5. Platform target to: Any CPU, x86 and x64 any without luck.

  6. I did a lot of research.

  7. Deleting the /bin and /obj folders.

Warnings:

Severity    Code    Description Line    Suppression State
Warning     Referenced assembly 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\Microsoft.SqlServer.Msxml6_interop\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.Msxml6_interop.dll' targets a different processor than the application. C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets    3505
Warning     Referenced assembly '\\tsclient\C\Program Files (x86)\Microsoft SQL Server\120\SDK\Assemblies\Microsoft.SqlServer.DTSRuntimeWrap.dll' targets a different processor than the application. C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets   3505
Warning     Found conflicts between different versions of the same dependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed. C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets 1819

frmSSIS:

using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using System.Windows.Forms;
using Microsoft.SqlServer.Dts.Runtime;

namespace alerts_operations
{
    public partial class frmSSIS : Form
    {
        public frmSSIS()
        {
            InitializeComponent();
        }

        private void btnExit_Click(object sender, EventArgs e)
        {
            this.Close();
        }

        private void label1_Click(object sender, EventArgs e)
        {

        }

        private void btnFTP_Click(object sender, EventArgs e)
        {
            Microsoft.SqlServer.Dts.Runtime.Application myApplication = new Microsoft.SqlServer.Dts.Runtime.Application();

            //Package myPackage = myApplication.LoadPackage(@"C:\ftp_extract.dtsx", null);
            Microsoft.SqlServer.Dts.Runtime.Package myPackage = myApplication.LoadPackage(@"V:\ftp_extract.dtsx",null);

            lblStatus.Text = "Executing package...";

            Microsoft.SqlServer.Dts.Runtime.DTSExecResult myResult = myPackage.Execute();

            // Show the execution result

            lblStatus.Text = "Package result: " + myResult.ToString();
        }
    }
}

Build Log:

'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities\14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities.Sync\14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\14.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'Z:\ACOLON\Projects\operations\operations\bin\Debug\operations.vshost.exe'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.Extensions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Deployment\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Net.Http\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Net.Http.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread 0x2348 has exited with code 0 (0x0).
The thread 0x1c24 has exited with code 0 (0x0).
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'Z:\ACOLON\Projects\operations\operations\bin\Debug\operations.exe'. Symbols loaded.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.ManagedDTS.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\Microsoft.SqlServer.DTSRuntimeWrap\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.DTSRuntimeWrap.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Diagnostics.STrace\12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.Diagnostics.STrace.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.SqlServer.ScriptTask\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.ScriptTask.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.SqlServer.VSTAScriptingLib\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.VSTAScriptingLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\Microsoft.SqlServer.Msxml6_interop\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.Msxml6_interop.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.SqlServer.DtsMsg\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.DtsMsg.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.SqlServer.ExecProcTask\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.ExecProcTask.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\Microsoft.SqlServer.SQLTask\v4.0_12.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.SQLTask.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'ST_9d880699f696403b9ab1169dab706d45'. Module was built without symbols.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.PowerShell.Commands.Diagnostics\v4.0_3.0.0.0__31bf3856ad364e35\Microsoft.PowerShell.Commands.Diagnostics.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Configuration.Install\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.Install.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.PowerShell.ConsoleHost\v4.0_3.0.0.0__31bf3856ad364e35\Microsoft.PowerShell.ConsoleHost.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.PowerShell.Commands.Utility\v4.0_3.0.0.0__31bf3856ad364e35\Microsoft.PowerShell.Commands.Utility.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.PowerShell.Commands.Management\v4.0_3.0.0.0__31bf3856ad364e35\Microsoft.PowerShell.Commands.Management.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.PowerShell.Security\v4.0_3.0.0.0__31bf3856ad364e35\Microsoft.PowerShell.Security.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Microsoft.WSMan.Management\v4.0_3.0.0.0__31bf3856ad364e35\Microsoft.WSMan.Management.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'Anonymously Hosted DynamicMethods Assembly'.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Diagnostics.Tracing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Diagnostics.Tracing.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread 0x7e0 has exited with code 0 (0x0).
'operations.vshost.exe' (CLR v4.0.30319: operations.vshost.exe): Loaded 'ST_c01711d8321445bcbe1c4f5abc4dee25'. Module was built without symbols.
The thread 0x246c has exited with code 0 (0x0).
The thread 0x54 has exited with code 0 (0x0).
The thread 0x1df0 has exited with code 0 (0x0).
The program '[7748] operations.vshost.exe' has exited with code 0 (0x0).

Any other alternative, options or suggestion to fix this?

Configure SSIS Package with Environment variables

0
0

While Configuring SSIS Project on Environment Variable match, the drop down list is a mess, especially when you have a long list of vaiables, it is very hard to locate the one you need.

Anyone knows any solution?

It won't allow me to post screen shot, not sure how to validate my account.

Validation Failing

0
0

I can run this successfully once but it's not formatting the resultant text correctly. the next time I try to run the code I get a list of all of the columns and an error:

The external column "MFG Deal Name TWO" (817) needs to be removed from the external columns.

for each column. 

Error: 0xC004706B at Data Flow Task, SSIS.Pipeline: "component "OLE DB Source" (724)" failed validation and returned validation status "VS_NEEDSNEWMETADATA".

Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.

Error: 0xC0024107 at Data Flow Task: There were errors during task validation.

SSIS package "PMFridayRepeat.dtsx" finished: Failure.

How should I correct this?  I've tried removing the external columns, deleting and creating the Flat File Destination from scratch. Right now my OLE DB Source object is red.

TIA

Harry

Is it risky to have a high frequency batch process?

0
0
There is a job that I keep getting asked to run. It would make everybody's life easier if that job just ran every five minutes. I hesitate to do that because that just doesn't seem like a good idea but I have no real reason. The process is pretty healthy and rarely fails. If I up the schedule to every five minutes during business hours, what kind of nonsense am I asking for?

SQL Express 2012 - SSIS package

0
0

Hello everyone,

I've Windows 2012 R2 server with SQL Express 2012.

I would like to setup a package here on this server that will read the data from CSV file and insert the same into SWL Express 2012 database.

Please advise. 



Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com


Error logging in a file with timestamp or error logging in a table with timestamp for each batch.

0
0

We have a flat file and it contains secure data and we are running the load every hour and would like to know the best practice for redirecting rows.

Also we would like to send an email based on the record count in each batch .

Which is the best option to load sensitive data -error logging in a table using redirect rows to table or error logging in a table using redirect rows to flat file for a hourly job?

I think table is better

1. Permission management 

2.Archiving based on loaddate

Files can have issues with permission management.




Sql Query to make pair from one table

0
0

i have senario

rtyperestypecommnkey

a 1a

ba 1a

c d 2b

dc 2b

ab 3c

b 3c

 UACB6

CBUA6
NECD6
UCCD6
CDNE6
UCNE6
CDUC6
NEUC6

i need to remove duplicate key like

a  b

b  a

should be one pair

  NE CD

 CD   NE 

should  one pair same for all 

ssis - google analytics

0
0

Hello,
How is it to use the google analytics with ssis so that I can save client's activities in our website into sql server database?
Where do I start from?
What are the main tasks required to use in ssis?
etc.?

Thank you

SQL Job trigger for SSIS packages

0
0

Hello, 

In one of our project we have scheduled SSIS package every 30min in day. As long as the package finishes the within that 30m there are no issues. But by any chance due to large number of records if the file processing takes more than 30m, the next scheduled job will not be triggered to process the available file to process. This I have clearly observed by looking at the job history. Here the problem is , We have multiple portals and every individual portal can upload the file. Within the package by using multithreading we are processing maximum of 5 files at time. 

Due to the overlap of the job, the other pending files uploaded after the first file processing are not picked up by the job. Any solutions or suggestions to initiate the another job even one jon is in progress.

Thanks

Kris

ssis package configuration wizard 2012 not adding Package User variables to XML Config file

0
0

I have tried exporting Package user variable to XML by selecting the variable and its property 'Value',The wizard show the variable will be added but the XML file doesnt have the property added to configuration,Can any one please help in this regards,


Message in the Wizard


Name:
SSIS Tutorial Directory configuration

Type:
Configuration File

New configuration file will be created.

File name:
C:\Workspace\SampleProject\SSISTutorial.dtsConfig

Properties:
\Package.Variables[User::varFolderName2].Properties[Value]




Actual content of config file GENERATED BY WIZARD,No user variables exported to XML file



<?xml version="1.0"?><DTSConfiguration><DTSConfigurationHeading><DTSConfigurationFileInfo GeneratedBy="REDWOOD\Barry" GeneratedFromPackageName="Lesson 4" GeneratedFromPackageID="{C5AC717C-861D-475B-969B-383C9436F74D}" GeneratedDate="4/30/2016 1:30:04 PM"/></DTSConfigurationHeading></DTSConfiguration>


SSIS Package Not Executing from C#

0
0

Hi all!  Trying to get a local SSIS package to kick off after the user clicks the Audit button on a Windows form project I built.  Here is the code so far:

            //Variable & object declaration
            string pkgLocation;
            SSIS.Package pkg;
            SSIS.Application app;
            SSIS.DTSExecResult pkgResults;

            //Create new ofd
            OpenFileDialog ofd = new OpenFileDialog();

            //Set ofd settings
            ofd.Title = "Select audit file for processing";
            ofd.Filter = "*.txt files|*.txt";
            ofd.FilterIndex = 2;

            //Display ofd
            DialogResult result = ofd.ShowDialog();

            //Set path for package to execute
            pkgLocation =
                @"C:\Documents\Test\ImportFile.dtsx";
            app = new SSIS.Application();
            pkg = app.LoadPackage(pkgLocation, null);

            //Send variables to package
            pkg.Variables["User::InputFile"].Value = ofd.FileName;

            MessageBox.Show("Next command is to execute package using variable: " + pkg.Variables["User::InputFile"].Value);

            //Execute package
            pkgResults = pkg.Execute();

            MessageBox.Show("Execute command sent");

            //Check the results for Failure and Success
            if (pkgResults == Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure)
            {
                string err = "";
                foreach (Microsoft.SqlServer.Dts.Runtime.DtsError local_DtsError in pkg.Errors)
                {
                    string error = local_DtsError.Description.ToString();
                    err = err + error;
                }
            }
            if (pkgResults == Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success)
            {
                MessageBox.Show("SSIS import triggered successfully.");
            }
            //You can also return the error or Execution Result
            //return Error;

Here are the details:

MessageBox.Show("Next command is to execute package using variable: " + pkg.Variables["User::InputFile"].Value);

and

MessageBox.Show("Execute command sent");

both appear as expected, but then the project just hangs (it seems).  I have the SSIS project open in Visual Studio as well while debugging, and when it gets to that point in the script, VS does not appear to be running the SSIS.  Also, I have never seen the messagebox from this line:

MessageBox.Show("SSIS import triggered successfully.");

so it seems it's hanging somewhere between sending pkg.Execute() and actually starting the SSIS project.

Any thoughts?

FlatFile import column definitions

0
0

Just two questios:

  1. How can I import column definitions to FlatFile Data Source (200 columns)?
  2. My column definitions are of the form columnN starts at = n1, columnN ends at = n2
    It is possible that there is unused space between columns. How can I handle such Situation (for 200 columns)?

Regards


Varchar(max) equivalent in SSIS

0
0

Hi All,

          I have a column in my table that is of varchar(max) datatype, when I try selecting the same using a ExecuteSQLtask and assign it to a variable of String datatype, its failing with the error,

[Execute SQL Task] Error: Executing the query "Select [Path] from PARAMETERS where [Name] = 'List File'" failed with the following error: "The type of the value being assigned to variable "User::list_file_path" differs from the current variable type. Variables may not change type during execution. Variable types are strict, except for variables of type Object. ". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

What is the equivalent datatype, is String not good enough? Is there something I am missing out here ?

If someone has gone through this and figured out a solution please help....

Data Flow Task:Error: Excel Source failed the pre-execute phase and returned error code 0xC0202009. Works fine in SSDT in debug mode. Fails once deployed in SSISDB catalog.

0
0

I am trying to import data from an Excel (.xlsx) file into SQL Server. Excel file size is pretty big (128MB). It works fine if run in debug mode in SSDT but starts failing when I am trying to deploy it and run in SSISDB. I am using provider=Microsoft.ACE.OLEDB.12.0; for excel connector and running in 32 bit compatible mode in both SSDT and in SSISDB catalog.

To single out the problem I created the package with only 1 dataflow task. Source is excel connection and destination in OLEDB destination connecting to local SQL Server 2012 database. I tried changing the buffer size etc and finally I got the following error message.

I am getting following errors:

OnError

View Context

06.04.2015 10:06:24

Data Flow Task:Error: Excel Source failed the pre-execute phase and returned error code 0xC0202009.

OnError

View Context

06.04.2015 10:06:24

Data Flow Task:Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "Unexpected error from external database driver (1).".

Earlier before changing any properties I was getting memory related errors like:

OnError

06.04.2015 11:26:41

Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008);   at Microsoft.SqlServer.Dts.Runtime.DtsContainer.Execute(Connections connections, Variables variables, IDTSEvents events, IDTSLogging log, Object transaction)    at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ISServerExecutionEvents.StartPackage()   at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()    at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()

Transact-SQL stored procedure

OnError

06.04.2015 11:26:40

Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008);   at Microsoft.SqlServer.Dts.Runtime.DtsContainer.Execute(Connections connections, Variables variables, IDTSEvents events, IDTSLogging log, Object transaction)    at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ISServerExecutionEvents.StartPackage()

Transact-SQL stored procedure

DiagnosticEx

06.04.2015 11:26:40

<?xml version="1.0"?><DTS:ProcessMemoryUsage xmlns:DTS="www.microsoft.com/SqlServer/Dts"><DTS:PeakWorkingSetSize>1352765440</DTS:PeakWorkingSetSize></DTS:ProcessMemoryUsage>

Although I did observed that there was still sufficient memory on the server. (Server is a VM having 16GB RAM and MAX utilization did not reached beyond 6GB)

I tried using both ways - Excel file on local and Excel file on shared path.

I am using 

Microsoft SQL Server 2012 - 11.0.5058.0 (X64) 
May 14 2014 18:34:29 
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

Any suggestions will be more than welcome?

Also wanted to add that the same package is running fine for other smaller excel files.

In the original design I had a For Each enumerator to execute 15 files - all other 14 except for this large file were getting executed successfully.



How to Re Run the Job through Programming

0
0

Hi ALL,

I have a scenario where in a ETL (SSIS) package  taking csv file from X location and putting into oledb table. But problem the file came in the folder end of month; so there is not a fix time my file is come but my schedule job which run my package executed and get failed. 

What I want to create here is my package first check file is present or not and if it present then it proceed other wise send a message

and this part i already done.

But problem is in SQL Job . How I re run my Job again to Process my file without Manual effort. It should be Automatically.


Abhishek Parihar BI Consultant (Please mark the post as answered if it answers your question)

odd error message from DTSExec - "install Update CDE_Transaction of Integration Services"

0
0

Hi all,

When trying to run a package (actually a set of nested packages) using DTSExec called within a batch file, I get the following error:

"Source: Load CDE Transaction for T_Ref_12CFR363_FilingReqmnt SSIS.Pipeline

 Description: To run a SSIS package outside of SQL Server Data Tools you must install Update CDE_Transaction of Integration Services or higher."

What is "Update CDE_Transaction of Integration Services"? Is this part of SQL Server Data Tools or part of the SQL Server Client Tools? Is DTSExec.exe part of SSDT or SSCT or SSDT-BI?

Thanks.

SSIS Finishes with a status of Canceled

0
0

I have inherited a package from another developer that was originally created for SSIS 2005.   I pushed it through the upgrade process to run on 2014; however, I am getting the below output from my Output window:

SSIS package "D:\Visual Studio SQL Server Management Studio\Application Projects\Integrated Services 2014\Feed.dtsx" starting.
Information: 0x40016041 at Package: The package is attempting to configure from the XML file "F:\Config\Feed.dtsConfig".
Information: 0x4004300A at Save Runtime to the Database, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Create File, SSIS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at Create File, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Create File, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x402090DC at Create File, TGR Sap File [109]: The processing of file "\\produtil-db\G\$Files\QA\CreatePath\Reg\load.txt" has started.
Information: 0x4004300C at Create File, SSIS.Pipeline: Execute phase is beginning.
SSIS package "D:\Visual Studio SQL Server Management Studio\Application Projects\Integrated Services 2014\Feed.dtsx" finished: Canceled.
The program '[9052] DtsDebugHost.exe: DTS' has exited with code 0 (0x0).

The Create File is a Script Task that pre-configures some variables for the package.  

When running it, the visual portion of the DTS package simple shows the next step (a data flow task) as processing.  I have the script task steps and could not determine what might be causing the package to simple cancel.  I have read that SSIS 2005 did not have the feature, so I think it might be caused by the upgrade, but I have looked at all that I am aware of.

I should also note that when running the same package via a SQL Job, it step fails, returning this:

The step did not generate any output.  The return value was unknown.  The process exit code was -1073741819.  The step failed.

Thank you for your assistance,


Robert Johnston

Viewing all 24688 articles
Browse latest View live




Latest Images