Cannot Execute SSIS package through SP
Hi, I have created a simple SSIS package which imports data from .xlsm file to Sql Server DB. When I build and execute the package through Solution its working. Also when I tried to Execute through command dtexec /f "C:\SSIS\SSIS_FFIEC101\Package.dtsx" it is working. But when I try to execute the same using xp_cmdshell 'dtexec /f "C:\SSIS\SSIS_FFIEC101\Package.dtsx"' in a SP, its failing. I have also tried executing the package through a job, it is failing. My actual requirement is to cal the package from MSAccess form Button event. My idea is to call the package through a SP. I am stuck in calling the package through a SP, any suggestions or help is highly appreciated. Thanks for the help.
July 14th, 2012 9:57am
xp_cmdshell is probably not enabled in the machine Arthur My Blog
July 14th, 2012 10:04am
xp_cmdshell is probably not enabled in the machine Arthur My Blog It is enabled in my machine.
July 14th, 2012 10:14am
it is enabled.
July 14th, 2012 10:19am
The please elaborate on what does xp_cmdshell 'dtexec /f "C:\SSIS\SSIS_FFIEC101\Package.dtsx"' in a SP, its failing. means. Is it an error?Arthur My Blog
July 14th, 2012 11:16am
hi, I have created a job using file system and run the job, below is the error am seeing. When I run the same using BI studio and through command , it is running properly. Please help me. Message Microsoft (R) SQL Server Execute Package Utility Version 10.0.1600.22 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:30:43 PM Error: 2012-07-05 14:30:43.26 Code: 0xC0202009 Source: Package Connection manager "Excel Connection Manager" 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: "Unspecified error". End Error Error: 2012-07-05 14:30:43.26 Code: 0xC020801C Source: Data Flow Task 1 Excel Source  Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2012-07-05 14:30:43.26 Code: 0xC0047017 Source: Data Flow Task 1 SSIS.Pipeline Description: component "Excel Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2012-07-05 14:30:43.26 Code: 0xC004700C Source: Data Flow Task 1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2012-07-05 14:30:43.26 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: 2:30:43 PM Finished: 2:30:43 PM Elapsed: 0.234 seconds
July 14th, 2012 12:57pm
64 bit mode may be the issue use Arthur My Blog
July 14th, 2012 1:14pm
I did enable that, but still giving the same error...:S
July 14th, 2012 1:18pm
When I manually execute the package it is working, but when i run it as a job, it is failing. I have set the package properties Run64BitRuntime to FALSE. Also I have set Use 32 bit runtime. Still the package fails. Utterly confused. My data source is Excel and destiantion is Sql DB. Am using XP SP3.
July 14th, 2012 1:53pm
Now run it as usign a proxy: http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/Arthur My Blog
July 14th, 2012 1:54pm
Thanks again for your prompt response, I did it and still facing the same error... Do I have left with any choices...
July 14th, 2012 2:08pm
You misconfigured your package most likely, namely the protection level. It must be RelyOnServerStorage if you store in MSDB or EncryptSensstiteWithpassword for you because I actually see you are running it off the file system Arthur My Blog
July 14th, 2012 4:00pm