SSIS OLE DB Error

• A Little Help Please

  SSCarpal Tunnel

  Points: 4764

  More actions

  November 19, 2008 at 3:05 am

  #154927

  I am importing a flat file (.txt) into SQL2005 DB.

  I seem to betting the following error. I am trying to import one column.

  SSIS package "Package.dtsx" starting.

  Information: 0x4004300A at Export Files, DTS.Pipeline: Validation phase is beginning.

  Information: 0x4004300A at Export Files, DTS.Pipeline: Validation phase is beginning.

  Information: 0x40043006 at Export Files, DTS.Pipeline: Prepare for Execute phase is beginning.

  Information: 0x40043007 at Export Files, DTS.Pipeline: Pre-Execute phase is beginning.

  Information: 0x402090DC at Export Files, House [1]: The processing of file "E:\Applications\Account\Accountfiles\house.txt" has started.

  Information: 0x402090DC at Export Files, CheckPointFile [17]: The processing of file "E:\Applications\Account\Accountfiles\POINT.TXT" has started.

  Error: 0xC0202009 at Export Files, OLE DB Destination 1 [1778]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E21.

  An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".

  Error: 0xC0202025 at Export Files, OLE DB Destination 1 [1778]: Cannot create an OLE DB accessor. Verify that the column metadata is valid.

  Error: 0xC004701A at Export Files, DTS.Pipeline: component "OLE DB Destination 1" (1778) failed the pre-execute phase and returned error code 0xC0202025.

  Information: 0x40043008 at Export Files, DTS.Pipeline: Post Execute phase is beginning.

  Information: 0x402090DD at Export Files, House [1]: The processing of file "E:\Applications\Account\Accountfiles\house.txt" has ended.

  Information: 0x402090DD at Export Files, CheckPointFile [17]: The processing of file "E:\Applications\Dealbook\NewDealbookFiles\CHECKPOINT.TXT" has ended.

  Information: 0x402090DF at Export Files, OLE DB Destination [1177]: The final commit for the data insertion has started.

  Information: 0x402090E0 at Export Files, OLE DB Destination [1177]: The final commit for the data insertion has ended.

  Information: 0x40043009 at Export Files, DTS.Pipeline: Cleanup phase is beginning.

  Information: 0x4004300B at Export Files, DTS.Pipeline: "component "OLE DB Destination" (1177)" wrote 0 rows.

  Information: 0x4004300B at Export Files, DTS.Pipeline: "component "OLE DB Destination 1" (1778)" wrote 0 rows.

  Task failed: Export Files

  Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (3) 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 "Package.dtsx" finished: Failure.

  Any help would be wonderful!!

• brian clements-470670

  Mr or Mrs. 500

  Points: 521

  More actions

  November 20, 2008 at 6:13 am

  #900995

  Error: 0xC0202025 at Export Files, OLE DB Destination 1 [1778]: Cannot create an OLE DB accessor. Verify that the column metadata is valid.

  I'm not 100 percent sure, but you may have to use a different data type than whats coming in from the file. If you needed to be consistent use a data conversion

  transforamtion to return to the original data type.

  Again, I'm not 100 percent sure but it may give you a starting point.

• brian clements-470670

  Mr or Mrs. 500

  Points: 521

  More actions

  November 20, 2008 at 6:17 am

  #900999

  Check your ole db destination table to see what data types are being used

• sayan ghosh

  Old Hand

  Points: 315

  More actions

  June 23, 2009 at 5:51 am

  #1013851

  If you are giving wrong indexes for a parameter in the SQL Task, sit throws this error.

  - Sayan

• srkrell

  Ten Centuries

  Points: 1349

  More actions

  August 24, 2009 at 8:26 am

  #1043651

  I had the same problem and discovered that changing the datatype in a derived column from unicode text stream (DT_NTEXT) to Unicode String (DT_WSTR) cleared up my problem.

• aionica

  SSC Rookie

  Points: 39

  More actions

  September 15, 2010 at 4:01 pm

  #1221756

  Many thanks...solved this error I got today based on your idea of checking data types! Fixed based on this:

  "consistent use a data conversion transformation to return to the original data type"

  Error was:

  [OLE DB Destination [55]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.

  Error code: 0x80040E21.

  [OLE DB Destination [55]] Error: Cannot create an OLE DB accessor. Verify that the column metadata is valid.

  [DTS.Pipeline] Error: component "OLE DB Destination" (55) failed the pre-execute phase and returned error code 0xC0202025.

• cbalamurali

  Valued Member

  Points: 71

  More actions

  January 13, 2011 at 1:44 am

  #1272849

  This is not Data conversion error, its Registry Error ,,see this link http://support.microsoft.com/kb/269495

• david.ostrander

  SSCommitted

  Points: 1828

  More actions

  August 28, 2012 at 12:21 pm

  #1531011

  srkrell (8/24/2009)

  ---

  I had the same problem and discovered that changing the datatype in a derived column from unicode text stream (DT_NTEXT) to Unicode String (DT_WSTR) cleared up my problem.

  Srkrell - Your solution fixed my issue.

  Thanks....