Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Import Excel .xls fails on SSIS2012 Expand / Collapse
Posted Sunday, February 17, 2013 6:28 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, November 21, 2016 10:45 PM
Points: 87, Visits: 240

I am seeking some assistance in troubleshooting a package that imports data from a network location based Excel ( .xls ) file.

The SSIS 2012 server is 64-bit.

When I execute the package, from the Advanced tab I select 32-bit runtime.

The error:
"ImportWestPacBankStatement:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: ""Microsoft JET Database Engine"" Hresult: 0x80004005 Description: ""The Microsoft Jet database engine cannot open the file '\\server\directory$\folder\filename.xls'. It is already opened exclusively by another user, or you need permission to view its data."".
"Import Westac XLS:Error: 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.

I have checked that the account SSIS runs under has access to the file. ( I logged onto the PC with the SSIS agent account and checked the file, and it opens OK ).

When 32-bit is not selected, I receive a different error:

ImportWestPacBankStatement:Error: The requested OLE DB provider Microsoft.Jet.OLEDB.4.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".

So, I think that I am using the correct approach in using the 32-bit runtime, and I am certain as much as I can be that the account has the correct permissions, but it doesn't work.

PS. on 2005 I had to run the 2005 written package with the dtexec command.
eg: "c:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe" /DTS "\MSDB\packagename" /SERVER servername /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V

Thanks for any suggestions.
Post #1421020
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse