SSIS Deployment

Hi All
I am having a problem with a package I am trying to deploy to our SSIS 2014 / SQL Server 2014 environment.
I have 4 connections in the project,
3 have been converted to Project Level connections and parameterised for ServerName and InitialCatalogue
The last connection is at Package level and feeds some ForeEach loops / populates some local variables. this is also parameterised but only with a local variable which is basically what i need
The entire package runs as expected from BIDS - no errors atall.
Now fast forward, I have setup a Dev environment in the environments tab - and I can see the 3 sets of params for the 3 project connections - all values have been configured and set as required. But when i run the package - it is complaining about one of
the lookups with the following error:
Error1:
DFT-CURRENCY:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description: "Deferred prepare could not be completed.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description: "Statement(s) could not be prepared.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description: "Invalid object name 'ETL.Source'.".
Error2:
DFT-CURRENCY:Error: OLE DB error occurred while loading column metadata. Check SQLCommand and SqlCommandParam properties.
Error3:
DFT-CURRENCY:Error: "LKP_GETCLIENT" failed validation and returned validation status "VS_ISBROKEN".
Error4:
DFT-CURRENCY:Error: One or more component failed validation.
The lookup that is failing validation is simply using a basic connector - dragged and dropped from source to destination and one tick for the output - if i preview it i get the output and if i run it from BIDS all goes through fine
Does anyone know how to solve this? I dont know if it makes any difference but the Source connector is the Package level and the lookup values are in a project level connector.
If this is the issue - how do i solve it? I cant change that connection to project level as it will no longer be able to feed the Foreach loops in the project.
Thanks

Are you sure you've configured the connection properties for this connection properly? Is it also based on environment variables? If yes, have you configured them correctly?
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

SSIS Deployment in 2012/2014

Hi, I upgraded SSIS packages from 2008 R2 to 2014 and deployed to IntegrationServicesCatalogs->ssisDB. Now I m trying to use DTExec to schedule the packages in SQL Agent. I saved the package configurations to SQL Server table. Can someone help in the
below command? I m getting the error "Cannot find the folder" when I run the package. All the packages are deployed into SSISDB->GBI Folder->GDM Project.
Would appreciate any help, THank you!
"C:\Program Files\Microsoft SQL Server\120\DTS\Binn\DTExec" /SQL "\SSISDB\GBI\GDM\Master Load.dtsx" /SERVER "GBIVCST01" /CHECKPOINTING OFF /REPORTING E /CONNECTION Admin;"Provider=SQLNCLI11;Data Source=BRIDCDW01\BRIDCDW01;Persist
Security Info=True;Password=GBI1;User ID=G_BI;Initial Catalog=GDMConfiguration1"

>>>> I saved the package configurations to SQL Server table.
Where to? I mean a database? It is possible the Agent cannot read the data? Do you run it locally?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

SSIS Deployment VS 2013

HI,
I've got an SSIS solution file with project deployment model in VS 2013 and would like to deploy that to SSISDB on different environments.
All these days I followed the regular way to create a project in SSISDB and deploy it to that. Now want to find out if i can automate this process and so got some questions
1. Can we automate the process of creating a project on SSISDB based on our SSIS project name?
This will be like when we do a deployment it should check if the project exists or not on SSISDB based on our SSIS project name, if the project exists we just deploy the packages in the project and if the project does not exists in SSISDB it will
create that project and deploy the packages.
2. Can we also automate the process of creating environments?
In traditional way we manually create the environment variables under environment tab of SSISDB, but can we make that also as part of deployment? Like when we are releasing to Dev server we look if that particular Dev variable exists on that server,
if it exists we just update the existing stuff and if it does not exists we just create it.
Thanks!

I found a series of this blog posts has the answer, e.g. creating the Environment http://blogs.msdn.com/b/dataaccesstechnologies/archive/2013/10/08/ssis-2012-automation-part-2-create-environment-map-it-to-project-and-package-level-parameters-and-assign-reference-to-project.aspx
Checking if folder exists can be done by say trying to apply a different variable value and if it fails then it does not exists, but there are may be better ways.
Arthur
MyBlog
Twitter

Ssis deployment process in Server/remote box

Could you please suggest the best approach for package configuration and deployment process.
1. The SSIS package need to deployed in remote box , so what should be set the encryption property , i.e encrypt with password or which option should be selected.
2. Which type of Package configuration will be the best way to configure the SSIS package.
3. Since we are planning to run the SSIS package , through SQL Agent jobs , which will be best way to deploy the package.

Why don't you read MSDN?
Re #1, 3, if you deploy to MSDB or Catalog (SSISDB) then "Rely on server" is the one you need, otherwise any other than "user key", for all others you need the password included and the connection string with all the credentials. Oftentimes a proxy is needed
to run a package via an Agent. I suggest you deploy to MSDB/Catalog.
Re 2: Depends. Most times a config file (in XML) is the way to go though.
Arthur My Blog

How to migrate an existing Microsoft SSIS deployment if it is decided to replace SQL Server with an Oracle database?

Hi Oracle Gurus!
Currently, I am designing an ETL solution that transforms and loads a lot of data from flat files and sends it to an SQL Server 2008 R2 database for storage. However, at a future point of time, it may be decided to add or even replace SQL Server with an Oracle 11g database.
Currently, I am writing script transforms in C# to dynamically generate SSIS packages to tansform and load the data into SQL Server. But considering that in future, an Oracle 11g or 12c database might be added to, or replace the SQL Server database, how do I make my script transforms (or whatever else I am developing currently for SQL Server) reusable to the extent possible?
Or more precisely, what steps do I take, from an Oracle point of view, to ensure that any future migration of data to an Oracle database would be smooth to the extent possible?
Looking up to my Oracle Gurus for enlightenment in this matter!
Novice Kid

When you're writing your on C# code to load data into the SQL Server you have to modify the routines so that they will work with Oracle.
One approach is to use the extproc agent which would allow you to directly call external programs with all the logic in it to perform the load of your files and to put the data into the Oracle database. Another option would be to use utl_file package (or equivalents) which will allow you to open external files from your Oracle database and to directly read its content and then to pass it to the related tables.

Mssql2012 SSIS deployment error: Could not fined Source.conmgr file

Techies--
I'm deploying a colleague's project today which includes 60+ packages. I suspect "Source.conmgr" was probably a default early on that was deleted. Is there an quick way to determine which package may still be referencing this? Unfortunately
the message shows up in the build on one of the key calling packages that invokes the others...

Hi plditallo,
Glad to hear you have resolved the issue, thank you for the sharing.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

SSIS Deploy package - Too many configurables - how to do quickly ?

I am trying to create a deployment config/file for package. I have many configurables like variables, connection managers etc. For variables, I only want to configure the value and nothing else. I don't want to go to each variable and then click the
checkbox for that. Is there a quicker way of configuring the package for deployment ?

Hi blastoSO,
In my opinion, I still recommend that you modify the package configurations from the SSDT/BIDS. If you don’t want to modify the package configurations through the Package Configurations Organizer in the SSDT/BIDS, you can manually modify the .dtsConfig file.
When doing this, be careful to make sure the syntax of the XML confirmation file is correct. The smallest unit we can delete from the XML configuration file is as follows:
<Configuration ConfiguredType="Property" Path="\Package.Variables[User::var2].Properties[Expression]" ValueType="String">
<ConfiguredValue />
</Configuration>
Regards,
Mike Yin
TechNet Community Support

What is the most common way of deployment of SSIS package?

Hi everybody,
I am new to SSIS. I have created an SSIS package in development server. I want to deploy it to production server. What is the most common and efficient way of deployment? Please let me know the procedure in details.
Thanks in advance.
Regards,
Anujit Karmakar
Anujit Karmakar Sr. Software Engineer

Hi Anujit,
SSIS deployment is nothing but just to copy the .dtsx files from DEV to PROD. (Either file system or SQL Server)
File system deployement is the common way of SSIS deployment
1. File system deployment using manifest file
http://sivasqlbi.blogspot.in/2012/05/ssis-step-by-step-process-of-creating.html
2. SQL Server deployment using manifest file
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
3. By using Command line
http://www.mssqltips.com/sqlservertutorial/215/command-line-deployment-tool-for-ssis-packages/
If you are working on SQL Server Data Tools (2012), then you need to go through below article
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-1-of-2/
-Vaibhav Chaudhari

Manifest Deployment Fails

Hi,
I had a working SSIS package deployment methodoligy (double clicking on the manifest file) and suddently it's not working. I'm running SSIS as administrator and get the error below.
TITLE: Package Installation Wizard
You need to specify the full path to a SSIS deployment manifest file.
When I remote into the Server, I can get the Wizard to run and deploy the package; however, I think there is an encryption error as nothing is actually processes when I run the associated job.

Is it on a 64-bit box?
Are your *.SSISDeploymentManifest files on a share or mapped drive, or on a local drive? Microsoft support is investigating some troubles with UNC shares and mapped drives with the dtsinstall.exe deployment wizard currently.
Another point of confusion is that it works/fails depending on which bitness of the tool is run and the version (90 or 100) of the tool in side-by-side situations.
Compare running the different versions and bitness from the command line or the run dialogue in the start menu...
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtsinstall.exe" "c:\folder\file.ssisdeploymentmanifest"
"C:\Program Files\Microsoft SQL Server\90\DTS\Binn\dtsinstall.exe" "c:\folder\file.ssisdeploymentmanifest"
"C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtsinstall.exe" "c:\folder\file.ssisdeploymentmanifest"
"C:\Program Files\Microsoft SQL Server\100\DTS\Binn\dtsinstall.exe" "c:\folder\file.ssisdeploymentmanifest"
Thanks, Jason
Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

Trying to Execute Catalog SSIS Package using Catalog stored proc by a Master SSIS package inside a Loop

Hi Guys ,
To Execute Packages deployed in Catalog , I have created a wrapper SP which internally calls catalog SP ( below is the code )
ALTER PROCEDURE [Publish].[usp_ExecutePackages]
@PackageName NVARCHAR(255)
, @ProjectFolder NVARCHAR(255)
, @ProjectName NVARCHAR(255)
AS
BEGIN
SET NOCOUNT ON;
DECLARE @Execution_id BIGINT ;
EXEC [SSISDB].[catalog].[create_execution] @package_name
= @PackageName
, @execution_id
= @Execution_id OUTPUT
, @folder_name
= @ProjectFolder
, @project_name
= @ProjectName
, @use32bitruntime=
True;
EXEC [SSISDB].[catalog].[set_execution_parameter_value]
@execution_id,
@object_type=50,
@parameter_name=N'SYNCHRONIZED',
@parameter_value=1
EXEC [SSISDB].[catalog].[start_execution] @Execution_id
Since i have multiple Packages , I am looping through list of PackageName and trying to pass package names to this SP by ExecureSQLTask inside ForLoop Container . But it errors out saying
"Cannot access the package or the package does not exist. Verify that the package exists and that the user has permissions to it.
BUt same Execute SQL task , if i keep it outside the ForLoop Container it works perfectly fine .
I am clueless , Please Please HELP me ASAP :(
Question :
How is that possible to execute same SP with same parameter outside Container , But not in SEQUENCE or FORLOOP or FOREACH Container ?
Also
How to make a master package to execute SSIS deployed packages via TSQL using catalog stored proc ?
Please help me out .
Thanks
Prasanna Selvaraju

Hi ,
After debugging i am getting parameter values as
{Extract - ARTL.dtsx\r\n} Unable to evaluate the expression.
Why do i get \r\n which i dont want in parameters .
Actually i pick the values of package name from a custom table . I check it there are no spaces in the cell.
Any IDEA WHY ? Please help
Finally it worked to call Wrapper Class for EXEC [SSISDB].[catalog].[create_execution]
stored procedure .
Basically , ERROR MESSAGE is culprit
"Cannot access the package or the package does
not exist. Verify that the package exists and that the user has permissions to it.
Above Message : causing us to think
its an Access issue , But actually when you pass parameter incorrectly even a " " space or "\n" extra to value, you will get that error .
Nothing related to access problem .
Actually , In the parameter which i was passing :
{Extract - ARTL.dtsx\r\n} --> String with Enter / Carriage Return and Break line was there
I have removed the Enter in that variable value .
Now its WORKING FINE ! Hurry :D :)

Failed to locate project named ... in SSIS 2012 package scheduled in agent

Hi
I have 2 packages that are deployed using Project deployment model on a, the are scheduled to run every 1/2 hour, for the last 2days the have been failing with Failed to locate project named ...:A .Net framework error occurred during execution of user defined
routine or aggregate "decript_binarydata": System.IO.LoadException Could not load file or assembly.....The thing is that the package was working without issue, this seems to be a decryption issue, so I believe it is to do with Project Deployment
model, but I am not sure
Any help would be much appreciated
Regards
Andy
CRM 4, SQL Server and .Net developer using C#

Hi Andy,
Based on my research, please refer to the following suggestions to fix this issue:
Change the SQL Server Service Account from built in default “NT Service\MSSQLSERVER“ to another account with admin rights on the system.
Grant appropriate permissions to SQL Server Service Account & SQL Agent Service Account.
1. Note down your SQL Server Service Account & SQL Agent Service Account.
2. Go to Start-> Run-> secpol.msc-> Local Policies->User Rights Assignment
3. Check if these 2 accounts are a part of the following policies.
    • Log on as a service
    • Act as part of OS
    • Adjust memory quotas
    • Logon as batch job
    • Replace a process level token
4. If not, add them explicitly.
5. Reboot the machine
Repair the SQL Server instance to test the issue again.
The following two blogs are for your references:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2012/08/20/error-while-deploying-ssis-2012-project-from-ssdt-to-ssis-catalog-system-componentmodel-win32exception-a-required-privilege-is-not-held-by-the-client.aspx
http://blog.oraylis.de/2013/09/fixing-sql-2012-ssis-deployment-error-6522-a-required-privilege-is-not-held-by-the-client/
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

OLE DB Destination" failed validation and returned validation status "VS_ISBROKEN.

Hi
I have a package which has 10 sequence containers. Have 10 Flat File Source files and all is working perfect on BI Debug mode. When I deploy this package to server I am getting the following error.
I have changed the property Retain the same connection = True but same problem. I have changed the data flow task to Load Project instead of Load Into Project but in error message it is still showing the old name. I have tried to remove the whole step i.e.
Removed Load into Project Data flow with sequence container but I am getting the same error message.
I am not able to understand the reason. Any Idea why am I getting the same error message even I do not have the Data Flow named Load Into Package. It is in SSIS 2008 and being deployed on SQL 2012 server.
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 15:28:32 Error: 2014-07-22
15:28:36.86 Code: 0xC020201B Source: Load Into Project OLE DB Destination [62] Description: The number of input columns for OLE DB Destination.Inputs[OLE DB Destination Input] cannot be zero. End Error Error:
2014-07-22 15:28:36.86 Code: 0xC004706B Source: Load Into Project SSIS.Pipeline Description: "OLE DB Destination" failed validation and returned validation status "VS_ISBROKEN". End Error
Error: 2014-07-22 15:28:36.86 Code: 0xC004700C Source:
Load Into Project SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-07-22 15:28:36.87 Code: 0xC0024107 Source: Load Into Project Description:
There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 15:28:32 Finished: 15:28:36 Elapsed: 4.39 seconds. The package execution failed. The
step failed.
Many Thanks.
MH
this the error log
starttime
endtime
event
source
message
57:26.0
57:26.0
OnError
Load Into Project
The number of input columns for OLE DB Destination.Inputs[OLE DB Destination Input] cannot be zero.
57:26.0
57:26.0
OnError
Load Into Project
OLE DB Destination failed validation and returned validation status "VS_ISBROKEN".
57:26.0
57:26.0
OnError
Load Into Project
One or more component failed validation.
57:26.0
57:26.0
OnError
Load Into Project
There were errors during task validation.
57:19.0
57:19.0
OnPostExecute
Load Into TrialBalance
57:19.0
57:19.0
OnPostExecute
Trial Balance
57:19.0
57:19.0
OnPostExecute
SSIS_LoadCheck_CoreManGroup
57:19.0
57:19.0
PackageEnd
SSIS_LoadCheck_CoreManGroup
End of package execution.
57:18.0
57:18.0
OnPostExecute
Load Into JournalLine
57:18.0
57:18.0
OnPostExecute
JournalLine
57:18.0
57:18.0
OnPreExecute
Trial Balance
57:18.0
57:18.0
OnPreExecute
Truncate TrialBalance
57:18.0
57:18.0
OnPostExecute
Truncate TrialBalance
57:18.0
57:18.0
OnPreExecute
Load Into TrialBalance
57:07.0
57:07.0
OnPostExecute
Load Into Journal Type
57:07.0
57:07.0
OnPostExecute
JournalType
57:07.0
57:07.0
OnPreExecute
JournalLine
57:07.0
57:07.0
OnPreExecute
Truncate Table JournalLine
57:07.0
57:07.0
OnPostExecute
Truncate Table JournalLine
57:07.0
57:07.0
OnPreExecute
Load Into JournalLine
57:05.0
57:05.0
OnPostExecute
Load Into UserName
57:05.0
57:05.0
OnPostExecute
UserName
57:05.0
57:05.0
OnPreExecute
Business Area
57:05.0
57:05.0
OnPreExecute
Truncate Table Business Area
57:05.0
57:05.0
OnPostExecute
Truncate Table Business Area
57:05.0
57:05.0
OnPreExecute
Load Into Business Area
57:05.0
57:05.0
OnPostExecute
Load Into Business Area
57:05.0
57:05.0
OnPostExecute
Business Area
57:05.0
57:05.0
OnPreExecute
Cost Centre
57:05.0
57:05.0
OnPreExecute
Truncate CostCenter
57:05.0
57:05.0
OnPostExecute
Truncate CostCenter
57:05.0
57:05.0
OnPreExecute
Load Into Cost Centre
57:05.0
57:05.0
OnPostExecute
Load Into Cost Centre
57:05.0
57:05.0
OnPostExecute
Cost Centre
57:05.0
57:05.0
OnPreExecute
Project Status
57:05.0
57:05.0
OnPreExecute
Truncate Table Project Status
57:05.0
57:05.0
OnPostExecute
Truncate Table Project Status
57:05.0
57:05.0
OnPreExecute
Load Into Project Status
57:05.0
57:05.0
OnPostExecute
Load Into Project Status
57:05.0
57:05.0
OnPostExecute
Project Status
57:05.0
57:05.0
OnPreExecute
Project
57:05.0
57:05.0
OnPreExecute
Truncate Table Project
57:05.0
57:05.0
OnPostExecute
Truncate Table Project
57:05.0
57:05.0
OnPreExecute
Load Project
57:05.0
57:05.0
OnPostExecute
Load Project
57:05.0
57:05.0
OnPostExecute
Project
57:05.0
57:05.0
OnPreExecute
JournalType
57:05.0
57:05.0
OnPreExecute
Truncate Table Journal Type
57:05.0
57:05.0
OnPostExecute
Truncate Table Journal Type
57:05.0
57:05.0
OnPreExecute
Load Into Journal Type
57:03.0
57:03.0
OnPostExecute
Load Into Entity
57:03.0
57:03.0
OnPostExecute
Entity
57:03.0
57:03.0
OnPreExecute
Account
57:03.0
57:03.0
OnPreExecute
Truncate Table Accounts
57:03.0
57:03.0
OnPostExecute
Truncate Table Accounts
57:03.0
57:03.0
OnPreExecute
Load Into Account
57:03.0
57:03.0
OnPostExecute
Load Into Account
57:03.0
57:03.0
OnPostExecute
Account
57:03.0
57:03.0
OnPreExecute
UserName
57:03.0
57:03.0
OnPreExecute
Truncate Table User Name
57:03.0
57:03.0
OnPostExecute
Truncate Table User Name
57:03.0
57:03.0
OnPreExecute
Load Into UserName
57:02.0
57:02.0
PackageStart
SSIS_LoadCheck_CoreManGroup
Beginning of package execution.
57:02.0
57:02.0
OnPreExecute
SSIS_LoadCheck_CoreManGroup
57:02.0
57:02.0
OnPreExecute
CoA
57:02.0
57:02.0
OnPreExecute
Truncate Table CoA
57:02.0
57:02.0
OnPostExecute
Truncate Table CoA
57:02.0
57:02.0
OnPreExecute
Load Into CoA
57:02.0
57:02.0
OnPostExecute
Load Into CoA
57:02.0
57:02.0
OnPostExecute
CoA
57:02.0
57:02.0
OnPreExecute
Entity
57:02.0
57:02.0
OnPreExecute
Truncate Table Entity
57:02.0
57:02.0
OnPostExecute
Truncate Table Entity
57:02.0
57:02.0
OnPreExecute
Load Into Entity

Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 15:28:32 Error: 2014-07-22
15:28:36.86 Code: 0xC020201B Source: Load Into Project OLE DB Destination [62] Description: The number of input columns for OLE DB Destination.Inputs[OLE DB Destination Input] cannot be zero.
22 15:28:36.86 Code: 0xC004700C Source: Load Into Project 22 15:28:36.87 Code: 0xC0024107 Source: Load Into Project Description: There were errors during task validation. End
Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 15:28:32 Finished: 15:28:36 Elapsed: 4.39 seconds. The package execution failed. The step failed.
Hi MustafaH,
According to the error message(hightlight above), it seems it's a mapping issue that Naarasimha point out in the post above. Please check this carefully.
An OLE DB destination includes mappings between input columns and columns in the destination data source. You do not have to map input columns to all destination columns, but depending on the properties of the destination columns, errors can occur if
no input columns are mapped to the destination columns.
Reference form: http://msdn.microsoft.com/en-us/library/ms141237.aspx
In your post, you said that it is in SSIS 2008 and being deployed on SQL 2012 server. Do you mean that you create the package deployment utility by using SSIS 2008, and then implement SSIS deployment in SSIS 2012 environment? If so, you need to
convert the project to package deployment model to generate Manifest file in SSIS 2012. Please see:
Use the SQL Server 2008 version of Business Intelligence Development Studio to develop and maintain packages that are based on SQL Server 2008 Integration Services (SSIS)
Use SQL Server Data Tools - Business Intelligence for Visual Studio 2012 to develop and maintain packages that are based on SQL Server 2012 Integration Services (SSIS).
For more information, please see:
Interoperability and Coexistence (Integration Services):
http://msdn.microsoft.com/en-us/library/bb522577.aspx?ppud=4
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

SSIS package not working on 2012 Integration Service Catalog deployment

I've set up a package that imports data from an excel spreadsheet(my only possible data source). I deployed it and it worked for a while and then broke. I had to switch to a generated connection string for excel with IMEX=1 to make things work.
Now it works fine on from Visual Studio on my local machine, but when I run it from Integration Services I get:
"The external column "<COLUMN NAME>" needs to be updated, for every column in the spreadsheet. I am using the same excel file on my local machine as on the other machine.
Why can't I get it to work when it's deployed to the SSIS Server?

Hi,
Excel files are a bit tricky to work with. Any small change in data type, metadata can make your package fail.
I have had such experience earlier. The file contents, columns everything was same but it used to fail with same metadata issue.
Here is what helped me:
1. I tried to clear all formatting using the excel formatting options and it worked for me. But we can't ask the users to do all these things manually before uploading files to the application.
2. So, I created a new excel file and created all column headers manually. Please make sure don't copy paste from any other excel file otherwise formatting and metadata will get changed.
3. Once you have the template ready. Configure your package Excel columns according to the template.
4. Now, If you copy and paste data into this plain formatting free file, data will adapt the template settings and won't give the metadata errors.
5. We uploaded the same template on our application and users created the data in same template which resolved the issue for us.
CSVs on the other hand don't have any such issues.
Hope this helps. Good Luck!

Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

Hi,
how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
This question has worried me for days.
Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
Or just an new solution instead of using the catalog.deploy_project?
best wishes from Qingyuan Lee.

Sorry, my description may be confusable.
I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
In fact, I don't care about the authority.
I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
so, using EXECUTE AS to change the execution context is accaptable.
The requirement for a Windows Authentication Account makes sense.
I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
Thanks very much for your help.

How to deploy parent child SSIS package to production/live server.

Hi all I am very new to SSIS. I have got SSIS package developed by some other guy this package reads data from flat files and stores to database after mapping.
Flow: 1) First package extract records from flat file and stores in table. 2) Then it calls child package using Execute package tasks. 3) Then child package do some calculations and update the database table.
SSIS is using Environment variable to get database information.
Every thing is working fine but now I want to deploy this package to my client's server.
Ques: Do I need to copy and paste files from bin folder and paste on clients machine?
What I Tried: I copy files from bin folder and placed on my local computer. Then I create a job in MSSQL and run the job. Package runs perfectly. But Later I changed location of my project and problem starts job stops working.
Issue: Error says location of child package is not available(As I changed position of my project files)
Kindly suggest what to do.

Hi Anuj,
The issue occurs because the path of the child package is invalid once you change the location of the project. When configuring the child package reference for Execute Package Task, we can configure it to use Project Reference or External Reference:
As for the Project Reference, it is used when the project is not deployed or the project to deployed to the SSISDB catalog in SSIS 2012.
As for the SQL Server External Reference, it is used when the project or child package is deployed to the msdb database. The File System External Reference can be used no matter whether the child package is deployed or not.
Since the SQL Server Agent job runs correctly after you copied the bin folder to the local computer, it seems that the Execute Package Task uses File System reference and reference to a mapped network driver which maps to the folder that contains the original
IS project. Otherwise, the SQL Server Agent job should fail because of the invalid path of the child package even if you don’t change the location of the original IS project.
In your scenario, after copying the bin folder to your local computer, it is recommended that you install the child package to the File System or msdb on your local server, and then edit the parent package in BIDS/SSDT to change the reference of the installed
child package from the File System or SQL Server storage. After that, you can but don’t have to install the parent package.
Regards,
Mike Yin
TechNet Community Support

SSIS Deployment

Similar Messages

Maybe you are looking for