Patrick.O.Ige

Knowledge Creation is Essential to Business, and Communication is Essential to Knowledge Creation

  Home  |   Contact  |   Syndication    |   Login
  94 Posts | 5 Stories | 342 Comments | 0 Trackbacks

News

SharePoint SharePoint SharePoint

Article Categories

Archives

Post Categories

ADO.NET

Ajax

API/WebServices

ASP.NET Resources

BizTalk Server

Blogs I read

Free Books

How to

JQuery

LINQ

Misc

Mobile BI

Reporting Services

SEO

Sharepoint Resources/Tools

SharePoint 2010 Branding

SharePoint 2010 Videos

SilverLight

SQL Server

Sql Server 2012

SSIS

Windows Phone

WorkFlows

WSS V3

xml

I have a SSIS package that loads data from a Sharepoint List using s Sharepoint List Source component.
When i run the package from V.S NET it works well and the data destination is to a sql table.

But when i create a job for it and schedule it i get error:
Failed to open package file "Package.dtsx" due to error 0x80070005 "Access is denied."

I spent time looking at the history of the job and all i could see is that the job failed saying  it was was invoked by me but i noticed its been executed by another USER :(

After pulling out my hair and making sure i granted the acct running Sql server agent admin access but still didn't work.
I later came across PROXIES you can find them under the Sql Server Agent Folder

There s also a a Proxy tutorial here.

After i configured the proxy and used it to run the job as specified in the articles above. The job worked like a charm:)
** Remember you have to create credentials first before you see them when creating a job.To do that just go to your root folder in SQL SERVER Management Studio and right click > Security > New > Credentials.

Hope that helps and keep integrating


  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
posted on Sunday, February 15, 2009 4:10 PM

Feedback

# re: Failed to open package file "Package.dtsx" due to error 0x80070005 "Access is denied." SSIS 2008 1/11/2012 12:41 AM Pradeep nambiar
I tried with the following steps and was able to run the jobs in Local

1) Type service in run command
2) Check for the SQL server Agent (MSSQLSERVER)
3) Right click on Sql server agent and select Properties
4) Choose log on tab
5) Changed to my system account instead of default Network service account with pswd
6) Stopped the service
7) Re started the service
8) tried Executing the job and success was the result .

Please do have a try if face the above problem

Post A Comment
Title:
Name:
Email:
Website:
Comment:
Verification: