I have an SSIS package on a server that takes a table from a linked server(access database) and copies it to a table on a remote server. The packages works great with no errors when run after initially creating it, and even running it over and over again manually.
However, I want to set this package to run under the SQL Agent. But every time I set the package to run under the agent it errors out and gives me all kinds of grief that it can't find the OLE DB datasource, which is bull because the package runs fine on that server if not initiated from the agent. Why won't this run under the agent but runs fine any other way? I have even set the agent to run under a domain admin account because somebody mentioned it may be permissions related, but that didn't help either. Here is the error:
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E14 Description: "Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "LinkedServerName".". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E14 Description: "OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "LinkedServerName" returned message "'H:\access\database.mdb' 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.".".
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: pettmansPosted on 2009-11-04 at 19:04:38ID: 25746417
It looks you have mapped drive H to a remote network location while logged in under your account. So the linked server object works for you. However when you try to access it via a SQL Agent job, the Agent service account does not have that drive mapped.
A few ways forward:
Copy the database to a local drive; or
Specify a url for the linked server object instead of a mapped drive and ensure the Agent service account has appropriate permissions; or
Log onto the server as the Agent service account, map the drive making it persistant and then restart the Agent service.