Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error while exporting data from SQL to Access Expand / Collapse
Author
Message
Posted Friday, March 28, 2014 5:57 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, August 18, 2014 5:44 AM
Points: 84, Visits: 394
Hi,

I am developing a SSIS package where I am trying to pull records from SQL server tables and pushing the records into Access (2000) tables. I am doing this for 10 different tables in a sequence container. It exports successfully for 6 tables and it keeps failing for 4 tables with some unknown error. Column data types for the failing tables are same as the other 6 tables. Below is the error. Please help.

[Access Database [53]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.

[Access Database [53]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (66)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (66)" 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 "Access Database" (53) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (66). 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.


Thanks in Advance
Post #1555848
Posted Friday, March 28, 2014 6:42 AM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, July 1, 2014 7:42 AM
Points: 20, Visits: 2,250
what's the size of the data you're transferring? I believe that there is a size limit on access 2k databases being 2gb
Post #1555867
Posted Friday, March 28, 2014 6:49 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, August 18, 2014 5:44 AM
Points: 84, Visits: 394
Very less number of Records and the columns are also not of huge size.
Post #1555873
Posted Friday, March 28, 2014 8:47 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 15, 2014 7:59 PM
Points: 1,194, Visits: 2,222
You need to check for errors before this ..

[Access Database [53]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.

Could you post those errors before that ?

--
SQLBuddy
Post #1555963
Posted Friday, March 28, 2014 10:46 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, August 18, 2014 5:44 AM
Points: 84, Visits: 394
No other errors. Now I am getting below 2 errors only

[Access Database [173]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E03.

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Access Database" (173) failed with error code 0xC0202009 while processing input "OLE DB Destination Input" (186). 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.
Post #1556043
Posted Friday, March 28, 2014 9:24 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 12:30 PM
Points: 839, Visits: 5,388
just for grins, can you attach to SQL Server from Access and create a Make Table query to create the columns you need? I'm just wondering because maybe the sizes/types of the columns in Access are not big enough to hold the data you're trying to put in them. Create a quick view in SQL Server containing all the columns you need but only a few rows and then base a Make Table query on that view and see what field types and sizes you Access creates.
Post #1556185
Posted Tuesday, April 8, 2014 12:32 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, June 27, 2014 2:05 PM
Points: 287, Visits: 810
I also think it is either data types or truncation.
Post #1559647
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse