Monday, February 20, 2012

Maintenance Plan Transaction Log

We're running Sql Server 2000 and set up a maintenance plan for two of our
databases. It is set to create a full backup in the evening and at the
moment, a transaction log backup every 4 hours. The transaction log backup
fails inconsistently with the following message in the job history:
Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
42000] (Error 22029). The step failed.
Looking further in the logfile created for logging successes and failures,
it provides a little more:
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998
[Microsoft SQL-DMO (ODBC SQLState: HYT00)] Error 0: [Microsoft][
ODBC SQL
Server Driver]Timeout expired
Msg 22029, Sev 16: sqlmaint.exe failed. [SQLSTATE 42000]
I have looked at others with similar issues and the suggested solutions, but
none apply or have resolved the problem. The maintenance plan does not do
any optimization or integrity checking prior to the backup. I also increase
d
the login timeout from 45 to 60 seconds to no avail.
The only thing I've seen is a recommendation to dump the maintenance plan
and create the job under SQL Server Agent. Call me stubborn, but I'd sure
like to know what's going on rather than throwing in the towel and taking
another approach!Hi,
Too bad noone could help you - I have the same problem :-(
Using SQL Server Agent directly is not the best solution - one shortkomming
(of several) is the lack of integrated backupfile management.
Chris
"Zim" <Zim@.discussions.microsoft.com> wrote in message
news:6C695DCA-3960-4B57-A639-9F52314054C5@.microsoft.com...
> We're running Sql Server 2000 and set up a maintenance plan for two of our
> databases. It is set to create a full backup in the evening and at the
> moment, a transaction log backup every 4 hours. The transaction log
> backup
> fails inconsistently with the following message in the job history:
> Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTA
TE
> 42000] (Error 22029). The step failed.
> Looking further in the logfile created for logging successes and failures,
> it provides a little more:
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
>
> [Microsoft SQL-DMO (ODBC SQLState: HYT00)] Error 0: [Microsoft]
1;ODBC SQL
> Server Driver]Timeout expired
>
> Msg 22029, Sev 16: sqlmaint.exe failed. [SQLSTATE 42000]
>
> I have looked at others with similar issues and the suggested solutions,
> but
> none apply or have resolved the problem. The maintenance plan does not do
> any optimization or integrity checking prior to the backup. I also
> increased
> the login timeout from 45 to 60 seconds to no avail.
> The only thing I've seen is a recommendation to dump the maintenance plan
> and create the job under SQL Server Agent. Call me stubborn, but I'd sure
> like to know what's going on rather than throwing in the towel and taking
> another approach!

No comments:

Post a Comment