SSIS Data Flow Task An OLE DB error has occurred. Error code: 0x80040E37.


PROBLEM:


When using OLE DB Source Editor, the drop down “Name of the table or view” shows ” doublequotes around the schema and table name.  Selecting the table (for example “dbo”.”Table1″), then Preview returns the error below:



Error at Data Flow Task [OLE DB Source [1]]: An OLE DB error has occurred. Error code: 0x80040E37.


Error at Data Flow Task [OLE DB Source [1]]: Opening a rowset for “”dbo”.”Table1″” failed. Check that the object exists in the database.


 (Microsoft Visual Studio)


===================================


Exception from HRESULT: 0xC02020E8 (Microsoft.SqlServer.DTSPipelineWrap)


——————————
Program Location:


   at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ReinitializeMetaData()
   at Microsoft.DataTransformationServices.DataFlowUI.DataFlowComponentUI.ReinitializeMetadata()
   at Microsoft.DataTransformationServices.DataFlowUI.DataFlowAdapterUI.connectionPage_SaveConnectionAttributes(Object sender, ConnectionAttributesEventArgs args)


RESOLUTION:


SSIS by default will use ” doublequotes as the quoted identifier if the OLE DB Provider does not override these settings.  Change SSIS OLE DB for SQLCommand and type “select * from dbo.table” instead of picking the table from the list. 


When using Sybase OLE DB provider, run the Sybase Configuration Manager and change the data source to “Enable Quoted Identifiers” to True (1) to suppot ” doublequotes around the schema and table name.


 


Comments (5)

  1. Keviv says:

    I can pull data into SQL Server from Sybase using your notes, but I cannot dump data from a SQL Server table back into Sybase using SSIS.  Any thoughts?

  2. Andrew_H says:

    I had the same problem with Informix. I fixed it by changing the registry DELIMIDENT key value in the InformixEnvironment from n to y.

  3. Matt_H says:

    I had the exact same error trying to import using SSIS with SQL Server 2008 from Access 2007. Weird thing was that only one table was causing the error to occur all other tables would import OK. I thought there might be some data corruption but it turned out that there was a ghost process of Access running – finally found it in Task Manager – once killed off the SSIS package worked again.

  4. Also refer: To change the data source to "Enable Quoted Identifiers" to True (1)

    media.datadirect.com/…/reldpcfg.htm

  5. ScubaBrittain says:

    Thank you so much! This solved my current issue!