Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
WJHamel
Aged Yak Warrior
651 Posts |
 Posted - 2012-04-03 : 14:38:11
|
| Alright, i have a sql job that holds several steps. Each step is an ssis package to import excel tables into a series of tables in a temp db. Executing these SSIS packages individually works perfectly, but executing them in the job only runs the first step in the package then kicks me out with "Execution of job 'SSIS for GADSDEN CIVIL' failed. See the history log for details. Where is this "history log"?? |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
WJHamel
Aged Yak Warrior
651 Posts |
Posted - 2012-04-03 : 14:42:16
|
| jesus flippin !#@!@#!!~! My supervisor sent me on a wild friggin goose chase for it, NOWHERE near "right clicking" the job.question authority. |
 |
|
|
WJHamel
Aged Yak Warrior
651 Posts |
Posted - 2012-04-03 : 14:44:24
|
| ok, so the error i have in that history log is as such:Executed as user: JHAMEL\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 1:28:25 PM Error: 2012-04-03 13:28:25.43 Code: 0xC00F9304 Source: GCSOSERVED-REBUILD Connection manager "SourceConnectionExcel" Description: SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available. End Error Error: 2012-04-03 13:28:25.43 So, if the job fails with this error, why would i be able to execute each SSIS package just fine, with NO errors? And does this mean i won't be able to pack these SSIS packages as steps in a single job? |
|
|
|
|
|
|
agent job errors