Database Maintenance Plan -> SQLMAINT.exe Error

Having a problem with a Database Maintenance Plan that runs a tran log
backup. The job has been running successfully until very recently. (The
failures seem to coincide with the installation of the Feb 2005 CTP.) When
the job runs, it fails almost immediately. No report is generated. No
Maintenance Plan History is recorded in the Plan History Window. The only
info that gets recorded is that the step failed in the Sql Agent Job history
for the job.
Here is output from running it directly from Query Analyzer.
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
/* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
not in the path and not in current directory)
-- but then that util fails - probably a dll overlaided by the sql2005 beta
install
output
-----------
NULL
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998
NULL
NULL
(5 row(s) affected)
Server: Msg 22029, Level 16, State 1, Line 0
sqlmaint.exe failed.
Not much info there, huh?
Any help would be appreciated.
Check to make sure the db is not in simple recovery mode.
Andrew J. Kelly SQL MVP
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
> Having a problem with a Database Maintenance Plan that runs a tran log
> backup. The job has been running successfully until very recently. (The
> failures seem to coincide with the installation of the Feb 2005 CTP.) When
> the job runs, it fails almost immediately. No report is generated. No
> Maintenance Plan History is recorded in the Plan History Window. The only
> info that gets recorded is that the step failed in the Sql Agent Job
> history for the job.
> Here is output from running it directly from Query Analyzer.
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
> Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
> DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
> not in the path and not in current directory)
> -- but then that util fails - probably a dll overlaided by the sql2005
> beta install
> output
> ----------
--
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> NULL
> (5 row(s) affected)
> Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed.
> Not much info there, huh?
> Any help would be appreciated.
>
|||Checked that already, all dbs are in full. It appears as if the job isnt
even getting off the ground. It returns failure in a few seconds (< 5
seconds). Previously, if we had included a DB in simple mode in the job, the
job would run, but exit with a return code of 1 and a report would be
created. It appears the job is failing before it tried to hit any of the
databases.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eTz5ke$IFHA.2356@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Check to make sure the db is not in simple recovery mode.
> --
> Andrew J. Kelly SQL MVP
>
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
--
>
|||I solved the problem. It appears that the uninstallation of Sql server 2005
interferes/unregisters the sqldmo.dll library. I reregistered the DLL and
all is well. Thanks!
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
> Having a problem with a Database Maintenance Plan that runs a tran log
> backup. The job has been running successfully until very recently. (The
> failures seem to coincide with the installation of the Feb 2005 CTP.) When
> the job runs, it fails almost immediately. No report is generated. No
> Maintenance Plan History is recorded in the Plan History Window. The only
> info that gets recorded is that the step failed in the Sql Agent Job
> history for the job.
> Here is output from running it directly from Query Analyzer.
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
> Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
> DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
> not in the path and not in current directory)
> -- but then that util fails - probably a dll overlaided by the sql2005
> beta install
> output
> ----------
--
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> NULL
> (5 row(s) affected)
> Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed.
> Not much info there, huh?
> Any help would be appreciated.
>
|||You should NOT be running SQL2005 on a production server. I won't even run
it in anything other than a virtual server myself.
Andrew J. Kelly SQL MVP
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:eBiPnu$IFHA.1476@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
>I solved the problem. It appears that the uninstallation of Sql server
>2005 interferes/unregisters the sqldmo.dll library. I reregistered the DLL
>and all is well. Thanks!
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
--
>
|||This is a DEV server, not PROD.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:udfY5pFJFHA.3064@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> You should NOT be running SQL2005 on a production server. I won't even
> run it in anything other than a virtual server myself.
> --
> Andrew J. Kelly SQL MVP
>
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:eBiPnu$IFHA.1476@.TK2MSFTNGP09.phx.gbl...
--
>

Database Maintenance Plan -> SQLMAINT.exe Error

Having a problem with a Database Maintenance Plan that runs a tran log
backup. The job has been running successfully until very recently. (The
failures seem to coincide with the installation of the Feb 2005 CTP.) When
the job runs, it fails almost immediately. No report is generated. No
Maintenance Plan History is recorded in the Plan History Window. The only
info that gets recorded is that the step failed in the Sql Agent Job history
for the job.
Here is output from running it directly from Query Analyzer.
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
/* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
not in the path and not in current directory)
-- but then that util fails - probably a dll overlaided by the sql2005 beta
install
output
----
----
----
--
NULL
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998
NULL
NULL
(5 row(s) affected)
Server: Msg 22029, Level 16, State 1, Line 0
sqlmaint.exe failed.
Not much info there, huh?
Any help would be appreciated.Check to make sure the db is not in simple recovery mode.
Andrew J. Kelly SQL MVP
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
> Having a problem with a Database Maintenance Plan that runs a tran log
> backup. The job has been running successfully until very recently. (The
> failures seem to coincide with the installation of the Feb 2005 CTP.) When
> the job runs, it fails almost immediately. No report is generated. No
> Maintenance Plan History is recorded in the Plan History Window. The only
> info that gets recorded is that the step failed in the Sql Agent Job
> history for the job.
> Here is output from running it directly from Query Analyzer.
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
> Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
> DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
> not in the path and not in current directory)
> -- but then that util fails - probably a dll overlaided by the sql2005
> beta install
> output
> ----
----
----
--
--
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> NULL
> (5 row(s) affected)
> Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed.
> Not much info there, huh?
> Any help would be appreciated.
>|||Checked that already, all dbs are in full. It appears as if the job isnt
even getting off the ground. It returns failure in a few seconds (< 5
seconds). Previously, if we had included a DB in simple mode in the job, the
job would run, but exit with a return code of 1 and a report would be
created. It appears the job is failing before it tried to hit any of the
databases.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eTz5ke$IFHA.2356@.TK2MSFTNGP12.phx.gbl...
> Check to make sure the db is not in simple recovery mode.
> --
> Andrew J. Kelly SQL MVP
>
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
--[vbcol=seagreen]
>|||I solved the problem. It appears that the uninstallation of Sql server 2005
interferes/unregisters the sqldmo.dll library. I reregistered the DLL and
all is well. Thanks!
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
> Having a problem with a Database Maintenance Plan that runs a tran log
> backup. The job has been running successfully until very recently. (The
> failures seem to coincide with the installation of the Feb 2005 CTP.) When
> the job runs, it fails almost immediately. No report is generated. No
> Maintenance Plan History is recorded in the Plan History Window. The only
> info that gets recorded is that the step failed in the Sql Agent Job
> history for the job.
> Here is output from running it directly from Query Analyzer.
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
> Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
> DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
> not in the path and not in current directory)
> -- but then that util fails - probably a dll overlaided by the sql2005
> beta install
> output
> ----
----
----
--
--
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> NULL
> (5 row(s) affected)
> Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed.
> Not much info there, huh?
> Any help would be appreciated.
>|||You should NOT be running SQL2005 on a production server. I won't even run
it in anything other than a virtual server myself.
Andrew J. Kelly SQL MVP
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:eBiPnu$IFHA.1476@.TK2MSFTNGP09.phx.gbl...
>I solved the problem. It appears that the uninstallation of Sql server
>2005 interferes/unregisters the sqldmo.dll library. I reregistered the DLL
>and all is well. Thanks!
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
--[vbcol=seagreen]
>|||This is a DEV server, not PROD.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:udfY5pFJFHA.3064@.TK2MSFTNGP12.phx.gbl...
> You should NOT be running SQL2005 on a production server. I won't even
> run it in anything other than a virtual server myself.
> --
> Andrew J. Kelly SQL MVP
>
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:eBiPnu$IFHA.1476@.TK2MSFTNGP09.phx.gbl...
--[vbcol=seagreen]
>

Database Maintenance Plan -> SQLMAINT.exe Error

Having a problem with a Database Maintenance Plan that runs a tran log
backup. The job has been running successfully until very recently. (The
failures seem to coincide with the installation of the Feb 2005 CTP.) When
the job runs, it fails almost immediately. No report is generated. No
Maintenance Plan History is recorded in the Plan History Window. The only
info that gets recorded is that the step failed in the Sql Agent Job history
for the job.
Here is output from running it directly from Query Analyzer.
EXECUTE master.dbo.xp_sqlmaint N'-PlanID
8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
/* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
not in the path and not in current directory)
-- but then that util fails - probably a dll overlaided by the sql2005 beta
install
output
-----------
NULL
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998
NULL
NULL
(5 row(s) affected)
Server: Msg 22029, Level 16, State 1, Line 0
sqlmaint.exe failed.
Not much info there, huh?
Any help would be appreciated.Check to make sure the db is not in simple recovery mode.
--
Andrew J. Kelly SQL MVP
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
> Having a problem with a Database Maintenance Plan that runs a tran log
> backup. The job has been running successfully until very recently. (The
> failures seem to coincide with the installation of the Feb 2005 CTP.) When
> the job runs, it fails almost immediately. No report is generated. No
> Maintenance Plan History is recorded in the Plan History Window. The only
> info that gets recorded is that the step failed in the Sql Agent Job
> history for the job.
> Here is output from running it directly from Query Analyzer.
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
> Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
> DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
> not in the path and not in current directory)
> -- but then that util fails - probably a dll overlaided by the sql2005
> beta install
> output
> -----------
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> NULL
> (5 row(s) affected)
> Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed.
> Not much info there, huh?
> Any help would be appreciated.
>|||Checked that already, all dbs are in full. It appears as if the job isnt
even getting off the ground. It returns failure in a few seconds (< 5
seconds). Previously, if we had included a DB in simple mode in the job, the
job would run, but exit with a return code of 1 and a report would be
created. It appears the job is failing before it tried to hit any of the
databases.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eTz5ke$IFHA.2356@.TK2MSFTNGP12.phx.gbl...
> Check to make sure the db is not in simple recovery mode.
> --
> Andrew J. Kelly SQL MVP
>
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
>> Having a problem with a Database Maintenance Plan that runs a tran log
>> backup. The job has been running successfully until very recently. (The
>> failures seem to coincide with the installation of the Feb 2005 CTP.)
>> When the job runs, it fails almost immediately. No report is generated.
>> No Maintenance Plan History is recorded in the Plan History Window. The
>> only info that gets recorded is that the step failed in the Sql Agent Job
>> history for the job.
>> Here is output from running it directly from Query Analyzer.
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt
>> "C:\MSSQL\Log\Backup\Transaction Log Bkup6.txt" -DelTxtRpt
>> 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia DISK -BkUpLog
>> "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
>> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
>> not in the path and not in current directory)
>> -- but then that util fails - probably a dll overlaided by the sql2005
>> beta install
>> output
>> -----------
>> NULL
>> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
>> Copyright (C) Microsoft Corporation, 1995 - 1998
>> NULL
>> NULL
>> (5 row(s) affected)
>> Server: Msg 22029, Level 16, State 1, Line 0
>> sqlmaint.exe failed.
>> Not much info there, huh?
>> Any help would be appreciated.
>|||I solved the problem. It appears that the uninstallation of Sql server 2005
interferes/unregisters the sqldmo.dll library. I reregistered the DLL and
all is well. Thanks!
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
> Having a problem with a Database Maintenance Plan that runs a tran log
> backup. The job has been running successfully until very recently. (The
> failures seem to coincide with the installation of the Feb 2005 CTP.) When
> the job runs, it fails almost immediately. No report is generated. No
> Maintenance Plan History is recorded in the Plan History Window. The only
> info that gets recorded is that the step failed in the Sql Agent Job
> history for the job.
> Here is output from running it directly from Query Analyzer.
> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt "C:\MSSQL\Log\Backup\Transaction
> Log Bkup6.txt" -DelTxtRpt 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia
> DISK -BkUpLog "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
> not in the path and not in current directory)
> -- but then that util fails - probably a dll overlaided by the sql2005
> beta install
> output
> -----------
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> NULL
> (5 row(s) affected)
> Server: Msg 22029, Level 16, State 1, Line 0
> sqlmaint.exe failed.
> Not much info there, huh?
> Any help would be appreciated.
>|||You should NOT be running SQL2005 on a production server. I won't even run
it in anything other than a virtual server myself.
--
Andrew J. Kelly SQL MVP
"Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
news:eBiPnu$IFHA.1476@.TK2MSFTNGP09.phx.gbl...
>I solved the problem. It appears that the uninstallation of Sql server
>2005 interferes/unregisters the sqldmo.dll library. I reregistered the DLL
>and all is well. Thanks!
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
>> Having a problem with a Database Maintenance Plan that runs a tran log
>> backup. The job has been running successfully until very recently. (The
>> failures seem to coincide with the installation of the Feb 2005 CTP.)
>> When the job runs, it fails almost immediately. No report is generated.
>> No Maintenance Plan History is recorded in the Plan History Window. The
>> only info that gets recorded is that the step failed in the Sql Agent Job
>> history for the job.
>> Here is output from running it directly from Query Analyzer.
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt
>> "C:\MSSQL\Log\Backup\Transaction Log Bkup6.txt" -DelTxtRpt
>> 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia DISK -BkUpLog
>> "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
>> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it is
>> not in the path and not in current directory)
>> -- but then that util fails - probably a dll overlaided by the sql2005
>> beta install
>> output
>> -----------
>> NULL
>> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
>> Copyright (C) Microsoft Corporation, 1995 - 1998
>> NULL
>> NULL
>> (5 row(s) affected)
>> Server: Msg 22029, Level 16, State 1, Line 0
>> sqlmaint.exe failed.
>> Not much info there, huh?
>> Any help would be appreciated.
>|||This is a DEV server, not PROD. :)
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:udfY5pFJFHA.3064@.TK2MSFTNGP12.phx.gbl...
> You should NOT be running SQL2005 on a production server. I won't even
> run it in anything other than a virtual server myself.
> --
> Andrew J. Kelly SQL MVP
>
> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
> news:eBiPnu$IFHA.1476@.TK2MSFTNGP09.phx.gbl...
>>I solved the problem. It appears that the uninstallation of Sql server
>>2005 interferes/unregisters the sqldmo.dll library. I reregistered the DLL
>>and all is well. Thanks!
>> "Frank Castora" <fcc8b_sqlserver@.hotmail.com> wrote in message
>> news:Oi%23d6A$IFHA.3916@.TK2MSFTNGP14.phx.gbl...
>> Having a problem with a Database Maintenance Plan that runs a tran log
>> backup. The job has been running successfully until very recently. (The
>> failures seem to coincide with the installation of the Feb 2005 CTP.)
>> When the job runs, it fails almost immediately. No report is generated.
>> No Maintenance Plan History is recorded in the Plan History Window. The
>> only info that gets recorded is that the step failed in the Sql Agent
>> Job history for the job.
>> Here is output from running it directly from Query Analyzer.
>> EXECUTE master.dbo.xp_sqlmaint N'-PlanID
>> 8C5C65BA-47A0-4605-8768-EA414FFE829A -Rpt
>> "C:\MSSQL\Log\Backup\Transaction Log Bkup6.txt" -DelTxtRpt
>> 4WEEKS -WriteHistory -VrfyBackup -BkUpMedia DISK -BkUpLog
>> "E:\MSSQL\DATA" -DelBkUps 4DAYS -CrBkSubDir -BkExt "TRN"'
>> /* -- definitely finds the 8.0 (Sql 2000) utility (somehow! - since it
>> is not in the path and not in current directory)
>> -- but then that util fails - probably a dll overlaided by the sql2005
>> beta install
>> output
>> -----------
>> NULL
>> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
>> Copyright (C) Microsoft Corporation, 1995 - 1998
>> NULL
>> NULL
>> (5 row(s) affected)
>> Server: Msg 22029, Level 16, State 1, Line 0
>> sqlmaint.exe failed.
>> Not much info there, huh?
>> Any help would be appreciated.
>>
>

database maintenance plan - reorganize data pages and indexes

I've set up a monthly maint. plan that will re-org the db. I'm hoping that since this is a very high tran vol that I'm being proactive.

But, when I do this against a matching test db (exact same one but the name) I get a SET QUOTED IDENTIFIER incorrect on the optimization step. I've checked the properties of the DB and the 'Use quoted identifiers' box is checked and needs to be. I created the maint plan using the wizard and the option I've tried it with the option of reorg to orig amt of free space and change free space selected.

Help!!!! Oh, this is a PeopleSoft DB, so I can't change the prop of the DB..

Try putting the following statements at the top of the step with the SQL Agent Job that the DB Maintenance Plan creates to schedule execution of the plan:

set nocount on
set arithabort on
set ansi_nulls on
set ansi_null_dflt_on on
set ansi_padding on
set ansi_warnings on
set cursor_close_on_commit off
set implicit_transactions off
set quoted_identifier on
set concat_null_yields_null on
set numeric_roundabort off

That should be directly followed by the statement that already existed within the step to execute the master.dbo.xp_sqlmaint procedure.

HTH

|||Sorry to take so long, I had to find out how to add the commands. Which I did, but I'm still getting the same error. I c&p'd them into the 'edit' of the job step and applied. Then I went back and checked that they were still there. I started the job (which I've set up on a copy of the prod db) and it died w/the same error.
As you can tell, this is new stuff to me.
What else can I try?|||Well, try changing the 'on' in the 'set quoted identifier on' statement to 'off' instead...all comes down to differences between these settings in the msdb, master, and your user database...|||I couldn't chg the flag. But did get the suggestion you sent to work. I removed the line returns at the end of each line and replaced them with just a space, so that the entries where all strung together when I edited the step. So that worked.

So thank you. Now I just have to learn how to keep them when the job is refreshed.

as you've probably guessed, I'm learning as I go.|||

I'm back! Thought I had this resolved, but am still having the same error. The bad thing is that it only occurs on some of the DBs in the same instance of SQL Server. I've checked the options on the DBs and they match between the ones that can be integrity checked and the ones that can not. The ones that can be i ckd will run w/o any of the overrides. For the ones that the job gets an error, I've tried quoted_identifier on and off, with the other options and w/o. All DBs have ANSI NULL default, Auto update statistics, torn page, auto create statistics and use quoted identifiers checked, others not. (sql 2000). Db compatibility level 80 is selected on the compatibility. Some Dbs are model simple, some are full. That doesn't seem to matter.

I'd appreciate any more ideas.........

database maintenance plan - integrity check

I've set up a monthly maint. plan that will re-org the db. I'm hoping that since this is a very high tran vol that I'm being proactive.

But, when I do this against a matching test db (exact same one but the name) I get a SET QUOTED IDENTIFIER incorrect on the optimization step. I've checked the properties of the DB and the 'Use quoted identifiers' box is checked and needs to be. I created the maint plan using the wizard and the option I've tried it with the option of reorg to orig amt of free space and change free space selected.

Help!!!! Oh, this is a PeopleSoft DB, so I can't change the prop of the DB..

Try putting the following statements at the top of the step with the SQL Agent Job that the DB Maintenance Plan creates to schedule execution of the plan:

set nocount on
set arithabort on
set ansi_nulls on
set ansi_null_dflt_on on
set ansi_padding on
set ansi_warnings on
set cursor_close_on_commit off
set implicit_transactions off
set quoted_identifier on
set concat_null_yields_null on
set numeric_roundabort off

That should be directly followed by the statement that already existed within the step to execute the master.dbo.xp_sqlmaint procedure.

HTH

|||Sorry to take so long, I had to find out how to add the commands.

Which I did, but I'm still getting the same error. I c&p'd

them into the 'edit' of the job step and applied. Then I went

back and checked that they were still there. I started the job

(which I've set up on a copy of the prod db) and it died w/the

same error.

As you can tell, this is new stuff to me.

What else can I try?|||Well, try changing the 'on' in the 'set quoted identifier on' statement to 'off' instead...all comes down to differences between these settings in the msdb, master, and your user database...|||I couldn't chg the flag. But did get the suggestion you sent to work. I removed the line returns at the end of each line and replaced them with just a space, so that the entries where all strung together when I edited the step. So that worked.

So thank you. Now I just have to learn how to keep them when the job is refreshed.

as you've probably guessed, I'm learning as I go.|||

I'm back! Thought I had this resolved, but am still having the same error. The bad thing is that it only occurs on some of the DBs in the same instance of SQL Server. I've checked the options on the DBs and they match between the ones that can be integrity checked and the ones that can not. The ones that can be i ckd will run w/o any of the overrides. For the ones that the job gets an error, I've tried quoted_identifier on and off, with the other options and w/o. All DBs have ANSI NULL default, Auto update statistics, torn page, auto create statistics and use quoted identifiers checked, others not. (sql 2000). Db compatibility level 80 is selected on the compatibility. Some Dbs are model simple, some are full. That doesn't seem to matter.

I'd appreciate any more ideas.........