SSIS package runs successfully on PC, but not Tivoli

[ApocY85]

I have a rather simple SSIS package I created that runs 100% successfully on my computer. However, when I use the Tivoli Job Scheduling Console, the job errors out. I click "Browse Job Log" and see the following errors:


Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available.

Description: "The Microsoft Jet database engine cannot open the file '<filename here>'. It is already opened exclusively by another user, or you need permission to view its data.".

Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "<excel connection name here>" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

Description: component "<excel connection name here>" (1) failed validation and returned error code 0xC020801C.


I have checked the Excel file time and time again. No one has the file open because when I open it, it does not prompt me to use it as read-only as it would if it were opened. Also, there are no permissions to the file. Any suggestions would be greatly appreciated! Please let me know if you need any more information. Thank you!!!

 

[mrdenny]

Is the job starting under a domain account? If so that that domain account have access to the network share and path to the file?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[RiverGuy]

When you deploy the package, it doesn't run under your login credentials. It runs under the service account on SQL Server. And if the service account cannot access the Excel file, then, well, it can't access it.

 

[ApocY85]

We were assuming it had access to the entire network share, as it has worked under several other directories. However, apparently this particular directory did not have the same permissions. I am new to SSIS packages and Tivoli. Even though the only thing that made any sense as possible issues were permissions, I wasn't knowledgable enough to know for sure, and took my team's assumptions first.

For any future readers, permissions was the case. For those who responded, many thanks for your prompt help!