SEO

#1 (**permalink**) 02-29-2008, 03:17 AM

Jobs are run from a master server and all the servers run the same
jobs.

A new server has been added and the jobs tested so far, ran OK but
for backups.(Transaction logs and database)with above listed error.

The same domain account is used for the agent and the sql server
engine for all databases

Out of ideas after browsing the web for a while

Your input on this is more than welcome

Vincento

#2 (**permalink**) 02-29-2008, 03:17 AM

"Vincento Harris" <wumutek@yahoo.com> wrote in message
news:2fa13ee7.0406180605.464a42f7@posting.google.c om...
> Jobs are run from a master server and all the servers run the same
> jobs.
>
> A new server has been added and the jobs tested so far, ran OK but
> for backups.(Transaction logs and database)with above listed error.
>
> The same domain account is used for the agent and the sql server
> engine for all databases
>
> Out of ideas after browsing the web for a while
>
> Your input on this is more than welcome
>
> Vincento

There are several possible reasons (search Google newsgroups for "sql 42000
22029"), but you should try to get more detailed information about the
error. What does it say in the maintenance plan report file or the
msdb.dbo.sysdbmaintplan_history table? I'm assuming that you're using a
maintenance plan, since all of the hits in Google for that error message
refer to using sqlmaint.exe.

If this doesn't help, please post some more information - which version of
MSSQL, which backups fail (system database or user databases), what recovery
model do those databases have, what options have you selected in the
maintenance plan (eg. "attempt to repair minor problems") etc.

Simon

#3 (**permalink**) 02-29-2008, 03:19 AM

"Simon Hayes" <sql@hayes.ch> wrote in message news:<40d4009e$1_1@news.bluewin.ch>...
> "Vincento Harris" <wumutek@yahoo.com> wrote in message
> news:2fa13ee7.0406180605.464a42f7@posting.google.c om...
> > Jobs are run from a master server and all the servers run the same
> > jobs.
> >
> > A new server has been added and the jobs tested so far, ran OK but
> > for backups.(Transaction logs and database)with above listed error.
> >
> > The same domain account is used for the agent and the sql server
> > engine for all databases
> >
> > Out of ideas after browsing the web for a while
> >
> > Your input on this is more than welcome
> >
> > Vincento
>
> There are several possible reasons (search Google newsgroups for "sql 42000
> 22029"), but you should try to get more detailed information about the
> error. What does it say in the maintenance plan report file or the
> msdb.dbo.sysdbmaintplan_history table? I'm assuming that you're using a
> maintenance plan, since all of the hits in Google for that error message
> refer to using sqlmaint.exe.
>
> If this doesn't help, please post some more information - which version of
> MSSQL, which backups fail (system database or user databases), what recovery
> model do those databases have, what options have you selected in the
> maintenance plan (eg. "attempt to repair minor problems") etc.
>
> Simon

I did realize the information was a bit sketchy right after posting

I was using sql server version 7 SP2 at the time but have been
patched to service Pack 4 ,after consistent failures to run
maintenance plan jobs from
a master server.

The maintenance plan had these checked
--- reorganize data and index pages
---verify integrity of backup after completion
n/b All the scripted jobs worked but for the maintenance plan.

The maintenance plan jobs have been recreated locally and work just
fine.
The backups for the user databases is what fails consistently

Thanks

vince

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Mostly backup jobs fail with Generic error sqlstate 42000 error 22029