Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

SSIS Excel connection manager fails only when run from SQL job

$
0
0

I have an SSIS package that is connecting to an Excel file via OLE DB connection that only fails (error message below) when put into a SQL job. If run via command line using DTEXEC it works. To make it even more confusing it runs on another server which should be configured the same as a SQL job.

The job set is set up to "run as" a SSIS Package Execution proxy account we set up on all our servers. This proxy account should be configured the same on all servers. We have other SSIS packages running on this server which work fine. The only difference I can see is that they do not use an OLEDB connection to an XLSX file. We do have SSIS packages that read tab deliminted files on this server.

At this point I'm not sure what to look at. I investigated the proxy account and it appears the same on all servers. I thought it might be a missing driver for the XLSX file but then why did it work when run via the command line? I went back to thinking it was a permission issue with the proxy but if set up the same on the other server then why would it work there an not on the problem server?

I suspect a permissions issue but permissions to what? I looked the folders for the input files and all other related folders and it all seems fine. At this point I don't know what else to look at to try and find the difference between the working and non-working servers.

Here is the error message that I find very unhelpful.

Microsoft (R) SQL Server Execute Package Utility  Version 10.0.4000.0 for 32-bit  Copyright (C) Microsoft Corp 1984-2005.
All rights reserved.   
Started:  5:38:22 PM 
Error: 2012-09-11 17:38:22.89    
Code: 0xC0202009    
Source: TimeTracking Connection manager "excel"    
Description: SSIS Error Code DTS_E_OLEDBERROR. 
An OLE DB error has occurred.
Error code: 0x80004005. 
An OLE DB record is available. 
Source: "Microsoft Access Database Engine" 
Hresult: 0x80004005  Description: "Unspecified error". 
End Error 
Error: 2012-09-11 17:38:22.89    
Code: 0xC020801C    
Source: Data Flow Task OLE DB Source [1]    
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. 
The AcquireConnection method call to the connection manager "excel" 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: 2012-09-11 17:38:22.89    
Code: 0xC0047017    
Source: Data Flow Task SSIS.Pipeline    
Description: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. 
End Error 
Error: 2012-09-11 17:38:22.89   
Code: 0xC004700C    
Source: Data Flow Task SSIS.Pipeline    
Description: One or more component failed validation. 
End Error 
Error: 2012-09-11 17:38:22.89    
Code: 0xC0024107    
Source: Data Flow Task     
Description: There were errors during task validation. 
End Error 
DTExec: The package execution returned DTSER_FAILURE (1). 
Started:  5:38:22 PM 
Finished: 5:38:22 PM 
Elapsed:  0.547 seconds. 
The package execution failed. 
The step failed.


Viewing all articles
Browse latest Browse all 24688

Trending Articles