none
SSIS ADO NET Destination error code 0xC0208452

    Question

  • I am using an Data Flow. Inside I have an OLE DB Source to get data from a Table of one Database of my SQL Server 2008 R2 and a ADO NET Destination to insert data in a Postgres 8.4 Database.

    My SO is a Windows Server 2008 R2 and I also have installed the official ODBC Connector for Postgres.

    I ran the package successfully almost 5 times before this problem occur.

    The problem happen when I try to run the task. Below are the two more important lines of the error message:

    [ADO NET Destination [120]] Error: ADO NET Destination has failed to acquire the connection {854BBE5B-0D3E-4C52-ADCD-818A4A2D73C0}. The connection may have been corrupted.
    [SSIS.Pipeline] Error: component "ADO NET Destination" (120) failed validation and returned error code 0xC0208452.

    Other info:
    The ODBC Connector works fine, and also the connection test of the ADO NET Destination

    Diogenes Caraballo
    Wednesday, May 19, 2010 10:14 PM

Answers

  • Error 0xC0208452 says: ADO NET Destination has failed to acquire the connection %1. The connection may have been corrupted.

    There might be some problem with the connection? Did you try it again? Does it fail continuously after the first time failure?

    Xiaochen


    Xiaochen Wu
    • Marked as answer by Tony Tang_YJ Friday, May 28, 2010 9:32 AM
    Friday, May 28, 2010 8:27 AM

All replies

  • Error 0xC0208452 says: ADO NET Destination has failed to acquire the connection %1. The connection may have been corrupted.

    There might be some problem with the connection? Did you try it again? Does it fail continuously after the first time failure?

    Xiaochen


    Xiaochen Wu
    • Marked as answer by Tony Tang_YJ Friday, May 28, 2010 9:32 AM
    Friday, May 28, 2010 8:27 AM
  • Delete and recreate your destination and try.
    Friday, May 28, 2010 9:12 AM
  • Im facing similar issue, creating connections and re-mapping multiple times haven been fruitful.

     

    SSIS package "dimdate pack.dtsx" starting.

    Information: 0x4004300A at Data Flow Task 1, SSIS.Pipeline: Validation phase is beginning.

    Error: 0xC0208452 at Data Flow Task 1, Destination - dimDate [43]: ADO NET Destination has failed to acquire the connection {AEACCC18-BBFF-4CBB-931A-F39B8506A448}. The connection may have been corrupted.

    Error: 0xC0047017 at Data Flow Task 1, SSIS.Pipeline: component "Destination - dimDate" (43) failed validation and returned error code 0xC0208452.

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

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

    SSIS package "dimdate pack.dtsx" finished: Failure.

     

    Sunday, November 21, 2010 9:56 AM
  • I was experiencing the same problem writing to MySQL 5.1.  When I would run the package in BIDS, it would work fine.  If I ran it from the UI, it worked fine.  When I ran it from a job, it failed.  I gave the agent account all sorts of permissions.  That didn't work.  In my case, the problem was that the data source was not in System Data Sources in ODBC administrator.  I had it in User Data Sources, but not System.  Therefore, when I would run the package as me, it would use the data source found in User Data Sources.  When run as a different user, the data source didn't exist for that user, so it looks in system data sources, but it's not there either, and generates the error.  The error is confusing.  "Could not find DSN <data source name>" would have been much better.

    • Proposed as answer by Steve_Williams Wednesday, July 20, 2011 6:49 PM
    Wednesday, July 20, 2011 6:34 PM