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

Maintenance Plan Job Returns Error

I get the following error when I execute the job that runs my maintenance plan.  The user running the job has sysadmin privledges.  Is there any way I can get more information on this?

Message
The job failed.  The Job was invoked by User xxxxx.  The last step to run was step 1 (Backup-Scales_Client).

Executed as user: xxxx. The package execution failed.  The step failed.

0
Fraser_Admin
Asked:
Fraser_Admin
  • 2
  • 2
1 Solution
 
mastooCommented:
Look at the job history with the "show steps" checked and highlight the last step - this might show details.  More likely go to the job itself for the step that failed, properties, advanced, and specify a log file then rerun the job and check the log file.
0
 
Fraser_AdminAuthor Commented:
The step error was the second error I showed above:
Executed as user: xxxx. The package execution failed.  The step failed

I don't see a place to specify a log file in the properties of the job, but i am displaying a log file in the maintenance plan and it show successful:

Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.1406
Report was generated on "xxxxx".
Maintenance Plan: Backup-Scales_Client
Duration: 00:00:00
Status: Succeeded.
Details:


Looks like the backup is done fine, just the job is throwing an error for some reason.
0
 
Fraser_AdminAuthor Commented:
I'm not very smart today...the error was because I had renamed a folder and forgot to change my maintenance plan's maintenance cleanup task to reflect that.  So the backup step was working fine, just not the maintenance step.  But its weird that it wouldn't give me a good error to go on.
0
 
mastooCommented:
Glad you got it going.  The log I was referring to is specified on the sql agent job, not the maintenance plan.  The maintenance plan generates 1 or more sql agent jobs.  You probably want to go to each job for a plan and specify the a log file.  On a job, edit a step, advanced, and enter a log file (with path).  If you use the same file for each step be sure it is append mode or each step will overwrite the previous.  I'm winging this from memory but it should be close - this is for Sql 2000.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

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