Package runs in Visual Studio, but not in SSIS

Discussion of issues, suggestions and bugs of Devart SSIS Data Flow Components, our product line for building SSIS-based ETL solutions, performing data access to popular cloud applications and databases.
Post Reply
KaiRo
Posts: 3
Joined: Tue 26 Feb 2019 09:16

Package runs in Visual Studio, but not in SSIS

Post by KaiRo » Tue 26 Feb 2019 10:03

Dear Forum.

I need assistance with a packge using DevArt PostgreSQL Data Flow Components.
The package runs without any issues in VS.

However when run in SQL Manager as SSIS package, or from Task Agent, it does not run, instead reports a missing component:
"Devart.SSIS.PostgreSql.PgSqlSource, Devart.SSIS.PostgreSql.140, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701" could not be loaded... file or assembly "Microsoft.SqlServer.DTSRuntimeWrap, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" or a dependancy thereof not found...

System:
Microsoft SQL Server 2016 (SP1-CU6) (KB4037354) - 13.0.4457.0 (X64) Nov 8 2017 17:32:23 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on
Windows Server 2012 R2 Datacenter 6.3 <X64> (Build 9600: ) (Hypervisor)

Please assist.

- KaiRo

Pinturiccio
Devart Team
Posts: 2406
Joined: Wed 02 Nov 2011 09:44

Re: Package runs in Visual Studio, but not in SSIS

Post by Pinturiccio » Wed 27 Feb 2019 12:59

You need to install SSIS Data Flow Components for PostgreSQL on your deployment computer. Please note that each SSIS Data Flow Components for PostgreSQL license allow you to install product on one deployment server per license.

Moreover, you need to activate the license on the production SQL Server. You can activate it in SSDT when you create or edit a DevartPgSQL connection.

If SQL Server Data Tools is not installed on the deployment computer or there is no access to it, you can add the license key in the following way: when you install SSIS Data Flow Components, it adds the License folder. By default, this is the C:\ProgramData\Devart\SSIS Data Flow\License folder. Copy the SSISPostgreSQL.lic file from the development computer to this folder on the deployment computer.

If the issue still reproduces after installing SSIS Data Flow Components for PostgreSQL on the deployment computer, please tell us the following:
1. The version of SQL Server Data Tools installed on your development computer.
2. If you use SSDT 2015 or 2017 on your development computer, tell us the value of the TargetServerVersion property of your project. It can be found in the project properties.
3. SQL Server version on your deployment and development computer.

KaiRo
Posts: 3
Joined: Tue 26 Feb 2019 09:16

Re: Package runs in Visual Studio, but not in SSIS

Post by KaiRo » Wed 27 Feb 2019 15:03

Hello, thank you for your help.

As of now, deployment = development, so the data flow components are installed. That may change if everything works as to my expectations... but as of now, same machine.

On this machine:
- SSIS Data Flow Components for PostgreSQL is installed
- SQL Server Data Tools are installed (Version 14.0.61707.300)
- TargetServerVersion was not set, I am testing now with 2016

System is:
- Microsoft SQL Server 2016 (SP1-CU6) (KB4037354) - 13.0.4457.0 (X64) Nov 8 2017 17:32:23 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on
Windows Server 2012 R2 Datacenter 6.3 <X64> (Build 9600: ) (Hypervisor)

KaiRo
Posts: 3
Joined: Tue 26 Feb 2019 09:16

Re: Package runs in Visual Studio, but not in SSIS

Post by KaiRo » Thu 28 Feb 2019 14:18

And setting the target server version properly helped my issue.
Thank you very much!

Pinturiccio
Devart Team
Posts: 2406
Joined: Wed 02 Nov 2011 09:44

Re: Package runs in Visual Studio, but not in SSIS

Post by Pinturiccio » Thu 28 Feb 2019 14:24

We are glad to hear that the issue is solved. Feel free to contact us if you have any further questions.

Post Reply