SQLMaint runs clean BUT Sched Task fails

[BC]

I have a number of test databases which were created from the same backup. Set up SQLMaint to run on them each night. SQL Maint seems to run clean on all of them, but on two the Scheduled Task shows "Failed". All tasks have been set up exactly the same.

Has anyone run into something like this?

Here's the output from the maintenance job for one of the failing db's:



Microsoft (R) SQLMaint Utility, Version 6.50.240
Copyright (C) Microsoft Corporation, 1995 - 1996

Logged on to SQL Server 'COSTGUARD2' as 'sa' (trusted)
Starting maintenance of database 'Test15' on Thu Jun 17 23:10:01 1999

[1] Check Data and Index Linkage...

** Execution Time: 0 hrs, 0 mins, 1 secs **

[2] Check Data and Index Allocation...

** Execution Time: 0 hrs, 0 mins, 2 secs **

[3] Check System Data...

** Execution Time: 0 hrs, 0 mins, 1 secs **

[4] Update Statistics...

** Execution Time: 0 hrs, 0 mins, 27 secs **

End of maintenance for database 'Test15' on Thu Jun 17 23:10:30 1999

SQLMAINT.EXE Process Exit Code: 0 (Success)

[Todd Carrico]

This may be obvious, but it looks to me like this text is for a successful run. Are you sure you got the file with the correct date?

Can you run the DBCC commands successfuly?

tc


------------
BC at 6/18/99 8:33:12 AM

I have a number of test databases which were created from the same backup. Set up SQLMaint to run on them each night. SQL Maint seems to run clean on all of them, but on two the Scheduled Task shows "Failed". All tasks have been set up exactly the same.

Has anyone run into something like this?

Here's the output from the maintenance job for one of the failing db's:



Microsoft (R) SQLMaint Utility, Version 6.50.240
Copyright (C) Microsoft Corporation, 1995 - 1996

Logged on to SQL Server 'COSTGUARD2' as 'sa' (trusted)
Starting maintenance of database 'Test15' on Thu Jun 17 23:10:01 1999

[1] Check Data and Index Linkage...

** Execution Time: 0 hrs, 0 mins, 1 secs **

[2] Check Data and Index Allocation...

** Execution Time: 0 hrs, 0 mins, 2 secs **

[3] Check System Data...

** Execution Time: 0 hrs, 0 mins, 1 secs **

[4] Update Statistics...

** Execution Time: 0 hrs, 0 mins, 27 secs **

End of maintenance for database 'Test15' on Thu Jun 17 23:10:30 1999

SQLMAINT.EXE Process Exit Code: 0 (Success)

[BC]

Yes, that is the output I get! It's a bit maddening. The process runs through with a return code
of zero (success) and yet it shows "failed" in the task schedule.

DBCC command run on its own also is successful.


------------
Todd Carrico at 6/18/99 10:18:18 PM

This may be obvious, but it looks to me like this text is for a successful run. Are you sure you got the file with the correct date?

Can you run the DBCC commands successfuly?

tc


------------
BC at 6/18/99 8:33:12 AM

I have a number of test databases which were created from the same backup. Set up SQLMaint to run on them each night. SQL Maint seems to run clean on all of them, but on two the Scheduled Task shows "Failed". All tasks have been set up exactly the same.

Has anyone run into something like this?

Here's the output from the maintenance job for one of the failing db's:



Microsoft (R) SQLMaint Utility, Version 6.50.240
Copyright (C) Microsoft Corporation, 1995 - 1996

Logged on to SQL Server 'COSTGUARD2' as 'sa' (trusted)
Starting maintenance of database 'Test15' on Thu Jun 17 23:10:01 1999

[1] Check Data and Index Linkage...

** Execution Time: 0 hrs, 0 mins, 1 secs **

[2] Check Data and Index Allocation...

** Execution Time: 0 hrs, 0 mins, 2 secs **

[3] Check System Data...

** Execution Time: 0 hrs, 0 mins, 1 secs **

[4] Update Statistics...

** Execution Time: 0 hrs, 0 mins, 27 secs **

End of maintenance for database 'Test15' on Thu Jun 17 23:10:30 1999

SQLMAINT.EXE Process Exit Code: 0 (Success)