Remove and Add SQL 2005 cluster nodes CHALLENGE!!!

I have a challenge!!!!!!!!!!!
Requirements are:
A. To replace the 2 nodes of SQL 2005 Cluster on Windows 2003 SP1, with a
set of 2 new nodes (hardware).
B. Keep all the settings of SQL 2005, Databases, .etc. the same way they
are.
C. WITH THE SAME IP ADDRESSES (no change to any IP address).
I know the theory is to implement this KB:
http://msdn2.microsoft.com/en-us/library/ms191545.aspx
My question is:
Can I do the following?
1. Remove the second OLD node, using the same ms191545 above.
2. Add (Join) the 1st New node to the cluster.
3. Remove the last OLD node.
4. Add the NEW second node.
Are the above steps feasible?
What are the things I have to be aware about (so I will not break anything).
How can get thru having the same IP addresses with no change on the 2 new
nodes?
Thanks in advance
wit1 wrote:
> I have a challenge!!!!!!!!!!!
> Requirements are:
> A. To replace the 2 nodes of SQL 2005 Cluster on Windows 2003 SP1, with a
> set of 2 new nodes (hardware).
> B. Keep all the settings of SQL 2005, Databases, .etc. the same way they
> are.
> C. WITH THE SAME IP ADDRESSES (no change to any IP address).
Maybe I'm missing something in your 3rd requirement. When you specify
"same IP address," it implies that your requirement is referring to the
cluster _node_, not a cluster group being hosted by the cluster. Why is
that, and what difference does it make?
As the cluster group is moved from one node to another during failure or
intentional move, there should be an IP address for that group that is
separate and unique from the node(s) that own it.
|||I meant that if node 2 (for example) has IP addresses of
1.2.3.4 for the Virtual IP (Cluster group IP)
2.3.4.5 for public (for the NODE itself not the Virtual IP),
and
1.1.1.1 for private (heart beat)
, the new (coming node) that will replace that node 2 should have the same
IP addresses.
So the plan is to un-install SQL from node 2, then evict it, after that join
the NEW node 2 and install SQL with same IP addresses.
Hope that clears things out.
"horseradish" <millardjk@.gmail.com> wrote in message
news:%237hk1iojHHA.5084@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> wit1 wrote:
with a[vbcol=seagreen]
they
> Maybe I'm missing something in your 3rd requirement. When you specify
> "same IP address," it implies that your requirement is referring to the
> cluster _node_, not a cluster group being hosted by the cluster. Why is
> that, and what difference does it make?
> As the cluster group is moved from one node to another during failure or
> intentional move, there should be an IP address for that group that is
> separate and unique from the node(s) that own it.

Remote Debugging Problems w/ VS.net 2005 SP1

I have done through all the MSDN documentation and Googled everything I could
on the errors I am receiving about installing and configuring remote
debugging. I believe it is communications related. This is the scenario:
The Visual Studio 2005 Remote Debugger service is started on the remote
database server that I want to debug SQL code on as Local System. I am a
member of the local administrators group on that server and a member of the
sa role in SQL Server. I configured all the DCOM settings on both the remote
server and my local workstation, which is running XP SP2, and opened the
firewall exceptions on my workstation.
When I attempt to step into a procedure, the message " Unable to start T-SQL
Debugging. Could not attach to SQL Server process on 'daysqltest02'. Remote
calls are not allowed for this process." displays. If I manually run the
Visual Studio Remote Debugging Monitor interactively on the remote server,
when I attempt to step into a procedure, an entry is displayed in the monitor
that a connection from my workstation has been made and the following message
is displayed "Unable to start T-SQL Debugging. Could not connect to computer
'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on the
remote computer does not have permission to connect to this computer. Please
see Help for assistance."
Other people in my office on the same network or other networks can
successfully debug and there is not firewall between my workstation and the
remote server so I know it is something with my security or communications
configuration. Any assistance would be much appreciated. Thanks in advance.
Ken
Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Hi Parch,
I suggest you try the tool SQL Ultimate Debugger:
http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
This tool is a post factum debugger and allows you to trace and
debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
waaaay better than the T-SQL debugger in VS. Also, since this software has
not yet been officially realeased, I would not recommend (YET) to use it in
a production environment.
You can learn more about it here:
http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
want a copy of its documentation. shoot me an email and i can send it to
you.
I hope that helps.
"parchk" <parchk@.discussions.microsoft.com> wrote in message
news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>I have done through all the MSDN documentation and Googled everything I
>could
> on the errors I am receiving about installing and configuring remote
> debugging. I believe it is communications related. This is the scenario:
> The Visual Studio 2005 Remote Debugger service is started on the remote
> database server that I want to debug SQL code on as Local System. I am a
> member of the local administrators group on that server and a member of
> the
> sa role in SQL Server. I configured all the DCOM settings on both the
> remote
> server and my local workstation, which is running XP SP2, and opened the
> firewall exceptions on my workstation.
> When I attempt to step into a procedure, the message " Unable to start
> T-SQL
> Debugging. Could not attach to SQL Server process on 'daysqltest02'.
> Remote
> calls are not allowed for this process." displays. If I manually run the
> Visual Studio Remote Debugging Monitor interactively on the remote server,
> when I attempt to step into a procedure, an entry is displayed in the
> monitor
> that a connection from my workstation has been made and the following
> message
> is displayed "Unable to start T-SQL Debugging. Could not connect to
> computer
> 'daysqltest02'. The Microsoft Visual Studio Remote Debugging Monitor on
> the
> remote computer does not have permission to connect to this computer.
> Please
> see Help for assistance."
> Other people in my office on the same network or other networks can
> successfully debug and there is not firewall between my workstation and
> the
> remote server so I know it is something with my security or communications
> configuration. Any assistance would be much appreciated. Thanks in
> advance.
> Ken
|||Thanks for the information. I will definitely look at this product and would
appreciate a copy of the documentation for review.
With this product, can stored procedures be interactiely debugged?
"The DBA" wrote:

> Hi Parch,
> I suggest you try the tool SQL Ultimate Debugger:
> http://lakesidesql.com/downloads/PFD/1_0_2007_809/PFDebugger_Setup_08-09-2007.zip.
> This tool is a post factum debugger and allows you to trace and
> debug obejcts (SP's Triggers, FN's, etc.) that had been executed. It's
> waaaay better than the T-SQL debugger in VS. Also, since this software has
> not yet been officially realeased, I would not recommend (YET) to use it in
> a production environment.
> You can learn more about it here:
> http://208.75.249.50/products/sql-ultimate-debugger/screenshots.html. If you
> want a copy of its documentation. shoot me an email and i can send it to
> you.
> I hope that helps.
>
>
> "parchk" <parchk@.discussions.microsoft.com> wrote in message
> news:F5E08E79-2BC6-4991-904A-A87465073520@.microsoft.com...
>

Remote connection failed, even with proper configuration

I am unable to connect to a SQL instance on the server from a workstation on the same network.

SQL Express SP1 is installed on the server, and allows mixed authentication. The instance name is <SERVERNAME>\SQLEXPRESS.

Both the Database and Browser services are running.

Local and remote connections are enabled under SAC. I also used sp_configure to make the same changes.

All Protocols for SQLEXPRESS have been Enabled using the Configuration Manager.

The firewalls on both machines have been disabled.

Rebooting the server or restarting services after various changes hasn't affected the outcome.

Local connections made directly on the server are always successful using either authentication mode.

SQL Native Client Driver is installed on the workstation.

The workstation user is trusted. However, neither authentication mode is successful.

The connection string from the workstation uses the named instance above and the SQL Native Client driver.

Other services on the server are working and avaialble to the workstation, such as shared folders.

When I attempt a connection from the workstation I receive the following errors:

Connection failed:

SQLState: '08001'

SQL Server Error: -1

[Microsoft][SQL Native Client]SQL Networtk Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].

Connection failed:

SQLState: 'HYT00'

SQL Server Error: 0

[Microsoft][SQL Native Client]Login timeout expired

Connection failed:

SQLState: '08001'

SQL Server Error: -1

[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections.

I have tried all of the recommendations I can find here without any luck. What am I missing?

Hi,

can you post full connection string used to connection machines!!?

Are you able to get connected each other servers from SSMS?

Hemantgiri S. Goswami

|||

Try to connect to the Server directly using the appropiate port rather than just using the instance name (to see if the SQL Browser is causing the problem) Use the format Servername,portnumber for this. If this does not work, you might have not enabled TCP/IP for connections.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||THank you for the suggestions. The problem was caused by an unrelated program on the same server. Uninstalling the offending program, and reinstalling SQL Express, did the trick.|||

Would you mind posting what the offending program was? I'm getting the same reaction from SQL Server 2005 Express in my LAN with an application that was running just a couple of weeks ago.

TIA

Mike Baker
Adobe Community Expert