I realize this isn't a SQL specific group, but figured I would try here
first...

Here is what I have;
2 node 2005 SQL cluster running on Windows 2003 SP2 R2.

After running through installing SQL on the cluster it was discovered the
virtual SQL name was mis-typed and was changed from SQLSERVER1 to SERVERSQL1
using the information found here;
How to: Rename a SQL Server 2005 Virtual Server
http://msdn2.microsoft.com/en-us/library/ms178083.aspx

This worked without issue and we moved forward with moving databases to the
new clustered environment.

We then created a new Maintenace Plan which does Full backups of all of the
databases, but realized this was failing.

When looking at the error we noticed this as the reason;
Message
Executed as user: domain\sqluser. ...ersion 9.00.3042.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:
1:27:04 PM  Error: 2007-12-27 13:27:22.32     Code: 0xC00291EC     Source:
{6CC39E82-B80C-45F8-A0C0-FC1F9E7B5DD2} Execute SQL Task     Description:
Failed to acquire connection *"Local server connection"*. Connection may not
be configured correctly or you may not have the right permissions on this
connection.

When I select Modify on the Maintenance Plan and look at the properties for
the Local server connection under the Manage Connections button it shows the
original virtual SQL server name of SQLSERVER1 instead of SERVERSQL1. It is
grayed out and I can't change it.

I have tried changing the Connection within the Maintenance Plan to use a
new connection instead of the default Local server connection, but get the
same error.

Aside from the Maintenance Plan failing, all other database activity is
working without issue.

I am assuming the fact that we changed the virtual SQL server name is the
cause of our issues. Could someone shed some light on this?

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to