December 9, 2014 at 5:11 pm
I have an SSIS package that I created and it works fine in BIDS and when I deploy it to the server it works fine as long as I log into Integration Services and run it by right-clicking on the package name and selecting the Execute Package option. When I create a job to run the package I get the following error:
Message
Executed as user: PNMAC\00DW_MSSQL_AGENT. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4321.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 3:23:37 PM Error: 2014-12-09 15:23:38.56 Code: 0xC0202009 Source: REO LOCOM Value Import Connection manager "Excel Connection Manager" 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: "Unexpected error from external database driver (????????).". End Error Error: 2014-12-09 15:23:38.56 Code: 0xC020801C Source: Update Base Value Excel Source [1662] Description: 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. End Error Error: 2014-12-09 15:23:38.56 Code: 0xC0047017 Source: Update Base Value SSIS.Pipeline Description: component "Excel Source" (1662) failed validation and returned error code 0xC020801C. End Error Error: 2014-12-09 15:23:38.56 Code: 0xC004700C Source: Update Base Value SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-12-09 15:23:38.56 Code: 0xC0024107 Source: Update Base Value Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:23:37 PM Finished: 3:23:38 PM Elapsed: 0.967 seconds. The package execution failed. The step failed.
I do have “32-bit” checked. The error leads me to believe that this is a drivers issue, but since I’m able to run it on the server and I have a couple of other packages running that are importing data from a “.xlsx” file I don’t think the issue is the drivers.
I set up a proxy on the server with my credentials and tried running the job with Run as set to my poxy. I get the same error.
I’m out of ideas. Please help.
July 23, 2015 at 4:13 pm
Same error here...It's because of 'big' Excel file as a source.
Seems to work when executing the package direclty from the Project in the SSIS Catalog, but I am still looking for a real resolution of this bug...
July 23, 2015 at 5:03 pm
Actually, if I recall correctly, this ended up being a permissions issue. The account running the SSIS package had read only access to the directory and so when you run the import from Excel it creates a “temp” file that starts with “~$”. And as far as I can tell this is what breaks it. If your system account has full access to the directory you should be able to do this. In the case of this import, I ended up having to move the file to another directory where my system account had full access. For another import that I had the same issue on, the user had to have it in the “secure” directory and with read only access, so they agreed to convert the file to a “.csv”. A “.csv” file doesn’t seem to have the same issue with the “shadow” file and Excel, so it works fine.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply