can't find maintenance plan wizard in MSS2005

Hello,
I use sql server 2005 standard edition, sp1 installed on win2003server.
I can't find the maintenance plan wizard in the object explorer in the
management-studio.
In documentation I found out, that the user connection must be done via
windows authentication and you have to
be a role-member of sysadmin (what does this mean exactly?).
Furthermore databases must have a compatibility of 80 (MSS2000) or
higher.
I met all conditions, but I still can't use the wizard.
Any ideas how to make the wizard 'visible' or is there a command line
statement to call it?
Thanks for any help!In SSMS open Management and right click on Maintenance Plans. The
second options is the manitenance plan wizard.
Markus|||MarkusB wrote:
> In SSMS open Management and right click on Maintenance Plans. The
> second options is the manitenance plan wizard.
> Markus
Already the item 'Maintenance Plans' under Management is missing !!!
Only under the subitem Legacy there is a item 'Database Maintenance
Plans'.
But rightclicking there doesn't show the wizard-item.
anymore ideas?|||keltchen wrote on 7 Aug 2006 03:58:42 -0700:

> MarkusB wrote:
> Already the item 'Maintenance Plans' under Management is missing !!!
> Only under the subitem Legacy there is a item 'Database Maintenance
> Plans'.
> But rightclicking there doesn't show the wizard-item.
> anymore ideas?
You did what I did - didn't install SQL Server Integration Services. The
Maintenance Plan Wizard (and the interface to plans from SMSS) is part of
SSIS. Install SSIS from the SQL Server CD and you should get it working.
Dan

can't find maintenance plan wizard in MSS2005

Hello,
I use sql server 2005 standard edition, sp1 installed on win2003server.
I can't find the maintenance plan wizard in the object explorer in the
management-studio.
In documentation I found out, that the user connection must be done via
windows authentication and you have to
be a role-member of sysadmin (what does this mean exactly?).
Furthermore databases must have a compatibility of 80 (MSS2000) or
higher.
I met all conditions, but I still can't use the wizard.
Any ideas how to make the wizard 'visible' or is there a command line
statement to call it?
Thanks for any help!In SSMS open Management and right click on Maintenance Plans. The
second options is the manitenance plan wizard.
Markus|||MarkusB wrote:
> In SSMS open Management and right click on Maintenance Plans. The
> second options is the manitenance plan wizard.
> Markus
Already the item 'Maintenance Plans' under Management is missing !!!
Only under the subitem Legacy there is a item 'Database Maintenance
Plans'.
But rightclicking there doesn't show the wizard-item.
anymore ideas?|||keltchen wrote on 7 Aug 2006 03:58:42 -0700:
> MarkusB wrote:
>> In SSMS open Management and right click on Maintenance Plans. The
>> second options is the manitenance plan wizard.
>> Markus
> Already the item 'Maintenance Plans' under Management is missing !!!
> Only under the subitem Legacy there is a item 'Database Maintenance
> Plans'.
> But rightclicking there doesn't show the wizard-item.
> anymore ideas?
You did what I did - didn't install SQL Server Integration Services. The
Maintenance Plan Wizard (and the interface to plans from SMSS) is part of
SSIS. Install SSIS from the SQL Server CD and you should get it working.
Dan

Can't delete old maintenance plan job

In SQL 2005, I've migrated my old SQL 2000 maintenance plans to the new
format and I'm trying to delete a couple of migrated plans that I've redone.
I've managed to delete the plans, but the jobs for those plans are still
left. When I try to delete a job, I get the following error:
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column 'job_id'.
The statement has been terminated. (Microsoft SQL Server, Error: 547)
I know what the error means, of course, but I'm not sure about the best way
to solve it. Thanks!Solved it myself -- I had to manually go into the system tables and delete
some orphaned references between the maintenance plans and jobs.
"Gary" wrote:
> In SQL 2005, I've migrated my old SQL 2000 maintenance plans to the new
> format and I'm trying to delete a couple of migrated plans that I've redone.
> I've managed to delete the plans, but the jobs for those plans are still
> left. When I try to delete a job, I get the following error:
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column 'job_id'.
> The statement has been terminated. (Microsoft SQL Server, Error: 547)
> I know what the error means, of course, but I'm not sure about the best way
> to solve it. Thanks!

Can't delete old maintenance plan job

In SQL 2005, I've migrated my old SQL 2000 maintenance plans to the new
format and I'm trying to delete a couple of migrated plans that I've redone.
I've managed to delete the plans, but the jobs for those plans are still
left. When I try to delete a job, I get the following error:
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column 'job_id'.
The statement has been terminated. (Microsoft SQL Server, Error: 547)
I know what the error means, of course, but I'm not sure about the best way
to solve it. Thanks!Solved it myself -- I had to manually go into the system tables and delete
some orphaned references between the maintenance plans and jobs.
"Gary" wrote:

> In SQL 2005, I've migrated my old SQL 2000 maintenance plans to the new
> format and I'm trying to delete a couple of migrated plans that I've redon
e.
> I've managed to delete the plans, but the jobs for those plans are still
> left. When I try to delete a job, I get the following error:
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column 'job_id'.
> The statement has been terminated. (Microsoft SQL Server, Error: 547)
> I know what the error means, of course, but I'm not sure about the best wa
y
> to solve it. Thanks!

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||

Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
BobsonWere you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:
> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 with
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server by
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connections.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object in
> the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson|||Dennis,
Great someone read my post :) Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
> > hi everyone,
> >
> > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > SP2.
> >
> > The database itself is checked with "2000 sql compatible". I also have TCP,
> > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > and SQL authentication with my sa account.
> >
> > I just created a maintenance plan in the Studio console so that the backup
> > and reindex can run on the server db. However, the job failed last nite. I
> > decide delete the plan and set up another one. I connected to the server by
> > using the Studio console on itself and tried to remove the plan, but it
> > failed. I clicked on the error (a link displayed in the Studio) said the
> > following:
> >
> > #############
> > Exception has been thrown by the target of an invocation. (mscorlib)
> >
> > Additional information:
> > An error has occurred while establishing a connection to the server. When
> > connecting to the SQL server 2005, this failure may be caused by the fact
> > that under the default settings SQL server does not allow remote connections.
> > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > Server)(Microsoft SQL server, Error:53)
> > ##############
> >
> > I have made sure the remote connection (right click on the server object in
> > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > is enabled (\\.\pipe\sql\query).
> >
> > May you provide idea so that I can remove the plan successfully?
> >
> > Thank you!
> >
> > Bobson|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since Iâ'm running on a cluster, after the maintenance plan was created. I
know thatâ's related, but I just want to be able to delete those problematic
plans and recreated them afterward. Any idea?
"Bobson" wrote:
> Dennis,
> Great someone read my post :) Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The problem
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
> > Were you able to fix your problem? I have the same issue but didn't found
> > anything helpful yet.
> >
> > Thanks
> >
> > Denis Desjardins
> >
> > "Bobson" wrote:
> >
> > > hi everyone,
> > >
> > > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > > SP2.
> > >
> > > The database itself is checked with "2000 sql compatible". I also have TCP,
> > > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > > and SQL authentication with my sa account.
> > >
> > > I just created a maintenance plan in the Studio console so that the backup
> > > and reindex can run on the server db. However, the job failed last nite. I
> > > decide delete the plan and set up another one. I connected to the server by
> > > using the Studio console on itself and tried to remove the plan, but it
> > > failed. I clicked on the error (a link displayed in the Studio) said the
> > > following:
> > >
> > > #############
> > > Exception has been thrown by the target of an invocation. (mscorlib)
> > >
> > > Additional information:
> > > An error has occurred while establishing a connection to the server. When
> > > connecting to the SQL server 2005, this failure may be caused by the fact
> > > that under the default settings SQL server does not allow remote connections.
> > > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > > Server)(Microsoft SQL server, Error:53)
> > > ##############
> > >
> > > I have made sure the remote connection (right click on the server object in
> > > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > > is enabled (\\.\pipe\sql\query).
> > >
> > > May you provide idea so that I can remove the plan successfully?
> > >
> > > Thank you!
> > >
> > > Bobson|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of Technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server name
> since Iâ'm running on a cluster, after the maintenance plan was created. I
> know thatâ's related, but I just want to be able to delete those problematic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:
> > Dennis,
> >
> > Great someone read my post :) Before telling my point of view... I would
> > like to ask if you do the following :
> >
> > 1.) Put the sql in the domain
> > 2.) rename the server couple times as the task already created
> > 3.) use different admin account to log on and config both sql and OS (I am
> > still thinking permission related)
> >
> > I have no one to respond to me as I could not find any solution on the Net
> > (the closest one is to run some scripts and clean up registry). The problem
> > still remains. But I did a test by setting up a clean new server with the
> > SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> > mentioned above...
> >
> > I was about to submit an issue to MS... but the SQL admin finally said we
> > could ignore the issue...so I just seize my action.
> >
> > May I get your person email so we can talk more about it? Mine is
> > ultrabobson@.hotmail.com
> >
> > Thank you, and stay in touch.
> >
> > Bobson
> >
> >
> >
> > "Denis Desjardins" wrote:
> >
> > > Were you able to fix your problem? I have the same issue but didn't found
> > > anything helpful yet.
> > >
> > > Thanks
> > >
> > > Denis Desjardins
> > >
> > > "Bobson" wrote:
> > >
> > > > hi everyone,
> > > >
> > > > Thank you for your help in advance. I just set up a MS SQL 2005 standard
> > > > server with SP2 for one of my finance software. The OS is Windows 2003 with
> > > > SP2.
> > > >
> > > > The database itself is checked with "2000 sql compatible". I also have TCP,
> > > > and Named Pipes enable. The server is in the AD domain. I use both Windows
> > > > and SQL authentication with my sa account.
> > > >
> > > > I just created a maintenance plan in the Studio console so that the backup
> > > > and reindex can run on the server db. However, the job failed last nite. I
> > > > decide delete the plan and set up another one. I connected to the server by
> > > > using the Studio console on itself and tried to remove the plan, but it
> > > > failed. I clicked on the error (a link displayed in the Studio) said the
> > > > following:
> > > >
> > > > #############
> > > > Exception has been thrown by the target of an invocation. (mscorlib)
> > > >
> > > > Additional information:
> > > > An error has occurred while establishing a connection to the server. When
> > > > connecting to the SQL server 2005, this failure may be caused by the fact
> > > > that under the default settings SQL server does not allow remote connections.
> > > > (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> > > > Server)(Microsoft SQL server, Error:53)
> > > > ##############
> > > >
> > > > I have made sure the remote connection (right click on the server object in
> > > > the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> > > > is enabled (\\.\pipe\sql\query).
> > > >
> > > > May you provide idea so that I can remove the plan successfully?
> > > >
> > > > Thank you!
> > > >
> > > > Bobson

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
Bobson
Were you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:

> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 with
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server by
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connections.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object in
> the Studio thing) is enabled. As mentioend, I also made sure the named pipes
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson
|||Dennis,
Great someone read my post Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since I’m running on a cluster, after the maintenance plan was created. I
know that’s related, but I just want to be able to delete those problematic
plans and recreated them afterward. Any idea?
"Bobson" wrote:
[vbcol=seagreen]
> Dennis,
> Great someone read my post Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The problem
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of Technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server name
> since I’m running on a cluster, after the maintenance plan was created. I
> know that’s related, but I just want to be able to delete those problematic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:

Can't delete a maintenance plan in SQL 2005

hi everyone,
Thank you for your help in advance. I just set up a MS SQL 2005 standard
server with SP2 for one of my finance software. The OS is Windows 2003 with
SP2.
The database itself is checked with "2000 sql compatible". I also have TCP,
and Named Pipes enable. The server is in the AD domain. I use both Windows
and SQL authentication with my sa account.
I just created a maintenance plan in the Studio console so that the backup
and reindex can run on the server db. However, the job failed last nite. I
decide delete the plan and set up another one. I connected to the server by
using the Studio console on itself and tried to remove the plan, but it
failed. I clicked on the error (a link displayed in the Studio) said the
following:
#############
Exception has been thrown by the target of an invocation. (mscorlib)
Additional information:
An error has occurred while establishing a connection to the server. When
connecting to the SQL server 2005, this failure may be caused by the fact
that under the default settings SQL server does not allow remote connections
.
(provide: Named Pipes Provide, error: 40 - Could not open a connection to SQ
L
Server)(Microsoft SQL server, Error:53)
##############
I have made sure the remote connection (right click on the server object in
the Studio thing) is enabled. As mentioend, I also made sure the named pipes
is enabled (\\.\pipe\sql\query).
May you provide idea so that I can remove the plan successfully?
Thank you!
BobsonWere you able to fix your problem? I have the same issue but didn't found
anything helpful yet.
Thanks
Denis Desjardins
"Bobson" wrote:

> hi everyone,
> Thank you for your help in advance. I just set up a MS SQL 2005 standard
> server with SP2 for one of my finance software. The OS is Windows 2003 wit
h
> SP2.
> The database itself is checked with "2000 sql compatible". I also have TCP
,
> and Named Pipes enable. The server is in the AD domain. I use both Windows
> and SQL authentication with my sa account.
> I just created a maintenance plan in the Studio console so that the backup
> and reindex can run on the server db. However, the job failed last nite. I
> decide delete the plan and set up another one. I connected to the server b
y
> using the Studio console on itself and tried to remove the plan, but it
> failed. I clicked on the error (a link displayed in the Studio) said the
> following:
> #############
> Exception has been thrown by the target of an invocation. (mscorlib)
> Additional information:
> An error has occurred while establishing a connection to the server. When
> connecting to the SQL server 2005, this failure may be caused by the fact
> that under the default settings SQL server does not allow remote connectio
ns.
> (provide: Named Pipes Provide, error: 40 - Could not open a connection to
SQL
> Server)(Microsoft SQL server, Error:53)
> ##############
> I have made sure the remote connection (right click on the server object i
n
> the Studio thing) is enabled. As mentioend, I also made sure the named pip
es
> is enabled (\\.\pipe\sql\query).
> May you provide idea so that I can remove the plan successfully?
> Thank you!
> Bobson|||Dennis,
Great someone read my post Before telling my point of view... I would
like to ask if you do the following :
1.) Put the sql in the domain
2.) rename the server couple times as the task already created
3.) use different admin account to log on and config both sql and OS (I am
still thinking permission related)
I have no one to respond to me as I could not find any solution on the Net
(the closest one is to run some scripts and clean up registry). The problem
still remains. But I did a test by setting up a clean new server with the
SQL. And I cannot duplicate the problem! In the test I do not do anythings I
mentioned above...
I was about to submit an issue to MS... but the SQL admin finally said we
could ignore the issue...so I just seize my action.
May I get your person email so we can talk more about it? Mine is
ultrabobson@.hotmail.com
Thank you, and stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Were you able to fix your problem? I have the same issue but didn't found
> anything helpful yet.
> Thanks
> Denis Desjardins
> "Bobson" wrote:
>|||Bobson,
I send you an email on your hotmail address but didn't have any answer yet.
Here's what i mention in my email:
Yes I actually renamed the server, or more precisely the virtual server name
since I’m running on a cluster, after the maintenance plan was created. I
know that’s related, but I just want to be able to delete those problemati
c
plans and recreated them afterward. Any idea?
"Bobson" wrote:
[vbcol=seagreen]
> Dennis,
> Great someone read my post Before telling my point of view... I would
> like to ask if you do the following :
> 1.) Put the sql in the domain
> 2.) rename the server couple times as the task already created
> 3.) use different admin account to log on and config both sql and OS (I am
> still thinking permission related)
> I have no one to respond to me as I could not find any solution on the Net
> (the closest one is to run some scripts and clean up registry). The proble
m
> still remains. But I did a test by setting up a clean new server with the
> SQL. And I cannot duplicate the problem! In the test I do not do anythings
I
> mentioned above...
> I was about to submit an issue to MS... but the SQL admin finally said we
> could ignore the issue...so I just seize my action.
> May I get your person email so we can talk more about it? Mine is
> ultrabobson@.hotmail.com
> Thank you, and stay in touch.
> Bobson
>
> "Denis Desjardins" wrote:
>|||Hi Dennis,
I am sorry if I might overlook it... Please try again with my
ultrabobson@.yahoo.com (or hotmail.com)
So you have very similar issue as what we did. We did not have any
reolsutions yet...even though we renamed the server back to the original
name. But it still could not resovle the issue. What we ran around was to
crate another plan.
I have couple of technet tickets and I might try to submit the issue to
them. I may not do this tsoon, but I will keep you posted once I do that.
Stay in touch.
Bobson
"Denis Desjardins" wrote:
[vbcol=seagreen]
> Bobson,
> I send you an email on your hotmail address but didn't have any answer yet
.
> Here's what i mention in my email:
> Yes I actually renamed the server, or more precisely the virtual server na
me
> since I’m running on a cluster, after the maintenance plan was created.
I
> know that’s related, but I just want to be able to delete those problema
tic
> plans and recreated them afterward. Any idea?
>
> "Bobson" wrote:
>

Can't create a Maint Plan in 2005

I am trying to create a maint plan in 2005 and no matter what types of
things I tell it to do, when it goes to create the plan I get the following
error message:
Create maint plan failed.
Additional information:
create failed for jobstep 'Subplan'
An exception occurred while executing a Transact-SQL statement or
batch.
The specified '@.subsystem' is invalid (valid values are returned
by sp_enum_sqlagent_subsystems) (Microsoft SQL Server Error:14234)
It's on a clustered system.
TIA - Jeff.Do you have SQL Agent running and do you have SSIS installed and running?
Andrew J. Kelly SQL MVP
"UJ" <fred@.nowhere.com> wrote in message
news:epT9r3uQGHA.5808@.TK2MSFTNGP12.phx.gbl...
>I am trying to create a maint plan in 2005 and no matter what types of
>things I tell it to do, when it goes to create the plan I get the following
>error message:
> Create maint plan failed.
> Additional information:
> create failed for jobstep 'Subplan'
> An exception occurred while executing a Transact-SQL statement or
> batch.
> The specified '@.subsystem' is invalid (valid values are
> returned by sp_enum_sqlagent_subsystems) (Microsoft SQL Server
> Error:14234)
> It's on a clustered system.
> TIA - Jeff.
>

Can't create a Maint Plan in 2005

I am trying to create a maint plan in 2005 and no matter what types of
things I tell it to do, when it goes to create the plan I get the following
error message:
Create maint plan failed.
Additional information:
create failed for jobstep 'Subplan'
An exception occurred while executing a Transact-SQL statement or
batch.
The specified '@.subsystem' is invalid (valid values are returned
by sp_enum_sqlagent_subsystems) (Microsoft SQL Server Error:14234)
It's on a clustered system.
TIA - Jeff.
Do you have SQL Agent running and do you have SSIS installed and running?
Andrew J. Kelly SQL MVP
"UJ" <fred@.nowhere.com> wrote in message
news:epT9r3uQGHA.5808@.TK2MSFTNGP12.phx.gbl...
>I am trying to create a maint plan in 2005 and no matter what types of
>things I tell it to do, when it goes to create the plan I get the following
>error message:
> Create maint plan failed.
> Additional information:
> create failed for jobstep 'Subplan'
> An exception occurred while executing a Transact-SQL statement or
> batch.
> The specified '@.subsystem' is invalid (valid values are
> returned by sp_enum_sqlagent_subsystems) (Microsoft SQL Server
> Error:14234)
> It's on a clustered system.
> TIA - Jeff.
>

Can't create a Maint Plan in 2005

I am trying to create a maint plan in 2005 and no matter what types of
things I tell it to do, when it goes to create the plan I get the following
error message:
Create maint plan failed.
Additional information:
create failed for jobstep 'Subplan'
An exception occurred while executing a Transact-SQL statement or
batch.
The specified '@.subsystem' is invalid (valid values are returned
by sp_enum_sqlagent_subsystems) (Microsoft SQL Server Error:14234)
It's on a clustered system.
TIA - Jeff.Do you have SQL Agent running and do you have SSIS installed and running?
--
Andrew J. Kelly SQL MVP
"UJ" <fred@.nowhere.com> wrote in message
news:epT9r3uQGHA.5808@.TK2MSFTNGP12.phx.gbl...
>I am trying to create a maint plan in 2005 and no matter what types of
>things I tell it to do, when it goes to create the plan I get the following
>error message:
> Create maint plan failed.
> Additional information:
> create failed for jobstep 'Subplan'
> An exception occurred while executing a Transact-SQL statement or
> batch.
> The specified '@.subsystem' is invalid (valid values are
> returned by sp_enum_sqlagent_subsystems) (Microsoft SQL Server
> Error:14234)
> It's on a clustered system.
> TIA - Jeff.
>