sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029)

  • Hello all,

    I get this error on one of the instances of SQLSERVER: maintenance plans. The jistory just says:

    sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).  The step failed.

    Other instance's maintenance plans works fine except for this.

    What could be the reason ?

     

  • What type of maint is this job doing?

    Transaction log backups? One or more databases are probably in SIMPLE recovery model.

    DBCC? You probably have attempt to repair errors when they occur checked! This will try and put the database in single user mode, which will fail if a any connections exist in that db.

  • "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029)" can mean anything from I/O error, out of disk space, or trying to backup a database that is not available (dropped, offline or suspect)

    Using Enterprise Manager, go to Management ==> Database Maintenance Plans. Right click the maintenance plan and then from the menu, pick "Maintenance Plan History"

    This will show more details on what went wrong.

    SQL = Scarcely Qualifies as a Language

  • This is a brand new instance with master/model/msdb/tempdb databases.

    I have one user database which is not live yet.

    The following maintenance plans are in this instance:

    Backup system dbs

    Backup user dbs

    The following jobs are scheduled:

    Backup system dbs

    bacckup user dbs

    backup system db transaction logs

    backup user db transaction logs

    Integrity check jobs x2: system and user

    Optimization jobs x2: system and user

    Other instances of SQLSERVER on the same box have these jobs and they run per schdule.

    There is enough space, report log has nothing. Maintenance history is also blank.

     

    -ch

     

  • Which job is failing?

  • My guess is that the "backup system db transaction logs" job is failing. If that is in fact the case it is because the 'system' databases (master, model & msdb) are set to 'simple recovery' which is correct and should not be modified.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • I am making the same assumption and was trying to walk him, into it!

    I don't reccommend doinf DBCC's, Index rebuilds or stats on system databases if that is attempted here.

    Integrity check jobs x2: system and user

    Optimization jobs x2: system and user

  • All the jobs fail.

    Only model and my test db are set to full recovery.

    All others are set to simple.

    very strange.

    -chr

     

Viewing 8 posts - 1 through 7 (of 7 total)

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