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]
>
No comments:
Post a Comment