Integrity and Reindex failure when executed Sqmaint.exe

  • When executeted the Sqlmaintenance job for Integrity check we found the below error message:

    Date26/05/2009 22:00:01

    LogJob History (OnePoint - Check Integrity)

    Step ID1

    ServerC134PC001\PC001

    Job NameOnePoint - Check Integrity

    Step NameCheck OnePoint Integrity

    Duration00:00:00

    Sql Severity16

    Sql Message ID22029

    Operator Emailed

    Operator Net sent

    Operator Paged

    Retries Attempted0

    Message

    Executed as user: COREBUS1\SVCSQLRUNC134PC001. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.

    When executed the reindex job for Sqlmaintenance we are getting the below error message:

    Date27/05/2009 03:00:00

    LogJob History (OnePoint - Reindex)

    Step ID1

    ServerC134PC001\PC001

    Job NameOnePoint - Reindex

    Step NameReindex OnePoint tables

    Duration00:00:00

    Sql Severity16

    Sql Message ID22029

    Operator Emailed

    Operator Net sent

    Operator Paged

    Retries Attempted0

    Message

    Executed as user: COREBUS1\SVCSQLRUNC134PC001. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.

    Can anyone please help us out. We have executed DBCC commands in all the databases still it is occuring daily.

  • Are you including logging for the maintenance plan? If so that detailed logging will provide a great deal more information to help identify the issue at hand.



    Shamless self promotion - read my blog http://sirsql.net

  • We have included the logging as well and found the below mentioned output only for reindex:

    Job 'OnePoint - Reindex' : Step 1, 'Reindex OnePoint tables' : Began Executing 2009-05-13 12:14:22

    output

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    (null)

    Microsoft (R) SQLMaint Utility (Unicode), Version 9.00.3042.00

    Copyright (c) Microsoft Corporation.

    (null)

    (null)

    Msg 22029, Sev 16, State 1: sqlmaint.exe failed. [SQLSTATE 42000]

    Job 'OnePoint - Reindex' : Step 1, 'Reindex OnePoint tables' : Began Executing 2009-05-14 03:00:00

  • Have you enable extended logging? There should be more information than that.

    Open up the maintenance plan, click on the reporting and logging button, in the window that opens up select "generate a text file report", put in a location for the report, and check the "log extended information" box. Hit ok and save the plan.

    When it runs it will create the file and include vastly improved logging that should help identify the issue.



    Shamless self promotion - read my blog http://sirsql.net

  • Can you please tell me where extended logging button is available in SQL Server2005.

    When anaylsed further, I found another message:

    Date27/05/2009 22:00:00

    LogJob History (OnePoint - Check Integrity)

    Step ID0

    ServerC134PC001\PC001

    Job NameOnePoint - Check Integrity

    Step Name(Job outcome)

    Duration00:00:00

    Sql Severity0

    Sql Message ID0

    Operator Emailed

    Operator Net sent

    Operator Paged

    Retries Attempted0

    Message

    The job failed. The Job was invoked by Schedule 9 (Check Integrity Schedule). The last step to run was step 1 (Check OnePoint Integrity).

    Can you please tell where the problem should be.

    Thanks for your response

  • Checked the report and logging icon and found log extended information is already selected. The error description which I sent is from that log file only.:-)

  • are you logging to a text file? Is that error the entire contents of the file?



    Shamless self promotion - read my blog http://sirsql.net

  • Instead of looking at the history of the job - view the history of the maintenance plan (Open the Maintenance Plan folder, right-click on the maintenance plan and select View History).

    This should give you additional information on what is causing the problem.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Yes, that is the entire contents of the log file. So not clear where it is failing.

    Can you tell me what are the possibilities.

    Thanks in advance

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

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