This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 57.99999999999999%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
Hello, we have a SSIS Package with a ODBC Source for extracting data from a DB2 data base. This package works perfectly in Visual Studio 2017 and TargetServerVersion SQL Server 2017. When we try to run this package in Visual Studio 2019 and TargetServerVersion SQL Server 2019 it fails.
Even if we create a SSIS project from scratch and try to use a ODBC Source to DB2 in VS2019 still fails.
We have tried some other things like change the Batch Size. Depend on the Source Table, if we set the Batch Size to 1 it works, but not with all tables. With the default Batch Size (1000), the Data Flow seems to work, but get a error message and the number of rows is not equal to the number of rows of the source table:
If we create a SSIS project in VS2019 but set TargetServerVersion to SQL Server 2017, it works, but our production server is SQL Server 2019.
Visual Studio Info:
Microsoft Visual Studio Professional 2019
Versión 16.10.0
VisualStudio.16.Release/16.10.0+31321.278
Microsoft .NET Framework
Versión 4.8.04084
SQL Server Integration Services Projects extension version 3.13.1
SQL Server Analysis Services 15.0.19526.0
Diseñador de Microsoft SQL Server Analysis Services
Versión 15.0.19526.0
SQL Server Data Tools 16.0.62105.04180
Microsoft SQL Server Data Tools
SQL Server Integration Services 15.0.2000.166
Diseñador de MS SQL Server Integration Services
Versión 15.0.2000.166
SsmsVsIntegration 1.0
Any solution?
Thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 26%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYK%3C/text%3E%3C/svg%3E)
Please add to your question the following:
Visual Studio Info:
Microsoft Visual Studio Professional 2019
Versión 16.10.0
VisualStudio.16.Release/16.10.0+31321.278
Microsoft .NET Framework
Versión 4.8.04084
SQL Server Integration Services Projects extension version 3.13.1
SQL Server Analysis Services 15.0.19526.0
Diseñador de Microsoft SQL Server Analysis Services
Versión 15.0.19526.0
SQL Server Data Tools 16.0.62105.04180
Microsoft SQL Server Data Tools
SQL Server Integration Services 15.0.2000.166
Diseñador de MS SQL Server Integration Services
Versión 15.0.2000.166
Problem solved installing the latest version of the IBM i Access ODBC Driver: 13.64.25.00
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 80%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENG%3C/text%3E%3C/svg%3E)
I know this is an old thread, but this solution does not work for me.
I have this exact same issue, but installing the latest version did not work for me.
An observation:
Version 13.64.25.00 I only see as the version for the 64bit version of the driver. When I add a 32 bit version of the driver I see version 13.00.25.00.
Whether I use 64 or 32, I get the same PrimeOutput failure. I have tested in Visual Studio with 32 and 64 bit runtime. I have tested calling the 32 and 64 bit version of dtexec from command line. No combination works except for setting the package to 2017 deployment, running it out of visual studio, and using a 32bit odbc driver.
Was there anything else you did to get it working?
Hi @Nick Greene
It was enough for me to install the latest version of the driver, and now still working perfectly. Have you tried to make a fresh install of all components? I recently had another issue with the latest version of VS2019. It was a problem with the Data Viewer and the workaround was to set the language of my Windows 10 to English (I had the Spanish version for de SO and the English version of VS2019). IDK if that could help in your case.
It is a bit hard for us to narrow down the issue.
Could you please share the error message with us so that we could do more analysis?
Is the issue only occur with ODBC?
Could you help test that create a simple package with flat file to see if the issue will occur?
Regards，
Zoe
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October
Hello @ZoeHui-MSFT , thanks for your reply.
Yes, it only occurs with ODBC and TargetServerVersion 2019. If we use OLEDB against the same data base with the same query, it works but is pretty slower (in 2017 and 2019).
The ODBC Source works perfectly with TargetServerVersion set to 2017.
I have been able to make it work in 2019 setting the property Batch Size to 1, but in this case ODBC is as slow as OLEDB. In 2017, ODBC works perfectly with Batch Size = 1000.
This is the only error message we get:
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Origen ODBC returned error code 0x80004005. 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.
What OLEDB you are uisng? For what database?
It's a DB2 data base (AS/400, version 7) and I'm using the iSeries Access ODBC Driver 13.00.01.00 (v7r2m0).
Thanks.
For OLEDB:
IBM DB2 for i IBMDA400 OLE DB Provider