• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 151
  • Last Modified:

NEED HELP...SQL 2005 Job keeps failing everytime. Created job proxy and credential etc.

Hi all.  I cant seem to figure this out.  I had a SQL 2K DTS package where I transferred it over as a SSIS package and changed everything over etc.  I can manually run the package without any problems.  I created a job proxy and credential etc.  I can run the job manually with no problem.  When it is scheduled however it fails everytime.  How can I troubleshoot this?  I dont know what to change and what is going on as it seems if I am logged onto the PC it works fine.  Is there a way to change the owner of the package or something to admin?  No idea what to do from here as I am really hating SQL 05 right now.
  • 2
1 Solution
what error does it fail with?
check the job step history....

it sounds like a permission issue

what is the job doing... writing files / read files...?

sbornstein2Author Commented:
if I am logged onto the PC the job runs fine even when its scheduled.  Once I logoff it fails everytime.  The error is:

Executed as user: SGIDOMAIN\mwalsh. The package execution failed.  The step failed.

so its definatly a permission issue but why does it run fine scheduled when I am logged onto the PC?
when you logon do you automatically bring in other network drives/devices that the job needs?

that wont happend in the background...?

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now