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

Similar Messages

Error while executing SSIS package - Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)

Hi,
We are getting the following error when running our SSIS packages on Microsoft SQL Server 2012 R2 on Windows Server 2008 R2 SP1:
Error: 4014, Severity:20, State: 11. A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0)
SQL Server Data Tools and SQL Server Database Engine reside on the same server.
We tried the following:
Disabling TCP Chimney Offload
Installed Windows Server 2008 SP1
Splitting our SSIS code into multiple steps so it is not all one large continuous operation
The error occurs during a BulkDataLoad task.
Other options we are investigating with the engineering team (out-sourced, so delayed responses):
Firewall configurations (everything is local, so this should not make a difference)
Disabling the anti-virus scanner
Are there other things we can try?
Any insight is greatly appreciated.
Thanks!

Hi HenryKwan,
Based on the current information, the issue can be caused by many reasons. Please refer to the following tips:
Install the latest hotfix based on your SQL Server version. Ps: there is no SQL Server 2012 R2 version.
Change the MaxConcurrentExecutables property from -1 to another one based on the MAXDOP. For example, 8.
Set "RetainSameConnection" Property to FALSE on the all the connection managers.
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/774370/ssis-packages-abort-with-unexpected-termination-message
If the issue is still existed, as Jakub suggested, please provide us more information about this issue.
Thanks,
Katherine Xiong
Katherine Xiong
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

SQL Server Job that were written in SSIS packages failed

could not load package files system because of error 0x80070002. Description: could not find file 'C:\program files\microsoft SQL Server\100\DTS\Binn\. The package could not be loaded. The step failed. I found this error on one of my job configured in
ssis packages which take a view statement from my production server, which actually is in a cluster environment. Thank you guys

It's a little difficult to infer what could be happening without having an idea about what the package does. If you can share one or two screenshots of it, it would be great. You will need Business Intelligence Development Studio (BIDS) for SQL 2008 or previous,
or SQL Data Tools if SQL 2012. Right click over the package in the file system and select "Edit".
In the meanwhile, let me give some ideas for troubleshooting:
If your servers are 64bits, be sure your SQL Agent Job step for the SSIS package is running also in 64bits.
Assuming your package basically takes data from the view and move it to other server, main of the workload should be at read time from the view. Try running the SQL statement that package is issuing and take the time. If the time is still less than
3 minutes, your package should have more logic/transformations doing other tasks that we will need to look in. If time is much more, maybe you have much more data in the view underlying tables.
If querying from the view is still so fast, we will need to understand what the package is doing after the initial read.
HTH
Please, mark this post as Answer if this helps you to solve your question/problem.
Alan Koo | "Microsoft Business Intelligence and more..."
http://www.alankoo.com

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

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

Error while executing SSIS Package after upgrading the Oracle Client

Hello,
I am running to the below error after we upgraded the Oracle client to 11g from 10g. The source of the Data is Oracle database . Looked online but each error is pointing towards different route, Confused here any help is very much appreciated. Have to say
I am not a pro with SSIS.
SSIS package "Bentek_ISO_Package (2).dtsx" starting.
Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator,
or on the system's console.
Information: 0x40043006 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Error: 0xC0202009 at Temp_tbl Injection Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80040E14 Description: "ORA-12801: error signaled in parallel query server P183, instance *****:qrmgmt2 (2)
ORA-01861: literal does not match format string".
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80004005 Description: "ORA-12801: error signaled in parallel query server P183, instance ****:qrmgmt2 (2)
ORA-01861: literal does not match format string".
Error: 0xC004701A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: component "OLE DB Source" (1) failed the pre-execute phase and returned error code 0xC0202009.
Information: 0x4004300B at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: "component "OLE DB Destination" (52)" wrote 0 rows.
Information: 0x40043009 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Temp_tbl Injection Data Flow Task
Warning: 0x80019002 at *******: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches
the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "****** (2).dtsx" finished: Failure.

Do you have any Date conversion functions in your Oracle datetime fields? I did run into a similar issue when we upgraded the oracle client and the provider started to decipher the metadata of the date columns. The SSIS metadata conversion for the date
columns yielded dates that were not valid. I had to update my queries to use the TO_CHAR conversion to bring it out as a string and then save it to the date field.
TO_CHAR (DATE, 'MM/DD/YYYY HH24:MI:SS')
Regards, Dinesh

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

Multiple SSIS Packages into one single package

Hello All,
I have created 4 SSIS Packages.
1st package- To load data from FlatFiles to DB(MasterTable)
2nd package- split the MasterTable into 2 different tables(ChildTable1, ChildTable2).
3rd package- join the child table to another mastertable to get an ID column.
4rd package - Remove the duplicates from childtables and load all the duplicates into another table.
Is it possible to have them all in a single Package? Which is the best way to develop them in a single
package?
Please Help me.
Thanks, Shyam Reddy.

Your approach of keeping these logical steps into separate packages suits a situation where you'd want to execute some of these steps ad-hoc or be able to restart from the point of failure onwards if the load fails mid way on a given day. However, if you
really want to run this flow as a single, end-to-end workflow, you can create a Master package which then calls these 4 child packages in a certain order (using Execute package task). Alternatively, if you'd like to maintain one SSIS package rather than 5,
you can simply copy individual tasks from each package (Ctr+c, Ctrl+v) into a single package and eliminate the ones you don't need.
Note that you might have to recreate the connection managers those individual SSIS packages were using after you copy the contents of the packages over to a single one.
I hope this helps!
Cheers!
Muqadder.

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

Error coming after using an ssis package to create an sql job

Hi
I have created an SSIS package and try to create a job on the same when i run the job it if failing an dgiving me the below error
Executed as user: xxxxx\FESGSQLA. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 12:33:03 AM Error: 2014-03-19
00:33:03.12     Code: 0xC0011007     Source: {DD3B52A8-850A-4328-94DC-CF51B4376BCB}      Description: Unable to load the package as XML because of package does not have a valid XML format. A
specific XML parser error will be posted. End Error Error: 2014-03-19 00:33:03.12     Code: 0xC0011002     Source: {DD3B52A8-850A-4328-94DC-CF51B4376BCB}      Description: Failed
to open package file "D:\Users\xxxxxx\Desktop\I11_Load_SAP_Recon_Data.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly
into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error Could not load package "D:\Users\H139933\Desktop\I11_Load_SAP_Recon_Data.dtsx"
because of error 0xC0011002. Description: Failed to open package file "D:\Users\xxxxxx\Desktop\I11_Load_SAP_Recon_Data.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package
and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. Source: {DD3B52A8-850A-4328-94DC-CF51B4376BCB}
Started: 12:33:03 AM Finished: 12:33:03 AM Elapsed: 0.046 seconds. The package could not be found. The step failed.
Please throw some light on the issue and stpes to resolve.
Thanks
Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

The package was created using a newer SSIS version than you have in the target (server).
Arthur My Blog

Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCP

Hi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP

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 packages are failing after upgrade to SQL server 2014

Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.

I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari

SSIS packages go into Pending Execution state after SP1 CU7 deployment

Similar Messages

Maybe you are looking for