|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by dgooge in Databases Miscellaneous, SQL Server 2005, MS SQL DTS
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.".".
20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625
