Re: Backup job reported as failed

On Oct 7, 12:45 pm, "Tibor Karaszi"
<tibor_please.no.email_kara...@xxxxxxxxxxxxxxxxxx> wrote:
Perhaps you can find some details if you specify a report file for the plan and investigate that
file?

--
Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi

"BlackToe" <goo...@xxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:1191777184.181970.184540@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



Using the wizard, I set up a maintenance plan to backup a few
databases in MS SQL Server 2005. The plan does:

1) Integrity check
2) Database shrink
3) Rebuilds indexes
4) Backs up the databases
5) Deletes old backup files

I also configured Database Email and SQL Agent to run the plan nightly
and email me the results. The email states that the job is failing:

JOB RUN: 'Nightly backup' was run on 10/7/2007 at 2:00:00 AM
DURATION: 0 hours, 1 minutes, 44 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 1 (Nightly
backup). The last step to run was step 1 (Subplan).

However, the backups all appear to be made correctly, and the log file
shows no errors. I also can't get any detail from the Job History to
determine exactly what is failing.

Thanks in advance for any help.- Hide quoted text -

- Show quoted text -

I'll give that a shot. Here's some more information that may or may
not be helpful:

In the "Maintenance Plan" node of the log viewer:
1) There are green checkmarks next to each entry for "Nightly backup"
2) There are two identical entries for each time the plan was executed
3) The duration on all is listed as "00:00:00"

In the "Job History" node of the log viewer:
1) Every entry has a red X next to it.
2) There is only one entry for each time the job was run.
3) The duration is between 1:40 and 1:50 (i.e. < 2 minutes) for each
entry

.

Relevant Pages

  • Re: Slow UPDATE and DELETE on SQL Server 2000
    ... databases: one on the new machine and one on the old machine (by the ... The plan from the old machine was more complex and has PARALLELISM ... > wrong with the SQL Server installation and unlikely that there are sub-system ... > linked-server driver parameters are not properly set. ...
    (microsoft.public.sqlserver.server)
  • Re: Backup job reported as failed
    ... Perhaps you can find some details if you specify a report file for the plan and investigate that file? ... Tibor Karaszi, SQL Server MVP ... databases in MS SQL Server 2005. ... Deletes old backup files ...
    (microsoft.public.sqlserver.tools)
  • Re: Backing up transaction logs
    ... You can't do log backups of master and SQLAgent will ... I'd usggest 1 plan for system databases (full backups ... Jasper Smith (SQL Server MVP) ...
    (microsoft.public.sqlserver.security)
  • Re: Backup job reported as failed
    ... databases in MS SQL Server 2005. ... Deletes old backup files ... I also configured Database Email and SQL Agent to run the plan nightly ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.sqlserver.tools)
  • Re: Run job from DTS package
    ... DTS package then you can have the Account under which it runs have perms to ... How do you propose to know that the backup job you have selected comes from ... Which maint plan? ... You may have one for logs and one for some databases, ...
    (microsoft.public.sqlserver.dts)