Maintenance Plan Failure

SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
I have two jobs, based on maintenance plans, that have been running fine for
over two years. One updates statistics for a database, and the other rebuild
s
indexes. Yesterday, they both started failing. The only info I can get is
from the Maintenance Plan History, both messages are similar:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options
have
incorrect settings: 'QUOTED_IDENTIFIER'.
and
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]UPDATE STATISTICS failed because the following
SET
options have incorrect settings: 'QUOTED_IDENTIFIER'.
quoted_identifier is set to 1, and has not been changed. Nothing has changed
at all with the database and server.
I created two new plans to duplicate the above, and each of them fails with
the same messages.
I have no clue as to why these all of a sudden started to fail, and any
assistance would be greatly appreciated.
TomTSorry for the double post, I got a message saying the post was unsuccessful,
and posted again (and got the same message, by the way)...
"TomT" wrote:

> SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
> I have two jobs, based on maintenance plans, that have been running fine f
or
> over two years. One updates statistics for a database, and the other rebui
lds
> indexes. Yesterday, they both started failing. The only info I can get is
> from the Maintenance Plan History, both messages are similar:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET option
s have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> and
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft]
[ODBC SQL
> Server Driver][SQL Server]UPDATE STATISTICS failed because the followi
ng SET
> options have incorrect settings: 'QUOTED_IDENTIFIER'.
> quoted_identifier is set to 1, and has not been changed. Nothing has chang
ed
> at all with the database and server.
> I created two new plans to duplicate the above, and each of them fails wit
h
> the same messages.
> I have no clue as to why these all of a sudden started to fail, and any
> assistance would be greatly appreciated.
> TomT|||Hi Tom,
That's OK, I am composing a reply to that thread
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Maintenance Plan Failure

I have a maintenance plan setup that among other tasks is supposed to backup
Transaction Logs every 3 hours and then delete Log files that are older than
2 days. However, this job keeps failing when it tries to delete the older
files. It makes the 3 hour backups ok, but then shows a failure for the
delete action inside Enterprise Manager > Server > Maintenance > Jobs. Any
idea what could be happening here? It used to work fine. The only error I
get is posted below (though probably not much help).
*************
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 12/17/2004
Time: 2:00:06 PM
User: N/A
Computer: SERVER
Description:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'Backup Maintenance Plan'' (0x205B61B1C1A7D54BA426DF0C810C8F05) - Status:
Failed - Invoked on: 2004-12-17 14:00:00 - Message: The job failed. The Job
was invoked by Schedule 43 (Schedule 1). The last step to run was step 1
(Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Brandon
IT Director
Presentations Direct - Office Equipment & Supplies
http://www.presentationsdirect.com
"Brandon S." wrote:
I don't know if this is what is causing your problem, but we had our backup
directory shared and that was enough to stop the deletes.
|||Thanks, but that's not the case here.
Brandon
IT Director
Presentations Direct - Office Equipment & Supplies
http://www.presentationsdirect.com
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4C8DBE2F-99D8-4FCD-85DB-13609E06EC84@.microsoft.com...
> "Brandon S." wrote:
> I don't know if this is what is causing your problem, but we had our
> backup
> directory shared and that was enough to stop the deletes.
|||It is usually due to some other process locking the file or dir such as a
tape device. But this blurb from Bill at MS does a pretty good job of
outlining the issues:
http://support.microsoft.com/default...;en-us;Q303292
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Andrew J. Kelly SQL MVP
"Brandon S." <bsmith@.presentationsdirect.nospam.com> wrote in message
news:uE0Ol3H5EHA.2804@.TK2MSFTNGP15.phx.gbl...
>I have a maintenance plan setup that among other tasks is supposed to
>backup Transaction Logs every 3 hours and then delete Log files that are
>older than 2 days. However, this job keeps failing when it tries to delete
>the older files. It makes the 3 hour backups ok, but then shows a failure
>for the delete action inside Enterprise Manager > Server > Maintenance >
>Jobs. Any idea what could be happening here? It used to work fine. The
>only error I get is posted below (though probably not much help).
> *************
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 12/17/2004
> Time: 2:00:06 PM
> User: N/A
> Computer: SERVER
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'Backup Maintenance Plan'' (0x205B61B1C1A7D54BA426DF0C810C8F05) -
> Status: Failed - Invoked on: 2004-12-17 14:00:00 - Message: The job
> failed. The Job was invoked by Schedule 43 (Schedule 1). The last step
> to run was step 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> --
> Brandon
> IT Director
> Presentations Direct - Office Equipment & Supplies
> http://www.presentationsdirect.com
>

Maintenance Plan Failure

SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
I have two jobs, based on maintenance plans, that have been running fine for
over two years. One updates statistics for a database, and the other rebuilds
indexes. Yesterday, they both started failing. The only info I can get is
from the Maintenance Plan History, both messages are similar:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER'.
and
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]UPDATE STATISTICS failed because the following SET
options have incorrect settings: 'QUOTED_IDENTIFIER'.
quoted_identifier is set to 1, and has not been changed. Nothing has changed
at all with the database and server.
I created two new plans to duplicate the above, and each of them fails with
the same messages.
I have no clue as to why these all of a sudden started to fail, and any
assistance would be greatly appreciated.
TomT
Sorry for the double post, I got a message saying the post was unsuccessful,
and posted again (and got the same message, by the way)...
"TomT" wrote:

> SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
> I have two jobs, based on maintenance plans, that have been running fine for
> over two years. One updates statistics for a database, and the other rebuilds
> indexes. Yesterday, they both started failing. The only info I can get is
> from the Maintenance Plan History, both messages are similar:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET options have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> and
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
> Server Driver][SQL Server]UPDATE STATISTICS failed because the following SET
> options have incorrect settings: 'QUOTED_IDENTIFIER'.
> quoted_identifier is set to 1, and has not been changed. Nothing has changed
> at all with the database and server.
> I created two new plans to duplicate the above, and each of them fails with
> the same messages.
> I have no clue as to why these all of a sudden started to fail, and any
> assistance would be greatly appreciated.
> TomT
|||Hi Tom,
That's OK, I am composing a reply to that thread
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
sql

Maintenance Plan Failure

I have a maintenance plan setup that among other tasks is supposed to backup
Transaction Logs every 3 hours and then delete Log files that are older than
2 days. However, this job keeps failing when it tries to delete the older
files. It makes the 3 hour backups ok, but then shows a failure for the
delete action inside Enterprise Manager > Server > Maintenance > Jobs. Any
idea what could be happening here? It used to work fine. The only error I
get is posted below (though probably not much help).
*************
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 12/17/2004
Time: 2:00:06 PM
User: N/A
Computer: SERVER
Description:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'Backup Maintenance Plan'' (0x205B61B1C1A7D54BA426DF0C810C8F05) - Status:
Failed - Invoked on: 2004-12-17 14:00:00 - Message: The job failed. The Job
was invoked by Schedule 43 (Schedule 1). The last step to run was step 1
(Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
Brandon
IT Director
Presentations Direct - Office Equipment & Supplies
http://www.presentationsdirect.com"Brandon S." wrote:
I don't know if this is what is causing your problem, but we had our backup
directory shared and that was enough to stop the deletes.|||Thanks, but that's not the case here.
--
Brandon
IT Director
Presentations Direct - Office Equipment & Supplies
http://www.presentationsdirect.com
"Maury Markowitz" <MauryMarkowitz@.discussions.microsoft.com> wrote in
message news:4C8DBE2F-99D8-4FCD-85DB-13609E06EC84@.microsoft.com...
> "Brandon S." wrote:
> I don't know if this is what is causing your problem, but we had our
> backup
> directory shared and that was enough to stop the deletes.|||It is usually due to some other process locking the file or dir such as a
tape device. But this blurb from Bill at MS does a pretty good job of
outlining the issues:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303292
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Andrew J. Kelly SQL MVP
"Brandon S." <bsmith@.presentationsdirect.nospam.com> wrote in message
news:uE0Ol3H5EHA.2804@.TK2MSFTNGP15.phx.gbl...
>I have a maintenance plan setup that among other tasks is supposed to
>backup Transaction Logs every 3 hours and then delete Log files that are
>older than 2 days. However, this job keeps failing when it tries to delete
>the older files. It makes the 3 hour backups ok, but then shows a failure
>for the delete action inside Enterprise Manager > Server > Maintenance >
>Jobs. Any idea what could be happening here? It used to work fine. The
>only error I get is posted below (though probably not much help).
> *************
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 12/17/2004
> Time: 2:00:06 PM
> User: N/A
> Computer: SERVER
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'Backup Maintenance Plan'' (0x205B61B1C1A7D54BA426DF0C810C8F05) -
> Status: Failed - Invoked on: 2004-12-17 14:00:00 - Message: The job
> failed. The Job was invoked by Schedule 43 (Schedule 1). The last step
> to run was step 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> --
> Brandon
> IT Director
> Presentations Direct - Office Equipment & Supplies
> http://www.presentationsdirect.com
>

Maintenance Plan Failure

SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
I have two jobs, based on maintenance plans, that have been running fine for
over two years. One updates statistics for a database, and the other rebuilds
indexes. Yesterday, they both started failing. The only info I can get is
from the Maintenance Plan History, both messages are similar:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]DBCC failed because the following SET options have
incorrect settings: 'QUOTED_IDENTIFIER'.
and
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
Server Driver][SQL Server]UPDATE STATISTICS failed because the following SET
options have incorrect settings: 'QUOTED_IDENTIFIER'.
quoted_identifier is set to 1, and has not been changed. Nothing has changed
at all with the database and server.
I created two new plans to duplicate the above, and each of them fails with
the same messages.
I have no clue as to why these all of a sudden started to fail, and any
assistance would be greatly appreciated.
TomTSorry for the double post, I got a message saying the post was unsuccessful,
and posted again (and got the same message, by the way)...
"TomT" wrote:
> SQL Server 2000 sp3a, running on Windows 2003 server, sp1.
> I have two jobs, based on maintenance plans, that have been running fine for
> over two years. One updates statistics for a database, and the other rebuilds
> indexes. Yesterday, they both started failing. The only info I can get is
> from the Maintenance Plan History, both messages are similar:
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
> Server Driver][SQL Server]DBCC failed because the following SET options have
> incorrect settings: 'QUOTED_IDENTIFIER'.
> and
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL
> Server Driver][SQL Server]UPDATE STATISTICS failed because the following SET
> options have incorrect settings: 'QUOTED_IDENTIFIER'.
> quoted_identifier is set to 1, and has not been changed. Nothing has changed
> at all with the database and server.
> I created two new plans to duplicate the above, and each of them fails with
> the same messages.
> I have no clue as to why these all of a sudden started to fail, and any
> assistance would be greatly appreciated.
> TomT|||Hi Tom,
That's OK, I am composing a reply to that thread :)
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Maintenance Plan email report failure

Hello,
I have a simple daily maintenance plan for backups.(check integrity, back up, clean up history and then report) However, sending the email report always fails with the following error:

"Could not generate mail report.An exception occurred while executing a Transact-SQL statement or batch.Incorrect syntax near 'sys'."

How can the wizard output Incorrect syntax?

I have set up and tested Database mail and set the default public profile.
I have enabled the mail profile in SQL server agent properties and then restarted SQL server agent.
I have set up operator to receive the mail.
The frustrating thing is that if I set up and schedule a really simple test maintenance plan, the email report works! But it always fails on the real one.
How can I get more detail in the error message and actually see the SQL it is trying to execute when it send the mail?

Thanks,
Adam

More detail.

Having done a few tests it seems that this mail report error only occurs after the check integrity job fails. eg.

Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error:

"Incorrect PFS free space information for page (1:278) in object ID 60, index ID 1, partition ID 281474980642816, alloc unit ID 71776119065149440 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'sys.sysobjvalues' (object ID 60).

CHECKDB found 0 allocation errors and 1 consistency errors in database 'RHJ'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (RHJ).".

Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

This failure does not affect the backup and maintenance cleanup tasks that run afterwards, only the email report that it tries to send at the end.

Maintenance Plan Creation Failure in Wizard

When trying to create a maintenance plan in MS SQL 2005 using the
wizard I get the following error
TITLE: Maintenance Plan Wizard Progress
--
Create maintenance plan failed.
ADDITIONAL INFORMATION:
Could not load type
'Microsoft.SqlServer.Management.Smo.Agent.JobBaseCollection' from
assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91'.
(Microsoft.SqlServer.MaintenancePlanTasks)
BUTTONS:
OK
--
This seems like something did not install correctly on my server or
something. Any ideas are greatly appreciated.I'm getting the following error when trying to modify an existing maintenanc
e
plan in SQL 2005:
Class not registered (Exception from HRESULT: 0x80040154
(REGDB_E_CLASSNOTREG)) (System.Windows.Forms)
at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid,
Object punkOuter, Int32 context, Guid& iid)
at System.Windows.Forms.AxHost.CreateWithoutLicense(Guid clsid)
at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid
clsid)
at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
at System.Windows.Forms.AxHost.CreateInstance()
at System.Windows.Forms.AxHost.GetOcxCreate()
at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
at System.Windows.Forms.AxHost.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at Microsoft.DataWarehouse.Design.ComponentDiagram.CreateDdsView(Control
parentControl)
at
Microsoft.DataTransformationServices.Design.DtsComponentDiagram.CreateDdsVie
w(Control parentControl)
at
Microsoft.DataWarehouse.Controls.DdsDiagramHostControl.set_ComponentDiagram(
ComponentDiagram value)
at
Microsoft.DataTransformationServices.Design.DbMaintSequenceDesigner.get_DbMa
intDiagramHost()
at
Microsoft.DataTransformationServices.Design.DbMaintSequenceDesigner.Microsof
t.DataTransformationServices.Design.IDbMaintSequenceDesigner.get_DiagramHost
()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.ge
t_SelectedSubPlanDesignerHost()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.Se
lectSubPlan()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.gr
id_SelectionChanged(Object sender, SelectionChangedEventArgs args)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl.OnSelectionChanged(BlockO
fCellsCollection selectedCells)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl.SelectedCellsInternal(Blo
ckOfCellsCollection col, Boolean bSet)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl.set_SelectedCells(BlockOf
CellsCollection value)
at
Microsoft.SqlServer.Management.UI.Grid.DlgGridControl.SetSelectedCellInt(Int
32 rowIndex, Int32 colIndex)
at
Microsoft.SqlServer.Management.UI.Grid.DlgGridControl.SetSelectedCell(Int32
rowIndex, Int32 colIndex)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.Po
pulateGrid()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.In
itialize(MaintenancePlanData planData)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintView.LoadMaintenan
cePlan(String connectionString, IManagedConnection connection, String object
Urn)
at
Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDe
signer(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.
Invoke()
"pyrahna" wrote:

> When trying to create a maintenance plan in MS SQL 2005 using the
> wizard I get the following error
> TITLE: Maintenance Plan Wizard Progress
> --
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Could not load type
> 'Microsoft.SqlServer.Management.Smo.Agent.JobBaseCollection' from
> assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral,
> PublicKeyToken=89845dcd8080cc91'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> --
> BUTTONS:
> OK
> --
> This seems like something did not install correctly on my server or
> something. Any ideas are greatly appreciated.
>

Maintenance Plan Creation Failure in Wizard

When trying to create a maintenance plan in MS SQL 2005 using the
wizard I get the following error
TITLE: Maintenance Plan Wizard Progress
Create maintenance plan failed.
ADDITIONAL INFORMATION:
Could not load type
'Microsoft.SqlServer.Management.Smo.Agent.JobBaseC ollection' from
assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91'.
(Microsoft.SqlServer.MaintenancePlanTasks)
BUTTONS:
OK
This seems like something did not install correctly on my server or
something. Any ideas are greatly appreciated.
I'm getting the following error when trying to modify an existing maintenance
plan in SQL 2005:
Class not registered (Exception from HRESULT: 0x80040154
(REGDB_E_CLASSNOTREG)) (System.Windows.Forms)
at System.Windows.Forms.UnsafeNativeMethods.CoCreateI nstance(Guid& clsid,
Object punkOuter, Int32 context, Guid& iid)
at System.Windows.Forms.AxHost.CreateWithoutLicense(G uid clsid)
at System.Windows.Forms.AxHost.CreateWithLicense(Stri ng license, Guid
clsid)
at System.Windows.Forms.AxHost.CreateInstanceCore(Gui d clsid)
at System.Windows.Forms.AxHost.CreateInstance()
at System.Windows.Forms.AxHost.GetOcxCreate()
at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
at System.Windows.Forms.AxHost.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at Microsoft.DataWarehouse.Design.ComponentDiagram.Cr eateDdsView(Control
parentControl)
at
Microsoft.DataTransformationServices.Design.DtsCom ponentDiagram.CreateDdsView(Control parentControl)
at
Microsoft.DataWarehouse.Controls.DdsDiagramHostCon trol.set_ComponentDiagram(ComponentDiagram value)
at
Microsoft.DataTransformationServices.Design.DbMain tSequenceDesigner.get_DbMaintDiagramHost()
at
Microsoft.DataTransformationServices.Design.DbMain tSequenceDesigner.Microsoft.DataTransformationServ ices.Design.IDbMaintSequenceDesigner.get_DiagramHo st()
at
Microsoft.SqlServer.Management.DatabaseMaintenance .DbMaintDiagramHostCtrl.get_SelectedSubPlanDesigne rHost()
at
Microsoft.SqlServer.Management.DatabaseMaintenance .DbMaintDiagramHostCtrl.SelectSubPlan()
at
Microsoft.SqlServer.Management.DatabaseMaintenance .DbMaintDiagramHostCtrl.grid_SelectionChanged(Obje ct sender, SelectionChangedEventArgs args)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl .OnSelectionChanged(BlockOfCellsCollection selectedCells)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl .SelectedCellsInternal(BlockOfCellsCollection col, Boolean bSet)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl .set_SelectedCells(BlockOfCellsCollection value)
at
Microsoft.SqlServer.Management.UI.Grid.DlgGridCont rol.SetSelectedCellInt(Int32 rowIndex, Int32 colIndex)
at
Microsoft.SqlServer.Management.UI.Grid.DlgGridCont rol.SetSelectedCell(Int32
rowIndex, Int32 colIndex)
at
Microsoft.SqlServer.Management.DatabaseMaintenance .DbMaintDiagramHostCtrl.PopulateGrid()
at
Microsoft.SqlServer.Management.DatabaseMaintenance .DbMaintDiagramHostCtrl.Initialize(MaintenancePlan Data planData)
at
Microsoft.SqlServer.Management.DatabaseMaintenance .DbMaintView.LoadMaintenancePlan(String connectionString, IManagedConnection connection, String objectUrn)
at
Microsoft.DataTransformationServices.VsIntegration .DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance .MaintDesignerMenuHandler.Invoke()
"pyrahna" wrote:

> When trying to create a maintenance plan in MS SQL 2005 using the
> wizard I get the following error
> TITLE: Maintenance Plan Wizard Progress
> --
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Could not load type
> 'Microsoft.SqlServer.Management.Smo.Agent.JobBaseC ollection' from
> assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral,
> PublicKeyToken=89845dcd8080cc91'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> --
> BUTTONS:
> OK
> --
> This seems like something did not install correctly on my server or
> something. Any ideas are greatly appreciated.
>

Maintenance Plan Creation Failure in Wizard

When trying to create a maintenance plan in MS SQL 2005 using the
wizard I get the following error
TITLE: Maintenance Plan Wizard Progress
--
Create maintenance plan failed.
--
ADDITIONAL INFORMATION:
Could not load type
'Microsoft.SqlServer.Management.Smo.Agent.JobBaseCollection' from
assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral,
PublicKeyToken=89845dcd8080cc91'.
(Microsoft.SqlServer.MaintenancePlanTasks)
--
BUTTONS:
OK
--
This seems like something did not install correctly on my server or
something. Any ideas are greatly appreciated.I'm getting the following error when trying to modify an existing maintenance
plan in SQL 2005:
Class not registered (Exception from HRESULT: 0x80040154
(REGDB_E_CLASSNOTREG)) (System.Windows.Forms)
at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid,
Object punkOuter, Int32 context, Guid& iid)
at System.Windows.Forms.AxHost.CreateWithoutLicense(Guid clsid)
at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid
clsid)
at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
at System.Windows.Forms.AxHost.CreateInstance()
at System.Windows.Forms.AxHost.GetOcxCreate()
at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
at System.Windows.Forms.AxHost.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at Microsoft.DataWarehouse.Design.ComponentDiagram.CreateDdsView(Control
parentControl)
at
Microsoft.DataTransformationServices.Design.DtsComponentDiagram.CreateDdsView(Control parentControl)
at
Microsoft.DataWarehouse.Controls.DdsDiagramHostControl.set_ComponentDiagram(ComponentDiagram value)
at
Microsoft.DataTransformationServices.Design.DbMaintSequenceDesigner.get_DbMaintDiagramHost()
at
Microsoft.DataTransformationServices.Design.DbMaintSequenceDesigner.Microsoft.DataTransformationServices.Design.IDbMaintSequenceDesigner.get_DiagramHost()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.get_SelectedSubPlanDesignerHost()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.SelectSubPlan()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.grid_SelectionChanged(Object sender, SelectionChangedEventArgs args)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl.OnSelectionChanged(BlockOfCellsCollection selectedCells)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl.SelectedCellsInternal(BlockOfCellsCollection col, Boolean bSet)
at
Microsoft.SqlServer.Management.UI.Grid.GridControl.set_SelectedCells(BlockOfCellsCollection value)
at
Microsoft.SqlServer.Management.UI.Grid.DlgGridControl.SetSelectedCellInt(Int32 rowIndex, Int32 colIndex)
at
Microsoft.SqlServer.Management.UI.Grid.DlgGridControl.SetSelectedCell(Int32
rowIndex, Int32 colIndex)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.PopulateGrid()
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintDiagramHostCtrl.Initialize(MaintenancePlanData planData)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.DbMaintView.LoadMaintenancePlan(String connectionString, IManagedConnection connection, String objectUrn)
at
Microsoft.DataTransformationServices.VsIntegration.DtsDesignerService.OpenDesigner(String connectionString, Object connection, String objectUrn)
at
Microsoft.SqlServer.Management.DatabaseMaintenance.MaintDesignerMenuHandler.Invoke()
"pyrahna" wrote:
> When trying to create a maintenance plan in MS SQL 2005 using the
> wizard I get the following error
> TITLE: Maintenance Plan Wizard Progress
> --
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Could not load type
> 'Microsoft.SqlServer.Management.Smo.Agent.JobBaseCollection' from
> assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral,
> PublicKeyToken=89845dcd8080cc91'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> --
> BUTTONS:
> OK
> --
> This seems like something did not install correctly on my server or
> something. Any ideas are greatly appreciated.
>sql

Maintenance Plan 2005 invalid argument

trying to create an mp and i can't get past this failure (regardless of
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!
can you list the repro steps here.
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegr oups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>
sql

Maintenance Plan 2005 invalid argument

trying to create an mp and i can't get past this failure (regardless of
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!can you list the repro steps here.
--
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegroups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>

Maintenance Plan 2005 invalid argument

trying to create an mp and i can't get past this failure (regardless of
which steps and databases i select):
"saving maintenance plan failed, one or more arguments are invalid."
the plans all show up under jobs and i'm not able to delete them.
nothing shows up in the logs and i couldn't find anything online about
this. any advice? tia!can you list the repro steps here.
-oj
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1143837952.390577.114240@.j33g2000cwa.googlegroups.com...
> trying to create an mp and i can't get past this failure (regardless of
> which steps and databases i select):
> "saving maintenance plan failed, one or more arguments are invalid."
>
> the plans all show up under jobs and i'm not able to delete them.
> nothing shows up in the logs and i couldn't find anything online about
> this. any advice? tia!
>

Maintenance Plan "fails"..

Thanks in advance for any insight.
On occasion, one of my schedule jobs will "fail", in that all tasks
complete, but it still reports failure. Strangely enough, nothing is written
to SQL Server log, but I do have the following entry in the Event Viewer:
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Non-Great
Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The Job
was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
(Step 1)."
Any ideas on how to troubleshoot this?
Thanks,
MorganAny messages in the report file? (Did you specify a report file, btw?)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...[
vbcol=seagreen]
> Thanks in advance for any insight.
> On occasion, one of my schedule jobs will "fail", in that all tasks
> complete, but it still reports failure. Strangely enough, nothing is writt
en
> to SQL Server log, but I do have the following entry in the Event Viewer:
> "SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Non-Grea
t
> Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
> Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The Jo
b
> was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
> (Step 1)."
> Any ideas on how to troubleshoot this?
>
> Thanks,
> Morgan
>[/vbcol]|||Hi Tibor,
The only thing in the report file is that it was unable to delete one of the
database backups. Other than that, all of the steps completed. Would that
cause the job to think it failed?
Thanks,
Morgan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> Any messages in the report file? (Did you specify a report file, btw?)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Morgan" <abcd@.senditon.com> wrote in message
news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
written[vbcol=seagreen]
Viewer:[vbcol=seagreen]
'Non-Great[vbcol=seagreen]
Job[vbcol=seagreen]
>|||If I wrote the code, yes a failed deletion of a backup file would cause the
job to fail.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...[
vbcol=seagreen]
> Hi Tibor,
> The only thing in the report file is that it was unable to delete one of t
he
> database backups. Other than that, all of the steps completed. Would that
> cause the job to think it failed?
> Thanks,
> Morgan
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> written
> Viewer:
> 'Non-Great
> Job
>[/vbcol]|||Ha! I hear ya. Would be nice if each piece of a maintenance plan could be a
seperate job, that way if deleting a previous days backup failed it wouldn't
look like the databases didn't get backed up since that would be a seperate
task with its own status.
Thanks,
Morgan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3i9JIvTEHA.644@.tk2msftngp13.phx.gbl...
> If I wrote the code, yes a failed deletion of a backup file would cause
the job to fail.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Morgan" <abcd@.senditon.com> wrote in message
news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...
the[vbcol=seagreen]
that[vbcol=seagreen]
in[vbcol=seagreen]
The[vbcol=seagreen]
step 1[vbcol=seagreen]
>|||A "hack" way is to create a script that does a "DIR" in the directory and de
lete old files. This can be done
using ActiveScript, TSQL of whatever is your preference...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:OPwIwByTEHA.3480@.TK2MSFTNGP11.phx.gbl...[
vbcol=seagreen]
> Ha! I hear ya. Would be nice if each piece of a maintenance plan could be
a
> seperate job, that way if deleting a previous days backup failed it wouldn
't
> look like the databases didn't get backed up since that would be a seperat
e
> task with its own status.
> Thanks,
> Morgan
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:e3i9JIvTEHA.644@.tk2msftngp13.phx.gbl...
> the job to fail.
> news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...
> the
> that
> in
> The
> step 1
>[/vbcol]

Maintenance Plan "fails"..

Thanks in advance for any insight.
On occasion, one of my schedule jobs will "fail", in that all tasks
complete, but it still reports failure. Strangely enough, nothing is written
to SQL Server log, but I do have the following entry in the Event Viewer:
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Non-Great
Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The Job
was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
(Step 1)."
Any ideas on how to troubleshoot this?
Thanks,
Morgan
Any messages in the report file? (Did you specify a report file, btw?)
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> Thanks in advance for any insight.
> On occasion, one of my schedule jobs will "fail", in that all tasks
> complete, but it still reports failure. Strangely enough, nothing is written
> to SQL Server log, but I do have the following entry in the Event Viewer:
> "SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Non-Great
> Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
> Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The Job
> was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
> (Step 1)."
> Any ideas on how to troubleshoot this?
>
> Thanks,
> Morgan
>
|||Hi Tibor,
The only thing in the report file is that it was unable to delete one of the
database backups. Other than that, all of the steps completed. Would that
cause the job to think it failed?
Thanks,
Morgan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> Any messages in the report file? (Did you specify a report file, btw?)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Morgan" <abcd@.senditon.com> wrote in message
news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
written[vbcol=seagreen]
Viewer:[vbcol=seagreen]
'Non-Great[vbcol=seagreen]
Job
>
|||If I wrote the code, yes a failed deletion of a backup file would cause the job to fail.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...
> Hi Tibor,
> The only thing in the report file is that it was unable to delete one of the
> database backups. Other than that, all of the steps completed. Would that
> cause the job to think it failed?
> Thanks,
> Morgan
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> written
> Viewer:
> 'Non-Great
> Job
>
|||Ha! I hear ya. Would be nice if each piece of a maintenance plan could be a
seperate job, that way if deleting a previous days backup failed it wouldn't
look like the databases didn't get backed up since that would be a seperate
task with its own status.
Thanks,
Morgan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3i9JIvTEHA.644@.tk2msftngp13.phx.gbl...
> If I wrote the code, yes a failed deletion of a backup file would cause
the job to fail.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Morgan" <abcd@.senditon.com> wrote in message
news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
the[vbcol=seagreen]
that[vbcol=seagreen]
in[vbcol=seagreen]
The[vbcol=seagreen]
step 1
>
|||A "hack" way is to create a script that does a "DIR" in the directory and delete old files. This can be done
using ActiveScript, TSQL of whatever is your preference...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:OPwIwByTEHA.3480@.TK2MSFTNGP11.phx.gbl...
> Ha! I hear ya. Would be nice if each piece of a maintenance plan could be a
> seperate job, that way if deleting a previous days backup failed it wouldn't
> look like the databases didn't get backed up since that would be a seperate
> task with its own status.
> Thanks,
> Morgan
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:e3i9JIvTEHA.644@.tk2msftngp13.phx.gbl...
> the job to fail.
> news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...
> the
> that
> in
> The
> step 1
>

Maintenance Plan "fails"..

Thanks in advance for any insight.
On occasion, one of my schedule jobs will "fail", in that all tasks
complete, but it still reports failure. Strangely enough, nothing is written
to SQL Server log, but I do have the following entry in the Event Viewer:
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Non-Great
Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The Job
was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
(Step 1)."
Any ideas on how to troubleshoot this?
Thanks,
MorganAny messages in the report file? (Did you specify a report file, btw?)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> Thanks in advance for any insight.
> On occasion, one of my schedule jobs will "fail", in that all tasks
> complete, but it still reports failure. Strangely enough, nothing is written
> to SQL Server log, but I do have the following entry in the Event Viewer:
> "SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Non-Great
> Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
> Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The Job
> was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
> (Step 1)."
> Any ideas on how to troubleshoot this?
>
> Thanks,
> Morgan
>|||Hi Tibor,
The only thing in the report file is that it was unable to delete one of the
database backups. Other than that, all of the steps completed. Would that
cause the job to think it failed?
Thanks,
Morgan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> Any messages in the report file? (Did you specify a report file, btw?)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Morgan" <abcd@.senditon.com> wrote in message
news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> > Thanks in advance for any insight.
> >
> > On occasion, one of my schedule jobs will "fail", in that all tasks
> > complete, but it still reports failure. Strangely enough, nothing is
written
> > to SQL Server log, but I do have the following entry in the Event
Viewer:
> > "SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
'Non-Great
> > Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
> > Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The
Job
> > was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
> > (Step 1)."
> >
> > Any ideas on how to troubleshoot this?
> >
> >
> > Thanks,
> >
> > Morgan
> >
> >
>|||If I wrote the code, yes a failed deletion of a backup file would cause the job to fail.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...
> Hi Tibor,
> The only thing in the report file is that it was unable to delete one of the
> database backups. Other than that, all of the steps completed. Would that
> cause the job to think it failed?
> Thanks,
> Morgan
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> > Any messages in the report file? (Did you specify a report file, btw?)
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Morgan" <abcd@.senditon.com> wrote in message
> news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> > > Thanks in advance for any insight.
> > >
> > > On occasion, one of my schedule jobs will "fail", in that all tasks
> > > complete, but it still reports failure. Strangely enough, nothing is
> written
> > > to SQL Server log, but I do have the following entry in the Event
> Viewer:
> > > "SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
> 'Non-Great
> > > Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
> > > Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed. The
> Job
> > > was invoked by Schedule 35 (Schedule 1). The last step to run was step 1
> > > (Step 1)."
> > >
> > > Any ideas on how to troubleshoot this?
> > >
> > >
> > > Thanks,
> > >
> > > Morgan
> > >
> > >
> >
> >
>|||Ha! I hear ya. Would be nice if each piece of a maintenance plan could be a
seperate job, that way if deleting a previous days backup failed it wouldn't
look like the databases didn't get backed up since that would be a seperate
task with its own status.
Thanks,
Morgan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3i9JIvTEHA.644@.tk2msftngp13.phx.gbl...
> If I wrote the code, yes a failed deletion of a backup file would cause
the job to fail.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Morgan" <abcd@.senditon.com> wrote in message
news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...
> > Hi Tibor,
> >
> > The only thing in the report file is that it was unable to delete one of
the
> > database backups. Other than that, all of the steps completed. Would
that
> > cause the job to think it failed?
> >
> > Thanks,
> >
> > Morgan
> >
> >
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in
> > message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> > > Any messages in the report file? (Did you specify a report file, btw?)
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "Morgan" <abcd@.senditon.com> wrote in message
> > news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> > > > Thanks in advance for any insight.
> > > >
> > > > On occasion, one of my schedule jobs will "fail", in that all tasks
> > > > complete, but it still reports failure. Strangely enough, nothing is
> > written
> > > > to SQL Server log, but I do have the following entry in the Event
> > Viewer:
> > > > "SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
> > 'Non-Great
> > > > Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
> > > > Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed.
The
> > Job
> > > > was invoked by Schedule 35 (Schedule 1). The last step to run was
step 1
> > > > (Step 1)."
> > > >
> > > > Any ideas on how to troubleshoot this?
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Morgan
> > > >
> > > >
> > >
> > >
> >
> >
>|||A "hack" way is to create a script that does a "DIR" in the directory and delete old files. This can be done
using ActiveScript, TSQL of whatever is your preference...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Morgan" <abcd@.senditon.com> wrote in message news:OPwIwByTEHA.3480@.TK2MSFTNGP11.phx.gbl...
> Ha! I hear ya. Would be nice if each piece of a maintenance plan could be a
> seperate job, that way if deleting a previous days backup failed it wouldn't
> look like the databases didn't get backed up since that would be a seperate
> task with its own status.
> Thanks,
> Morgan
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:e3i9JIvTEHA.644@.tk2msftngp13.phx.gbl...
> > If I wrote the code, yes a failed deletion of a backup file would cause
> the job to fail.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Morgan" <abcd@.senditon.com> wrote in message
> news:eVp7v$uTEHA.3988@.tk2msftngp13.phx.gbl...
> > > Hi Tibor,
> > >
> > > The only thing in the report file is that it was unable to delete one of
> the
> > > database backups. Other than that, all of the steps completed. Would
> that
> > > cause the job to think it failed?
> > >
> > > Thanks,
> > >
> > > Morgan
> > >
> > >
> > > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in
> > > message news:ubeNMltTEHA.2544@.TK2MSFTNGP10.phx.gbl...
> > > > Any messages in the report file? (Did you specify a report file, btw?)
> > > >
> > > > --
> > > > Tibor Karaszi, SQL Server MVP
> > > > http://www.karaszi.com/sqlserver/default.asp
> > > > http://www.solidqualitylearning.com/
> > > >
> > > >
> > > > "Morgan" <abcd@.senditon.com> wrote in message
> > > news:eiY8NRjTEHA.1284@.TK2MSFTNGP10.phx.gbl...
> > > > > Thanks in advance for any insight.
> > > > >
> > > > > On occasion, one of my schedule jobs will "fail", in that all tasks
> > > > > complete, but it still reports failure. Strangely enough, nothing is
> > > written
> > > > > to SQL Server log, but I do have the following entry in the Event
> > > Viewer:
> > > > > "SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
> > > 'Non-Great
> > > > > Plains Daily Backup'' (0x01BF5D1C32E9FF418D67E99A77A4A014) - Status:
> > > > > Failed - Invoked on: 2004-06-08 20:00:00 - Message: The job failed.
> The
> > > Job
> > > > > was invoked by Schedule 35 (Schedule 1). The last step to run was
> step 1
> > > > > (Step 1)."
> > > > >
> > > > > Any ideas on how to troubleshoot this?
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Morgan
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

Maintenance Job failure

I'm getting the following error when my database is
integrity checked. Error 5070: Database state cannot be
changed while other users are using database.
Is there anyway to tell who or what is using the database?Yes, you can run sp_who to see who is in the database currently.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx
.gbl...
I'm getting the following error when my database is
integrity checked. Error 5070: Database state cannot be
changed while other users are using database.
Is there anyway to tell who or what is using the database?|||Run sp_who2 from within Query Analyzer, to see who are accessing the
database you are checking.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx
.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?|||You should not run the automatic repair option as part of checking
consistency (this option has been removed in SQL Server 2005). Firstly it
requires changing the database state to single_user mode and secondly you
should always do root cause analysis of any inconsistencies.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx
.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?

Maintenance Job failure

I'm getting the following error when my database is
integrity checked. Error 5070: Database state cannot be
changed while other users are using database.
Is there anyway to tell who or what is using the database?
Yes, you can run sp_who to see who is in the database currently.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
I'm getting the following error when my database is
integrity checked. Error 5070: Database state cannot be
changed while other users are using database.
Is there anyway to tell who or what is using the database?
|||Yes, you can run sp_who to see who is in the database currently.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
I'm getting the following error when my database is
integrity checked. Error 5070: Database state cannot be
changed while other users are using database.
Is there anyway to tell who or what is using the database?
|||Run sp_who2 from within Query Analyzer, to see who are accessing the
database you are checking.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?
|||Run sp_who2 from within Query Analyzer, to see who are accessing the
database you are checking.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?
|||You should not run the automatic repair option as part of checking
consistency (this option has been removed in SQL Server 2005). Firstly it
requires changing the database state to single_user mode and secondly you
should always do root cause analysis of any inconsistencies.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?
|||You should not run the automatic repair option as part of checking
consistency (this option has been removed in SQL Server 2005). Firstly it
requires changing the database state to single_user mode and secondly you
should always do root cause analysis of any inconsistencies.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?
sql

Maintenance Job failure

I'm getting the following error when my database is
integrity checked. Error 5070: Database state cannot be
changed while other users are using database.
Is there anyway to tell who or what is using the database?Yes, you can run sp_who to see who is in the database currently.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
I'm getting the following error when my database is
integrity checked. Error 5070: Database state cannot be
changed while other users are using database.
Is there anyway to tell who or what is using the database?|||Run sp_who2 from within Query Analyzer, to see who are accessing the
database you are checking.
Peter Yeoh
http://www.yohz.com
Need smaller SQL2K backups? Try MiniSQLBackup
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?|||You should not run the automatic repair option as part of checking
consistency (this option has been removed in SQL Server 2005). Firstly it
requires changing the database state to single_user mode and secondly you
should always do root cause analysis of any inconsistencies.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patty" <anonymous@.discussions.microsoft.com> wrote in message
news:223c001c45d25$a6206310$a301280a@.phx.gbl...
> I'm getting the following error when my database is
> integrity checked. Error 5070: Database state cannot be
> changed while other users are using database.
> Is there anyway to tell who or what is using the database?

Maintenance - Integrity Check failure

Found log for job:
'Error: 4062, Cannot open user default database '<ID>'.
Using master db instead.'
Will check Microsoft Error list.

>--Original Message--
>I've got a database in SQL Server 7/Windows 2000 that is
>maintained through 'Database Maintenance Plans'.
>Integrity of the database is checked once a week
>using 'Integrity Check'. The weekly 'Integrity Check'
is
>failing. The error message given is 'The job has failed
>in step one, please review step 1' and nothing is put
>into the application event log. The transaction sql
>command for checking the integrity check of a database
is
>DBCC Checkdb('database'). The command line integrity
>check works fine and returns no errors.
>Failures are also occuring for 'Update Statistics used
by
>query optimizer' and 'Reorganize data and index pages'
in
>Maintenance.
>What is causing these maintenance plans to fail?
>.
>If you get this when SQL Agent logs in to run a job then
most likely the default database for the SQL Agent service
account is assigned to a database that no longer exists on
the server. You may want to check the default database for
that account. You'd probably want it set to master.
-Sue
On Wed, 7 Apr 2004 14:24:33 -0700, "Jim"
<anonymous@.discussions.microsoft.com> wrote:
>Found log for job:
>'Error: 4062, Cannot open user default database '<ID>'.
>Using master db instead.'
>Will check Microsoft Error list.
>
>is
>is
>by
>in|||You should also not automatically repair errors. You shoudl always do
root-cause analysis as these errors are usually an indication that you have
a hardware problem.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:73ma70t1m49tgqnqmk0ccuiopd3qd4n4rj@.
4ax.com...
> If you get this when SQL Agent logs in to run a job then
> most likely the default database for the SQL Agent service
> account is assigned to a database that no longer exists on
> the server. You may want to check the default database for
> that account. You'd probably want it set to master.
> -Sue
> On Wed, 7 Apr 2004 14:24:33 -0700, "Jim"
> <anonymous@.discussions.microsoft.com> wrote:
>
>

Maintenance - Integrity Check failure

Found log for job:
'Error: 4062, Cannot open user default database '<ID>'.
Using master db instead.'
Will check Microsoft Error list.

>--Original Message--
>I've got a database in SQL Server 7/Windows 2000 that is
>maintained through 'Database Maintenance Plans'.
>Integrity of the database is checked once a week
>using 'Integrity Check'. The weekly 'Integrity Check'
is
>failing. The error message given is 'The job has failed
>in step one, please review step 1' and nothing is put
>into the application event log. The transaction sql
>command for checking the integrity check of a database
is
>DBCC Checkdb('database'). The command line integrity
>check works fine and returns no errors.
>Failures are also occuring for 'Update Statistics used
by
>query optimizer' and 'Reorganize data and index pages'
in
>Maintenance.
>What is causing these maintenance plans to fail?
>.
>
If you get this when SQL Agent logs in to run a job then
most likely the default database for the SQL Agent service
account is assigned to a database that no longer exists on
the server. You may want to check the default database for
that account. You'd probably want it set to master.
-Sue
On Wed, 7 Apr 2004 14:24:33 -0700, "Jim"
<anonymous@.discussions.microsoft.com> wrote:
>Found log for job:
>'Error: 4062, Cannot open user default database '<ID>'.
>Using master db instead.'
>Will check Microsoft Error list.
>
>is
>is
>by
>in
|||You should also not automatically repair errors. You shoudl always do
root-cause analysis as these errors are usually an indication that you have
a hardware problem.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:73ma70t1m49tgqnqmk0ccuiopd3qd4n4rj@.4ax.com...
> If you get this when SQL Agent logs in to run a job then
> most likely the default database for the SQL Agent service
> account is assigned to a database that no longer exists on
> the server. You may want to check the default database for
> that account. You'd probably want it set to master.
> -Sue
> On Wed, 7 Apr 2004 14:24:33 -0700, "Jim"
> <anonymous@.discussions.microsoft.com> wrote:
>