March 19, 2014 at 9:30 am
We are trying to import 2010 excel spreadsheet(I believe it 32 bit).
I created a siss package via the import\export wizard.
Am able to successful import the spreadsheet via the import\export tool.
Am able to successful import the spreadsheet from Integration Services.
However, when I create a SQL Server agent job, that points to the package, it fails with the following error;
xecuted as user: CWOPA\pwsrvsql001. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4297.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 8:18:56 AM Error: 2014-03-19 08:18:57.62 Code: 0xC0209302 Source: DaImportColumnDataDictionary Connection manager "SourceConnectionExcel" Description: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_ERROR. The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-03-19 08:18:57.62 Code: 0xC020801C Source: Data Flow Task 1 Source - Column$ [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0209302. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-03-19 08:18:57.62 Code: 0xC0047017 Source: Data Flow Task 1 SSIS.Pipeline Description: component "Source - Column$" (1) failed validation and returned error code 0xC020801C. End Error Error: 2014-03-19 08:18:57.62 Code: 0xC004700C Source: Data Flow Task 1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-03-19 08:18:57.62 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: 8:18:56 AM Finished: 8:18:57 AM Elapsed: 1.435 seconds. The package execution failed. The step failed.
I have googled this, is it something to do with 64 bit sql and 32 bit office? I have change the package to run in 32 bit mode, I have change the job to execute in 32 bit mode.
Is it a problem with Office 2010 and Sql server 2008r2?
Any thoughts, I spent more time on this then I ever expected I would?
Thanks!
Mike
March 19, 2014 at 11:51 am
What is the server 64/32 bit?
In either case, make sure the version matches the office install
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 20, 2014 at 11:36 am
SQL Server is 64 bit, office 2010 32 bit...
Mike
March 20, 2014 at 12:04 pm
If you haven't done so already, Install Office 2007 Data Connectivity Components (http://www.microsoft.com/download/en/confirmation.aspx?id=23734) for the 64-bit
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience
March 20, 2014 at 12:05 pm
On the server?
Mike
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply