SSISDB.Catalog.executions

Hello Everyone,
When I try to run SSISDB.Catalog.Executions from the Management Studio, it runs with no problems. My SSIS package executes. However, when I try to run it from a stored procedure being Activated from Service Broker, nothing happens. There
are no entries in SQL Server Logs, either. My account is a member of the SysAdmin role on SQL Server.
Are additional permissions needed to run this job automatically as opposed to interactively? Or am I missing something else?
JamesNT
ATTENTION MODERATORS: I do indeed mark responses as answers after I have had time to test said response and verify that it works. Please do NOT assume you speak on my behalf by marking responses to my questions as answers. Mass-proposing responses as answers
gets on my nerves, too. Thank you.

To execute catalog.Executions you need one of the following permissions
READ permission on the instance of execution
Membership to the ssis_admin database role
Membership to the sysadmin server role
Note: Row-level security is enforced; only rows that you have permission to view are displayed.
Source
The service-broker procedure or executor needs to be authorized to execute these commands. if you are accessing it from different database then you need to enable Cross
database chaining.

Similar Messages

SSIS Service and SSISDB Catalog in SQL 2012

I have currently production Server cluster (DB Engine / SQL Agent) with 2 nodes (active/active). It has SSIS installed on it.
Also another server built in a VM environment dedicated to SSISDB with SSIS installed to move away all the ETL processing/load from the production server.
We are facing some slowness in executing SSIS and looking at moving just the SSISDB from the VM machine to the production cluster.
Here are my questions and concerns
1. What is the interaction between SSISDB and SSIS Service in the case of package executions through the SSISDB Catalog ? Can I have just SSISDB and not have the SSIS service running to execute these packages?
2. Can I scale out the SSIS with SSIS Service running on one host and the SSISDB in another host?
Any input would be appreciated.
Thanks

Hi GiriATL,
Question 2: No. We cannot create SSISDB catalog database without installing SSIS service. For more information, you can refer to the following blog:
http://blogs.msdn.com/b/pfebi/archive/2013/07/25/can-i-use-ssdb-without-installing-ssis.aspx
Question 1: As said above, the SSISDB catalog database cannot be created or work without installing SSIS. To execute a package, both DTExec utility and SSIS runtime are required, and both of them are installed by SSIS service. However, during
the execution of a package, the SSIS service is not required to be running. The SSIS service is a Windows service that monitors the SSIS packages that are running, and the SSIS service also manages the storage of SSIS packages. For more information, please
see:
http://support.microsoft.com/kb/942176
Saying you have to install the service is not 100% correct. You have to install Integration Services, which installs DTEXEC, the runtime and the SSIS service. The service itself is a byproduct necessary to support the package deployment model. You can disable
the service without any issue.
MCSE SQL Server 2012 - Please mark posts as answered where appropriate.

Migrate/Upgrade [SSIS Configurations] table 2005 to SSISDB Catalog in 2012

Hi Everyone,
Our SSIS are still in 2005 and we are using the SSIS Configurations table to store our parameters. Our set-up is based from this
link .
Now, we are moving to SSIS 2012 and wanted to maximize the SSISDB Catalog.
I just want to know how can we migrate this existing SSIS Configurations table to the new SSISDB Catalog to minimize the impact.
Also, if you guys could provide a detailed steps that would be awesome.
Many thanks.

Hi Vinxster,
According to your description, you want to upgrade SSIS 2005 packages to SSIS 2012, right?
After we upgraded SSIS 2005 packages to SSIS 2012, configurations are not upgraded. For example, a configuration file may reference an old driver that is no longer used in 2012, so we would have to manually upgrade these packages. For detail information,
please refer to the step by step in the link that sathiya.s has provided as below:
http://www.bidn.com/blogs/DustinRyan/bidn-blog/2610/upgrade-2005-2008-ssis-packages-to-2012-like-a-boss
http://www.sqlservercentral.com/blogs/dknight/2012/05/16/upgrading-packages-to-ssis-2012/
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.
Wendy Fu
TechNet Community Support

SSISDB Catalog

I'm just getting started with Integration Services in SQL Server 2012, and am a bit confused as to how things work now, especially with the SSIS catalog.
So my question is does SSIS no longer use MSDB to store packages? My old projects all deploy to a folder in MSDB in SQL Server 2008 using BIDS Helper. What does the SSIS catalog actually do?
Specifically, I ran the upgrade wizard on my current SSIS packages. The first issue is tht I have a ton of Execute Package packages, and the upgrade wizard just chose a path for the child package being called, which was not what the path I wanted.
For example, the originl path for one of the packages being called by an Execute Package task was \OLSON BI\<package name>. The wizard just chose <package name> as the path. I'm going to have te same folder structure on the new instance of SQL
Server 2012. So now I have to go in and manually change every one of those packages.
After the wizard, I now have 275 packages sitting in the SSISDB database/catalog. So now how do I get those into MSDB??
Any hints would be appreciated!
A. M. Robinson

SSIS 2012 still has the"legacy" deployment model that allows to store packages in MSDB (http://technet.microsoft.com/en-us/library/hh213290.aspx).
See
a pic http://goo.gl/bPi6LO
Using the "Catalog" SSISDB is preferred. Catalog has many features. I suggest you pick a book to learn SSIS 2012 as it is a too broad of a topic to cover in a forum reply.
SSDT 2010 or Visual Studios 2010 to 2012 can be used to author SSIS 2012 packages
Arthur My Blog

DTEXEC does not fail when SSIS package fails

I need to run my SSIS 2012 packages through the catalog with DTEXEC. This works very well, except that if my SSIS package fails, DTEXEC does not fail. I need DTEXEC to fail, so my scheduler knows that there is an error.
I use the following command:
dtexec /ISServer "\SSISDB\MyFolder\MyProject\MyPackage.dtsx" /Ser MyServer /Par $Package::Partition;201412 /Env 5
When I check the status of the run in the Catalog, it is failed.
When I used SSIS 2008, I had no problem getting DTEXEC to fail when the packages failed.

I've had the same problem, and come up with the following prototype for a SQL Script which I run in our JAMS Enterprise Scheduler. It uses SSISDB stored procedures to start the SSIS package and polls every 5 seconds to report any messages, and final
status code of the package. JAMS parameters are delimited by << >> symbols, and will need to be changed for your scheduler/batch process. I guess the script could be converted to a stored procedure. I'm also hoping it will work with SQL High
Availability groups to ensure the SSIS package runs on the server that's hosting the active database.
DECLARE @execution_id BIGINT
DECLARE @status INT= 1
DECLARE @Event_Message_id BIGINT= 0
DECLARE @Last_Event_Message_id BIGINT= 0
DECLARE @message_time DATETIME2(7)
DECLARE @message NVARCHAR(MAX)
--Create a SSIS execution for the required SSIS package and return the execution_id
EXEC [SSISDB].[catalog].[create_execution] @package_name = N'<<pPackageName>>.dtsx',
    @execution_id = @execution_id OUTPUT, @folder_name = N'<<pSSISFolderName>>',
    @project_name = N'<<pSSISProjectName>>', @use32bitruntime = <<p32Bit>>, @reference_id = NULL
RAISERROR('Starting SSIS package <<pPackageName>> with execution_id %I64d on server %s',0,0,@execution_id,@@SERVERNAME) WITH NOWAIT
--Set the logging level 0-none, 1-basic (recommended), 2-performance, 3-verbose
EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id,
    @object_type = 50, @parameter_name = N'LOGGING_LEVEL',
    @parameter_value = <<pLogging_Level>>
--Start the package executing
EXEC [SSISDB].[catalog].[start_execution] @execution_id
WHILE @status IN ( 1, 2, 5, 8 ) --created (1), running (2), canceled (3), failed (4), pending (5), ended unexpectedly (6), succeeded (7), stopping (8), and completed (9).
    BEGIN
        WAITFOR DELAY '00:00:05'
    --Get the status to see later if we've finished
        SELECT @status = status
        FROM    SSISDB.catalog.executions
        WHERE   execution_id = @execution_id
    --Are there any event messages since we last reported any?
        DECLARE curEventMessages CURSOR FAST_FORWARD
        FOR
            SELECT event_message_id ,
                    message_time ,
                    message
            FROM    SSISDB.catalog.event_messages
            WHERE   operation_id = @execution_id
                    AND event_message_id > @Last_Event_Message_id;
        OPEN curEventMessages
        FETCH NEXT FROM curEventMessages INTO @Event_Message_id, @message_time,
            @message
        WHILE @@FETCH_STATUS = 0
            BEGIN
        --We've found a message, so display it - watch out for % signs in the message, they'll cause an error if we don't replace them
                SET @message = CONVERT(NVARCHAR(MAX), @message_time, 113)
                    + ' ' + replace(@message,'%',' percent')
                RAISERROR(@message,0,0) WITH NOWAIT
                SET @Last_Event_Message_id = @Event_Message_id --Make a note that we've reported this message
                FETCH NEXT FROM curEventMessages INTO @Event_Message_id,
                    @message_time, @message
            END
        CLOSE curEventMessages
        DEALLOCATE curEventMessages
    END
--@Status indicates that package execution has finished, so let's look at the outcome, and error if there's a problem
IF @status = 7
    RAISERROR('Package Succeeded',0,0)
ELSE
    IF @status = 9
        RAISERROR('Package completed',0,0)
    ELSE
        IF @status = 3
            RAISERROR('Package Cancelled',16,1)
        ELSE
            IF @status = 4
                RAISERROR('Package failed (see error message above)',16,1)
            ELSE
                IF @status = 6
                    RAISERROR('Package ended unexpectedly',16,1)
                ELSE
                    RAISERROR('Package ended with unknown status %i',16,1,@status)

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).

SSISDB VS MSDB VS FILE SYSTEM

Hi,
Does SQL server 2012,no more prefer MSDB and File system deployments?
If not migrated what are implications in future??
is it really necessary to upgrade now??
when I use Smo, why does my package executed using SSISDB resources rather than using client resources??
Regards,
Navin
Navin.D http://dnavin.wordpress.com

BOL: "The SSISDB catalog is the central point for working with Integration Services (SSIS) projects that you’ve deployed to the Integration Services server. For example, you set project and package parameters, configure environments to specify
runtime values for packages, execute and troubleshoot packages, and manage Integration Services server operations.
The objects that are stored in the SSISDB catalog include projects, packages, parameters, environments, and operational history.
You inspect objects, settings, and operational data that are stored in the
SSISDB catalog, by querying the views in the SSISDB database. You manage the objects by calling stored procedures in the
SSISDB database or by using the UI of the SSISDB catalog. In many cases, the same task can be performed in the UI or by calling a stored procedure.
To maintain the SSISDB database, it is recommended that you apply standard enterprise policies for managing user databases. For information about creating maintenance plans, see
Maintenance Plans.
The SSISDB catalog and the SSISDB database support Windows PowerShell. For more information about using SQL Server with Windows PowerShell, see
SQL Server PowerShell. For examples of how to use Windows PowerShell to complete tasks such as deploying a project, see the blog entry,
SSIS and PowerShell in SQL Server 2012, on blogs.msdn.com.
For more information about viewing operations data, see Monitoring for Package Executions and Other Operations.
You access the SSISDB catalog in SQL Server Management Studio by connecting to the SQL Server Database Engine and then expanding the
Integration Services Catalogs node in Object Explorer. You access the
SSISDB database in SQL Server Management Studio by expanding the Databases node in Object Explorer. "
LINK: http://technet.microsoft.com/en-us/library/hh479588.aspx
BOL reference: catalog.executions (SSISDB Database)
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

How can DTExec show the execution package progress while running it in the DOS console?

[SSIS 2012]
Hi,
We need to view the package results/progress during the execution of the package by the DTExec command. Isn´t it possible?
The user can´t view the details for the execution by the GUI.
The package is deployed in the SSIDB (Catalog). The final idea is to Audit the result in a *.log file from the Batch we have created. We are not considering to use the "Logging" feature while designing the package. We expect to have same SSIS events
in the DOS console while executing it.
DTExec always says: To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report
How could it be possible?
Thanks,
Alex Berenguer

Hi Alex,
I don’t think it is possible to display the package execution details in the Command Prompt when we execute a package stored in the SSISDB catalog. Except for enabling the package logging, we have to view the execution details from the “All Executions” Standard
Report for the SSISDB Catalog.
Regards,
Mike Yin
TechNet Community Support

SSIS 2012 Scheduled SSIS package fail to start – Execution timed out

Hi
I am currently running into an issue that seem to have a live Connect issue raised for it. The following is the link to the connect issue https://connect.microsoft.com/SQLServer/feedback/details/783291/ssis-package-fails-to-start-application-lock-timeout-in-ssisdb-catalog-create-execution
There is also a blog post that explains this issue in more detail, however the solution
it provides does not work all the time and I am very reluctant to create custom stored procedures in the SSISDB. http://speaksql.wordpress.com/2013/06/27/ssis-2012-fail-to-start-execution-timed-out/
Just to give some more background. When scheduling 10 or more, in my case I scheduled 14, SQL Server Agent Jobs all executing a package in the SSIS Catalog and all kicking off on exactly the same time about 10% to 20% of these jobs fail stating one of the
following error messages:
The operation failed because the execution timed out. Source: .Net SqlClient Data Provider Started: 12:20:01 Finished: 12:20:07 Elapsed: 5.797 seconds. The package execution failed. The step failed.
Description: Transaction (Process ID 66) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Source: .Net SqlClient Data Provider Started: 14:06:48 Finished: 14:06:53
Elapsed: 4.719 seconds. The package execution failed. The step failed.
This timeout takes place both when using TSQL to start the package in the Job or when the step in the Job is set to start the package as an Integration Services Package.
Steps to recreate this:
1. Create one SSIS package that simply executes for around a minute. For example you can use an Execute SQL Task and simply execute the following TSQL "WAITFOR DELAY '00:01:00'"
2. Create 14 SQL Server Agent Jobs each executing the same package and schedule all of them to run at the same time.
3. Watch the execution of the jobs take place and note the failures. (This does not always happen and you might get one run in which everything executes without a problem. The next run might have 6 or 7 of the jobs fail.)
You can also create 14 different SSIS packages, one for each job, and the result is the same.
I am running on SQL 2012 SP1 CU4. Windows Server 2012 R2 patched to the lastest patch level.
This issue does not happen when the packages are deployed to the SSIS Package Store the way that it was done in SQL2008 and before. It only occurs when the SSIS packages are deployed to the SSIS Catalog.
Any help or feedback on this would be greatly appreciated.
Kind Regards,
Christo Olivier

Hi Tom
Thank you for the fast response. I went and increased the value by 1024KB instead of the initial
512KB. Unfortunately this seems to only alleviate the issue but does not stop it from occurring. It
is happening much less often now but still occurring intermittently.
Regards,
Christo

SSIS Catalog views are not executing from PROC calling from a service broker

Hi Exprets,
I have a package deployed on SSISDB (the new concept in MS SQL 2012, SSIS catalogs). I have t-sql code in which i will be able to execute SSIS package in SSISDB with no problems. But if i place the same t-sql code inside of a procedure which will be called
by a service broker , the code is not executing.
I am using the following code to execute a package in the SSISDB catalog
Declare @execution_id bigint
EXEC [SSISDB].[catalog].[create_execution] @package_name=N'LoadToABC.dtsx',
@execution_id=@execution_id OUTPUT, @folder_name=N'ABC', @project_name=N'LoadToABC',
@use32bitruntime=False, @reference_id=Null
DECLARE @var0 NVARCHAR(200)
= N'D:\MyData\SampleText20120830100001.txt'
EXEC [SSISDB].[catalog].[set_execution_parameter_value] @execution_id, @object_type=30,
@parameter_name=N'strFileName', @parameter_value=@var0
EXEC [SSISDB].[catalog].[start_execution] @execution_id
This code executes if run it alone or placed in a regular stored procedure , but not executes if i palce this same code inside of a procedure which is being called/executed by a service broker call like this:
CREATE QUEUE dbo.SampleQueue
WITH STATUS=ON, ACTIVATION
(STATUS = ON, MAX_QUEUE_READERS
= 1,
PROCEDURE_NAME = spMessageProcSample,
EXECUTE AS OWNER);
The problem occurs if we call the SSIS catalogs inside a proc which will be calling through a service broker queue.
I am running all these steps on my local instance of SQL SERVER 2012 in which i am the administrator.
Please advice where i am doing wrong ?
Thanks,
Jyodhu.

Hi ArthurZ,
Thanks for reply. What i ment was i tried with all the "EXECUTE AS" options. but no luck.
Can you please explain step by step if you can ? That would be great help.
This is the error message from server log.
Message
The activated proc '[dbo].[spMessageProcSample]' running on queue 'FileTableDB.dbo.SampleQueue' output the following: 'The server principal "USA\cccsat1nmg" is not able to access the database "SSISDB" under the current security context.'
I logged in with WIndows authentication (Admin) and i created all the objects including Integration services Catalog.
Thanks,
Jyodhu.

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

Job execution considerations

I've created a job on a SQL Server 2008 R2 instance. There is a step that executes an SSIS package on a SQL Server 2012 instance in the SSISDB catalog. It fails due to the following error:
Option "/ISSERVER" is not valid. The command line parameters are invalid.
This leads to the question, which version of DTEXEC is executed, the local version, i.e. SQL Server 2008 R2 or the version of DTEXEC that lives on the server where the package is stored? In other words, is "/ISSERVER" and invalid parameter on 2008
R2 but valid on 2012? If so, why was it generated by 2008 R2?
I created a job that runs the same package on the 2012 server and it runs fine.
If I generate scripts of the job from each instance, the two scripts match exactly.
My thought was that it shouldn't matter that the job lives on an older version since the command executes on the machine with the newer version but it appears that the command is validated on the older version.
Does anyone have any insight?

Hi Frank,
Based on your description, you have configured a SQL Server 2008R2 job to run a SSIS 2012 package which is stored in SQL Server 2012 instane. Right? If I have something misunderstood, please point out.
I found a piece of description regarding this scenario in this document:
http://technet.microsoft.com/en-us/library/bb522577(v=sql.110).aspx, please see:
We can run SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS) packages by using the SQL Server 2012 version of the
dtexec utility or of SQL Server Agent. Whenever a SQL Server 2012 Integration Services (SSIS) tool loads a package that was developed in SQL Server 2005 Integration Services (SSIS) or SQL Server 2008 Integration Services (SSIS),
the tool temporarily converts, in memory, the package to the package format that SQL Server 2012 Integration Services (SSIS) uses. If the SQL Server 2005 Integration Services (SSIS) or SQL Server 2008 Integration Services (SSIS) package has issues that prevent
a successful conversion, the SQL Server 2012 Integration Services (SSIS) tool cannot run the package until those issues are resolved.
In addition, the dtexec 2008 version(SSIS 2008) doesn't support to run the package was developed in SQL Server 2012 Integration Services (SSIS). For more information, please refer to the article below:
Interoperability and Coexistence (Integration Services):
http://msdn.microsoft.com/en-us/library/bb522577(v=sql.110).aspx
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

.rdl file for ssis package execution reports.

Can I get a .rdl file for the SSIS Packages execution report which shows execution timing status and etc.. .where it stores (location) and possibility of the Stored procedure for the .rdl file

Not sure where the SQL Server is storing the .rdl file for the above mentioned reports. But if you just want to get summary of ETL execution you can use something similar to below query and create your own report in SSRS.
SELECT e.executable_id AS [ID] , CASE es.execution_result when 0 then 'Success' when 1 then 'Failure' when 2 then 'Completion' when 3 then 'Cancelled' END AS [Status] , ex.folder_name AS [FolderName] , ex.project_name AS [ProjectName] , e.package_name AS [PackageName] , CONVERT(datetime, es.start_time) AS [StartTime] , CONVERT(datetime, es.end_time) AS [EndTime] , CAST(es.execution_duration AS float)/1000 AS [Duration]FROM catalog.executables e INNER JOIN catalog.executable_statistics es ON e.executable_id = es.executable_id AND e.execution_id = es.execution_id INNER JOIN catalog.executions ex ON e.execution_id = ex.execution_id AND es.execution_id = ex.execution_idWHERE package_path = '\Package'ORDER BY StartTime DESC
More info can be found
here.

Issue during Running Package using Sql Agent

hi all
I have an issue when I deployed Package and Run package using sql agent.
before a Successfully Run Package without Any error. but in job It gives me error.
Executed as user: abc\sqlserver. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 08:28:11 Error: 2014-02-12
08:28:11.86     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified
state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2014-02-12 08:28:11.97     Code: 0xC0202009
Source: PAckageNameReport Connection manager "....................."     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user .....". End Error Error: 2014-02-12 08:28:11.97     Code: 0xC020801C
Source: Import into Excel OLE DB Source [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "....................." failed
with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-02-12 08:28:11.97     Code: 0xC0047017
Source: Import into Excel SSIS.Pipeline     Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2014-02-12 08:28:11.97     Code: 0xC004700C
Source: Import into Excel SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2014-02-12 08:28:11.97     Code: 0xC0024107     Source: Import into Excel
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 08:28:11 Finished: 08:28:11 Elapsed: 0.14 seconds. The package execution failed.
The step failed.
I'm using Sql Authentication.
Kindly Help.
thanks

Hi BI_group,
According to the error message, the issue may occur due to two possible reasons: protection level of the package or the 32-bit/64-bit driver issue.
For the first possible reason, it may be that package still uses the default protection level EncryptSensitiveWithUserKey after it is deployed, however, the SQL Server Agent job runs under a different user account. To avoid the issue, you can re-deploy the
package and set the package protection level to EncryptSensitiveWithPassword or DontSaveSensitive during the deployment. If it is set to EncryptSensitiveWithPassword, we need to configure the Execution options of the job step to use the
/decrypt password option in the DTexec utility command line to decrypt the encrypted data. If the package is deployed to the SQL Server or SSISDB catalog, we can set the protection level to Rely on server storage for encryption or ServerStorage.
If it is not the case, check whether it is caused by the 32-bit/64-bit driver issue. For a 64-bit SSIS server, it uses 64-bit drivers by default, however, BIDS/SSDT uses 32-bit drivers unless the Run64BitRuntime property of the IS project is set to true.
In the BIDS/SSDT, check the Run64BitRuntime property to see if it runs in 32-bit or 64-bit runtime. This enable us to judge whether we need to check the “Use 32 bit runtime” option for the job step.
Regards,
Mike Yin
TechNet Community Support

SSIS 2012 job hangs dataflow task

hi all,
i have 2 data flow tasks in a package that run based on parameters.
the package is being run as a sql agent job using catalog execution model.
the job sometimes hangs without reason. also, when i looked at the target sql tables, only few rows have been loaded into the 2 target tables and stopped when the job hanged,
the data flow tasks loads data from source into a target sql table.please advice on why the job hangs, are there issues with the catalog model of ssis 2012 that is causing this?

Perhaps this info (scripts) somehow shed light on the problem
http://sqlblog.com/blogs/davide_mauri/archive/2014/07/23/ssisdb-analysis-script-on-gist.aspx
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

SSISDB.Catalog.executions

Similar Messages

Maybe you are looking for