SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On



Transaction log backup failure in maintenance plan Expand / Collapse
Author
Message
Posted Monday, October 13, 2008 4:54 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, December 13, 2008 2:57 AM
Points: 2, Visits: 8
Hi,

I'm getting the below message when viewed in the job history of 'transaction log backup' maintenance plan.

"The job failed. The Job was invoked by Schedule 200 (Schedule 1).
The last step to run was step 1 (Step 1)."

Also the below error when viewed in the event log.

"Error 22029 Database. ... error sqlmaint.exe failed."

How can I know the cause behind this?

Although, the error relating to this is not logged in the errorlog.

thanks in advance :)
Post #584776
Posted Monday, October 13, 2008 5:09 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Sunday, March 14, 2010 9:06 PM
Points: 376, Visits: 740
Check the sql agent log and job history for more information on why the maintenance plan fail. Did you changed the job owner? Some time this might be the reason. Once done with the checking try to run the job once again manually and check if this was successfull. If still you find issue check the above log and paste the error.



Let down ur worries and be happy,


"Lets make our earth more green !! Plant a tree today
Post #584785
Posted Monday, October 13, 2008 8:24 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 3:24 PM
Points: 17,071, Visits: 12,178
You can set the main plan to log all errors to a text file. In SQL 2005 and 2008 that's done by selecting the 'Reporting and Logging' button from the maint plan's toolbar.
Set it to log to a text file and you'll be able to see the full error message.



Gail Shaw

We walk in the dark places no others will enter
We stand on the bridge and none may pass

Post #584903
Posted Sunday, October 19, 2008 2:53 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, March 10, 2010 9:00 AM
Points: 124, Visits: 170
Check whether you have applied latest SQL Server service pack(SP2 refresh version) on the server


Cheers ! ;)


_____________________________________________

Kindest Regards,
- Tushar
MCP,MCDBA(SQL 2000),MCTS(SQL 2005),MCITP(SQL 2005)

" Most Good Experience Comes From Judgement,
Most Judgement Comes From Bad Experience "
Post #588314
Posted Wednesday, January 14, 2009 1:23 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, January 14, 2009 1:18 AM
Points: 1, Visits: 1
Although it may be a little late for answering your questions, it may be useful for other people. Check if your database recovery model is Simple. You can not perform Transaction Log Backup on simple recovery mode databases. In that case you can change the recovery model of the databases from SIMPLE to either FULL or BULK LOGGED.
Post #636047
« Prev Topic | Next Topic »


Permissions Expand / Collapse