Why SSIS package returning 5

Hi,
I am facing issues and unable to resove it. We made SSIS package in dev environment in windows 2008R2 and SQL server 2012. Same packages were placed on SAN disks in cluster environment and are invokded with security contexxt of admin user and wih dtexec utility
( we call this using an sp). rarely but procedure completed i see the log text file by SSIS package and find the reqturn code 5 means package is unable to load. Googling i cannt found what are the exact reasons for return code 5.
Today again the same error occurred. There is no log.
SQL procedure was called which in turn calls SSIS package via dtexec utility.
But the error return code is 5 again.
version is sql server 2012.

Look in all logs. Especially in Event Viewer.
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Similar Messages

Find out why an SSIS package takes so long execute ?

Is there any guideline which shows how to find out why a package is taking "too long" to execute ? I guess one situation could be that an SQL query (if you have one) is taking too long. Perhaps the query could be optimized or perhaps its table
could use indexes. Any more scenarios which can make execution take too long ?

I guess it would be better to google "ssis package running slowly" or something like that and read each post to learn reasons for slow execution. Some links I got -
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/55f3bc47-675f-487f-8bc1-b9c9d6b2a0d9/-ssis-package-running-very-slow-writing-512kb-chunk-per-cycle-?forum=sqlintegrationservices
http://stackoverflow.com/questions/2678119/is-there-a-reason-why-ssis-significantly-slows-down-after-a-few-minutes
http://stackoverflow.com/questions/16181921/dataflow-task-in-ssis-is-very-slow-as-compared-to-writing-the-sql-query-in-execu
These ones caught my attention -
http://blogs.msdn.com/b/mattm/archive/2011/08/07/troubleshooting-ssis-package-performance-issues.aspx
http://sqlblog.com/blogs/rob_farley/archive/2011/02/17/the-ssis-tuning-tip-that-everyone-misses.aspx

Error while running the SSIS package from SQL DB to excel file - export option

hi all,
I have 4.6 million records in my sql db and i want to copy this into a excel file. for this i went to the db and rt click and export to command and started the ssis package running. but after
few minutes, it throws me an error that "error in transferring data into excel file."
Can anyone help me why this happened and the resolution ?
help is appreciated!
Copying to `excel1_Wbook` (Error)
Messages
Error 0xc0202009: Data Flow Task 1: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x8007000E.
(SQL Server Import and Export Wizard)
Error 0xc0047022: Data Flow Task 1: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Destination - excel1_Wbook" (217) failed with error code 0xC0202009 while processing input "Destination Input" (228).
The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information
about the failure.
(SQL Server Import and Export Wizard)
Error 0xc02020c4: Data Flow Task 1: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
(SQL Server Import and Export Wizard)
Error 0xc0047038: Data Flow Task 1: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Source - excel1_Wbook returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The
meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
(SQL Server Import and Export Wizard)

You need to split your data and create (at least 5) worksheet targets.
For example if you have a ROW_NUMBER column you can use for instance a
Conditional Split for something like:
ROW_NUMBER % 5 == 0 for Case 1 (excel 1)
ROW_NUMBER % 5 == 1 for Case 2 (excel 2)
ROW_NUMBER % 5 == 2 for Case 3 (excel 3)
ROW_NUMBER % 5 == 3 for Case 4 (excel 4)
ROW_NUMBER % 5 == 4 for Case 5 (excel 5)

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 package is failing when using SQL server agent

I am trying to execute an SSIS package through an SQL server agent and receiving the following error:
Message
Executed as user: serv-syst\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 1:56:53 PM Error: 2014-04-21
13:56:54.81     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"     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 11.0" Hresult: 0x80040E4D Description: "Login failed for user 'hsnzha'.". End Error Error: 2014-04-21
13:56:54.82     Code: 0xC00291EC     Source: Drop table(s) SQL Task 1 Execute SQL Task     Description: Failed to acquire connection "DestinationConnectionOLEDB". Connection may not be configured
correctly or you may not have the right permissions on this connection. End Error Error: 2014-04-21 13:56:54.82     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"
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 11.0" Hresult: 0x80040E4D Description: "Login
failed for user 'hsnzha'.". End Error Error: 2014-04-21 13:56:54.82     Code: 0xC00291EC     Source: Preparation SQL Task 1 Execute SQL Task     Description: Failed to acquire connection
"DestinationConnectionOLEDB". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:56:53 PM
Finished: 1:56:54 PM Elapsed: 0.844 seconds. The package execution failed. The step failed.
My SSIS package retrieves a excel file and saves the vales into an SQL table. When I run the package by itself in my server it works fine but when it's called from a SQL agent, it fails with the above error. Please help me resolve it.

That's the issue. If it's a SQL login the password cannot be retrieved by account executing the package from the job which is why login fails. In that case best thing would be set password in job properties or pass it using configuration created in the package
See
HTTP://blogs.msdn.com/b/runeetv/archive/2011/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs
My package is saved with ServerStorage which appears under \\server\Stored Packages\MSDB\PACKAGE and when I run it, it works fine.
There is a new error message that I get now after following the steps from the link...
Message
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.1600.1 for 32-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 3:34:22 PM
Error: 2014-04-21 15:34:23.82
   Code: 0xC0202009
   Source: PACKAGEWMG Connection manager "SourceConnectionExcel"
   Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005 Description: "Unexpected error from external database driver (????????).".
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC020801C
   Source: Data Flow Task 1 Source - 'Contact Center$' [1]
   Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" 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-04-21 15:34:23.82
   Code: 0xC0047017
   Source: Data Flow Task 1 SSIS.Pipeline
   Description: component "Source - 'Contact Center$'" (1) failed validation and returned error code 0xC020801C.
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC004700C
   Source: Data Flow Task 1 SSIS.Pipeline
   Description: One or more component failed validation.
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC0024107
   Source: Data Flow Task 1
   Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 3:34:22 PM
Finished: 3:34:23 PM
Elapsed: 1.25 seconds

Error trying to run SSIS Package via SQL Server Agent: DTExec: Could not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object

Situation:
SSIS Package designed in SQL Server 2012 - SQL Server Data Tools
Windows 7 - 64 bit.
The package (32 bit) extracts data from a SQL Server db to an Excel Output file, via an OLE DB connection.
It uses 3 package variables:
*) SQLCommand (String) to specify the SQL Statement to be executed by the package
Property path: \Package.Variables[User::ExcelOutputFile].Properties[Value]
Value: f:\Output Data.xls
*) EXCELOutputFIle (String) to specify path and filename of the Excel output file
Property path: \Package.Variables[User::SQLCommand].Properties[Value]
Value: select * from CartOrder
*) VarObjectDataSet (Object) to hold the data returned by SQL Server)
Property path: \Package.Variables[User::VarObjectDataSet].Properties[Value]
Value: System.Object
It consists out of 2 components:
*) Execute SQL Task: executes the SQL Statement passed on via a package variable. The resultng rows are stored in the package variable VarObjectDataSet
*) Script Task: creates the physical output file and iterates VarObjectDataSet to populate the Excel file.
Outcome and issue:The package runs perfectly fine both in SQL Server Data Tools itself and in DTEXECUI.
However, whenever I run it via SQL Server Agent (with 32 bit runtime option set), it returns the errror message below.
This package contains 3 package variables but the error stating that a package variable can not be set, pops up for the VarObjectDataSet only. This makes me wonder if it is uberhaupt possible to set the value of a package variable
of type Object.
Can anybody help me on this please ?
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 6:40:20 PM DTExec: Could
not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object. Started: 6:40:20 PM Finished: 6:40:21 PM Elapsed: 0.281 seconds. The package execution failed. The step failed.
Thank you very much in advance
Jurgen

Hi Visakh,
thank you for your reply.
So, judging by your reply, not all package variables used inside a package need to be set a value for when run in DTEXEC ?
I already tried that but my package ended up in error (something to do with "... invocation ...." and that error is anything but clearly documented. Judging by the error message itself, it looks like it could be just about anything. that is why I asked my
first question about the object type package variable.
Now, I will remove it from the 'set values' list and try another go cracking the unclear error-message " ... invocation ...". Does an error message about " ... invocation ..." ring any bells, now that we are talking about it here ?
Thx in advance
Jurgen
Yes exactly
You need to set values only forthem which needs to be controlled from outside the package
Any variable which gets its value through expression set inside package or through a query inside execute sql task/script task can be ignored from DTExec
Ok I've seen the invocation error mostly inside script task. This may be because some error inside script written in script task. If it appeared after you removed the variable then it may because some reference of variable existing within script task.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS Package Runs OK Manually But Not From SQL Server Agent...Permissions?

I have a problem where I have an SSIS package (SQL Server 2005) that won't run properly from SQL Server Agent, but it runs fine when kicked off manually from Integration Services -> Run Package or when run in debug from Visual Studio.
The first step in the package checks for the existance of a file via a script task. The script looks like this...
Code Block
Public Sub Main()
Dim TaskResult As Integer
Dim ImportFile As String = CStr(Dts.Variables("BaseDirectory").Value) + CStr(Dts.Variables("ImportDirectory").Value) + CStr(Dts.Variables("ImportFile").Value)
If Dir(ImportFile) = "" Then
Dts.TaskResult = Dts.Results.Failure
Else
Dts.TaskResult = Dts.Results.Success
End If
Return
End Sub
This script runs fine and the file is seen as expected when I run the package manually. But as a step in a SQL Server Agent job, it doesn't see the file.
The SQL Server Agent service is set to start up / log on as a Local System Account. I've also tried setting up a credential / proxy (using an account that I know can see and even move / rename the file) to run the job as but that didn't seem to help.
The package is being run from SQL Server (stored in MSDB) and is set to rely on SQL Server for sensitive information, so I don't think that's an issue; other packages are set up like this in terms of sensitive data and run fine.
Any ideas why my script can't "see" the file I'm looking at when it's kicked off by SQL Server agent? I've looked and looked...I can't seem to figure this out. I would really appreciate any help you might be able to offer up.

If the variables are fine, then I think it is very likely that this is security related. Since the Agent is running under the local system account, have you verified that the local account can access the file? When you tried the proxy account, are you positive that it was set up properly, and that the account had the permissions to read the file?
Another thing to check - is this a local file or is on another computer? If it is on another computer, make sure you are using a UNC path and not a mapped drive.

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

Calling SSIS package from C# Windows Service Fails

Hi All.
I've got an SSIS package that reads from an Excel file and populates a database. The Excel file location gets passed in to the package as a variable. Also the Protection Level of the package is set to EncryptSensitiveWithPassword.
This all works fine when I run the package from Visual Studio or using DTEXEC. When I try to run it from a C# Windows Service though I get the following exception:
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005 Description: "The Microsoft Office Access database engine cannot open or write to the file ''. It is already opened exclusively
by another user, or you need permission to view and write its data.".
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Input Excel Connection" failed with error code 0xC0202009. There may be error messages posted before this
with more information on why the AcquireConnection method call failed.
Dedupe Worksheet failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
The windows service runs with LocalSystem account and the following code is used to call the SSIS Package:
                Application app = new Application();
                Package package = null;
                app.PackagePassword = "*******";
                //Load the SSIS Package which will be executed
                package = app.LoadPackage(@"C:\Projects\DataDedupeMatch\DataDedupeMatch\DataDedupe.dtsx", null);
                //Pass the varibles into SSIS Package
                package.Variables["User::FilePath"].Value = e.FullPath.Replace(@"\\", @"\");
                Microsoft.SqlServer.Dts.Runtime.DTSExecResult results = package.Execute();
I would really appreciate if someone could help me out with this.
Thanks in advance,
Deon

Instead of hosting the SSIS runtime in your service, you should use a separate host process for your SSIS package. You're using the Office drivers, which aren't designed or supported for running in long-lived unattended processes like a Windows Service.
You can use your own SSIS hosting code, or just use dtexec.exe to host your package. In either case you would start the child process with
Process.Start.
David
David http://blogs.msdn.com/b/dbrowne/

Calling ALL Experts...SSIS Package keep failing in Debug Mode..SQL 2005

Hello everyone,
I just want to thank you in advance for all the help that you can give today.
I just started at a new Company, as a junior DBA, the previous person left. Before that person left he created a lot of SSIS packages and
turn them into jobs basically to refresh many different tables on the SQL server. The datas are being import from another datasource, which is why the SSIS packages was created so we can bring the datas over to SQL side. Whenever I want to create a new
SSIS Package for a new job, I always get the same failure as below...
"Error: 0xC0047062 at Data Flow Task, Source - Query [1]: System.OverflowException: Arithmetic operation resulted in an overflow.
at System.Data.Odbc.OdbcStatementHandle.RowCount(SQLLEN& rowCount)
at System.Data.Odbc.OdbcDataReader.GetRowCount()
at System.Data.Odbc.OdbcDataReader.FirstResult()
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader, Object[] methodArguments,
SQL_API odbcApiMethod)
at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method, Boolean needReader)
at System.Data.Odbc.OdbcCommand.ExecuteReader(CommandBehavior behavior)
at System.Data.Odbc.OdbcCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PreExecute()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSManagedComponentWrapper90 wrapper)
Error: 0xC004701A at Data Flow Task, DTS.Pipeline: component "Source - Query" (1) failed the pre-execute phase and returned error
code 0x80131516.
Information: 0x40043009 at Data Flow Task, DTS.Pipeline: Cleanup phase is beginning.
Information: 0x4004300B at Data Flow Task, DTS.Pipeline: "component "Destination - GLCGLDS" (103)" wrote 0 rows.
Task failed: Data Flow Task
SSIS package "SSIS_GLCGLDS_GL.dtsx" finished: Failure.
The program '[16836] SSIS_GLCGLDS_GL.dtsx: DTS' has exited with code 0 (0x0)."
All the SSIS packages are failing for me, not just the one I created, even the ones that were working
before, the ones that were created by the previous person, I just went to Start Debugging and it would failed at the same exact stage
Below are the exact steps that I do to create the SSIS Package (based on the notes from previous person)
1. right click on SSIS Package and select sql server import and export wizard and click next
2. Select data source as .Net framework Data Provide for ODBC
3. Input Datasource, and driver as: TS ODBC Multi – Tier Driver
4. Choose destination as Microsoft OlE DB Provide for SQL Server
5. Write a basic select statement.
6. Click edit Mappings
7. Here's the important part... I am ABLE to preview the DATA.
8. Click ok  next  finished
9. Click debug start debugging
10. The preparation SQL task will be green, but the Data Flow Task will failed everytime for me.
If anyone has any suggestion please let me know, b/c I have try every possible ways and out of luck, and I don't want to explain to my boss
I don't know how to do it or how the previous person does it without any failures.
TL

Below are the exact steps that I do to create the SSIS
Package (based on the notes from previous person)
1. right click on SSIS Package and select sql server import and export wizard and click
next
2. Select data source as .Net framework Data Provide for ODBC
3. Input Datasource, and driver as: TS ODBC Multi – Tier Driver
4. Choose destination as Microsoft OlE DB Provide for SQL Server
5. Write a basic select statement. (select * from tableA)
6. Click edit Mappings to modify few column with their data type
7. Next -> Here's the important part... when I clicked on Preview Data, I am ABLE to
preview the DATA.
Finished.

Truncate that does not work in a SSIS package but works in SSMS

Hi guys I have this simple code
if object_id('[dbo.generator Only production 2011]') is not null
begin
truncate table [generator Only Production 2011]
end
embedded in a SSIS package. It does not work and I don't understand why. If I run the truncate table [generator Only Production 2011] directly from SSMS it works perfectly.
Any clue?
Thanks

if object_id('[dbo.generator Only production 2011]') is not null
You quoted the whole schema + object name with brackets; that query will never return a result =>
if object_id('[dbo].[generator Only production 2011]') is not null
Olaf Helper
[ Blog] [ Xing] [ MVP]

Error while processing with XML but not with SSIS Package

Hi All,
In the project that I am currently working we are using SQL Server 2005 and its components. We recently upgraded SSRS 2005 to 2008. Now we are in the process of upgrading SSAS from 2005 to 2008.
To process the cubes in 2005 version, we were using 2 methods. One is using XML and the other is SSIS packages. We upgraded one of our cubes to 2008 and we are unable to process the cube using XML but its processing fine when we are using SSIS package.
I Suspect it is something to do with the "Ignore Dimension Key Errors". There are some dimension keys that are missing. It was working fine in 2005 version and also in 2008 version with SSIS.
Please help me with this and let me know the reasons why this happens.
Thanks
Vineesh
vineesh1701

Hi Thomas,
Below are the things you have asked for.
1.
We are running XMLA Scripts as jobs Under SQL Server Agent. The job fails. But cube is processed and the key errors are logged in the specified path.
2.
The same script runs fine in Management Studio.
Executed as user: XXXX. <return xmlns="urn:schemas-microsoft-com:xml-analysis"><results xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root
xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Warning WarningCode="1092354050" Description="Server: Operation completed with 17 problems logged." Source="Microsoft SQL Server
2008 R2 Analysis Services" HelpFile="" /></Messages></root></results></return>. The step failed.
Thanks
Vineesh
vineesh1701

Error connecting to Oracle from when running SSIS Package on Windows 64-bit

Hi.
I have an SSIS (SQL Server Integration Services) Package that reads a view on Oracle and loads data into table in SQL Server 2005. This is on a Windows 2008 Server (64-bit). SQL Server 2005 with SP3. Oracle Client 11g (32 bit & 64 bit) Runtime Version installed on server. The server has been rebooted since installing OracleClient.
I get the following error when run as a SQLAgent job 64 Bit (Execution type SQL Server Integration Services Package)...
Started: 9:29:24 AM
Error: 2010-01-04 09:29:25.37
Code: 0xC0202009
Source: SADM_CURR_Address_and_Cell_Phone-Oracle Connection manager "Oracle/PeopleSoft"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
End Error
Error: 2010-01-04 09:29:25.37
Code: 0xC020801C
Source: DFT-Oracle to SS2005 OLE DB Source [1]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Oracle/PeopleSoft" 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: 2010-01-04 09:29:25.37
Code: 0xC0047017
Source: DFT-Oracle to SS2005 DTS.Pipeline
Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.
End Error
Error: 2010-01-04 09:29:25.37
Code: 0xC004700C
Source: DFT-Oracle to SS2005 DTS.Pipeline
Description: One or more component failed validation.
End Error
Error: 2010-01-04 09:29:25.37
Code: 0xC0024107
Source: DFT-Oracle to SS2005
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 9:29:24 AM
Finished: 9:29:25 AM
Elapsed: 1.108 seconds
When I execute this same exact package as a SQLAgent job 32-bit (type Operating System CmdExec) it runs successfully. When I run the package using the Execute Package Utility, it runs successfully. When I am editting the package in BIDS I can connect to Oracle. For both 64 and 32 bit, I use a dtsconfig file which specifies the Oracle connection string and password.
Someone mentioned on another forum that maybe there is no Oracle ODBC driver for 64-bit Windows. I would assume that the OracleClient 64-bit would include that.
I hope I have included all info needed. Please let me know if you may have a resolution to this problem.
Thanks.
John

I was trying to transfer data from oracle to sql server 2008 on a daily basis.
I have very hard time connecting to oracle from ssis package on windows server 2008. I am almost dead and cannot find any help. i was able to connect to oracle using import/export 64 bit feature of SQL Server 2008 using Oracle provider for OLEDB. But I am not sure why the same does not work with BIDS?
Here's the environment info:
1. Oracle Client 10g
2. SQL Server 2008
3. Windows Server 2008
Appreciate your help. Please save me.
Thanks,

Error While executing a SSIS package which contains a script task through SQL Server Agent job

Hi,
I have a SQL Server 2012 SSIS package with a script task along with other tasks [data flow, execute sql tasks ]. When I manually executed the job through BIDS, its completed successfully.
Then I have automated the execution of the package through SQL Server Agent Job. But when I executed the package through SQL Agent job, it runs successfully for all the tasks except script task. When it comes to execute the Script Task, it is getting failed
with the below error message.
"Error: 2012-08-29 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
I have installed the SSIS on the 64-bit environment and SSIS service is running. Also I tried to run the job through 32 bit [job option] but I am getting the above error in all cases.
Any help will be greatly appreaciated !
Thanks,
Navin
- naveen.reddy

Hi Arthur,
My script task access the excel files in a network share, refresh them all and save them. When I execute the ETL manually or thru DTEXEC, it is executing successfully. I am facing the issue when I am executing thru SQL Agent Job only. Logging also showing
the same error.
"Error: 2012-08-23 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
- naveen.reddy

Why SSIS package returning 5

Similar Messages

Maybe you are looking for