SSIS Packages Pending Execution

Hi,
We are facing issue with running ssis packages from job.
The package is going to "PendingExecutionstatus" and it is struck in the same status.
We are using windows service account to run the job.
The package is running successfully if we run through a windows user account from catalog.
Please let us know if there is any way to proceed further.
We are using sqlserver2014.

Can you give some more details on this? whats the package doing? Is it having some steps like execute process task etc. If yes, please check if the service account has the sufficient priviledges to execute the exe/bat called by the execute process task.
In any case creating a proxy account and giving it required permissions and using it to run the job would be preferred
see
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
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 Package Fails when Scheduled as a SQL Server Agent Job

I have an SSIS package that runs without any problems when executed through BIDS.
However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
My question is - what is the advised way of doing this?
Thanks
Gary

Hi Garyv.King,
When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
For more detailed information about the issue, please following this KB article:
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
http://support.microsoft.com/kb/918760
You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
The following 4 issues are common encountered in the SSIS forum.
1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
2. Data source connection issue.
3. File or registry access permission issue.
4. No 64-bit driver issue.
For more information about it, please see:
How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc
Thanks,
Eileen

Errors running SQL Agent Jobs for 64 bit SSIS packages on a 64 bit server, but Source server 32 bit

Hi,
I can able ran the SSIS package in BIDS, since set to false in Run64BitRuntime property.
Then I created SQL server Agent job I tried the following ways
Step 1:
Type is set as SQL Server Integration Services Packages,
Run as - SQL Server Agent Service Account
Package source - FileSystem
then Execution option tab I selected 32 bit runtime
and then run the job I am getting the below error
Message
Executed as user: CIT\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 7:29:17 AM Error: 2013-11-28
07:29:18.57     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 07:29:18.57
Code: 0xC0014009     Source: Imports20_OAC_Gifts Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the
database server. End Error Error: 2013-11-28 07:29:18.59     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection
manager DataSource.DataExtract failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 07:29:18.59
Code: 0xC0047017     Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-2
Step 2:
Type - Operating sytem (CmdExec)
Run as - Sql Server agent service account
Command - C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe /FILE "D:\Example\Example.dtsx" /x86 /CHECKPOINTING OFF /REPORTING E
then run the job I am getting the below error
Message
Executed as user: MIS\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 6:37:58 AM Error: 2013-11-28
06:37:58.94     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 06:37:58.96
Code: 0xC0014009     Source: Example Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.
End Error Error: 2013-11-28 06:37:59.01     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection manager DataSource.DataExtract
failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 06:37:59.07     Code: 0xC0047017
Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-28 06:37:59.12     Code: 0xC004700C
Source: DFT_Example SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2013-11-28 06:37:59.16     Code: 0xC0024107     Source: DFT_Example
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1).Started: 6:37:58 AM Finished: 6:37:59 AM Elapsed: 1.373 seconds. Process Exit Code 1.
The step failed.
Note:
My source server is 32 bit and development environment in 64 bit
if anybody have idea please share your knowledge

Hi BIRam,
Based on the current information, the issue may be caused by the factor that the SQL Server Agent Service Account doesn’t have access to the MySQL server. Try to create a SQL Server Agent Proxy account that has sufficient permission on the MySQL server.
In addition, also pay attention to the package protection level setting.
For more information, please see:
http://social.technet.microsoft.com/Forums/sqlserver/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job?forum=sqlintegrationservices.
Regards,
Mike Yin
TechNet Community Support

SSIS packages go into Pending Execution state after SP1 CU7 deployment

I performed an upgrade of our SQL 2012 environment this weekend. I applied 2012 SP1 and CU7. I now notice that all my scheduled tasks for my SSIS package fail with the same message:
=====
The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
=====
In addition all package that I execute directly go into a Pending Execution state.
Has anyone else seen this behavior?
-Brian

What I found was that when a package is execute directly it goes into a 'pending execution. state. When it is invoked via job the job errors out with 'Failed to deploy project. For more information, query the operation_messages view for the operation
identifier ’123456′. (Microsoft SQL Server, Error: 27203)'
Also I discovered that importing a new package on the system would fail and SSMS could not be opened on the server via a TCP/IP connection. In addition I found the following error: at SNINativeMethodWrapper.SNIClose(IntPtr)
   at System.Data.SqlClient.SNIHandle.ReleaseHandle()
   at System.Runtime.InteropServices.SafeHandle.InternalFinalize()
   at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean)
   at System.Runtime.InteropServices.SafeHandle.Finalize()
What I found was that the .Net framework was having an issue.  I was able to resolve this by following this kb: http://support.microsoft.com/kb/2915689

ERROR WHILE MIGRATING SSIS PACKAGE FROM DEVELOPMENT TO PRODUCTION IN EXECUTION

HI,
I have a problem while executing the package after migrating from DEVELOPMENT to PRODUCTION.
We have two SQL database connections DEVMIDDLEWARE and PRODMIDDLEWARE for dev and prod respectively. When we have created package in development we have used DEVMIDDLEWARE and we have credentials in CONFIG file of that package and executed sucessfully. When
we migrated this same package to PRODUCTION when have given credentials of PRODMIDDLEWARE in CONFIG FILE of this package we are getting error as below
"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-10-28 07:41:44.24     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-10-28 07:41:44.85     Code: 0xC0202009     Source: Package Connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware"     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 'devmiddleware'.".
End Error Error: 2014-10-28 07:41:44.85     Code: 0xC020801C     Source: Package Log provider "SSIS log provider for SQL Server"     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "DEVBIZTALKDB01.RHUL_Staging.devmiddleware" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method
call failed. COM error object information is available. Source: "Package" error code: 0xC0202009 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 'devmiddleware'.". ". End Error Error: 2014-10-28 07:41:44.98
Code: 0xC0202009     Source: Package Connection manager "AGRDB01.abwr66"     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 'CC\epsdbuser'.". End Error Error: 2014-10-28 07:41:44.98     Code:
0xC020801C     Source: Data Flow Task OLE DB Source [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "AGRDB01.abwr66"
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-10-28 07:41:44.99     Code: 0xC0047017
Source: Data Flow Task SSIS.Pipeline     Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2014-10-28 07:41:44.99     Code: 0xC004700C
Source: Data Flow Task SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2014-10-28 07:41:45.00     Code: 0xC0024107     Source: Data Flow Task
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 07:41:44 Finished: 07:41:45 Elapsed: 0.859 seconds. The package execution failed.
The step failed."
Can anyone help for this error.
Many thanx in Advance

Hi Babloo,
According to the error message, the package may have failed are as follows:
The user account that is used to run the package under SQL Server Agent in PRODUCTION server differs from the original package author.
The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
The package may not run in the following scenarios:
The current user cannot decrypt secrets from the package. This scenario can occur if the current account or the execution account differs from the original package author, and the package's ProtectionLevel property setting does not let the current user
decrypt secrets in the package. In this scenario, we can change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword, then modify the SQL Server Agent job step command line to include this password.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. In this scenario, we can create a SQL Server Agent proxy account. This proxy account must use a credential
that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.
References:
SSIS package does not run when called from a SQL Server Agent job step
Run an SSIS Package Under a Different Account
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Ssis 2012 parallel execution of ssis packages using catalog database hangs

i have a simple ssis package in 2012 where I am executing several data flow tasks in parallel using sequence containers, however very often the sql job just runs forever although all the tables have been loaded or I cant see whats going on, the job neither
fails nor succeeds, just goes on executing,is there an issue with executing several data flow tasks in parallel, why does the job continue to run forver, how to troubleshoot and fix the error, please guide, are there any issues using the catalog db execution,
is that the reason this behavior is showing?

multiple execute sql tasks within sequence containers running to execute the ssis packages deployed in ssisdb in sunchronous mode using the catalog database execution model
all of the ssis packages that have the data flow taks retrieve data from source to 3 different tables.
some of them push data into the same table.
please let me know if you need more information.
the job just runs forever, looks like all the data flow tasks ran and it is still running, because I don't see an increase in the row count of the tables, I may be wrong, if I check the execution status, 1 task does not show as succeeded, I don't know why
thanks a lot for ur help, ur help is much appreciated nik

How Can I Kill Excel.exe Process After finish my Execution of SSIS Package in Sqlserver2008r2

Hi !,
am new for c# and SSIS Package Creation , I am Trying to Read Excel file, and load the value into Sqlserver using SSIS package . My Problem is , After Execution of SSIS package Still Running EXCEL.exe Process in my server. i need to
kill that process . I post my Code Exactly where am release my excel file object , please guide me where am going to wrong?
Server Configuration
OS:windows7
SqlServer :2008r2
Framework:3.5
please give me some suggestion to correct my error .
Here is My Code:
Microsoft.Office.Interop.Excel.Application xlApp;
Microsoft.Office.Interop.Excel.Workbook xlWorkBook;
Microsoft.Office.Interop.Excel.Worksheet xlWorkSheet;
var missing = System.Reflection.Missing.Value;
xlApp = new Microsoft.Office.Interop.Excel.Application();
xlWorkBook = xlApp.Workbooks.Open(filename, false, true, missing, missing, missing, true, Microsoft.Office.Interop.Excel.XlPlatform.xlWindows, '\t', false, false, 0, false, true, 0);
xlWorkSheet = (Microsoft.Office.Interop.Excel.Worksheet)xlWorkBook.Worksheets.get_Item(1);
Microsoft.Office.Interop.Excel.Range xlRange = xlWorkSheet.UsedRange;
Array myValues = (Array)xlRange.Cells.Value2;
int vertical = myValues.GetLength(0);
int horizontal = myValues.GetLength(1);
System.Data.DataTable dt = new System.Data.DataTable();
bool isNameRead = false;
// get header information
for (int i = 1; i <= horizontal; i++)
string cellValue1 = "";
object cellObj = myValues.GetValue(1, i);
if (cellObj != null)
cellValue1 = myValues.GetValue(1, i).ToString();
if (cellValue1 == "Name")
if (!isNameRead)
dt.Columns.Add(new DataColumn(cellValue1));
isNameRead = true;
else
dt.Columns.Add(new DataColumn(cellValue1 + 1));
isNameRead = false;
else
dt.Columns.Add(new DataColumn(cellValue1));
// Get the row information
for (int a = 2; a <= vertical; a++)
//string cellrowvalue = "";
string isemt = "";
object[] poop = new object[horizontal];
for (int b = 1; b <= horizontal; b++)
isemt =(string) myValues.GetValue(a, b);
if (isemt != null)
poop[b - 1] = myValues.GetValue(a, b);
DataRow row = dt.NewRow();
row.ItemArray = poop;
dt.Rows.Add(row);
xlWorkBook.Close(true, missing, missing);
xlApp.Quit();
releaseObject(xlWorkSheet);
releaseObject(xlWorkBook);
releaseObject(xlApp);
return dt;
releaseObject
private void releaseObject(object obj)
try
System.Runtime.InteropServices.Marshal.ReleaseComObject(obj);
obj = null;
catch (Exception ex)
obj = null;
MessageBox.Show("Unable to release the Object " + ex.ToString());
finally
GC.Collect();
GC.WaitForPendingFinalizers();
GC.Collect();
GC.WaitForPendingFinalizers();
Thanks
Parthasarathi Purushothaman

Why are you programmatically opening an Excel sheet in C# instead of using the DataFlow task with an Excel input?
Since your task is programmatically starting Excel via "new Microsoft.Office.Interop.Excel.Application();", it is your responsibility to stop it.
Please see "Quit":
http://msdn.microsoft.com/en-us/library/microsoft.office.interop.excel._application.quit(v=office.15).aspx

SSIS Package execution error from powershell

Hi I have written a powershell script to exec SSIS packages. I am passing variable values at runtime by reading it from a text file.
But it throws an error.
Here is my script.
#Read Data from Parameter File
$variable=Get-Content D:\Batch\Bin\ETLParameters.txt
$variable.GetType()
$dest_conn_str=$variable[1]
$mail_cc=$variable[2]
$mail_from=$variable[3]
$mail_str=$variable[4]
$mail_to=$variable[5]
$pkg_path=$variable[6]
$ps_exe_path=$variable[7]
$ps_script_cmd=$variable[8]
$ps_script_path=$variable[9]
$src_conn_str=$variable[10]
$src_sys_id=$variable[11]
#Executing SSIS packages from command prompt
$cmd = 'dtexec /f "' + $pkg_path + 'pkg_ntas_all.dtsx' + '"' + ' /SET \Package.Variables[User::src_conn_str].Properties[Value];"' + $src_conn_str + '"' + ' /SET \Package.Variables[User::dest_conn_str].Properties[Value];"'
+ $dest_conn_str + '"' + ' /SET \Package.Variables[User::src_sys_id].Properties[Value];"' + $src_sys_id + '"' + ' /SET \Package.Variables[User::pkg_file_path].Properties[Value];"' + $pkg_path + '"' +
' /SET \Package.Variables[User::mail_str].Properties[Value];"' + $mail_str + '"' + ' /SET \Package.Variables[User::mail_from].Properties[Value];"' + $mail_from + '"' + ' /SET \Package.Variables[User::mail_to].Properties[Value];"'
+ $mail_to + '"'+ ' /SET \Package.Variables[User::mail_cc].Properties[Value];"' + $mail_cc + '"' + ' /SET \Package.Variables[User::ps_exe_path].Properties[Value];"' + $ps_exe_path + '"' + ' /SET
\Package.Variables[User::ps_script_path].Properties[Value];"' + $ps_script_path + '"' + ' /SET \Package.Variables[User::ps_script_cmd].Properties[Value];"' + $ps_script_cmd + '"'
$cmd
DECLARE @returncode int
EXEC @returncode = xp_cmdshell @cmd
Types of error that I get -
If I run the $cmd directly. Which is the concatenated string of dtexec command with parameters. It doesn't do anything, not even an error and the pwoershell execution just completes.
If I use exec EXEC @returncode = xp_cmdshell @cmd    ----- Then it throws me the error that the exec is not recognized name of cmdlet.
Please help as I a noob in any kind of scripting.

I did but it just printed the entire string on the command line and assigned all the values.
PS C:\Users\dev_setup> . D:\Batch\Bin\runETL.ps1
IsPublic IsSerial Name                                     BaseType
True     True     Object[]
System.Array
dtexec /f "D:\ETL\test\test\test_ETL\pkg_all.dtsx" /SET "\Package.
Variables[User::src_conn_str].Properties[Value]";"Data Source=SOURCE1;Initial Catalog=tagtest;Provider=SAOLEDB.11;Integrated Security=SSPI;
" /SET "\Package.Variables[User::dest_conn_str].Properties[Value]";"destinationDb;User ID=FP_DEV;Password=**********;Initial Catalog=xyz;Provider=SQLOLEDB.1;Persist Security Info=True;Auto Translate=False;Packet Size=10240;" /SET " \Package.Variables[User::src_sys_id].Properties[Value]
";"100200" /SET "\Package.Variables[User::pkg_file_path].Properties[Value]";"D:\ETL\test\test\test_ETL\" /SET "\Package.Variables[User::mail_str].Properties[Value]";"SmtpServer=mailhost.test.com;UseWindowsAuthentication=False;EnableSsl=False;" /SET "\Package.Variables[User::mail_from].Properties[Value]
";"[email protected]" /SET "\Package.Variables[User::mail_to].Properties[Value]";"[email protected]" /SET "\Package.Variables[User::mail_cc].Properties[Value]";"[email protected]" /SET "\Package.Variables[User::ps_exe_path].Properties[Value]";"C:\Windows\System32\WindowsPower
Shell\v1.0\PowerShell.exe" /SET "\Package.Variables[User::ps_script_path].Properties[Value]";"D:\ETL\Powershell_Script\" /SET "\Package.Variables[User::ps_script_cmd].Properties[Value]";"create_historical_reject_file.ps1 -input_variable"
PS C:\Users\svc_sp_fp_dev_setup>
But when I just run it without passing the parameters it runs. What might be the issue.

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

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

SSIS Package fails in the middle of the execution with some error

Hi ALL,
I have an SSIS Package which basically loops across various files and various sheets and loads that data into a SQL table.Lets say i have 50 files it loads randomly somewhere around 30 and suddenly fails in the middle with the following error
[Excel Source [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "Excel" failed with error code 0xC0202009.
I have no idea what this mean, i googled around and saw that i need to change the debugging properties from TRUE to FALSE, i did that but no use.
Can someone please explain me what could be the reason for this one to be happening and how can i get around this one?
Thanks.

Hi Patrick,
The link you gave above helped me to achieve what i exactly want. I am using multiple processes to load the files now.
It really sucks that there is no solution for this one.But glad i am able to work it in different way.
Thanks a lot for your reply.
Not sure if its related
I've had similar error recently while working with ACE provider and these steps helped me to fix it
http://visakhm.blogspot.in/2013/12/how-to-solve-microsoftaceoledb120-error.html
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

Ssis packages execution fails while executing it by c#

Hi,
I have created one ssis package on server. Now i want to execute this package using c# code.
I have implemented following code to perform this task:
string pkgLocation = @"Package.dtsx";
Package pkg;
Application app;
DTSExecResult pkgResults;
Variables vars;
app = new Application();
pkg = app.LoadPackage(Server.MapPath(pkgLocation), null);
vars = pkg.Variables;
// vars["MonthInt"].Value = "02";
// vars["YearInt"].Value = "2014";
pkgResults = pkg.Execute();
foreach (DtsError pkgerror in pkg.Errors)
string err = "Error Source: " + pkg.Name + ": " + " Description: " + pkg.Description;
//lblErrorMsg.Visible = true;
// lblErrorMsg.Text = err;
if (pkgResults == DTSExecResult.Success)
// lblErrorMsg.Visible = true;
// lblErrorMsg.Text = "Package ran successfully in " + count;
else
But all the time it gets fail.
Its giving me following error in DTSError:
'To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher.'
Can you please guide me how can i resolve this issue.
Is it necessary to install SSIS standard edition on all client machine.
PLease help.
Thanks in advance!
Regards
Rajni

Hi ArthurZ,
Thanks for the quick response.
Actually i have created this package on server where everything is installed and i am executing this package from my local machine after coping this package in local machine.
SO is it mandatory to installed everything on local machine to execute the package?
can i execute package remotely?
Please help to solve the issue.
Thanks & Regards
Rajni

SSIS Package Execution, Windows Authentication, Error: Failed to acquire connection

Hello,
I have developed one SSIS Package in SSDT 2012 to create Reporting Database from SQL Datasource and 1 SharePoint List.
On Development Environment : (Windows Authentication)
Here everything is running fine.
On Test Environment Client Side : (Windows Authentication)
Deployed successfully.
Validating successfully.
While executing the package: getting below error.
SSISPackage:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error Code : 0x80040E21.
An OLE DB record is abailable. Source: "Microsoft OLE DB Service Componenets" Hresult: 0x80040E21 Description: "Multipe-step OLD DB operation generated errors. Check each OLD DB status value, if available. No work was done.".
Execute SQL Task: Error: Failed to acquire connection "ReportingDB". Connection may not be configured correctly or you may not have the right permissions on this connection.
I have done below things:
On SSIS Package side,
1. DelayValidation is Set to True for all the connections and each tasks in package
2. RetainSameConnection : True
3. ProtectionLevel : DoNotSaveSensitiveData
On SSMS,
1. Created one Credential
2. Create Proxy under SSIS SQL Service Agent to run package as Windows User
3. Checked all the permissions and roles.
Below is the connection string which I am using.
Data Source=DBTEST;Initial Catalog=ReportingDB;Integrated Security=SSPI; persist security info=False;
Trusted_Connection=Yes;
Can anyone please help me? As I am trying to resolve this error for the last 4 days and could not find any solution yet.
Thank you,
Mittal.

Can you try changing protection to - EncryptSensitiveWithUserkey
can you also enable DTC
To enable MSDTC on each Web server on Windows Server 2008
Click Start, click Run, type dcomcnfg and then click OK to open Component Services.
In the console tree, expand Component Services, expand Computers, expand My Computer, and then expand Distributed Transaction Coordinator.
Right click Local DTC, and click Properties to display the Local DTC Properties dialog box.
Click the Security tab.
In the Security Settings section, click Network DTC Access.
In the Client and Administration section, select Allow Remote Clients and Allow Remote Administration.
In the Transaction Manager Communication section, select Allow Inbound and Allow Outbound.
In the Transaction Manager Communication section, select Mutual Authentication Required (if all remote machines are running Windows Server 2003 SP1), select Incoming Caller Authentication Required (if running MSDTC in a cluster), or select No Authentication
Required if some of the remote machines are pre-Windows Server 2003 SP1. No Authentication Required is the recommended selection.
Select Enable XA Transactions, and then click OK.
Repeat steps 1 through 9 on the other Web servers.
Please mark
this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

The SSIS package execution failed

Hi all,
Please check the screenshot and provide me how to troubleshoot this issue!
Thanks
DBA

Hi dbadays,
Based on the error message that "cannot open the datafile'', there are two causes:
The account that SQL Agent is using does not have the correct permissions for the file or for the folder that contains the file.
Another process or user has the file open.
The following resolutions correspond to the previous list of causes:
Make sure the current execute user has access to the file and the folder that contains the file. We can create a SQL Server Agent proxy account. This proxy account must use a credential that lets SQL Server Agent run the job as the account that has the
required permissions. For more details, please see:
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
The "another user" may be Microsoft Visual InterDev. Close any Visual InterDev projects that contain a data connection to the file. Please close all instances of excel file and re-run the package.
Besides, we can use a tool like
SQL Server Profiler to see what is happening when you run the package.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

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 Packages Pending Execution

Similar Messages

Maybe you are looking for