I have reviewed a lot of the Forum discussions and referenced documentation on how to run SSIS on 64-bit machines and have an Excel source for the incoming data. I have tried a number of the suggestions without success.
First I will list the error. I will then note all the the conditions that I have tried and what I have seen. Please forgive me for the long post.
The error I'm getting is this:
Date 3/1/2011 3:00:00 AM
Log Job History (GSSETL)
Step ID 1
Server DB-METRICS-PRD
Job Name GSSETL
Step Name RunGSSETL
Duration 00:00:04
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: 3PAR\eng_metrics. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:00:00 AM Error: 2011-03-01
03:00:04.89 Code: 0xC0202009 Source: Package Connection manager "Excel GSS System" 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: "'Z:\Install_Base_SW-Tracker_Current.xlsx' is not a valid path. Make sure that the path name is spelled correctly and
that you are connected to the server on which the file resides.". End Error
Error: 2011-03-01 03:00:04.89 Code: 0xC020801C Source: Data Flow Component Source for Excel Connection Manager [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "Excel GSS System" 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: 2011-03-01 03:00:04.89 Code: 0xC0047017 Source: Data Flow Component SSIS.Pipeline Description: component "Source for Excel Connection Manager" (1) failed validation and returned
error code 0xC020801C. End Error Error: 2011-03-01 03:00:04.89 Code: 0xC004700C Source: Data Flow Component SSIS.Pipeline Description: One or more component failed validation.
End Error Error: 2011-03-01 03:00:04.89 Code: 0xC0024107 Source: Data Flow Component Description: There were errors during task validation. End Error DTExec: The
package execution returned DTSER_FAILURE (1). Started: 3:00:00 AM Finished: 3:00:04 AM Elapsed: 3.922 seconds. The package execution failed. The step failed.
Actions Discussion:
The SQL Server 2008 R2 server is 64-bit. I have mapped a drive to the other host that contains the Excel file I'm using for the source data.
I have confirmed that the Run64BitRunTime option = False.
The Connections delayValidation = True.
The Connection string points to OLEDB.12 -- Provider=Microsoft.ACE.OLEDB.12.0;Data Source=Z:\Install_Base_SW-Tracker_Current.xlsx;Extended Properties="EXCEL 12.0;HDR=YES;READONLY=TRUE";
The Job step is pointing to the correct file = E:\packages\GSSETL.dtsx
The Job command line is pointing to x86 = /FILE "E:\packages\GSSETL.dtsx" /X86 /CHECKPOINTING OFF /REPORTING E
The use 32 bit runtime Exectution option is checked.
I used the same domain id to edit, build and test the package as is used for the SQL Agent Service logon account. The same account is used for all of the SQL Services as well.
The domain account is in the local administrators account.
I can run the package and connect to the Excel spreadsheet from the same id in the BIDS debugs environment or the Execute package Utility.
It fails to connect when I run from SQL Server Agent job step. Or, if I start BIDS as Administrator and try to run the debug feature.
I'm assuming that some level of authority is different when the job is run under SQL Server Agent even when the same user id is used.
Can some one please give me some guidance?
Thank you,
Grant