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!

Similar Messages

SSIS 2012: Integration Services Catalog not showing data for most recent executions

Techies--
Under a previous deployment of an SSIS package, I was able to go to the Integration Services Catalog, look under the folder-->project--> package then right click and request a standard report for all executions. The report would display
the execution details.
Today a colleague recently deployed a newer version of the same package to a test server... which is failing from a job set up via sql agent. I went to look at the root cause by going to the Integration Services Catalog to review the report. No execution
data appears. I looked at the filter--compared it to the filter I have set on the production copy of the stable version. The folder name, package name and project name match. Both have a status of 'All'. The date range is the same (2/19 - 2/25).
In fact, I went back to the test deployment and changed the date range to the date of the last failure (1/30). Now I see data only from 1/30 but none for today's execution.
Something must have happened in the deployment process--but what? How do I debug this issue with the reports--but even more importantly, how do I get to the raw execution data to see what the story is on the failed execution itself?

@Arthur, thanks for responding. In a nutshell, I searched through the ssisdb.catalog.event_messages table to determine roughly the same thing you determined--an execution for that package (or for that matter, any misnamed package) with today's timestamp
simply never occurred--even though the job agent log appeared to indicate it had.
I re-deployed the package ... forced an execution with an interactive run from the catalog... and viola! The execution info appeared through the standard reports as expected.
Any idea where I could/should look for a wayward deployment? (BTW, the report for validations showed no data either on that first deployment).

Sql Server 2012 Integration Services Catalog views - cpu usage history

Hi,
I am new to SQL Server 2012. I have deployed and executed a SSIS package on the Integration Services catalog.
Now, to analyze the performance of the executed package I wish to query the SSISDB catalog views to retrieve the cpu & memory usage history. Please let me know in which catalog view/table I can find this info.
There is a column named "Process_Id" in the "catalog.operations" table. Can we tie this id to the Sql Server pid/kid and then retrieve the cpu
usage history ?
** I am using Sql Server 2012 **
Thanks

Hi All,
Thanks all for your inputs. One final question -
As I mentioned earlier, the Sql Server 2012 catalog views
DO NOT capture various performance metrics
(e.g. cpu usage history, memory usage history etc) of
an executing SSIS package . However, I am cognizant of the fact that it is possible to retrieve this exact info
(ie. cpu usage history, memory usage history etc) for
a Sql-Server internally generated SPID (present in [sys].[dm_exec_sessions]).
The approach is to find a way to join/relate the catalog provided "Process_id" to the Sql Server generated internal SPIDs in a session. If I am successful in joining these 2 process ids together,
it will allow me to gather all the information available from both sides - ie the catalog views + the sql-server internal process SPIDs of the session. Thus, by tagging the SSIS pprocess_id to
its sql-server session it will allow to retrieve the resource usage details by the executed SSIS process.
**Please also let me know if the above could be achieved by any other approach.
Any help is appreciated.
Thanks

SSIS Package Not working

Hi
We have SSIS Package in which all the tasks in control flow are connected with "Completion Precedence".
Ideally it should execute all the tasks irrespective of failed or successful execution of any of the task. And this works as expected from BIDS.
But when package is scheduled from SQL Server Agent job (Single step), it doesn't execute next task (Execute SQL Task) if there is failure with any of the task before that (Execute
SQL task) even though they are connected with Completion precedence.
We have several Execute Package tasks which call child packages to load the data and all are executed in parallel. There is one Execute Sql task at the end of one of the Execute Package
task (Connected using completion precedence) which calls stored procedure to do some cleansing activities.

I have now enabled the log and it seems that Execute SQL Task was executed but it didn't take any time to execute. Job started at 5:44:42 AM and ended at 5:44:42 AM. It logged the event Preexecute and PostExecute both at the same
time 5:44:42 AM but data was not updated through the SP but no Error event logged. Again when I ran SP anually it worked fine and updated data. SP Takes somewhere around 2 mins to execute.

ForEach Loop Container Mapping Variable From SSIS Package Not Working In SQL-Server StoredProcedure

I have an SSIS package that uses a ForEach Loop Container to enumerate Excel Files in a dir. I also have a Task Flow that inserts data from those Excel files into SQL-Server.
Im trying to insert the file names into a column into the same table in SQL-Server by using a mapping variable in my StoredProcedure.
Im having trouble with my MappingVariable at the end of the script with red squigglies. The following is my StoredProcedure script.
CREATE PROCEDURE [dbo].[Insert_F_STG_v2]
-- Add the parameters for the stored procedure here
@Hrs float,
@Type nvarchar(100),
@SN nvarchar(100),
@Op nvarchar(100),
@[USER::CurrentFileName]
AS
BEGIN
SET NOCOUNT ON;
INSERT INTO [CRM_RC].[dbo].[F_StgTbl]
[Hrs],
[Type],
[SN],
[Op],
[Report_Date]
VALUES
@Hrs ,
@Type,
@SN,
@Op,
@[USER::CurrentFileName]
END
The last @[USER::CurrentFileName] in the Values block at the bottom of the script is the one giving me issues.
The following is the error:
Msg 102, Level 15, State 1, Procedure Insert_F_STG_v2, Line 95
Incorrect syntax near 'USER::CurrentFileName'.

This seems to be the solution, but get the following exception:
[Derived Column [2]] Error: The "Derived Column" failed because truncation occurred, and the truncation row disposition on "Derived Column.Outputs[Derived Column Output].Columns[Derived Column 1]" specifies failure on truncation. A truncation error occurred
on the specified object of the specified component.
AND: [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Derived Column" (2) failed with error code 0xC020902A while processing input "Derived Column Input" (3). The identified component returned
an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.

Package working fine in SSDT but not in integration services catalog or sql job

Hi All
we have created a package which contains Project parameter , when we tried to run the package in SSDT it is working fine . we deployed the project to sql server and we want to test the package . we executed the package ( for testing purpose
we didnt refrenced Project parameter to any env variable ) from integration services catalog the package is getting success but the files are not moving ( deserved task in package ) , so i have created a job and run the package from the job ,, here
the files moved from stage 1 and stage 2 but from there it is not moving . do we missed any steps ?
Surendra Thota

Hi All
we have created a package which contains Project parameter , when we tried to run the package in SSDT it is working fine . we deployed the project to sql server and we want to test the package . we executed the package ( for testing purpose
we didnt refrenced Project parameter to any env variable ) from integration services catalog the package is getting success but the files are not moving ( deserved task in package ) , so i have created a job and run the package from the job ,, here
the files moved from stage 1 and stage 2 but from there it is not moving . do we missed any steps ?
Surendra Thota

Virtual Lab: Exploring SQL Server 2012 Integration Services - Setup script fails

I am trying to work through a Lab, but cannot get past the Setup script stage.
The lab is "Exploring SQL Server 2012 Integration Services". I have tried this several times (with new lab instances) and the result is always the same.
I double click the Setup command ... Press 2 ... when the popup dialog appears I press Ok ... the progress bar completes and the messages in the text box seem to indicate everything has completed (last line says "Done"). I click Close as per the
instructions and then the script moves to the "Configure SQL Server" stage.
After a short delay a number of error messages appear: "Could not open a connection ... Login / timeout expired" etc - basically it can't find or can't connect to the server.
I expected these labs to work seamlessly :)
Anyone know what's going wrong here?
Thanks,
Larry

I am moving it to SSIS.
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

SSIS Package execution - SQL Server 2012

Hi all
I am attempting to run a deployed package manually (not via a job) through the SSMS 2012 GUI and the error dictates that my Execute Process Task cannot access on of my network drives (\\Share\Directory).
If I run the package through SSDT, it runs fine.
How can I get my package to see the required directory please? It needs read/write permissions.
Thanks.

Hi warnerrj79,
If I understand correctly, you directly execute a package through SSDT, it works fine. When you right-click on a package under Integration Services Catalog \ SSISDB \ <Folder name> \ Projects \ <Project name> \ Packages \ <Package name>
and select Execute... to run a package in SQL Server Management Studio, it fails with the error ”Execute Process Task cannot access on the network drives (\\Share\Directory).”
When we execute a package under Integration Services Catalog, the package will run under the credentials used to connect to SQL Server Management Studio. Please note that we need run the package using Windows Authentication.
As to your issue, please make sure the account connects to SQL Server Management Studio has required permissions to access the shared folder.
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

ORA-12154: TNS:could not resolve the connect identifier specified Error in Integration Service Catalogs

Hi guys,
I tried to execute a package with Oracle Data Source from Integration Services Catalogs and I got the following error.
ORA-12154: TNS:could not resolve the connect identifier specified
The package runs fine from the SSIS project but once I deploy to SSIS Catalog it fails to run. I need help!
Thanks
me

Hello ,
The ORA-12154 is a very common error, always related to your local copy of the tnsnames.ora file, your listener configuration and your database name aliases.
Make sure that your listener is listening for the same service name that you are using.
Your service name might have an alias, so check for global (world) entries and local entries. Check:
$ORACLE_HOME/network/admin/tnsnames.ora
Check your global_name setting with this SQL:
select * from global_name;
Ref :
http://www.dba-oracle.com/t_ora_12154_tns_resolve_service_name.htm
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

What happens when a VM with 2012 Integrations Services migrates to a 2008 R2 Hyper-V server?

I've been going through our Hyper-V environment to make sure our VMs have the latest, greatest Integration Services installed. I found one 2012 running a 2012 version of Integration Services on this 2008 R2 Hyper-V server. What kind of issues can this
cause? Should I uninstall the current version and 'downgrade' them to 2008 R2?
Orange County District Attorney

Hi,
No, you should not. If the operating system is supported on a hyper-v version you can use it. This means if Windows Server 2012 is supported on Windows Server 2008 R2 hosts you can use Windows Server 2012 or Windows Server 2008 R2 with the Windows Server
2012 integration services installed as a guest OS.
You can find supported guest OS lists here
http://social.technet.microsoft.com/wiki/contents/articles/2761.hyper-v-supported-guest-os-list.aspx
http://OpsMgr.ru/

When migrating ssis packages from 2005 to 2012 Activex Script Task component doesn't exist in 2012 version

Hello,
We are migrating the ssis packages from 2005 to 2012.
I'm unable to convert Activex Script Task from 2005 vesrsion to 2012 because in 2012 version Activex Script Task doesn't exist.
Can anyone please let me know what is the alternative way to convert Activex Script Task from 2005 vesrsion to 2012?

Hi Vinay9738,
Have you tried to upgrade the SSIS 2005 packages to SSIS 2012 packages by using the SSIS Package Upgrade wizard? In certain cases, ActiveX script in SSIS won’t work and we need to either modify the script or replace the ActiveX Script with stock SSIS
tasks. You can find the mapping between some most common patterns used in DTS ActiveX Script and SSIS native tasks from the following link:
http://help.pragmaticworks.com/dtsxchange/scr/ActiveX%20Script%20Task.htm
Here is also a useful link about how to convert ADODB object of ActiveX Script to SSIS tasks:
http://help.pragmaticworks.com/dtsxchange/scr/FAQ%20-%20How%20to%20convert%20ADODB%20object%20of%20ActiveX%20Script%20to%20native%20SSIS%20Task.htm
Regards,
Mike Yin
TechNet Community Support

What works in 2008R2 is not working in 2012 SP1

Setup:
Visual studio 2010 and 2012.
Database: both 2008R2 and 2012 SP1
Issue:
I have a CLR routine that does bulk update.
I have trigger on the tables that are being updated.
Using the same code and the same data, This bulk update query works in 2008, but does not work in 2012, WHEN there is more than one record to be updated.
My query is simply an update statement, updating table 1 from fields in table 2
I get no errors when I trace through it in Visual studio 2012, the data simply doesn't update.
However, if I run it in studio manager, I will get a range of errors, like, 'statement is terminated', or that there was an error in the trigger, or that it completed successfully, but the data does not update.
Disabling and re-enabling the trigger works, but that's not a good idea, and since I have many bulk update queries (and have been plagued with issues for the sites that have updated to 2012), I need a solution.
Any one run into this? Any ideas about what I can do?

Well, earlier you said:
sometimes I get 'the statement was terminated' (nothing else), or I get some error occurred in the trigger, or I get query completed, but the data did not update.
So there is some confusion about what exactly is occurring. But without code, there is nothing to do but speculate. Now you say that when there are multiple records that match the criteria it does not work. I assume that your context here
is the update statement - when it updates multiple rows the trigger does not have the desired effect. If that is not correct, it would help if you could clarify a specific (and hopefully simple) scenario for this case.
But based on this information, it seems that the trigger may have an assumption built into it that is not appropriate. A trigger does not execute for each row - it executes at the statement level and the virtual tables (inserted and deleted) can contain
any number of rows (from zero - yes, zero - to any number). Often developers do not realize that the logic must be written to handle a variety of rows; rather they assume that only 1 row is present. I would also suggest that perhaps a
similar assumption is made in the update statement you posted - but I don't know the relationship between the 2 tables (Invoice and Cust) so I could be wrong. Perhaps the update statement joins a customer to multiple invoices in some cases (rather than
an assumed 1 invoice per customer)? Perhaps there is some other oddity that is not evident from a distance.

Need to re-install CS5.5 on my new hard drive. Serial number from disk package not working.

I need to re-install CS5.5 on my new hard drive. Serial number from disk package not working.

if there's a problem with the number of installations, you'll see a message about an excess activation problem.
if that's what you're seeing, contact adobe support for an activation count reset, https://helpx.adobe.com/contact.html
otherwise, attach a screenshot of the error message or quote it.

Scripting Integration Services Catalogs

Hi All,
I am using SS 2012 , So I wanna move
Integration Services Catalogs and SSISDB database from DEV server to QA server?
How can I script it out? SO I can run the script on QA machine
Thanks
Gok

Thanks for your answer Arthur but I think I couldnt explain what I wanna do
Also I have 9 years exp. in MS BI
I dont want to deploy any SSIS packages to QA server instead I want to create script for the SSISDB and Catalog
so I think I have to be able to restore SSISDB from DEV and create SSIS Catalog on QA server then I will be OK.
If you want is to backup restore SSIDB see this
http://blogs.msdn.com/b/mattm/archive/2012/03/23/ssis-catalog-backup-and-restore.aspx
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

How can I retrieve an existing .dtsx File out on Integration Services Catalog

I have a problem with an older SSIS Package and I am trying to decipher what exactly it does. I see the Package in Microsoft SQL Server Management Studio and in our Server and under
Integration Services Catalog. It has a .dtsx extension on it.
Is there any way that I can copy this Package, this .dtsx file, and open it Microsoft Visual Studio to see what exactly it does?
There doesn't seem to be anything available when I <Right-Click> on the .dtsx Package within Microsoft SQL Server Management Studio to Save As or anything similar. This is the first time I've ever had to look at something existing in the SSIS World.
I just don't know how to get it out and reference and view it is all.
Any help is greatly appreciated and Thanks in advance for your review.

Hi ITBobbyP,
Based on your description, you want to export a .dtsx package file from Integration Services Catalogs, then open it in SQL Server Data Tools.
Based on my test, we can create a project based on a project in Integration Services Catalogs, then we can look into the package in the project. For more details, please refer to the following steps:
Open SQL Server Data Tools, Click File, point to New, and click Project.
Expand Business Intelligence, and click Integration Services.
Select Integration Services Import Wizard in the middle pane, type a name for the solution, project, and specify the folder for the project, and then click OK.
In the Select Source page, select Integration Services Catalog option, specify the name of database server instance on which the catalog exists, and the path to the project in the catalog.
Click Next on the Select Source page to see the Review page.
Click Import to create a new Integration Services project based on the one you selected.
Double-click the desired package name to open the package in the project.
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

SSIS package not working on 2012 Integration Service Catalog deployment

Similar Messages

Maybe you are looking for