when I try to run a SSIS package , it fails throwing an error
Description: To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services or higher.
this occurs only with a few packages, few of them succeed while few of them fail with this error. I am confused, can someone help me on this ?
All the packages are the same, i am creating a ADO.net source and OLE DB destination which dumps the file to sql server 2012.
please advice.
In Visual studio.
Go To Projects Menu -> Package Properties ->Debugging
Change Run64BitRuntime to false
Related
Please could someone help me on similar/same issue as in this TOPIC - SSIS package that connects to an oracle DB using Attunity Connection Manager
My environment situation is:
DEV Virtual Machine: VS2019 Version 16.8.1 (Microsoft SQL Server Integration Services Designer Version 15.0.2000.132)
DEV SQL Sever: 2017 DEV (Microsoft SQL Server 2017 (RTM-CU22) (KB4577467) - 14.0.3356.20 (X64))
I have installed:
LINK Microsoft Connectors v5.0 for Oracle and Teradata ATTUNITY
(as i need SQL 2017 compatibility)
and
LINK Microsoft Connector for Oracle V1.0
(I have tried multiple time installing only 32 or only 64 versions, and uninstalling and restarting VMs)
I have SSIS package with Oracle Connection Manager.
In Visual Studio inside package:
IF SQL Target version is SQL 2019
Connection manager to oracle test: SUCCESS
Run Package: SUCCESS
Deply Package to SSIS DB: Fail (Reasonable -> I have SQL 2017 :)
IF SQL Target version is SQL 2017
Connection manager to oracle test: SUCCESS
Run Package: FAIL
ERROR in DEBUG MODE:
[OMS OrderLines ABBICS V_F_ORDERS_RO24881SRU 3] Error: The
AcquireConnection method call to the connection manager Oracle DB
failed with error code 0x80004005. There may be error messages posted
before this with more information on why the AcquireConnection method
call failed.
[SSIS.Pipeline] Error: OMS OrderLines ABBICS V_F_ORDERS_RO24881SRU
failed validation and returned error code 0x80004005.
Error: The ORACLE registry key cannot be opened. Verify that the Oracle Client for Windows x86 is installed properly.
Deply Package to SSIS DB: SUCCESS
Run Package on SQL Server (from SSIS Catalog or from JOB): FAIL -> Basically same errors as in package
I have tried running packages in 64 and 32 bit mode as well as running job in 32 bit mode. The only difference was
...Windows x86 is installed properly...
or
...Windows x64 is installed properly...
Thank you!
Wojciech
Finally I was able to solve that uninstalling everything and install what i mentioned in post above plus:
32-bit Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studio
ODAC 12.2c Release 1 and Oracle Developer Tools for Visual Studio (12.2.0.1.1)
https://www.oracle.com/database/technologies/dotnet-utilsoft-downloads.html
This fixed issue and package can be run in both 32 and 64 bit mode
The only question that remains, do i really need to install this whole package with unnecessary (for me) features? Now i have to install it on all DEV/UAT/PROD nodes :/ Is there any particular component I can install to get this up and running?
EDIT: To minimize installation components - >On machines with SQL server 2017 I did following things:
Downloaded 64-bit ODAC 12.2c Release 1 (12.2.0.1.0) Xcopy for Windows x64
(ODAC122010Xcopy_x64.zip) from LINK
Unzipped File on SQL VM
Run CMD as admin, navigate to unzipped location and run
install.bat basic F:\ORACLE myhome false true
This will install Oracle Instant Client Machine Wide
Added to system variable PATH value: F:\ORACLE\
This allows me run SQL jobs successfully (remember to install other components mentioned in main post!)
I'm working on a SSIS package which I've been developing inside Visual Studio Community 2019 (VS). I have installed Integration Services to develop the SSIS package.
The task of the package is pretty simple, connect to a PostgreSQL datasource via an ODBC connection and then perform a lookup to identify new and updated fields and pass these into a MS SQL database via an OLE DB connection. When I run this package from both VS and via cmdp using dtexec.exe it runs successfully without any error (yay).
I run into a problem when I try to execute this package after deploying it from VS using the Deploy Package Wizard to SSISDB on MS SQL Server(2016). The errors can be found in the image below. Please note that I have selected Target Server Version SQL Server 2016 so there should be no compatibility issues between the package and server.
I have read that there may be a compatibility issue between 64 & 32-bit. However, I have no idea how to configure this from within SSISDB. I did however, attempt to execute the package with run64bitruntime set to "false" (done inside vs) and "true" with no change in result. my version of SSMS 2016 is running 64-bit.
I should also add that I'm connecting remotely to SSMS 2016 to run the package from SSISDB, remote connections is set to true for this server.
Please let me know if I can supply further details to help debug this. Thank you.
Visual Studio 2015 Update 3 14.0.25341.01
SQL Server Data Tools 14.0.61707.300
SQL Server 2016 13.0.4435.0
I recently had a message in VS2015 that a update for SQL Server Data Tools was available. I decided to download and install it and now packages I deploy to SQL 2016 no longer work.
I do not know what my version of SQL Server Data Tools was before I installed the update, but I do know that inside my SSIS Project, I now see the TargetServerVersion option of SQL 2017 (used to only go to SQL 2016).
I confirmed my project (which is the project I use for all my SSIS packages and have since we deployed SQL 2016) is still set to TargetServerVersion SQL 2016. The project is set to Project Deployment Mode, and I've always deployed by opening a package, and clicking File -> Save Copy of filename.dtsx As... and then deploying to target SQL. Nothing has changed in our environment outside of my upgrade of SQL Server Data Tools.
Here's the error I receive when I try to run the package:
Executed as user: DOMAIN\ProxySvc.
Microsoft (R) SQL Server Execute Package Utility
Version 13.0.1601.5 for 64-bit
Copyright (C) 2016 Microsoft. All rights reserved.
Started: 3:32:33 PM
Error: 2017-09-28 15:32:33.37
Code: 0xC0010018
Source: Package_Name
Description: Error loading value "<DTS:ConnectionManagers xmlns:DTS="www.microsoft.com/SqlServer/Dts"><DTS:ConnectionManager DTS:refId="Package.ConnectionManagers[SERVER A]" DTS:CreationName="OLEDB" DTS:DTSID="{E5D397C2-477A-4E04-B930-613DDE14A054}" DTS:ObjectName="SERVER A"><DTS:ObjectData>" from node "DTS:ConnectionManagers".
End Error
Could not load package "\Maintenance Plans\Package_Name" because of error 0xC0010014.
Description: One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.
Source:
Started: 3:32:33 PM Finished: 3:32:33 PM Elapsed: 0.109 seconds.
The package could not be loaded.
The step failed.
The packages will however work if I deploy them using DtUtil from the SQL 2016 Dev Edition I have installed locally. For example:
"C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\dtutil" /FILE "C:\filename.dtsx" /DestServer SERVERNAME/INSTANCE /Encrypt SQL;"Maintenance Plans\Package_Name";2;PKG_PA$$
Has anyone else had issue with this? I can't be the only person deploying package this way that suddenly had the packages stop working when deployed in VS2015 and SQL Server Data Tools.
I've also opened a Connect for this issue.
Edit: I tried Visual Studio 2017 with the preview edition of SQL Server Data Tools for it. I get the same issue. Package deploys fine, but the package will not run.
Edit 2: If I create an empty package, it runs successfully (granted doing nothing). If I create an empty package with nothing but a single OLEDB connection, it fails with the message above. It also fails with the same message with an empty package and only a single ADO.NET connection.
Edit 3: I deployed two packages. One using SSDT (that fails to run on the server with error above) and another with DTUTIL that executes on the server fine. The packages are the exact same except for how they were copied to the server. I then used DTUTIL to copy the package back to my machine and compared them. Outside of the DTS:LastModifiedProductVersion version differences, the only other change is the EncryptionMethod Algorithm. The one deployed using SSDT says:
<EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes256-cbc"/>
And the one deployed using DTUTIL:
<EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/>
Obviously the Salt, IV, and CipherValues are different but I wonder if the encryption being applied by SSDT when deploying is causing the issue.
I had the same exact issue. What solved it for me was this: http://microsoft-ssis.blogspot.com/2016/12/ There's a missing assembly reference in the devenv.exe.config file. If you deploy via command line or using the ISDeploymentWizard, that's probably your issue.
I have VS2015 Community and SQL Server 2016 Developer installed. Using the MSFT link, I've ensured to download the latest version of SSDT, which appears to install without error (though, Integration Services do not show in the SQL Configuration Manager). Using previously validated projects that creates and executes SSIS packages, I cannot get the same code to work with the current setup.
The error showing when I debug:
Component: SSIS.Pipeline
Error: To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services or higher.
I've uninstalled, reinstalled, repaired, modified, etc., but cannot get the package to build and execute. Has anyone seen similar issues with the setup mentioned?
As per my understanding
You need to install SQL Server and make sure to select Integration Services. Then run DTExec.exe from the new SQL server installation folder.
I have exactly the same issue. I ended up installing SQL Server 2017, SSMS 17.4 and VS 2017, SSDT for VS2017 and successfully run my packages FINALLY! It looks like SQL server and SSDT/VS version has to be "matched". Not sure if they have to be the same version though. But this is quite annoying.
I am learning to work with the SSIS packages.
I have made an SSIS package to work with the delta data(changed data since last run).
But i am having troubles running the package outside the development enviroment
I have tried to runt it with DTEXECUI.EXE utilty but it gives me the following error.
I have also tried to run it from a stored procedure by enabling the xp_cmdshell but i still get some error like this.
Please help, i am also trying to Google my way through.
It's clear from the error messages To run a ssis package outside of sql server data tools you must...
SSIS 2012 components have to be installed on your server to resolve the issue.
As per this post:
What you need are the base SQL Server binaries which are installed
with the DB engine. So you need a SQL Server Instance of some flavour
to have dtexec running. Whether it's the DB Engine or the SSIS service
installed but disabled.
Running packages in BIDS is a special case. Run the package on the
same PC as BIDS via dtexec and it will fail unless you have installed
server components (= a SQL Server Instance)