Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
flipfyre
Starting Member
26 Posts |
 Posted - 2009-04-28 : 11:06:39
|
| Coders,I’m hoping you can assist with an error I am receiving while trying to create a SQL Server Agent Job. I have an excel file located on a web farm; in which, I am using SQL Server 2005 BIDS to create a package to import the excel file into my SQL Table. If I just run the package itself, it imports fine. I then save a copy of the package on the msdb server and run the job and that’s when I get the error (below):{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}}{\*\generator Msftedit 5.41.15.1507;}\viewkind4\uc1\pard\f0\fs20 1984-2005. All rights reserved. Started: 9:05:28 AM Progress: 2009-04-27 09:05:56.77 Source: Data Flow Import WFPCA Validating: 0% complete End Progress Progress: 2009-04-27 09:05:56.79 Source: Data Flow Import WFPCA Validating: 33% complete End Progress Progress: 2009-04-27 09:05:56.96 Source: Data Flow Import WFPCA Validating: 66% complete End Progress Error: 2009-04-27 09:05:58.07 Code: 0xC0202009 Source: Package Connection manager "Excel Connection Manager 9" Description: 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: "Failure creating file.". End Error Error: 2009-04-27 09:05:58.07 Code: 0xC020801C Source: Data Flow Import WFPCA Excel Source - WFPCA [1] ... The package execution fa... The step failed.\parI’ve done some research, and one option from Microsoft points to this: (link: http://support.microsoft.com/kb/918760)File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. For example, this scenario can occur with text log providers that do not use a login and a password. This scenario can also occur with any task that depends on the file connection manager, such as a SSIS file system task. I’ve tried the solutions from the site, but they don’t seem to help. Might you have any thoughts on how to resolve? |
|
|
Ice Polar
Starting Member
1 Post |
Posted - 2009-05-05 : 04:25:37
|
| Hi flipfyre,i think the difference between running the package interactively and running it in a job is the account.In the first matter your own account is the context in the last this will be the the account of the SQL Server Agent e.g. LOCALSYSTEM.This could be the reason for this difference.good luck Ice |
 |
|
|
|
|
|
SQL Server 2005 job + import excel