SSIS Student, ETL Staging Process - sql-server

I'm trying to perform a ETL Staging Process but keep running into this error. Turning off UAC as Microsoft suggests, setting XACT ABORT ON and all other things, nothing helps.
This is the error I get when I start debugging it on Visual Studio. Would really appreciate some assistance.
SSIS package "D:\Demofiles\Lab01\Starter\AdventureWorksETL\Stage Data.dtsx" starting.
Executing ExecutePackageTask: D:\Demofiles\Lab01\Starter\AdventureWorksETL\Extract Internet Sales Data.dtsx
Information: 0x4004300A at Extract Customers, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Extract Internet Sales, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Extract Customers, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Extract Internet Sales, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4001100A at Extract Internet Sales Data: Starting distributed transaction for this container.
Information: 0x4004300A at Extract Customers, SSIS.Pipeline: Validation phase is beginning.
Information: 0x40043006 at Extract Customers, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Extract Customers, SSIS.Pipeline: Pre-Execute phase is beginning.
Error: 0xC0202009 at Extract Customers, Customers [2]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E37 Description: "Invalid object name 'cdc.lsn_time_mapping'.".
Error: 0xC004701A at Extract Customers, SSIS.Pipeline: Customers failed the pre-execute phase and returned error code 0x80040E37.
Information: 0x4004300B at Extract Customers, SSIS.Pipeline: "Staging DB" wrote 0 rows.
Information: 0x40043009 at Extract Customers, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Extract Customers
Information: 0x4001100C at Extract Customers: Aborting the current distributed transaction.
Information: 0x4001100C at Extract Internet Sales Data: Aborting the current distributed transaction.
Task failed: Stage Internet Sales
Warning: 0x80019002 at Stage Data: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "D:\Demofiles\Lab01\Starter\AdventureWorksETL\Stage Data.dtsx" finished: Failure.
The program '[6628] DtsDebugHost.exe: DTS' has exited with code 0 (0x0).
The first line with Error in it specifies
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E37 Description: "Invalid object name 'cdc.lsn_time_mapping'.".

Your SSIS package errors, because the table cdc.lsn_time_mapping doesn't exist in target of your OLE DB connection. Did you specify the correct target database ?

Related

Exporting images from a SQL Server Table to a Folder using SSIS not working

I am trying to export images from sql server 2012 to a directory using SSIS. I followed the steps as in https://www.mssqltips.com/sqlservertip/2693/export-images-from-a-sql-server-table-to-a-folder-with-ssis/. There appears warning sign in OLE DB Source and when i run my ssis package, it shows one row affected.But when i search for directory it neither creates folder nor saves image.
My OlE DB Source :
and my export column:
and the result:
Output is like this:
Warning: 0x80208386 at Data Flow Task, OLE DB Source [18]: Rows sent to the error output(s) will be lost. Add new data flow transformations or destinations to receive error rows, or reconfigure the component to stop redirecting rows to the error output(s).
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80208386 at Data Flow Task, OLE DB Source [18]: Rows sent to the error output(s) will be lost. Add new data flow transformations or destinations to receive error rows, or reconfigure the component to stop redirecting rows to the error output(s).
Information: 0x40043006 at Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at Data Flow Task, SSIS.Pipeline: Execute phase is beginning.
Information: 0x40043008 at Data Flow Task, SSIS.Pipeline: Post Execute phase is beginning.
Information: 0x40043009 at Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
SSIS package "C:\Users\magnus_mani\Documents\Visual Studio 2010\Projects\Integration Services Project3\Integration Services Project3\Package.dtsx" finished: Success.
The program '[780] DtsDebugHost.exe: DTS' has exited with code 0 (0x0).
Can you make a data conversion (dt_ntext) in between and try?

2 Hours for an SSIS Job With a Linked Server

I have an SSIS job which takes on average 2 hours to complete (I did not write it and have never written an SSIS package). It will occasionally fail with the error:
Executed as user: ICAT\SQL_AgentSvc. Microsoft [...] Started: 12:15:00 AM Error: 2018-01-24 02:00:47.97 Code: 0xC0202009 Source: Data Flow Task 5 Source 21 - sSlip [260] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.". End Error Error: 2018-01-24 02:00:47.98 Code: 0xC0047038 Source: Data Flow Task 5 SSIS.Pipeline Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Source 21 - sSlip returned error code 0xC0202009. 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. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:15:00 AM Finished: 2:00:48 AM Elapsed: 6334.94 seconds. The package execution failed. The step failed.
Does this have anything to do with the time the job takes? I ask that because my usual resolution is to run the job manually in order to get the data the client is missing the day after it fails, but yesterday that failed and presented the error:
Login timeout expired
The job has several preparation steps and data flow steps. Each preparation step truncates tables in the destination database and then each data flow step grabs all data from identical tables in the linked source and moves the data to the destination. There are 23 tables it operates on. A couple of the tables have over one million records, one has 800k+ and several more have numbers in the tens of thousands.

Cannot load data from Excel into SQL using SSIS

I am trying to import an excel file into the SQL server using SSIS package, but every time I try to upload this file some rows from the last don't get uploaded, to be precise 55107 should be uploaded but only 54990 gets uploaded. 117 rows are creating some problem and am not able to figure out why is that so. Please help me out in understanding this error message so that I can resolve the issue. Below is the error message I'm getting:
SSIS package "C:\Users\A670814\Documents\Visual Studio 2015\Projects\Integration Services Project1\Integration Services Project1\NDCS Towers.dtsx" starting.
Information: 0x4004300A at NDCS tower, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at NDCS tower, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at NDCS tower, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
Information: 0x40043006 at NDCS tower, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at NDCS tower, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at NDCS tower, SSIS.Pipeline: Execute phase is beginning.
Error: 0xC0202009 at NDCS tower, OLE DB Destination [280]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Unspecified error".
Error: 0xC020901C at NDCS tower, OLE DB Destination [280]: There was an error with OLE DB Destination.Inputs[OLE DB Destination Input].Columns[Copy of ID] on OLE DB Destination.Inputs[OLE DB Destination Input]. The column status returned was: "The value violated the integrity constraints for the column.".
Error: 0xC0209029 at NDCS tower, OLE DB Destination [280]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "OLE DB Destination.Inputs[OLE DB Destination Input]" failed because error code 0xC020907D occurred, and the error row disposition on "OLE DB Destination.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.
Error: 0xC0047022 at NDCS tower, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "OLE DB Destination" (280) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (293). 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 NDCS tower, Excel Source [156]: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
Error: 0xC0047038 at NDCS tower, SSIS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Excel 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.
Information: 0x40043008 at NDCS tower, SSIS.Pipeline: Post Execute phase is beginning.
Information: 0x4004300B at NDCS tower, SSIS.Pipeline: "OLE DB Destination" wrote 55107 rows.
Information: 0x40043009 at NDCS tower, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: NDCS tower
Warning: 0x80019002 at NDCS Towers: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (6) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "C:\Users\A670814\Documents\Visual Studio 2015\Projects\Integration Services Project1\Integration Services Project1\NDCS Towers.dtsx" finished: Failure.
There was an error with OLE DB Destination.Inputs[OLE DB Destination Input].Columns[Copy of ID] on OLE DB Destination.Inputs[OLE DB Destination Input]. The column status returned was: "The value violated the integrity constraints for the column.".
It looks there are many rows where [Copy of ID] column is null, or there are some constraints on the [Copy of ID] column in SQL server that are violated in some rows in the excel files.
Try deleting rows that contains no data in [Copy of ID] column, or you can filter them by adding a conditional split component and filter on the following consition
ISNULL([Copy of ID])
Or you can access to the destination SQL table using Sql server management studio, and go to the SQL table design mode, and check the option Allow null for the column [Copy of ID]
Similar Question with many useful answers: The value violated the integrity constraints for the column

SSIS fails when exporting from OLEDB data to Excel File

When debugging it sais in the Output:
SSIS package "C:\Users\UserA\Documents\Visual Studio
2015\Projects\eSSIS\eSSIS\Package1.dtsx" starting.
Information: 0x4004300A at Data Flow Task 1, SSIS.Pipeline: Validation
phase is beginning. Information: 0x4004300A at Data Flow Task 1,
SSIS.Pipeline: Validation phase is beginning. Information: 0x40043006
at Data Flow Task 1, SSIS.Pipeline: Prepare for Execute phase is
beginning. Information: 0x40043007 at Data Flow Task 1, SSIS.Pipeline:
Pre-Execute phase is beginning. Error: 0xC0202009 at Data Flow Task 1,
Excel Destination 2: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB
error has occurred. Error code: 0x80040E21. An OLE DB record is
available. Source: "Microsoft Access Database Engine" Hresult:
0x80040E21 Description: "Multiple-step OLE DB operation generated
errors. Check each OLE DB status value, if available. No work was
done.". Error: 0xC002F445 at Data Flow Task 1, Excel Destination 2:
An error occurred while setting up a binding for the
"ShortDescription" column. The binding status was "DT_NTEXT". Error:
0xC0202025 at Data Flow Task 1, Excel Destination 2: Cannot create
an OLE DB accessor. Verify that the column metadata is valid. Error:
0xC004701A at Data Flow Task 1, SSIS.Pipeline: Excel Destination
failed the pre-execute phase and returned error code 0xC0202025.
Information: 0x4004300B at Data Flow Task 1, SSIS.Pipeline: "Excel
Destination" wrote 0 rows. Information: 0x40043009 at Data Flow Task
1, SSIS.Pipeline: Cleanup phase is beginning. Task failed: Data Flow
Task 1 Warning: 0x80019002 at Package1: SSIS Warning Code
DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but
the number of errors raised (4) reached the maximum allowed (1);
resulting in failure. This occurs when the number of errors reaches
the number specified in MaximumErrorCount. Change the
MaximumErrorCount or fix the errors. SSIS package
"C:\Users\UserA\Documents\Visual Studio
2015\Projects\eSSIS\eSSIS\Package1.dtsx" finished: Failure.
The program '[11704] DtsDebugHost.exe: DTS' has exited with code 0
(0x0).
Someone gave the answer below on this link:
You have to include the account you use to execute the package in the
performance counters group.
I would like to try out this workaround/answer but don't know how to include the account to execute a package. Please help

SSIS transactions with multiple OLE DB commands

I have the following Data Flow task in my SSIS package:
alt text http://img228.imageshack.us/img228/358/ssis1.png
It reads a file from an external vendor that has records with a column "change" that cointains A, C or D for add, change and delete. I have to process these in my SQL Server database. The conditional split checks the value of the change column and sends the row off to the appropriate command. This works fine.
Because the input files sometimes contain errors I would like to make this process transactional (there are 10 of these Data Flow tasks).
If I enable transactions on the SSIS package however the OLE DB commands seem to interfere with each other (they do not operate on the same rows). I get the error:
Error: 2010-02-02 12:21:08.39
Code: 0xC0202009
Source: name OLE DB Command 1 [58]
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0
" Hresult: 0x80004005 Description: "This operation conflicts with another pend
ing operation on this transaction. The operation failed.".
End Error
Error: 2010-02-02 12:21:08.39
Code: 0xC004701A
Source: name SSIS.Pipeline
Description: component "OLE DB Command 1" (58) failed the pre-execute phase
and returned error code 0xC0202009.
End Error
Progress: 2010-02-02 12:21:08.39
I have tried any order of the conditional split and all the IsolationLevels on the Transaction settings but nothing seems to work. If I make the conditional split use only 1 of the branches it works fine.
How to proceed?
Try replacing SQL Server Destination with a "OLEDB Destination" for the inserts.
SSIS is so bad it makes me scream - Seriosuly you should revist whether SSIS is the correct tool here

Resources