FIX: Error message when you run a SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 Integration Services package (SSIS) after you install the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1: "ADO NET Source [1424]"

Article ID: 969845 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2005, Microsoft SQL Server 2008, and Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005, Microsoft SQL Server 2008, or SQL Server 2008 R2 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You run a Microsoft SQL Server 2005, Microsoft SQL Server 2008, or SQL Server 2008 R2 Integration Services package (SSIS) on a computer that has one of the following .NET Framework installations:
    • The .NET Framework 2.0 Service Pack 2 (SP2)
    • The .NET Framework 3.5 Service Pack 1 (SP1)
  • The SSIS package uses a third-party ODBC driver that imports character data.
However, when you run the SSIS package, you receive the following error messages:
[ADO NET Source [1424]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "component "ADO NET Source" (1424)" failed because error code 0x80131937 occurred, and the error row disposition on "output column "columnname" (Number)" 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.

Error 0xc0209029: Data Flow Task: The "component "ComponentName" (1)" failed because error code 0x80131937 occurred...

[ADO NET Source [1424]] Error: The component "ADO NET Source" (1424) was unable to process the data. Pipeline component has returned HRESULT error code 0xC0209029 from a method call.

[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "ADO NET Source" (1424) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
This problem affects ODBC drivers that are accessed from the managed ODBC provider when the following conditions are true:
  • The ExecuteReader function is called by the CommandBehavior.SequentialAccess parameter. This call and parameter are used under the following circumstances:
    • When a SQL Server 2005 SSIS package reads data from a DataReader source or when a SQL Server 2008 SSIS package reads data from a managed ADO.NET data source.
    • The data source is not configured to redirect the error and truncation values.
  • The OdbcDataReader.IsDbNull function is called. The SSIS package uses this method to determine whether the value in a field is NULL or not.
  • One of the following functions is called:
    • The OdbcDataReader.GetBytes function is called to obtain certain data types, such as DT_BYTES, from the managed ODBC provider.
    • The OdbcDataReader.GetChars function is called to obtain certain string data types, such as DT_WSTR, from the managed ODBC provider.
Back to the top | Give Feedback

CAUSE

The .NET Framework 2.0 SP2 and the .NET Framework 3.5 SP1 introduce a change in the managed ODBC provider by which strings are read from the native ODBC driver in the scenario that is described in the "Symptoms" section. Because of this change, the managed ODBC provider that is called in the native ODBC driver by using the SQLGetData API function uses a buffer of size 0. Compliant ODBC drivers do not have problems in this call. However, noncompliant ODBC drivers may fail under these circumstances. For a compliant ODBC driver, the SQLGetData API function returns SUCCESS_WITH_INFO when a buffer of size 0 is detected. For a noncompliant ODBC driver, the call returns NO_DATA.
Back to the top | Give Feedback

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have .NET Framework 2.0 Service Pack 2 installed.

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
.NET Framework 2.0 for Windows 2000, Windows Server 2003, Windows XP, 32-bit versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.data.dll2.0.50727.40632,933,76019-05:08x86
.NET Framework 2.0 for Windows 2000, Windows Server 2003, Windows XP, x64 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.data.dll2.0.50727.40633,008,51218-23:51x64
System.data.dll2.0.50727.40632,933,76019-05:08x86
.NET Framework 2.0 for Windows 2000, Windows Server 2003, Windows XP, IA-64 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.data.dll2.0.50727.40632,933,76019-05:08x86
System.data.dll2.0.50727.40633,234,81619-01:09IA-64
.NET Framework 2.0 for Windows Vista, Windows Server 2008, 32-bit versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
System.data.dll2.0.50727.44002,933,76010-Sep-200911:54
.NET Framework 2.0 for Windows Vista, Windows Server 2008, x64 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
System.data.dll2.0.50727.44003,008,51210-Sep-200911:54
.NET Framework 2.0 for Windows Vista, Windows Server 2008, IA-64 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
System.data.dll2.0.50727.44003,234,81610-Sep-200911:54
Back to the top | Give Feedback

WORKAROUND

To work around this issue, use one of the following methods.

Method 1

Edit the SSIS package to configure Error and Truncation Redirection on the DataReader source or on the managed ADO.NET data source. After you edit the SSIS package to redirect the error output to a destination, the package will run successfully even though no rows are written to the destination. To do this, follow these steps.

Note The following steps assume that you are using a SQL Server 2005 SSIS package that reads data from a DataReader source.
  1. Open the SSIS package in SQL Server Business Intelligence Development Studio.
  2. Open the Advanced Editor for DataReader Source dialog box in the Data Flow designer.
  3. Click the Input and Output Properties tab, and then expand the DataReader Output node in the Inputs and outputs tree.
  4. Expand the Output Columns node.
  5. Click each column under the Output Columns node, and then examine the DataType property. For each column whose DataType property is DT_WSTR, DT_NTEXT, DT_BYTES, or DT_IMAGE, edit the following two properties:
    • Set the ErrorRowDisposition property to RD_RedirectRow.
    • Set TruncationRowDisposition property to RD_RedirectRow.
  6. Click OK to save the changes.
  7. In the Data Flow designer, add a new destination. For example, add a flat file destination or a SQL Server destination.
  8. Use the red arrow from the DataReader source to connect it to the newly added destination. This operation will direct the error rows and truncation rows to the destination in order to save the error rows.
  9. Repeat steps 1 through 8 for all Data Flow tasks that access ODBC string or image columns and that fail with the error messages that are mentioned in the "Symptoms" section.

Method 2

Uninstall the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1. However, we do not recommend that you uninstall a service pack because this sacrifices the reliability, feature improvements, and performance optimizations that the service pack offers.

To restore your system to the state that it was in before you installed the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1, follow these steps:
  1. In Control Panel, double-click Add or Remove Programs.
  2. Locate Microsoft .NET Framework 3.5 SP1, and then uninstall it.
  3. Locate Microsoft .NET Framework 3.0 SP2, and then uninstall it.
  4. Locate Microsoft .NET Framework 2.0 SP2, and then uninstall it.
  5. Reinstall the original release of the .NET Framework 3.5. This step will reinstall the .NET Framework 2.0 SP1 and the .NET Framework 3.0 SP1. To obtain the .NET Framework 3.5, visit the following Microsoft Web site:
    http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en
    (http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en)

Method 3

Contact the vendor of the third-party ODBC driver to determine whether the vendor has an update for the driver to resolve this issue.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

Properties

Article ID: 969845 - Last Review: December 1, 2011 - Revision: 6.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Standard Edition for Small Business
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Workgroup
Keywords: 
kbautohotfix kbhotfixserver kbsurveynew kbfix kbqfe kbexpertiseadvanced KB969845
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top