Maintenance Plan & Job Failed

Question

Maintenance Plan & Job Failed

sumit kumar sahay

SSC Enthusiast

Points: 109
More actions
April 20, 2006 at 10:35 pm

#113950

Hello Friends,
I encounter the following error in my maintenance plan and job history, please help me finding out the reason and solution.
1. Job History :
The job failed. The Job was invoked by Schedule 9 (Schedule 1). The last step to run was step 1 (Step 1).
Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
The job failed. The owner () of job Optimizations Job for DB Maintenance Plan 'Non-Core Maint Plan' does not have server access.

2: Maintenance plan:

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 927: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'restore_test' cannot be opened. It is in the middle of a restore.
[Microsoft][ODBC SQL Server Driver][SQL

3. Log file :

BACKUP failed to complete the command BACKUP DATABASE [restore_test] TO DISK = N'E:\SQL_Backups\restore_test\restore_test_db_200604160200.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT

Regards,
Sumit

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

John Rowan SSC Guru Points: 56440 More actions · Answer 1

Has this plan ever worked before? This looks like a permissions problem. Do you have your SQL Server service running under the system account or a local or domain account that you've specified? I would suggest running your job under an account other than the system account.

John Rowan

======================================================
======================================================
Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

Sven Nilsson Newbie Points: 7 More actions · Answer 2

ActuallyIt it doesn't need to be permissions related.

We ran into this suddenly after a somewhat unplanned restart due to a power failure.

3 out of 6 servers running W2003 Server/SQL 2K just couldn't run those old well proven maintenance plans with the above message.

Simply restarting the SQLSERVERAGENT service fixed the problem.

My humble guess is that the PDC was not yet responding during system start and that could be causing this behaviour.

With these kind of systems always try the restarting/reinstalling technique first instead of wasting time on searching for logical reasons when things suddenly stop working...

sumit kumar sahay SSC Enthusiast Points: 109 More actions · Answer 3

Hi,

Thank you for looking into it. Issue got resolved, by adding some point in job step, now it is running successfully.

again thanks for your time.

Regards,

Sumit