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