Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Error running SSIS package as job but not directly

Status
Not open for further replies.

RRinTetons

IS-IT--Management
Jul 4, 2001
333
US
SQL Server 2008RS on Windows Server 2008, VS 2008 BIDS
I'm logged into SSMS, SSIS, BIDS, etc with my domain account 'JHMR\rray'
The job service is currently running under that same account (I'm trying to change that, see my other recent post)


I have an SSIS package that imports data from an Excel spreadsheet into several tables and then calls several SP's in the target DB to process the import. When I run it from VS 2008 it works fine, or if I just double click it and hit the Execute button it's fine.

I created a job to run the package from the file system and set the job ownder to my domain account. It fails with the following message:

Message
Executed as user: JHMR\RRay. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 4:02:32 PM Error: 2012-12-01 16:02:33.42 Code: 0xC0209303 [highlight #FCE94F]Source: Budget Upload Connection manager "Excel Spreadsheet" Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.[/highlight] The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered -- perhaps no 64-bit provider is available. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2012-12-01 16:02:33.42 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Spreadsheet" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2012-12-01 16:02:33.42 Code: 0xC0047017 Source: DTSTask_DTSDataPumpTask_1 SSIS.Pipeline Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. End Error Error: 2012-12-01 16:02:33.42 Code: 0xC004700C Source: DTSTask_DTSDataPumpTask_1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2012-12-01 16:02:33.42 Code: 0xC0024107 Source: DTSTask_DTSDataPumpTask_1 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:02:32 PM Finished: 4:02:33 PM Elapsed: 0.592 seconds. The package execution failed. The step failed.

That looks like it's cascading from the original failure to connect to the Excel spreadsheet, and that seems to be driven by some sort of a 64-bit provider being missing. (highlighted above) It seems odd that I don't get the same error when I execute it directly, but that's why I'm asking for help!

-
Richard Ray
DBA, Developer, Data Analyst
Jackson Hole Mountain Resort
 
The other option is on the SQL agent job set to execute as 32 bit. Then it will use the 32bit agent and will then find the 32bit drivers.

Here shows where it is:

[URL unfurl="true"]http://blogs.msdn.com/b/mattm/archive/2008/06/12/use-32bit-runtime-option-for-sql-agent.aspx[/url]

----------------------------------------

Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind - Bernard Baruch

Computer Science is no more about computers than astronomy is about telescopes - EW Dijkstra
----------------------------------------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top