"Attempted to read or write protected memory error" in SSIS

I'm trying to import data from a Sybase ASE 12.0 database called "OurTestDatabase" into MS SQL Server 2005. I started SSIS Wizard and indicated "Sybase ASE OLEDB Provider" as a source and SQL Native Client as the target. I'm gettign the following error message:

--

Cannot get supported data types from the database connection

"Provider=Sybase.ASEOLDEDBProvider;Password=;Persist Security Info=True;User ID=sa;Data Source=sybase;Initial Catalog=OurTestDatabase"

Additional information

|_ Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Data)

--

The same data source worked with DTS when we thought we'd convert to MS SQL Server 2000. Is this a bug in SSIS? What can be done? Using ".Net Framework Provider for ODBC" is not a good option because this doesn't allow me to choose any tables from the Sybase source.

Any help is greatly appreciated.

Hi,

Did you get the chance ti figure out what was the problem. I do get the similar error while accessing AS400 database.

its fail in :

// Summary:

// Fixes any errors identified during design-time validation that result in

// the component returning Microsoft.SqlServer.Dts.Pipeline.Wrapper.DTSValidationStatus.VS_NEEDSNEWMETADATA.

void ReinitializeMetaData();

where its suppose to identify the errors in metadata it seems.

I still am investigating my metadata for AS400 tables.

Hope This helps you.

|||

I'm not sure that we can help debug in detail - we have not tested the Sybase drivers and don't know what behaviour they typically report.

However, most likely the issue arises because the Sybase provider does not support methods we are calling to get data types for columns. I have seen similar issues with the Sybase provider and linked servers. You may want to check with Sybase to see if they have tested their provider with SSIS.

The .Net provider for ODBC may be a workaround in terms of getting column level metadata. You are right that in the present version you cannot browse tables or views. However, although the provider does not list tables, it is still possible to access them, but you need to write the query yourself.

Donald

|||The same error came up when I used the ODBC drivers to access Sybase ASE|||

That sounds like a Sybase issue, then. Have you checked with them, or tested the same calls to the driver with other clients?

Donald