I'm having trouble using a Progress database as a source. I have an OpenLink driver installed and a System DSN set up. I can successfully test the connection.
I added this DSN to the connection manager and added it to a DataReader Source. I then added the SQLCommand property. I was able to map columns and such, so I believe the SQLCommand was successfully parsed. However, when I try to save the DataReader Source, I get an error:
Error at Data Flow Task [DataReader Source [2266]]: System.Data.Odbc.OdbcException: ERROR [HY010] [OpenLink][ODBC][Driver]Function sequence error
at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode)
at System.Data.Odbc.OdbcDataReader.NextResult()
at System.Data.Odbc.OdbcDataReader.Close()
at Microsoft.SqlServer.Dts.Pipleline.DataReaderSourceAdapter.ReinitializeMetaData()
at Microsoft.SqlServer.Dts.Pipleline.ManagedComponentHost.HostReinitialieMetaData(IDTSManagedComponentWrapper90 wrapper)
What am I doing wrong Why does the error reference DTS
Thanks,
stacy
Problem with ODBC Source
Hot Topic
- Adventure Works.sln DEPLOY ERROR first time
- I need URGENT help about **Lost DTS password**
- Configuration file reused by different packages
- Split txt file into multiple
- Strange behavior with Calculated Members
- Email tasks fail after an unsuccessful SQL 2005 installation
- Deploying Jet OleDb Provider
- How do I get AdventureWorks to show in sql2005.
- DtsBackup2000 for SSIS packages??
- Connection Reset by Remote Host Error
SQL Server
- Using SQL Server Express in Commercial App
- ON SCHEMA :: schema_name
- SSIS Fuzzy Matching
- Execute SSIS package from ".vbs" file
- Error 404 when opening reportserver
- RDA.Pull and INNER JOINS...
- SMO Connection String conversion
- problem to set properties on a subfolder if no access to the home folder
- Guids as primary keys
- Error messages upsizing from MSAccess database to SQLServer
Problem with ODBC Source
Matt Johnson
Everything under the covers is still pretty much called Dts. All the objects and their namespaces refer to Dts, just look in Books Online to see how far reaching this is. The SSIS name only came out about a year ago and renaming all that code would be a mammoth job.
Sorry I have no idea about the ODBC problem though.
nicomp
Have you made sure the provider you installed supports ADO.Net:ODBC connection Another thing to be aware of is we aren't obligated to support the openlink ODBC provider for Progress in the current release. However we may be able to tell in more details in the error mesg, e.g. what are the missing bits etc, in the future
Thanks