Counter settings: maintenance

Showing posts with label maintenance. Show all posts

Thursday, March 22, 2012

couldn't rename or delete maintenance plan in Management Studio

Hi,
I tried to rename and delete one old maintenance plan which is created by
other DBA and before the machine was renamed. But, I kept getting the
following error. I can rename and delete the maintenance plan I created.
An error has occurred while establishing a connection to the server. When
connecting to SQL server 2005, this failure may be cuased by the fact that
under the default settinfs SQL server does not allow remote connections
(provider: Named Pipes providers, error: 40 - could not open a connection to
SQL server) (Microsoft SQL server, Error: 53)
Shared Memory, TCP and Named Piples are all enabled.
Please advise.
Best Regards,
Lynn
I think the problem is that the maintenance plan use the Local Server
Connection which still point to the old machine name. (I couldn't move this
connection or modify the server name for this connection at all). I add
another connection, but I still couldn't delete this maintenance plan.
Please advise.
Best Regards,
Lynn
"Lynn" wrote:

> Hi,
> I tried to rename and delete one old maintenance plan which is created by
> other DBA and before the machine was renamed. But, I kept getting the
> following error. I can rename and delete the maintenance plan I created.
> An error has occurred while establishing a connection to the server. When
> connecting to SQL server 2005, this failure may be cuased by the fact that
> under the default settinfs SQL server does not allow remote connections
> (provider: Named Pipes providers, error: 40 - could not open a connection to
> SQL server) (Microsoft SQL server, Error: 53)
> Shared Memory, TCP and Named Piples are all enabled.
> Please advise.
> --
> Best Regards,
> Lynn
|||I've been pounding my head with a similar problem. A Server was renamed and
now I can't do anything with the plan.
Any more thoughts?
"Lynn" wrote:
[vbcol=seagreen]
> I think the problem is that the maintenance plan use the Local Server
> Connection which still point to the old machine name. (I couldn't move this
> connection or modify the server name for this connection at all). I add
> another connection, but I still couldn't delete this maintenance plan.
> Please advise.
> --
> Best Regards,
> Lynn
>
> "Lynn" wrote:

Monday, March 19, 2012

Could not locate file 'data01_log' in sysfiles

I need to shrink this log file, and setup some maintenance tasks, but I am
getting the above error. Any advice is greatly appreciated.
sp_helpdb output:
DATA01
1 e:\mssql\data\data01.mdf
PRIMARY 4102976 KB Unlimited 10% data only
DATA01_log
2 c:\logfiles\data01_log.ldf
NULL 327296 KB 460800 KB 10% log only
When I run shrinkfile I get this:
dbcc shrinkfile (data01_log,320)
Server: Msg 8985, Level 16, State 1, Line 1
Could not locate file 'data01_log' in sysfiles.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.Hi
If you do a SELECT * from sysfiles , what is the NAME returned ?
Are you then using the exact - case sensitive spelling?
Jack Vamvas
__________________________________________________________________
Receive free SQL tips - register at www.ciquery.com/sqlserver.htm
SQL Server Performance Audit - check www.ciquery.com/sqlserver_audit.htm
New article by Jack Vamvas - SQL and Markov Chains -
www.ciquery.com/articles/art_04.asp
"Rick Billingsley" <RickBillingsley@.discussions.microsoft.com> wrote in
message news:35983A24-DD51-43EA-A644-BA857A76F29B@.microsoft.com...
> I need to shrink this log file, and setup some maintenance tasks, but I am
> getting the above error. Any advice is greatly appreciated.
> sp_helpdb output:
> DATA01
> 1 e:\mssql\data\data01.mdf
>
> PRIMARY 4102976 KB Unlimited 10% data only
> DATA01_log
> 2
c:\logfiles\data01_log.ldf
>
> NULL 327296 KB 460800 KB 10% log only
> When I run shrinkfile I get this:
> dbcc shrinkfile (data01_log,320)
> Server: Msg 8985, Level 16, State 1, Line 1
> Could not locate file 'data01_log' in sysfiles.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>|||the select query returns the mastlog. This is not the log I am trying to
shrink/backup.
I believe the problem is that the log I want is on a different logical drive
(c vs. e) than the database.
I have tried running the shrinkfile with the exact case-sensitive spelling
with the same results.|||Change your database context to Data01. The select statement
indicates that you are trying to do this from the master
database. Shrinkfile applies to files in the current
database so you need to be in the appropriate database.
-Sue
On Mon, 23 Jan 2006 08:58:03 -0800, "Rick Billingsley"
<RickBillingsley@.discussions.microsoft.com> wrote:
>the select query returns the mastlog. This is not the log I am trying to
>shrink/backup.
>I believe the problem is that the log I want is on a different logical drive
>(c vs. e) than the database.
>I have tried running the shrinkfile with the exact case-sensitive spelling
>with the same results.

Saturday, February 25, 2012

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

On my local workstation I have performed a full installation of the client tool with SP 1. The Server is an SQL 2005 Cluster with SP1.
If I try to create a Maintenance Plan on an SQL Server without SP 1 it works.

What is the problem?

Thanks,
Markus

It seems like that should work. Please file a defect report for this on http://connect.microsoft.com/SQLServer. Issues reported on the connect site go directly into our internal issue tracking system. Be sure to describe how the cluster is configured, whether SSIS is installed on each node, etc.

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Maintenance plans rely on the SSIS runtime. If it is not present, the maintenance plan will not run. For the release version of SQL Server 2005, and for SP1, the SSIS runtime is included in the Tools install and in the SSIS install. This means that if your target server has only a relational engine install, a maintenance plan can not be expected to run.

Both of you assert that this problem commenced with SP1, so I don't expect that this is the problem, but I have to rule it out. Is it possible that the target server lacks a tools install and an SSIS install?

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

In SP2, the SSIS dependencies are included in the relational engine install. This should prevent this sort of thing from happening in the future. If you get a chance to try out CTP2 (expected very shortly), I would be happy to learn whether it resolves these issues.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

The information in this thread is a bit misleading...I am getting this error on the local, default instance, and have the client tools installed. SSIS, therefore, was obviously installed as well. Perhaps the runtime that comes with SP1 is defective?|||

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

1) Could not create jobs (error as above post)
2) Was able to design a maintenance plan (without ssis!) but when trying to save get error :
"Create failed for 'Job Maintenance Plan'"
(After closing maintenance plan designer, plan and job are still visible in Mgmt Studio, job contains no steps.
reopening maintenance plan and trying to save again results in "GUID should contian 32 digits with 4 dashes (xxx...)"

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

We are expecting SP2 very shortly. It will include lots of maintenance plan fixes and improvements. If possible, please install it when it comes out and see if your problems aren't resolved, and get back to us.

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

SP2 will ship very shortly. Any fixes we provide today are implemented in the sp2 code base. The first step of any investigation now is to install sp2 and see if the problem is resolved. Because we won't continue to hotfix sp1 after sp2 ships, efforts spent investigating sp1 faults are unproductive.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

What is the problem?

Thanks,
Markus

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

What is the problem?

Thanks,
Markus

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

What is the problem?

Thanks,
Markus

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

What is the problem?

Thanks,
Markus

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Could not create Maintenance Plan

Hello,

if I try to create a Maintenance Plan from my local workstation I get the following Error Message:

TITLE: Microsoft SQL Server Management Studio

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

What is the problem?

Thanks,
Markus

Thanks,
Steve

|||

Hello Markus,

this is happening to me after installing SQL2005 SP1. have you found a resolution?

SQL 2005 standard on x64...

Thanks, -justin

|||

As suggested above, more detail will be helpful to address this problem.

Given that SSIS appears on the target machine, make sure that sp1 was actually applied to all the 2005 components, viz. the engine, the tools, and/or the SSIS install.

If you have a cluster, know that SSIS is not cluster aware, and should be installed and serviced on each node.

|||Hey, if it makes you feel any better, I'm getting the same error.

I'm using SQL Server 2005 x64, and recently installed SP1.

James,

I do not agree. On x32 cluster inst. it was not necessery to install ssis to have maintenance plans (and sql agent jobs) running.

I just installed sql 2005 x64 enterprise + SP1 on a win2003 x64 r2 (non cluster) machine.

Problems:

1) Could not create mainenace plans as explained by threadopener

2) Could not create new jobs, getting:

Unable to cast object of type 'Microsoft.SqlServer.Management.Smo.SimpleObjectKey' to type 'Microsoft.SqlServer.Management.Smo.Agent.JobObjectKey'. (Microsoft.SqlServer.Smo)

Please advice !

TIA

acki

|||

Another little add on comment.

Reinstalled sql 2005 x64 ent. db server + client tools left all setting to default exept install directory.
(did not added sp1)

Problems:

Any help is highly appreciated !

acki

|||

I'm having the same issue. Have any of you resolved it?

Running Windows Server 2003 R2 x64 with x64 SQL 2005.

Todd

|||

I'm having the same problem here, too! SQL Server 2005 Standard x64 SP1.

Has anyone solved this? It's a big problem!

-md

|||

Todd

As referred above I believe x64 systems are affected with this bug, report/search it on the above Microsft COnnect link for more information.

|||

I am also getting the same error. Sounds like a hot fix will be in order.

Did everyone else install the recent hotfixes as well?

|||

Thanks,

jkh

|||

So if I am understanding correctly, this issue/error is a bug in the 64bit clustered version of SQL 2005 and the advice is wait for SP2 and hope it gets fixed? That’s not a very helpful solution...

|||

Let me see if I can clarify this a little.

We took fixes in sp2 to address this issue, and have not seen it reoccur in SP2 testing. We have every expectation that the problem is fixed.

Thanks,

jkh

|||Im not sure... fy im not running 64bit.. 32bit.

Friday, February 17, 2012

corruption of database maintenance wizard

when I try to add a job I am unable to use the wizard
the screen that holds the settings is corrupted
I can no longer define how many backups have to stay in the folder
(disk backup)
I can set the number but the listbox after that stays empty so I can
not set "hours" or "days"
the job itself doesn't work neither
the existing jobs keep happening but are no longer visible in the
enterprise manager
can I solve this some way?
maybe with queries?
I did try to use the "new" sql 2005 console for my 2k servers
could this be related?
thnxSQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
may have to redo them using 2000 EM since there is no telling what might
have changed.
--
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.3b897d6207852634.36062@.yahoo.com...
> when I try to add a job I am unable to use the wizard
> the screen that holds the settings is corrupted
> I can no longer define how many backups have to stay in the folder (disk
> backup)
> I can set the number but the listbox after that stays empty so I can not
> set "hours" or "days"
> the job itself doesn't work neither
> the existing jobs keep happening but are no longer visible in the
> enterprise manager
> can I solve this some way?
> maybe with queries?
> I did try to use the "new" sql 2005 console for my 2k servers
> could this be related?
> thnx
>|||> SQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
> what they can do etc. The 2005 tool is not meant to edit 2000 plans. You
> may have to redo them using 2000 EM since there is no telling what might have
> changed.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.3b897d6207852634.36062@.yahoo.com...
>> when I try to add a job I am unable to use the wizard
>> the screen that holds the settings is corrupted
>> I can no longer define how many backups have to stay in the folder (disk
>> backup)
>> I can set the number but the listbox after that stays empty so I can not
>> set "hours" or "days"
>> the job itself doesn't work neither
>> the existing jobs keep happening but are no longer visible in the
>> enterprise manager
>> can I solve this some way?
>> maybe with queries?
>> I did try to use the "new" sql 2005 console for my 2k servers
>> could this be related?
>> thnx
>>
I didn't try to change anything using the 2k5 VS tool
but I can't change it using the 2k enterprise manager anymore
since the wizard got corrupted somehow
I am not sure if it is related
my question is how to repair it without interrupting the server
functionality (too much)
grtz|||Since I have no way to know what is corrupted all I can say is to delete any
that you suspect are corrupt and rebuild them.
--
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.42317d62800a030b.36062@.yahoo.com...
>> SQL2000 Maintenance plans are treated as legacy in SQL2005 and limited in
>> what they can do etc. The 2005 tool is not meant to edit 2000 plans.
>> You may have to redo them using 2000 EM since there is no telling what
>> might have changed.
>> --
>> Andrew J. Kelly SQL MVP
>> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
>> news:mn.3b897d6207852634.36062@.yahoo.com...
>> when I try to add a job I am unable to use the wizard
>> the screen that holds the settings is corrupted
>> I can no longer define how many backups have to stay in the folder (disk
>> backup)
>> I can set the number but the listbox after that stays empty so I can not
>> set "hours" or "days"
>> the job itself doesn't work neither
>> the existing jobs keep happening but are no longer visible in the
>> enterprise manager
>> can I solve this some way?
>> maybe with queries?
>> I did try to use the "new" sql 2005 console for my 2k servers
>> could this be related?
>> thnx
>>
> I didn't try to change anything using the 2k5 VS tool
> but I can't change it using the 2k enterprise manager anymore
> since the wizard got corrupted somehow
> I am not sure if it is related
> my question is how to repair it without interrupting the server
> functionality (too much)
> grtz
>|||> Since I have no way to know what is corrupted all I can say is to delete any
> that you suspect are corrupt and rebuild them.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.42317d62800a030b.36062@.yahoo.com...
>>
>> I didn't try to change anything using the 2k5 VS tool
>> but I can't change it using the 2k enterprise manager anymore
>> since the wizard got corrupted somehow
>> I am not sure if it is related
>> my question is how to repair it without interrupting the server
>> functionality (too much)
>> grtz
>>
I'd like to but I can't
the interface doesn't show me any jobs
but they do still work
I just cannot add any new ones because the wizard is broken somehow
grtz|||You should still be able to create a new maintenance plan and add what ever
you want there. They don't have to all be in the same plan.
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.521c7d6216230948.36062@.yahoo.com...
>> Since I have no way to know what is corrupted all I can say is to delete
>> any that you suspect are corrupt and rebuild them.
>> --
>> Andrew J. Kelly SQL MVP
>> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
>> news:mn.42317d62800a030b.36062@.yahoo.com...
>>
>> I didn't try to change anything using the 2k5 VS tool
>> but I can't change it using the 2k enterprise manager anymore
>> since the wizard got corrupted somehow
>> I am not sure if it is related
>> my question is how to repair it without interrupting the server
>> functionality (too much)
>> grtz
>>
> I'd like to but I can't
> the interface doesn't show me any jobs
> but they do still work
> I just cannot add any new ones because the wizard is broken somehow
> grtz
>|||> You should still be able to create a new maintenance plan and add what ever
> you want there. They don't have to all be in the same plan.
> --
> Andrew J. Kelly SQL MVP
> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
> news:mn.521c7d6216230948.36062@.yahoo.com...
>>
>> I'd like to but I can't
>> the interface doesn't show me any jobs
>> but they do still work
>> I just cannot add any new ones because the wizard is broken somehow
>> grtz
>>
no I cannot,
for some reason the wizard doesn't allow me to set a value for how many
files I'd like to keep in the backup folder
I can set a number but not the type of value after that
I already tried to add a new job anyway but it keeps failing
since I have no idea how to fix the wizard I thought I'd give the
experts a try to tell me why,how and where the wizard might fail
and how to repair it's behaviour
perhaps thru sql?
grtz|||Without seeing what you have I really have no idea how to fix it. I rarely
advocate using the maintenance plan wizard at all for so many reasons, this
being just one. Anything you can do with he wizard can be done fairly
easily with simple tsql commands and a normal scheduled job. But you can use
the same utility that the wizard uses to execute these tasks and you don't
need to use the gui to do it. Create a new scheduled job and call the
sqlmaint utility with the appropriate parameters to do what you want done.
See "sqlmaint utility" in BooksOnLine for the details.
--
Andrew J. Kelly SQL MVP
"chriske911" <chriske911nospam@.yahoo.com> wrote in message
news:mn.53927d6233044d14.36062@.yahoo.com...
>> You should still be able to create a new maintenance plan and add what
>> ever you want there. They don't have to all be in the same plan.
>> --
>> Andrew J. Kelly SQL MVP
>> "chriske911" <chriske911nospam@.yahoo.com> wrote in message
>> news:mn.521c7d6216230948.36062@.yahoo.com...
>>
>> I'd like to but I can't
>> the interface doesn't show me any jobs
>> but they do still work
>> I just cannot add any new ones because the wizard is broken somehow
>> grtz
>>
> no I cannot,
> for some reason the wizard doesn't allow me to set a value for how many
> files I'd like to keep in the backup folder
> I can set a number but not the type of value after that
> I already tried to add a new job anyway but it keeps failing
> since I have no idea how to fix the wizard I thought I'd give the experts
> a try to tell me why,how and where the wizard might fail
> and how to repair it's behaviour
> perhaps thru sql?
> grtz
>

Thursday, March 22, 2012

couldn't rename or delete maintenance plan in Management Studio

Monday, March 19, 2012

Could not locate file 'data01_log' in sysfiles

Saturday, February 25, 2012

Could not create Maintenance Plan

Could not create Maintenance Plan

Could not create Maintenance Plan

Could not create Maintenance Plan

Could not create Maintenance Plan

Could not create Maintenance Plan

Friday, February 17, 2012

corruption of database maintenance wizard

corruption of database maintenance wizard

corruption of database maintenance wizard

Counter settings

Blog Archive

About Me